Jump to content


Sir_Timbit

Established Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sir_Timbit

  • Rank
    Newbie
  1. Found my mistake! /PackageName is looking for whatever is listed in the SCCM > Computer Management > Software Updates > Deployment Management node, not the Deployment Packages node. It ran after I made the change...
  2. Shouldn't the name listed for /packagename be the same as the name listed in SCCM > Software Updates > Deployment Packages? If so, that's what I have entered, but it reports no package found, and Im not sure why...
  3. Hi there, I'm new to FEP2010 and fairly new to SCCM 2007, but have managed to get it installed and have been able to deploy FEP clients. But I've been getting stuck with the Software Update Automation Tool. A lot of the posts out there have been referring to an older version and there's been some changes in regards to switches (/RefreshDP for example). I found a great article on installing and configuring FEP as well as the tool at http://blog.coretech.dk/coretech/the-complete-forefront-endpoint-protection-2010-installation-and-configuration-guide/ As far as I can tell, my syntax should be: SoftwareUpdateAutomation.exe /AssignmentName FEP2010_DefUpdates /PackageName "FEP2010 DefUpdates" /UpdateFilter "ArticleID='2461484' AND IsSuperseded=0 AND IsEnabled=1 AND IsExpired=0" But the result I get is: Values: /Help: Default (False) /SiteServer: Default (sccm2007srv) /UpdateFilter: Explicit (ArticleID='2461484' AND IsSuperseded=0 AND IsEnabled=1 AND IsExpired=0) /AssignmentName: Explicit (FEP2010_DefUpdates) /PackageName: Explicit (FEP2010 DefUpdates) /PreDownloadFolder: Default () /UpdateLanguages: Default (0) /DisableRefreshDP: Default (False) /Verbose: Default (False) SoftwareUpdateAutomation execution starting. ============================================ Version: 2.1.1116.101 Command line: SiteServerName: sccm2007srv; SoftwareUpdateFilter: ArticleID='246148 4' AND IsSuperseded=0 AND IsEnabled=1 AND IsExpired=0; PackageName: FEP2010 DefU pdates; UpdateLanguages: 0; SoftwareUpdateFolder: ; DisableRefreshDP: False; Log File: C:\ProgramData\SoftwareUpdateAutomation.log. UpdateAssignmentName: FEP2010 _DefUpdates Attempting to connect to site server 'sccm2007srv'... Connected to site server 'sccm2007srv', searching for matching software updates... Executing select query: 'SELECT * FROM SMS_SoftwareUpdate WHERE ArticleID='24614 84' AND IsSuperseded=0 AND IsEnabled=1 AND IsExpired=0'... Warning: Found 2 software updates matching the specified filter: ArticleID='2461 484' AND IsSuperseded=0 AND IsEnabled=1 AND IsExpired=0. Software update: CI_ID: 14766. ArticleID: 2461484. Name: Definition Update f or Microsoft Endpoint Protection - KB2461484 (Definition 1.145.942.0) Software update: CI_ID: 14779. ArticleID: 2461484. Name: Definition Update f or Microsoft Endpoint Protection - KB2461484 (Definition 1.145.1295.0) Searching for the specified software update deployment package: 'FEP2010 DefUpda tes'... Executing select query: 'SELECT * FROM SMS_SoftwareUpdatesPackage WHERE Name='FE P2010 DefUpdates''... Error: Found no software update packages matching specified name. Software updat e package name: FEP2010 DefUpdates. SoftwareUpdateAutomation execution completed unsuccessfully, errors occurred. ========================================================= So I have at least two problems here. I'm aware of the Technet article on the orphaned defintion updates and have since declined them in WSUS. If I understand that one I just need to wait for the next SUP refresh. But the main error message I'm dealing with is the error: "Found no software update packages mathcing specified name." Someone please help a noob! Exactly where is the name in /packagename determined in the SCCM console? I seem to have overlooked the distinction between these two (package name vs assignment name) Much thanks, Sir_Timbit
  4. Has anyone compared Flexera's AdminStudio to Scalable's WinInstall? If you need more of the Pro features, WinInstall licenses seem to be about half the price of AdminStudio. I don't have experience with either one and haven't been able to find a comparison of the two online so far...
  5. Thanks for the info. The old server has a few dynamic collections, but yes, most of the older ones which we still use are based on direct membership, from using either the Direct Membership wizard or by "adding resources" to a collection. So, given what you're telling me, is there any reason to make the new SCCM server a child of the existing server? The collection info was basically the one thing I was interested in moving down, but it sounds like that won't happen. If that's the case, I should just run that script and start adding the collections again, based on dynamic rather than direct membership this time. What about the "All Systems" collection--the one provided by SCCM itself? Will that replicate down to the new SCCM server?
  6. Hi there, I'm trying to get a clearer idea of the steps involved in doing a side by side migration of SCCM 2007. I've taken over an old SCCM 2007 server that has several issues and I'd like to start over from scratch with an entirely new server. The backup/restore process won't work for me because the previous setup had everything dumped on C and I'm setting up separate drives/partitions for SQL/SCCM/OS/WSUS, etc. Right now moving to SCCM2012 isn't an option for us either, just 2007.. I'm also moving from a Win2003 32bit to Win2008 R2 64bit environment. Based on what I've read, that means I'm looking at doing a side by side upgrade. My understanding is that I would install the new server a new primary server, then attach it to the old SCCM server as a child site, let it propogate settings down, then disconnect and shut down the old SCCM server. So...I've gone through various steps here and elsewhere. The new server has SQL Server 2008 R2 and everything's configured OK as far as permissions, etc. I ran the SCCM2007 Prerequisite checker and everything passed, so I guess I'm ready to actually install SCCM 2007 SP2 then R3 afterward. I guess my main question is...How do I get all my existing clients to see/point to the new SCCM server? It will have a new site code. Do people use startup scripts to uninstall the old client and reinstall. The previous client install used the autoassignment switch. I know you have to change IP boundaries between the old and new SCCM servers. I read elsewhere there was a ADM/GPO to set the site code but this apparently had issues? I'm not worried about packages, advertisements, inventories, reports or anything else. What I would like is for the existing collections to come over, which are mostly static. But my primary concern is to get all our existing clients to see the new SCCM server. The existing SCCM hierarchry is pretty simple. All in one box, one central site, one primary site, so this will be the only new addition. Hope someone can help. I've been searching around but have had a hard time finding a similar scenario...maybe I'm not asking the right question! Thanks in advance, Sir_Timbit
  7. Hi, just want to say thanks for the steps listed here.... So...I'm trying to figure out *why* this happens. On a test machine that I'd be reimaging, I could select "Clear Last PXE Advertisement" and that would work a few times, then stop, just as detailed here. I did the steps listed above (direct membership rules, finding a duplicate entry listed once I did that, deleting that, etc.) The strange part was once I did that, the test collection I had that one PC in was gone, as was the task sequence advertisement. I had to recreate both. No big deal, but is that normal? And, is this a bug with SCCM 2007, or is more to do with WDS caching as some have mentioned? Is the process any smoother in SCCM 2012?
  8. After some more hunting online, sounds like 75 PXE service points per site is the real limitation, not 10. And since my DPs are already WIn2008, they should be OK for WDS as well.
  9. Hi there, hoping for some clarification on the use of PXE service points in SCCM 2007. I'm pretty new to SCCM and have been tasked with migrating from Ghost/Fog to SCCM / MDT2010 for our imaging/OSD tasks. This is for a school environment, with a reasonably fast WAN connection and each school on its own subnet (10.x.x.x). We've been using SCCM primarily for application deployment and some basic reporting so far. Just getting our feet wet really. Each school has its own Ghost or Fog server that handled imaging at that location. Currently we have a pretty basic setup--one primary SCCM site server at our distric office that all schools connect to. Each school has its own site system as seen in SCCM; a server or a share for the DP. Boundaries have been set up for each school on the server. Currently the main site server handles all roles including the PXE service point. There's about 7000 PCs altogether spread throughout the district. SCCM2007 is currently running on WIndows 2003 (unfortunately, as I've read here that this complicates things with multicasting) but I do have test client PCs PXEbooting after installing WDS on the SCCM server. (I had to configure the DHCP scope options for 66/67 though...) So with all that background, I'm wondering how best to configure each school for PXEbooting for OSD. Is it as simple as just adding WDS to each school's Win2008 server, configure DHCP options 66/67, and then configuring SCCM to add the PXE service role to each location? The technet article at http://technet.microsoft.com/en-us/library/bb680869.aspx says up to 10 PXE service points are supported per site, up to 75 per primary site database. I have about 30 schools to configure, so obviously that's more than the 10 PXE service points per site but less than the 75. I'm not sure about the difference between the two. FInally, with regards to multicasting issues with Win2003, my understanding is I could move WDS to a Win2008 box and configure that as a PXE service point, to get around whatever limitations Win2003 and WDS have with multicasting. Hope I've clarified things. Thanks in advance. Sir_Timbit
×
×
  • Create New...