Hi!

I have an application based on a MSI-file.
After I upgraded SCCM 2012 to SCCM 2012 R2
the OSD task sequence reboots after the application is
installed and instead of continuing the task sequence the
computer boots into the login screen.

I have tried all the diffrent settings in the image below, the only
diffrence it makes is that the application installation hangs (wihout reboot)
even though the application gets installed.



What does the smsts.log report back?

What command-line are you using to install the MSI? Have you tried adding REBOOT=ReallySuppress?

An unexpected reboot during the TS often kills it so you need to configure your command-line to prevent this. ConfigMgr cannot override what an MSI actually does internally.

Yes i have tried to add REBOOT=ReallySuppress,
when i use that the task sequence hangs at the application installation.

I get this error from smsts.log:

Failed to create instance if Software Execution Request Managerr. 0x80070005 OSDSetupHook
GetActiveRequest failed with error code 0x87d01012 OSDSetupHook
GetActiveRequest failed. 0x87D01012. OSDSetupHook
ReleaseActiveRequest failed. 0x87d01012. OSDSetupHook
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram OSDSetupHook
GetTsRegValue() is unsuccessful. 0x80070002. OSDSetupHook

I also get this error in the msi log:

MSI (s) (90:3C) [10:15:02:027]: Unable to delete the file outside of the engine. LastError = 2

Hi,

We need the complete MSI.log file and SMSTS.log.

From the partial log file you posted, it seems the TS failed due to unexpected reboot. I guess the Program you intended to install had not returned a proper exit code to TS so that the TS cannot handle the reboot itself.

Did you try to configure "Configuration Manager client will force a mandatory device restart" for the application?

After the change did you update the Deployment Type (to be sure, that the change gets done)?

If the application needs a reboot, it should have it. With the abover configuration, the task sequence will not be killed.

You should also look  AppEnforce.log, AppDiscovery.log -files from the target machines %windir%\ccm\logs

• Edited by narcoticoo 4 hours 51 minutes ago
• Proposed as answer by narcoticoo 4 hours 51 minutes ago

Did you try to configure "Configuration Manager client will force a mandatory device restart" for the application?

After the change did you update the Deployment Type (to be sure, that the change gets done)?

If the application needs a reboot, it should have it. With the abover configuration, the task sequence will not be killed.

You should also look  AppEnforce.log, AppDiscovery.log -files from the target machines %windir%\ccm\logs

• Edited by narcoticoo Sunday, January 19, 2014 7:31 AM
• Proposed as answer by narcoticoo Sunday, January 19, 2014 7:32 AM

I have tried "Configuration Manager client will force a mandatory device restart"
it reboots and then exits the Task Sequence.

Here are the logs, the affected msi are cd-ord.msi.

https://www.dropbox.com/sh/p55il6rzcjirq82/p-k8mqtPv6

• Edited by Onners 2 hours 39 minutes ago

I have tried "Configuration Manager client will force a mandatory device restart"
it reboots and then exits the Task Sequence.

Here are the logs, the affected msi are cd-ord.msi.

https://www.dropbox.com/sh/p55il6rzcjirq82/p-k8mqtPv6

• Edited by Onners Monday, January 20, 2014 9:48 AM

Have you tried to configure exit code 1641 as Success (No Reboot) for the deployment type of the application causing the problems? I saw from your logs that the application exits with that code and by default it's a hard reboot.

More info here:

http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

• Proposed as answer by narcoticoo 17 hours 57 minutes ago
• Edited by narcoticoo 17 hours 56 minutes ago

Have you tried to configure exit code 1641 as Success (No Reboot) for the deployment type of the application causing the problems? I saw from your logs that the application exits with that code and by default it's a hard reboot.

More info here:

http://www.petervanderwoude.nl/post/working-with-the-restart-behavior-of-applications-in-configmgr-2012/

• Proposed as answer by narcoticoo Monday, January 20, 2014 6:23 PM
• Edited by narcoticoo Monday, January 20, 2014 6:25 PM

Did you try my proposal?