Windows Updates as part of Build and Capture
I am trying to update our image with all the Windows Updates during a build and capture. However every time I capture and deploy the image informs me there are updates right away.I am new to SCCM so not 100% sure how the process works. I have looked at the server as it has WSUS and SCCM configured as a downstream server. I found KB2509007 on MS and applied the patch yesterday but still can not see the patches installed. Can someone please tell me what I have to check to get this working? Thanks in advance. g.
September 10th, 2012 7:13pm

I may have found my own answer.. I found this site and it looks like it does what I want, I am just trying to see if I can configure it now. I'm not sure what WSUS server to point it to though..
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2012 7:53pm

Although using ZTIWindowsUpdate can work, it's not the out of the box solution. First, it is not supported to configure a ConfigMgr integrated WSUS system (aka a SUP) as a downstream server of another WSUS system (even though the interface allows you to do this). The top-level SUP in a heirarchy must synchronize with Microsoft. Next, have you properly configured your SUP? Finally, have you configured your update deployments and update packages? This is not automatic and is not comparable to manaing updates with WSUS.Jason | http://blog.configmgrftw.com
September 10th, 2012 10:01pm

We have WSUS managed by a security team and this is why it is not part of our SCCM deployment (used for helpdesk). I have just started at this company and been thrown in the deep end with SCCM. I have not configured the SUP (SCCM Update service?) assuming that it would have been done before I started. I also have not configured update deployments and update packages assuming that SCCM just looked at what was approved on the server and applied them.. So from this I think I still have to use ZTIWindowsUpdate due to my config, and I will look at update deployments and update packages to see what they do. Did I miss anything? Let me know if you need more info, I am just floundering in the dark here.
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2012 10:07pm

My site had not had the SUP role installed so am looking at that now but I must make sure that it is only downloading updated that have been approved by the Sec team on another WSUS server. I am looking at the Active Settings during install of the SUP, and wondering if I am meant to set "use this server as the active software update point"
September 10th, 2012 10:16pm

You really should go through this in a lab environment. Doing it in productio nwill get you into trouble. SUPs not marked as Active are only useful if you are going to use an NLB of SUPs. The TechNet documentation is fairly comprehensive: http://technet.microsoft.com/en-us/library/bb633264 There are also a couple of good books available (you can get them instantly via Amazon, like this one: http://www.amazon.com/System-Center-Configuration-Manager-Unleashed/dp/0672330237 [yes, shameless plug]).Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
September 10th, 2012 10:30pm

I agree, but this place does not give me access to a lab enviroment.. That's why I have to keep coming to here\web to check before I change to much.. Ideally I just need to get the updates part working (I can ignore all other issues if i must).. but understand that it could hit the fan even with just this.. In the end it is there problem for not providing labs\training\equipment etc..
September 10th, 2012 11:04pm

Hopefully I am not talking to myself here but I think that it still has a problem looking for an update server. Is it possible (even if not supported by MS) to pull updates from WSUS on another server or from WSUS on the SCCM server (set as downstream)? I am getting these errors and from what I can see it is due to not finding the update source.. RebootCoordinator.log Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 80004005 Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 80004005 Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x80004005
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2012 2:35am

As mentioned above (way above), configuring a SUP as downstream of another stand-alone WSUS instance is not supported. Those errors above are "normal" and only indicate that the UI components could not be launched -- this is typical when no one is logged on or the UI -- Explorer -- is not running. All of the log files should be in the client log files directory (C:\Windows\system32\ccm or C:\Windows\syswow64\ccm) under SMSTSLOG. Where in the TS are you adding this task?Jason | http://blog.configmgrftw.com
September 11th, 2012 8:21pm

I have looked for a log by the name of SMSTS but can not see anything on either the laptop or on the server. I have a TS that does the following http://imageshack.us/photo/my-images/222/captureza.png/ Note that it works fine with the ZTIWindows Update disabled
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2012 1:01am

http://blogs.technet.com/b/inside_osd/archive/2007/12/13/troubleshooting-tips.aspxJason | http://blog.configmgrftw.com
September 12th, 2012 8:10pm

Not really an answer but as usual it has been marked as one..
Free Windows Admin Tool Kit Click here and download it now
September 18th, 2012 2:15am

Hopefully I am not talking to myself here but I think that it still has a problem looking for an update server. Is it possible (even if not supported by MS) to pull updates from WSUS on another server or from WSUS on the SCCM server (set as downstream)? I am getting these errors and from what I can see it is due to not finding the update source.. RebootCoordinator.log Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 80004005 Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 80004005 Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x80004005
September 30th, 2012 6:03am

http://blogs.technet.com/b/inside_osd/archive/2007/12/13/troubleshooting-tips.aspxJason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2012 11:38pm

As mentioned above (way above), configuring a SUP as downstream of another stand-alone WSUS instance is not supported. Those errors above are "normal" and only indicate that the UI components could not be launched -- this is typical when no one is logged on or the UI -- Explorer -- is not running. All of the log files should be in the client log files directory (C:\Windows\system32\ccm or C:\Windows\syswow64\ccm) under SMSTSLOG. Where in the TS are you adding this task?Jason | http://blog.configmgrftw.com
September 30th, 2012 11:49pm

I have looked for a log by the name of SMSTS but can not see anything on either the laptop or on the server. I have a TS that does the following http://imageshack.us/photo/my-images/222/captureza.png/ Note that it works fine with the ZTIWindows Update disabled
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 4:29am

Not really an answer but as usual it has been marked as one..
October 1st, 2012 5:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics