There is not a limit on the number of updates, but there is a hard 30 minute limit on one of the SU steps. I think it's a policy refresh or something like that. Most people encounter it in their build & capture TS. The fix is to install SU, restart, scan for more SU, install SU again, then rinse and repeat until all your updates are installed. In my current Win7x64 w/Sp1 B&C I have to run it three times to catch all the updates. Two pre-apps and one post apps(.NET, Office, Lync, etc).
Daniel Ratliff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Trevor Sullivan Sent: Wednesday, November 20, 2013 1:48 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] Client thingy after OSD build Johan, I'm not aware of there being any limit on the number of updates that can be deployed to a client ... I have never heard of such a thing. Have you considered updating your reference image, using a build & capture task sequence? Cheers, Trevor Sullivan From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com]<mailto:[mailto:listsad...@lists.myitforum.com]> On Behalf Of Johan van Dijk Sent: Wednesday, November 20, 2013 12:12 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Client thingy after OSD build Not sure if someone had mentioned something similar couple of weeks ago....can't find it anymore... :| Is there any limit known regarding the amount of software updates you can advertise against a client...? After an OSD build it almost takes 30-45 minutes before ccmexec calms down and stops restarting itself and thus becomes usable...? Lots of activity regarding SUM entries within CIAgent.log passing by while this is occurring. I have a feeling that the number of patches being offered becomes a little too much....but not sure. Weird enough I only see this currently happening on an Optiplex 780 which is the oldest model we have... Anyone a hunch where to look for...? 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.
