we never had issues before, looking at the logs, I would say its with installing updates.
this is being repeated over and over and over again in smsts.log Waiting for job status notification ... InstallSWUpdate 23/05/2014 14:08:03 3620 (0x0E24) Update with CIID Site_F1E519DF-A4F0-4BD0-BA26-CDCC8B5CC8FF/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643 InstallSWUpdates 23/05/2014 14:08:16 3608 (0x0E18) Update with CIID Site_F1E519DF-A4F0-4BD0-BA26-CDCC8B5CC8FF/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643 InstallSWUpdates 23/05/2014 14:08:29 3608 (0x0E18) Update with CIID Site_F1E519DF-A4F0-4BD0-BA26-CDCC8B5CC8FF/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643 InstallSWUpdates 23/05/2014 14:08:38 3608 (0x0E18) Update with CIID Site_F1E519DF-A4F0-4BD0-BA26-CDCC8B5CC8FF/SUM_729a0dcb-df9e-4d02-b603-ed1aee074428 failed with hr = 0x80070643 InstallSWUpdates 23/05/2014 14:08:50 3608 (0x0E18) 729a0dcb-df9e-4d02-b603-ed1aee074428 is MS11-025 ( http://support.microsoft.com/kb/2538243) However its showing the below (MS11-085) WUAHandler shows the below over 1 hour ago, so is the above really the current update installing or is it MS11-085 Update (PendingReboot): Security Update for Windows 7 (KB2620704) (fe3053c7-cc35-4e94-b176-1e2a8e9c8c14, 101) WUAHandler 23/05/2014 13:03:41 3656 (0x0E48) Leaf: fc9817d9-1476-4d37-b281-d8cbccf06455, 101 Status: PendingReboot WUAHandler 23/05/2014 13:03:41 3656 (0x0E48) for Software updates 1 step we have on error resume next enabled, so when it eventually times out, guess around 8 hours based on prev tests, should be ok the only other option is to remove MS11-025 from deployment of the ref image and let normal patching catch it. Will test that week after next when Im back in the office. On 23 May 2014 13:13, Daniel Ratliff <[email protected]> wrote: > We do about that many updates and our software updates take about 1-2 > hours. Check the logs and see where the delay is? Download time? Install > time? > > -Daniel Ratliff > > > -----Original Message----- > *From: *Rickym61 [[email protected]] > *Sent: *Friday, May 23, 2014 05:03 AM Eastern Standard Time > *To: *[email protected] > *Subject: *Re: [mssms] SCCM 2007 Reference Image - Install Software > Updates takes forever. > > Thanks for responses so far. > > David - Sounds like a good plan, will look into it. > Niall - yes we do have a SLP defined, although not using FQDN, the VM I > use falls in with the subnet for dev enviroment in SCCM so that's ok. > > The last 6 or 7 reference images have never had this issue with the > updates, not sure why all of a sudden its started, the updates take around > 8 hours to complete, download and install approx 130-150 updates. It works > in the end but just takes forever. > > > On 23 May 2014 09:00, Niall Brady <[email protected]> wrote: > >> make sure your *setup windows and configmgr* step has a SLP >> defined<http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/>and >> that your reference computers *ip >> address* falls into a defined boundary (ip address range for example), >> you can create an ip address range boundary containing just one ip if you >> wish for this purpose as long as it matches the ip address of the virtual >> machine you are building the image on >> >> don't rely on AD site's boundarys for this as this computer will be in a >> workgroup so won't be in AD. >> >> >> On Fri, May 23, 2014 at 7:54 AM, Ben Glenz <[email protected]>wrote: >> >>> There was a really good session from Johan at TechEd about creating a >>> Windows 8.1 (you can use Win7 of course) Reference Image fully automated. >>> >>> >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of* David O'Brien >>> *Sent:* Freitag, 23. Mai 2014 00:18 >>> *To:* [email protected] >>> *Subject:* RE: [mssms] SCCM 2007 Reference Image - Install Software >>> Updates takes forever. >>> >>> >>> >>> If possible switch over to creating your reference image with MDT >>> standalone. >>> >>> By the time you have that set up and working you would probably still be >>> troubleshooting your ConfigMgr problem. >>> >>> ConfigMgr and Software Updates during OSD are a pain. >>> >>> >>> >>> Cheers >>> >>> David >>> >>> ----------------------------------------------------------------- >>> >>> David O'Brien >>> >>> Microsoft Enterprise Client Management MVP >>> >>> http://www.david-obrien.net >>> >>> >>> >>> >>> >>> >>> >>> *From:*[email protected] [ >>> mailto:[email protected] <[email protected]>] *On >>> Behalf Of* Rickym61 >>> *Sent:* Friday, May 23, 2014 8:13 AM >>> *To:* [email protected] >>> *Subject:* [mssms] SCCM 2007 Reference Image - Install Software Updates >>> takes forever. >>> >>> >>> >>> Question: how long does it take to complete the Install Software Updates >>> step when creating a reference image for others? >>> >>> >>> >>> SCCM 2007 SP2 R2 >>> >>> W7 SP1 x86 with Office 2010 SP1 >>> >>> >>> >>> Just want to get an idea on how long it takes for others out in the >>> field, just creating this quarters new ref image and had a few issues, >>> mainly the install software updates step timing out, updates never >>> downloading, if installing takes a considerable amount of time. None if >>> these issues occurred last quarter. >>> >>> >>> >>> Issues and Solutions I found. >>> >>> >>> >>> Timing out possible due to 30min hard coded limit, adding a reboot after >>> install software updates step 1 possible solution as per a KB I found. >>> >>> >>> >>> Updates never downloading, (downloading 1 of 134, stays at 0% forever) >>> is resolved by KB2509007, but this is already installed, confirmed in log >>> files and checking the version of dll it replaces so shouldn't happen. >>> >>> >>> >>> If gets to installing software updates, it takes around 8 hours just to >>> do the install software updates step 1. Crazy I know. >>> >>> >>> >>> As I get the 8 hours to install updates, it's getting me my image so >>> progressing but not sure why it takes so long. >>> >>> >>> >>> Anyone had similar symptoms in the past. >>> >>> >>> >>> Thanks all. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
