Jump to content


SCCM Client re-installing (badly) after OSD Completes

Recommended Posts

Morning, got a weird issue here, current setup SCCM 2012 R2 CU3...


We're seeing the config manager client re-install itself after OSD Completes successfully.


It's not straight away, it can take 40 mins or so after OSD completes. We've noticed it because Software Centre goes walkabout...


I'm installing the CU3 patch as part of OSD via the patch switch and that works.


You can logon to the machine after OSD has completed and everything looks fine, software will install, patches will install, everythings great (no errors in logs for instance).


Initially I thought it might be the upgrade collection for clients (To update all clients to Cu3), but I've excluded all machines in the OSD collections from this collection and confirmed that the update doesn't try to happen (I thought it might be trying to upgrade the client to the CU3 despite it already being Cu3)


Any ideas? I'm starting to wonder if it's the client health function thinking it's borked, trying to repair itself, and breaking itself...


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...