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
Tuesday, February 10, 2015 4:16 AM
Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windows
All replies (6)
Monday, February 16, 2015 11:42 AM ✅Answered
Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You can mount the Image and check those settings.
RunOnce Key Reference : https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This can be beneficial to other community members reading the thread.
Tuesday, February 10, 2015 5:23 AM | 1 vote
Please don't just post logs, actually look at them and read them. Specifically, you need to check ccmsetup.log and possibly client.msi.log. These are located in c:\windows\ccmsetup\logs.
Also, what does this mean: "If we change the image specified under "Apply Operating System" step, everything works ok." Change it from what to what? Simply saying you changed it is completely meaningless unless you describe what exactly the difference is.
Jason | http://blog.configmgrftw.com | @jasonsandys
Wednesday, October 17, 2018 5:00 PM
Hello,
I've got the exact same problem.
Where in the TS do I have to add the "SMSTSPostAction"?
Is it a variable in the "Setup Windows and Configuration Manager" step?
e.g. Options -> Conditions -> TS Variable ?
Best regards,
Christopher
Wednesday, October 17, 2018 5:47 PM
The above solution is for a very specific use case. Are you sure you are having this issue? Specifically, you have a "Run Once" action configured in the registry in your image? If so, then the recommendation above is to not do this but instead set the SMSTSPostAction to perform whatever configuration would have been done by the Run Once action.
Otherwise, I doubt its related to your issue.
Have you reviewed the logs as suggested?
To answer the question directly though, SMSTSPostAction is a task sequence variable that can be set anywhere in the TS using any valid method that sets TS variables. It's not a condition.
Jason | https://home.configmgrftw.com | @jasonsandys
Thursday, October 25, 2018 3:03 AM
I also have the same issue with a new machine model (HP Elitebook 840r G4 (7thGen)). I'm installing a Windows 10 OS, the task sequence we have have no problem with other / old models that install Windows 7 and Windows 10.
The first few sequence are okay
1. Partition disk
2. Installation of Operating System
3. Installation of drivers
Next step is the installation of Configuration Manager client.
All client pre-requisites are being installed, after installation machine will restart and it won't continue on the rest of the sequence.
I'm seeing errors on ccmsetup.log
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 25/10/2018 10:25:57 AM 4664 (0x1238)
Failed to send status 100. Error (87D00215) ccmsetup 25/10/2018 10:25:57 AM 4664 (0x1238)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
Failed to send status 306. Error (87D00215) ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
Failed to connect to policy namespace. Error 0x8004100e ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
CcmSetup failed with error code 0x80004004 ccmsetup 25/10/2018 10:26:02 AM 4664 (0x1238)
Error on client.msi.log
MSI (s) (28:38) [10:28:08:806]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (28:38) [10:28:08:806]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8498.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
Already checked some blogs relating to this error, but with no luck on fixing it.
I also tried to deploy the client via SCCM console. but i'm having an error as well.
MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent. ccmsetup 25/10/2018 10:55:39 AM 2804 (0x0AF4)
MSI: Module C:\Windows\CCM\StatusAgentProxy.dll failed to register. HRESULT -2147024703. Contact your support personnel. ccmsetup 25/10/2018 10:55:51 AM 2804 (0x0AF4)
File C:\Windows\ccmsetup\EF4FF44A-5960-4DD5-AC5A-4E10625AEA63}\client.msi installation failed. Error text: ExitCode: 1603
Action: SelfRegModules.
ErrorMessages:
Module C:\Windows\CCM\StatusAgentProxy.dll failed to register. HRESULT -2147024703. Contact your support personnel.
ccmsetup 25/10/2018 10:55:53 AM 2804 (0x0AF4)
Error in smsts.log
Command line: "C:\Windows\system32\SMSOSDSetup\TsProgressUI.exe" /UnregisterTsProgressUI 25/10/2018 11:47:28 AM 4976 (0x1370)
Unregistering COM classes TsProgressUI 25/10/2018 11:47:28 AM 4976 (0x1370)
Unregistering class objects TsProgressUI 25/10/2018 11:47:28 AM 4976 (0x1370)
Shutdown complete. TsProgressUI 25/10/2018 11:47:28 AM 4976 (0x1370)
Process completed with exit code 0 OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Successfully unregistered TS Progress UI. OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Failed to install SMS Client (0x80004005) OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Uninstalling Setup Hook OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Removing setup hook from registry. OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Successfully removed C:\Windows\system32\OSDGINA.DLL OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Successfully removed C:\Windows\system32\OSDSETUPHOOK.EXE OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Successfully removed C:\Windows\system32\SMSOSDSetup OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
GetTsRegValue() is unsuccessful. 0x80070002. OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
End program: OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Could not finalize logs to SMS client log directory (80070002) OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Successfully finalized logs to C:\Windows\TEMP\SMSTSLog OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Cleaning up task sequence folder OSDSetupHook 25/10/2018 11:47:28 AM 4044 (0x0FCC)
Deleting volume ID file C:\SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... OSDSetupHook 25/10/2018 11:47:30 AM 4044 (0x0FCC)
Failed to execute task sequence (0x80004005) OSDSetupHook 25/10/2018 11:47:30 AM 4044 (0x0FCC)
Someone already experience this error? It would be a big help sharing a fix on this.
Thanks,
Friday, November 2, 2018 3:36 PM
First, you really need to start a new thread instead of tacking on to a three (nearly four) year old one.
Next, simply posting errors from logs is more or less meaningless for troubleshooting. Logs are about context and flow and every line is important.
Finally, note that this is a ConfigMgr 2012 forum and Windows 10 is not supported in any way on ConfigMgr 2012.
Jason | https://home.configmgrftw.com | @jasonsandys