Application Deployment Task Sequence Fails on User initiated Reboot

Hi all, We are deploying a set of applications via a task sequence. Some of the applications require the user to be logged off. We have a Package that prompts the user to log off. The package is stated by the TS. However we have had some users reboot the workstations. This is causing the TS to fail because of the external shutdown request.

I have tired creating a group which contains all the applications and scripts required. The group and the applications have the 'Continue on Error' set. But it still fails. What I am wondering is there any way to force the TS to run again after this failure with external intervention or a way of detecting the external reboot request and starting the TS from where it left off?

I did look at changing the shutdown permissions on the start menu for the workstation to stop this use behaviour. But that seems to be a sled hammer approach to the problem and I would not like have to resort to.  

 I get this in the smsts.log.

ServiceCtrlHandler - STOP/SHUTDOWN control request received TSManager 1/09/2015 8:37:37 AM 4696 (0x1258)
ServiceCtrlHandler - Signalling shutdown event TSManager 1/09/2015 8:37:37 AM 4696 (0x1258)
Cancel request was detected. Terminating command line execution. TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
ServiceCtrlHandler - Leaving Task Sequence Manager ServiceCtrlHandler TSManager 1/09/2015 8:37:37 AM 4696 (0x1258)
!--------------------------------------------------------------------------------------------! TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
External system shutdown request is received during execution of the action (<logoff application>) TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
Set a global environment variable _SMSTSLastActionRetCode=1115 TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
Set a global environment variable _SMSTSExternalShutdownRequestReceived=true TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
The action (<logoff application>) is either not set for retry or exhausted the number of retry attempts. It will not be retried after the reboot.(Current retry count: 1, Total retries: 0) TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
Set a global environment variable _SMSTSLastActionNeedsRetry=false TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
Clear local default environment TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)
A external system reboot request was received when running the instruction (<logoff application>), attempting to save TS execution state TSManager 1/09/2015 8:37:37 AM 1212 (0x04BC)

And then the TS ends with this in the smsts.log;

Waiting for CcmExec service to be fully operational TSManager 1/09/2015 8:38:13 AM 3108 (0x0C24)
CcmExec service is up and fully operational TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Remediating TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Error getting system isolation info. Code 8027000C TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Remediation failed. Code 8027000C TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Remediation failed with error code 8027000C TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Task sequence failed due to an external shutdown request received during the TS execution and the TS action is not configured for retry on reboot. TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Task Sequence Manager could not initialize Task Sequence Engine. code 80004005 TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Task sequence execution failed with error code 80004005 TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Cleaning Up. TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Removing Authenticator TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Cleaning up task sequence folder TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)
Executing command line: "C:\windows\CCM\TsProgressUI.exe" /Unregister TSManager 1/09/2015 8:40:35 AM 3108 (0x0C24)

August 31st, 2015 11:52pm

Hi,

Continue on error doesn't make it possible for the Task Seqeunce to recover from an unexpected reboot. In Configuration Manager 2012 Sp1 / R2 Sp1 there is a new option for APplication and software update "Retry this step if computer restarts unexpectedly" using that option you should be able to recover. But the it must be an application and not a package/program. Another option is to modify the package and use a different command lien during OSD.

Regards,
Jrgen

Free Windows Admin Tool Kit Click here and download it now
September 1st, 2015 2:00am

How about just forcing a reboot at the beginning of the TS yourself in the TS? This accomplishes the goal. It's a little more intrusive, but not by much. Or, assuming you are are doing this to ensure that the applications are not in use when being updated, prompt the users to close those apps with something like the PowerShell deployment Toolkit?
September 1st, 2015 9:23am

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

Other recent topics Other recent topics