Share via

OSD stuck at "The task sequence execution engine performed a system reboot initiated by the action (Setup Windows and ConfigMgr)"

  • Article

Question

Thursday, August 27, 2015 4:39 PM

Hi All

We are in the process of migrating from 2007 to 2012 but facing a strange issue. We are using SCCM 2012 R2 SP1 (with Adaptiva OneSite)

The OSD is getting stuck at "The task sequence execution engine performed a system reboot initiated by the action (Setup Windows and ConfigMgr)" 

It is a MDT based SCCM TS migrated from 2007. The WIM was created using SCCM 2007.

The strange part is the same task sequence/image deploys without issues in another location on the exact same model.

I disabled the model drivers just to isolate the issue but still no luck.

I see there are few people raised similar questions but answers are not convincing. 

Any idea? Anyone who faced the issue?

All replies (4)

Monday, August 31, 2015 6:08 AM

Hi,

Please check the logs for client installation. Is the client installed successfully?

ccmsetup.log and client.msi.log

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].

Wednesday, September 23, 2015 6:48 AM

This issue is occurring on random machines.

On some machines it takes 15 minutes and on many machines it takes around 54 minutes to complete.

We have raised a case with MS and we are still troubleshooting the issue.

MS says it is something to do with the ProvisioningMode.

The client is stuck initializing and taking additional 35 minutes to progress.

 

Wednesday, September 23, 2015 10:33 AM

Because you created your operating system wim file using Configuration Manager 2007, its going to have that old version of the client embedded in it.

I would highly recommend re-creating your reference image either with Configuration Manager 2012 or with MDT 2013 Update 1 as a starting point. If you use MDT you will avoid having the Configuration Manager client embedded in the image.

Its obviously impossible to be sure that this is your issue without examining your logs however re-using a reference image from a 2007 environment in a 2012 environment has the potential to cause problems and I've seen plenty of posts from people over the years with similar types of problems.

Cheers

Damon

Friday, January 8, 2016 6:58 PM

Did you ever get to the bottom of this?