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, June 30, 2015 7:09 PM
So I've got an experimental task sequence installing some packages (its not an image deployment), and for some reason it got stuck at 'installing' on my test machine.
When I went to kill the tsmanager process there is no such process running. Is there any other way to kill it or where would I find the flag that ensures the TS survives a reboot (so that I can kill that flag maybe?)?
All replies (3)
Wednesday, July 1, 2015 6:05 AM âś…Answered
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, July 1, 2015 12:07 AM
To kill task sequence progress, look for TSprogressUI.exe and end this process.
did you verify the logs (smsts.log,execmgr.log) for the status of execution why is it stuck ? did that package worked when you install manually or via package deployment ?package is that waiting for some input from end user.
Eswar Koneti | Configmgr Blog: www.eskonr.com | Linkedin: Eswar Koneti | Twitter: eskonr
Thursday, July 2, 2015 3:32 PM
@Eswar - there is no TSProgressUI.exe running. The logs were just telling me it was downloading (over and over and over). But the status in Software Center was "Installing". I think I had the TS opened and modified unsaved before kicking off the install - maybe that caused it.
@Torsten - thanks. I followed that link and in the end I just blew away WMI and after the client repaired itself it worked.
1. net stop winmgmt
2. winmgmt /resetrepository
3. Reboot
4. CCMRepair.exe