Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, June 12, 2017 7:29 AM
Hi,
Maybe you can help. I'm stuck in an OS Deployment for a workstation. It stops at a random moment and the system doesn't give me a lead to troubleshoot this.
I have a Task Sequence for OSD. It contains an OS install and also a lot of packages. During the installation process, the TS stops at a random package installation and the system reboots. After the reboot the computer doesn't continue where it was left.
The Deployment log shows no error. I see the latest packages installed with Exit Code 0. This is step 40.
The SMSTS.log on the client shows no error. I paste the last lines (I don't want to paste pages of logfile, but let me know when you need more information).
==========[ TsProgressUI started in process 3924 ]========== TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
Command line: "C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe" /Register:WinPE TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
Registering COM classes TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
sbModulePath = C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
Unregistering class objects TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
Shutdown complete. TsProgressUI 5/31/2017 4:26:33 PM 3816 (0x0EE8)
Process completed with exit code 0 OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Successfully registered TS Progress UI. OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Executing C:\SMSTaskSequence\OSD\S0100002\ccmsetup.exe /useronly /source:C:\SMSTaskSequence\OSD\S0100002 /config:MobileClient.TCF /status:796 OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Command line for extension .exe is "%1" %* OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Set command line: "C:\SMSTaskSequence\OSD\S0100002\ccmsetup.exe" /useronly /source:C:\SMSTaskSequence\OSD\S0100002 /config:MobileClient.TCF /status:796 OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Executing command line: "C:\SMSTaskSequence\OSD\S0100002\ccmsetup.exe" /useronly /source:C:\SMSTaskSequence\OSD\S0100002 /config:MobileClient.TCF /status:796 OSDSetupHook 5/31/2017 4:26:33 PM 3536 (0x0DD0)
Process completed with exit code 0 OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Install succeeded. Blocking other instances of ccmsetup. OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Creating ccmsetup mutex. OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Installed Client OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Backing up current global client logging settings that are read from registry OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Overwrote client global logging setting in registry with OSD logging settings. OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Start to cleanup TS policy OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
TS Deleted 0 instances OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
TS Policy cleanup done OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
End TS policy cleanup OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Setting variable to indicate a client installation was done OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Registering the task sequence with the execution manager in the newly installed operating system. OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE. OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
Saving the new active request handle for the task sequence: {EC181B7C-4476-41FE-859F-B5941C4FAF04} OSDSetupHook 5/31/2017 4:27:12 PM 3536 (0x0DD0)
CoCreateInstance succeeded OSDSetupHook 5/31/2017 4:27:14 PM 3536 (0x0DD0)
Succesfully registered the tasksequence with the execution manager OSDSetupHook 5/31/2017 4:27:15 PM 3536 (0x0DD0)
Command line for extension .exe is "%1" %* OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
Set command line: "C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe" /Unregister OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
Executing command line: "C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe" /Unregister OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
==========[ TsProgressUI started in process 3752 ]========== TsProgressUI 5/31/2017 4:27:16 PM 3744 (0x0EA0)
Command line: "C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe" /Unregister TsProgressUI 5/31/2017 4:27:16 PM 3744 (0x0EA0)
Unregistering COM classes TsProgressUI 5/31/2017 4:27:16 PM 3744 (0x0EA0)
Unregistering class objects TsProgressUI 5/31/2017 4:27:16 PM 3744 (0x0EA0)
Shutdown complete. TsProgressUI 5/31/2017 4:27:16 PM 3744 (0x0EA0)
Process completed with exit code 0 OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
Successfully unregistered TS Progress UI. OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
Moving logs to SMS client directory OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
LOGGING: Resetting log path. OSDSetupHook 5/31/2017 4:27:16 PM 3536 (0x0DD0)
The line in **bold **is marked yellow in CMtrace.
Did some have the same experience? How did you troubleshoot this?
Please let me know when you require more information to understand this case.
Best regards,
Yuri
All replies (5)
Wednesday, June 28, 2017 4:50 PM ✅Answered
Hi,
I couldn’t find a lead in SCCM because the error was related to the packages. The task sequence during OSD runs before Windows starts. Apparently the installation of some packages require to run in Windows. I’ve made another task sequence, included the suspect packages, and made that available via Software Center. Now everything runs smooth.
Thank you for participating.
Yuri
Wednesday, June 14, 2017 6:45 AM
I found a lead.
The Deployment Status is In Progress, so I took a look at the status via Status Message Queries and 'All Status Messages for a Specific Deployment at a Specific Site'. The last log is:
"Deployment .. from site .. was rejected because the client's platform is not supported."
The TS has Run on any platform and the packages are also configured to Run on any platform.
I read a post where someone re-installed the SCCM client. But in my case this is a OSD with an installation of a Operating System and applications. Recently (after the original TS was created) I updated SCCM 2012 to build 1702. So I checked the SCCM Client installation package in the TS. This points to the default "Configuration Manager Client Package" which is updated by the upgrade.
It seems I have a dead end again. Anyone some more idea's for me?
Wednesday, June 14, 2017 7:05 AM
I found this: http://henkhoogendoorn.blogspot.nl/2014/07/strange-issue-in-monitoring-status.html
and changed the setting Deploy the Task Sequence to "Configuration Manager clients, media and PXE".
Unfortunately it didn’t solve the original issue of this post.
The client spontaneously rebooted in the process and the Task Sequence didn’t complete. The Status Message Queries gives me: Message ID 10002
“Deployment .. was received from site ..
The client passes any supported platform requirements and Configuration Manager will add the Deployment's program to the list that will be displayed to users and/or run via assignment. If a deployment is received but not displayed on a client, verify that the current time on the client is between the deployment start and expiration times, and that the program specified in the deployment is enabled.”
(It solved the ‘client platform is not supported’ message)
So I double checked the deployment expiration date, but the deployment doesn’t have an expiration date.
I guess, the deployment never continues after a spontaneously reboot by the client, so it’s better to look for a lead why the TS is disrupted in the first place.
Anyone idea’s on which logs to check?
Wednesday, June 14, 2017 9:40 AM
Use "All Status Messages from a Specific System" to get an idea which Task sequence steps ran.
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, June 14, 2017 11:14 AM
Hi Torsten,
I have a breakdown from the log and will comment on that, please read from bottom up.
__ end
Severity Type Site code Date / Time System Component Message ID Description
Information Milestone S01 14-6-2017 10:42:49 WS-163 Software Distribution 10035 The program for deployment "S0120001 has not yet started because the content for the package "S0100002" - "*" (version 7) has not been acquired. Possible cause: The content for this program must be downloaded into the computer's cache, or the content could not be located. Solution: If the program is being downloaded, no action is required. The program will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer. Distribution point availability can be affected by boundary configuration which is used to determine whether distribution points are classified as local or remote, or by enabling distribution points as protected distribution points.
(after 35 mins this is registered in the log, this package is little over 2 GB.)
Information Milestone S01 14-6-2017 10:06:52 WS-163 Software Distribution 10002 Deployment "S0120000" was received from site "S01". The client passes any supported platform requirements and Configuration Manager will add the Deployment's program to the list that will be displayed to users and/or run via assignment. If a deployment is received but not displayed on a client, verify that the current time on the client is between the deployment start and expiration times, and that the program specified in the deployment is enabled.
(there is no expiration on the deployment)
Information Milestone S01 14-6-2017 10:05:42 WS-163 Software Distribution Content Access 10027 The cache size has been modified from 5120 MB to 25600 MB. The cache is located at C:\Windows\ccmcache.
(the cache size has been changed according the Client Policy)
Information Milestone S01 14-6-2017 10:04:22 WS-163 Advanced Client 10804 The ConfigMgr client was reassigned. The previous site code was "". The new site code is "S01".
(there has been an unexpected reboot of the client, there is a log about the ConfigMgr client site code)
Information Milestone S01 14-6-2017 09:59:59 WS-163 Task Sequence Engine 11124 The task sequence execution engine started the group (6Install [conditions]).
Severity Type Site code Date / Time System Component Message ID Description
Information Milestone S01 14-6-2017 09:59:59 WS-163 Task Sequence Engine 11127 The task sequence execution engine successfully completed the group (5Install [conditions]).
(the logs shows that everything is fine, group 5 of the TS ended and group 6 starts)
__ start
This made me think:
- Is the packages size to big to be deployed via a Task Sequence?
- Is it normal that the side code and the cache size are changed in this moment?
Or what get your attention when you read this?
Thanks,
Yuri