Hi, I'm running SCCM 2007 R2 with WSUS integrated and trying to capture a new Windows 7 image with all updates (137 updates are required). After installing the OS, the machine is joined to the domain and a couple of Install Software Updates tasks are inserted in the capture TS The first Install Updates installs a bunch of updates, Then some components/applications are installed Then again some Install Software Updates tasks are inserted to make sure all updates are installed, but on the last update tasks it will not find any available update. When the freshly captured image is deployed it will find available updates, so not all are installed during the capture I tried to assign the updates to different collections, first i created a Capture collection with had a direct membership for the capture computers' MAC-address. I've also tried assigning the updates to the All known Computers collection. I've found a couple of topics with the same problem, but none helped. Found a script that will initiate the CCM client to search for updates, appearently the install step only used the first scan, during the complete capture TS. Schid = "{00000000-0000-0000-0000-000000000113}" sMachine = "." Set WMItarget = GetObject("winmgmts://" & sMachine) Set WMICCM=GetObject("Winmgmts:{impersonationLevel=impersonate,authenticationLevel=pktPrivacy}!\\" & sMachine & "\root\ccm") set SMSCli = WMICCM.Get("SMS_Client") set oParams = SMSCli.Methods_("TriggerSchedule").inParameters.SpawnInstance_() oParams.sScheduleID = Schid set res = WMICCM.ExecMethod("SMS_Client", "TriggerSchedule", oParams) wscript.sleep(180000) I tried the following scenario's: 1.) Capture TS, added only the Install Software Updates step and set it to install all updates. Updates are assigned to Capture collection Result: only first install step installs some updates, the rest are not installing any update (37 updates in total) 2.) Capture TS, script for updates scan is now started before every Install Updates tasks. Updates are assigned to Capture collection Result: 3 of the Install updates tasks are now installing updates (63 updates in total) 3.) Capture TS, added only Install Software Updates and set it to install all updates.) Updates are now assigned to collection "All Unknown Computers" Result: only first install step installs some updates, the rest are not installing any update (41 updates are installed in total) In scenario 1 and 3 all updates are installed before the installation of e.g. Office 2010. After Office 2010 is installed 4 Install updates tasks and reboots should install all remaining updates. But it doens't install any updates in the 4 steps. In scenario 2 it installs some office 2010 updates after the installation, but Office SP1 and at least 50 other updates are not installed. When any of the images created by Scenario 1,2 and 3 are deployed to a computer, all remaining updates are installed when the TS is done. I'd like to have all available updates captured, but it never will. Regards, Dennis

Have tried using an install updates offline (MDT) step instead? See http://myitforum.com/cs2/blogs/jsandys/archive/2011/04/10/software-updates-and-osd-revisited.aspx for details.Miguel Rodriguez

Have tried using an install updates offline (MDT) step instead? See http://myitforum.com/cs2/blogs/jsandys/archive/2011/04/10/software-updates-and-osd-revisited.aspx for details. Miguel Rodriguez Hi Miguel, Haven't tried the install updates offline, so i read the article to which you linked. It is not to be used for build and capture TS and it will not install non-OS updates. The Install updates offline seems to be created for installing updates during deployment. Als the problem described in the article is a different one as i'm experiencing. They talk about a Install Software Updates that hangs, mine do not hang, but just won't install all updates. Since this is the only thing that might help, i will try to add the step to the capture TS and report the results. Regards, Dennis

I know, it's not waht automation looks like, but you could also try using 2 tasksequences. The first for to build the reference machine and a second one (advertised, not mandatory) to capture the machine if it's ready. This way the system has enough time to install all updates and you can control the result before starting the capture. If it's just for one refernce machine I would give it a try. Also, Check windowsupdate.log and updateshandler.log on the reference machine when updates are installed.Miguel Rodriguez

A couple of comments -- not a solution though. - Joining a reference system to the domain is generally bad practice. Things like GPOs leave a mark on the system that really shouldn't be part of the refernce image There is no technical reason to do this. - Updating Office 2010 to SP1 is best done by dropping the MSP in the Office 2010 Updates folder and the Office installer will automatically install SP1 at the same time. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

A couple of comments -- not a solution though. - Joining a reference system to the domain is generally bad practice. Things like GPOs leave a mark on the system that really shouldn't be part of the refernce image There is no technical reason to do this. - Updating Office 2010 to SP1 is best done by dropping the MSP in the Office 2010 Updates folder and the Office installer will automatically install SP1 at the same time. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys Hi Jason, When we start using SCCM and the capture TS, we couldnt get any update on the target machine. Some people reported to join the machine to the domain and at the end of the TS unjoin it again. Since SCCM got some updates i will remove the join step and check if any updates are installed. Dennis

Keep in mind that a SLP is required then: http://blogs.technet.com/b/mniehaus/archive/2008/12/10/configmgr-install-software-updates-task-failing-when-building-a-reference-machine.aspxTorsten Meringer | http://www.mssccmfaq.de

yup, and here's a guide for doing just that Build and Capture Windows 7 sample task sequence adding windows updates by specifying the SLP My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks for the replies. I'm changing the TS now to join the computer the a Workgroup and adding the SMSSLP, SMSMP, FSP to the ConfigMgr client. does it matter to which collection I assign the updates deployment or does it check all available deployment packages for applicability?

Started TS. Windows installs, configrMgr has SMSSLP, SMSMP, FSP. At first Install Software Updates it fails. Error 80040669 And One or more updates failed to install 80004005 With SMS trace, the following error is found: Failed to resolve 'SMS_SLP' to IP address from WINS This should indicate, that i mistyped. but i'm 100% sure i didn't

does your SLP have a record published in your WINS server? http://technet.microsoft.com/en-us/library/bb694195.aspx from the client where you are running the capture, can you resolve/ping the SLP by its WINS name?Don

does your SLP have a record published in your WINS server? http://technet.microsoft.com/en-us/library/bb694195.aspx from the client where you are running the capture, can you resolve/ping the SLP by its WINS name? Don SMS_SLP is published in WINS. Unfortunalty during the TS I cannot ping the SMS_SLP. Could be a confiruation issue with WINS. DHCP option 44 with server name and ip is added to the DHCP scope It still fails at Install Updates step. Checked the LocationServices.log: It now has only 1 error message: Failed to reset certificate request times. (0x80041002) and it reports a warning, that is ignored: Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. UpdatesDeployment.log: No updates were added to the job, returning failure Failed to set update list for the CI Agent Job, error = 0x80004005 Detection job failed for assignment ({8709BE3B-432E-4A37-AAA3-C91639BDE6DE}) Assignment redetection failed, error = 0x80004005 Failed to redetect assignment {8709BE3B-432E-4A37-AAA3-C91639BDE6DE}, error = 0x80004005 UpdatesHandler.log keeps repeating: Unable to get locations, no need to continue with download CBundledUpdate -- Failed to download update (f4489776-00d7-40c4-a060-bb74f001d682). Error = 0x80040669 CDeploymentJob -- Failed to download update (067bbc91-5f81-42e1-9fc4-f1765802a27a). Error = 0x80040669 UpdatesStore.log seems to detect all updates and reports their status properly.

TS will now join machine to domain in a OU without any GPO. This will at least install some updates. Maybe someone has a resolution for the errors in my previous post, but to me it feels like installing all updates in a TS is an illusion. Since the domain version of the TS will also not install all updates, i will try to get the logs from the capture where it will install about 37 till 63 updates.

CBundledUpdate -- Failed to download update (f4489776-00d7-40c4-a060-bb74f001d682). Error = 0x80040669 CDeploymentJob -- Failed to download update (067bbc91-5f81-42e1-9fc4-f1765802a27a). Error = 0x80040669 0x80040669 = "The requested operation completed successfully. The system will be restarted so the changes can take effect." so that's not an error.Torsten Meringer | http://www.mssccmfaq.de

CBundledUpdate -- Failed to download update (f4489776-00d7-40c4-a060-bb74f001d682). Error = 0x80040669 CDeploymentJob -- Failed to download update (067bbc91-5f81-42e1-9fc4-f1765802a27a). Error = 0x80040669 0x80040669 = "The requested operation completed successfully. The system will be restarted so the changes can take effect." so that's not an error. Torsten Meringer | http://www.mssccmfaq.de The strange thing is, that it won't install any update. Another Capture TS is currently running (machine is joined into Domain) and passed the first Install Update step by installing 37 updates. However i think it will fail to install any updates after the first successful Install step. The UpdatesDeployment now has a lot of the errros below: Failed to open to WMI namespace '\\.\root\CCM\SoftwareUpdates\DeploymentAgent' (8007045b) CTargetedUpdate::Save - Failed to open \\.\root\CCM\SoftwareUpdates\DeploymentAgent namespace, error 8007045b Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) CUpdatesAssignmentPolicy - spPolicyAgent->ConnectSettings failed, error 8007045b\ Might be WMI corruption?

Ok, This morning i used SMS trace to look at the logs of the Capture TS. This TS has 2 Install updates steps at the end of the TS. The first steps install 39 updates. The second step doensn't install any update. After the first update step it acts like it is not able to find any DP, MP or SUP. But it is able to indicate the status of the updates. The step has no continue on error and the TS just continues, so it doesn't report a 'fatal' error and captures the machine. I guess we all have to deal with it and wait for SCCM 2012

Just curious if you have http://support.microsoft.com/kb/2509007 installed and deployed during the TS?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys