Hello,

Our OSD task sequence fails to install the SCCM client with certain images.

The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.

The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence

If we change the image specified under "Apply Operating System" step, everything works ok.

It appears there is something wrong with this particular image. Any ideas?

Logs show no errors. Let me know which logs you'd like me to post (and from which location)

There is no ccm folder under c:\windows

• Edited by mblagoje123 Tuesday, February 10, 2015 4:18 AM

Please don't just post logs, actually look at them and read them. Specifically, you need to check ccmsetup.log and possibly client.msi.log. These are located in c:\windows\ccmsetup\logs.

Also, what does this mean: "If we change the image specified under "Apply Operating System" step, everything works ok." Change it from what to what? Simply saying you changed it is completely meaningless unless you describe what exactly the difference is.

Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You can mount the Image and check those settings.

RunOnce Key Reference : https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx

If the above key is present in the Image, TS Engine won't resume after the reboot.

You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.

The above variable is applicable in CM 2012 SP1 and R2.