Trying to target software update group only to machines during operating system deployment

I have a System Center 2012 R2 Configuration Manager environment with a mix of Windows 7 and Windows 8 clients and OS deployments.

I'm in the process of switching my software updates over to automatic deployment rules. I've been wrestling with configuration manager and software updates for a while. On two separate occasions, I've had my update deployments quit working. The last time this happened I put in a ticket. The engineer assigned to the ticket found the cause to be too many updates deployed to machines. The fix, according to the engineer, was to limit the number of updates deployed to machines, avoid double deploying updates to computers by preventing membership in multiple collections targeted by different deployments of the same update group. and by purging deployments of updates where there is full compliance.

I created a catch up group that is only deployed to machines being imaged. I tried to target the OSD machines by deploying the catch up group to the "unknown computer" and "unprovisioned computers" collections. However, when the Install Software Updates portion of the task sequence runs, there are no updates to install.

To make things easier for the helpdesk, I have my imaging jobs available to all computers from PXE boot so that the computer object does not have to be deleted before a machine can be imaged. This causes the majority of our machines to be "known" by SCCM when they are imaged. I was hoping that since a new agent/guid is created during the process of operating system deployment, that maybe one of the "unknown computer" or "unprovisioned computers" collections would be applicable. This does not seem to be the case.

I am aware of Maik Koster's web services, but it seems like overkill to use this just to add the OSD target to an "OSD Updates" collection, install the updates, and then remove the OSD target from the collection at the end of the task sequence. Is there an easier way to accomplish this without removing the requirement to delete the computer object from configmgr?



  • Edited by AMReagan 7 hours 6 minutes ago
May 21st, 2015 8:36pm

 The fix, according to the engineer, was to limit the number of updates deployed to machines, avoid double deploying updates to computers by preventing membership in multiple collections targeted by different deployments of the same update group. and by purging deployments of updates where there is full compliance. 


How was this set up initially? How many software update groups? What updates and how many did each contain?
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 1:54am

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

Other recent topics Other recent topics