Hi Guys, This TS was given to me that Installs Software Updates. Steps in the TS: Sets TS Variable: SMSTSReboot Runs a Software Update Scan (VBScript) Sets TS Variable Value: 180 Minutes Installs Software Updates: All Applicable Updates. The machine reboots if required and some of these machines do not continue after the reboot, instead I can see these machines in the 'Running' state of the advertisement Status. When I check the logs of the advertisement Status it says the machine was rebooted, but still says 'Running' after the TS completed. Kindly please suggest what I should look for. Best Regards, Simon.

What do you see in the smsts.log and the smsts<datetime>.log files on the client? Nash Pherson, Senior Systems Consultant, Now Micro - http://www.nowmicro.com <--- If this post was helpful, please click "Vote as Helpful".

Hi Nash, As the TS was run couple of months ago, I am unable to see what exactly happened. Is there a way to check? The current smsts.log and the smsts<Date-Time>.log just mentions that the TS Advertisement was successful. When I check the Task Sequence - Advertisement Status, this is the Action Output: machine' namespace Policy verification done GetIPriviledgedInstallInterface successful Refreshing Updates Successfully initiated RefreshUpdates operation Waiting for RefreshUpdates complete notification from Updates Deployment Agent Notification received, RefreshUpdates have been completed Signaled RefreshComplete notification Received RefreshUpdates complete notification from Updates Deployment Agent RefreshUpdates operation has been completed, hr=0x00000000 GetIPriviledgedInstallInterface successful Installing all updates targetted for this computer Installation of updates started Waiting for installation job to complete Waiting for job status notification ... NotifyComplete received Received job completion notification from Updates Deployment Agent Reboot Required Setting TSEnv variable SMSTSRebootRequested=HD Setting TSEnv variable SMSTSRetryRequested=TRUE Installation is not yet complete, action needs to be re-run after reboot Setting TSEnv variable SMSTSInstallUpdateJobGUID= The next & last step is the machine was rebooted (The Task Sequence execution engine performed a system reboot initiated by an action) This results in the machine reporting the Execution State as 'Running' instead of 'Succeeded'. Can anything be done to remove the machines from the 'Running' State to 'Succeeded'? Best Regards, Simon.

This issue can be caused by the Task Sequence not exiting cleanly and it is still in the provisioning mode. A Task Sequence not exiting cleanly is usually caused by one of the following scenarios: 1. At some point after the "Setup Windows and ConfigMgr" task, a power failure or crash occurs on the PC. At this point the PC may be bootable and the user may be able to log into the PC. However because the Task Sequence never exited cleanly, the ConfigMgr client is left in provisioning mode, and the problem may exist. 2. A "Restart Computer" task at some point after the "Setup Windows and ConfigMgr" task that is accidentally set to restart into the WinPE boot image assigned to the Task Sequence instead of the full Windows OS. This will cause the Task Sequence to end in WinPE. Because the ConfigMgr client is actually installed as part of the full Windows OS and not WinPE, and because the Task Sequence ends in WinPE instead of the full Windows OS, it cannot properly take the ConfigMgr client out of provisioning mode. This error is common because the "Restart Computer" task defaults to restarting into the WinPE boot image instead of the full Windows OS. The "Restart Computer" task option "The boot image assigned to this task sequence" will cause it to reboot into WinPE, while the option "The currently installed default operating system" will cause it to reboot into the full Windows OS being deployed by the Task Sequence. If the option is not specifically switched from the default setting when the "Restart Computer" task is added to the Task Sequence, then the issue will occur. 3. In Windows XP and Windows Server 2003, if an application is installed during the Task Sequence that installs a custom Gina, the problem will happen. In Windows XP and Windows Server 2003, the ConfigMgr OSD Task Sequence will install a custom Gina called OSDGina. This Gina is used for several reasons during a Task Sequence such as accomplishing automatic log ins between reboots, disabling all user interfaces such as Explorer, etc. If the OSDGina is replaced by another custom Gina, then the Task Sequence cannot end or exit cleanly and the ConfigMgr client will not be taken out of provisioning mode. Note: Custom Ginas can only be used in Windows XP or Windows Server 2003. Custom Gina issues will not occur in Windows Vista or newer since custom Ginas, including OSDGina, are not used in Windows Vista or newer. You may refer to the following blogs to see if the information helps: Solution: After a ConfigMgr 2007 OSD Task Sequence completes, the client may not automatically pull down policy Installing a Custom GINASabrina TechNet Community Support

Hi Sabrina, We have only Vista OS and I believe custom Gina issues will not occur in Windows Vista or new OS. We use TS to Install software updates in this organisation. Hence this TS does only have the four steps mentioned below: Sets TS Variable: SMSTSReboot Runs a Software Update Scan (VBScript) Sets TS Variable Value: 180 Minutes Installs Software Updates: All Applicable Updates. I believe the machine is rebooted and the TS doesn't exit properly hence the machines are stuck in 'Running' State. When the TS is rerun on these machines it mentions about the Rerun only applies for machines where it failed and as it was successful in the previous attempt it won't rerun. Not sure what needs to be done to get the machines out of the 'Running' State. Please advise. Best Regards, Simon.

Hi Guys, Any one else has experienced similar issues? Simon.

Hi, We are expriencing a similar issue: at the end of our TS's we have a Restart Computer task. In some computers the task does not finish and remains running. We are still looking at this issue, if we came up with a solution i'll post it here. Regards.Filipe Lopes

Hi Filipe, Were you able to find a solution for this issue? If you have a solution please post it here as I still have this problem. Best Regards, Simon.

Hi! Nop after several tests and log reading didn't came up with a solution. Had to remove the last reboot on the TS or the SCCM agent would be stuck on provisioning mode. Regards,Filipe Lopes