dozi Posted August 1, 2014 Report post Posted August 1, 2014 Hello, i have configured the monitoring from the MDT-Workbench and it works like a charm. I can see the SCCM-Task-Sequences running and reporting every time the MDT-Gather step runs. My only problem is now, that i would not show, when the TS is finished. It hangs on "Running" forever and change to "not responding" after some time. Do i need some "finishing" step at the end of the UDI-Tasksequence to inform the Monitoring-Web-Service that the TS is finished? I have tryed to put a "Gather"-Step at the end, but its not working. Additionally i have added a FinishAction= and SkipFinalSummary= Step to the CustomSettings.ini in the settings-files. Haven't tested that yet, because of running installations of other users. Is that maybe the right step? Thanks for helping. Dominik Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted August 3, 2014 Report post Posted August 3, 2014 have you actually confirmed via the smsts.log file that the installation has completed successfully ? Quote Share this post Link to post Share on other sites More sharing options...
dozi Posted August 5, 2014 Report post Posted August 5, 2014 Yep, the last step (SMSTSPostAction) is executed. I have manually confirmed it trough the logs aswell. All is fine here. Any ideas? Quote Share this post Link to post Share on other sites More sharing options...
dozi Posted August 5, 2014 Report post Posted August 5, 2014 Ok, after some researching and stuff, theres an error on the end of the TS: End program: cmd /c shutdown /r /t 0 /f TSManager 05.08.2014 14:42:31 1564 (0x061C) Finalize logging request ignored from process 1528 TSManager 05.08.2014 14:42:31 1564 (0x061C) Waiting for CcmExec service to be fully operational TSManager 05.08.2014 14:42:31 1564 (0x061C) CcmExec service is up and fully operational TSManager 05.08.2014 14:42:31 1564 (0x061C) Access handle will be read from _SMSTSActiveRequestHandle TSManager 05.08.2014 14:42:31 1564 (0x061C) Access handle: {2B55AA51-7853-439B-8F7E-7C5D801C1416} TSManager 05.08.2014 14:42:31 1564 (0x061C) Attempting to release request using {2B55AA51-7853-439B-8F7E-7C5D801C1416} TSManager 05.08.2014 14:42:31 1564 (0x061C) CoCreateInstance succeeded TSManager 05.08.2014 14:42:31 1564 (0x061C) pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 05.08.2014 14:42:31 1564 (0x061C) ReleaseRequest failed with error code 0x80004005 TSManager 05.08.2014 14:42:31 1564 (0x061C) Task Sequence Manager could not release active TS request. code 80004005 TSManager 05.08.2014 14:42:31 1564 (0x061C) Process completed with exit code 0 TSMBootstrap 05.08.2014 14:42:31 1924 (0x0784) Exiting with return code 0x00000000 TSMBootstrap 05.08.2014 14:42:31 1924 (0x0784) Process completed with exit code 0 OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Task sequence completed 0x00000000 OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Waiting for command shell to complete. OSDSetupHook 05.08.2014 14:42:31 1800 (0x0708) Resume SCCM Client. OSDSetupHook 05.08.2014 14:42:31 1016 (0x03F8) Uninstalling Setup Hook OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Removing setup hook from registry. OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\OSDGINA.DLL OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully removed C:\WINDOWS\system32\_SMSOSDSetup OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) End program: cmd /c shutdown /r /t 0 /f OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs OSDSetupHook 05.08.2014 14:42:39 1016 (0x03F8) But it says "Task Sequence Completed" with "0". So i don't get it ... Attached you will find the log-files from that deployment. smsts.log smsts-20140805-144202.log smsts-20140805-234018.log Quote Share this post Link to post Share on other sites More sharing options...
dozi Posted August 19, 2014 Report post Posted August 19, 2014 No ideas here? Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted August 19, 2014 Report post Posted August 19, 2014 Not every error is a problem. This task sequence seems to end fine. Are you having any issues after the deployment is completed? Quote Share this post Link to post Share on other sites More sharing options...
dozi Posted August 20, 2014 Report post Posted August 20, 2014 Absolutely no problems after the TS finishes. Just wanted to no if theres a problem with our OSD. Its simply annoying that we cant use the monitoring feature like its meant ... Quote Share this post Link to post Share on other sites More sharing options...
cfreeman21 Posted January 12, 2016 Report post Posted January 12, 2016 I am having this exact same issue... Did you ever figure this out? Quote Share this post Link to post Share on other sites More sharing options...
cfreeman21 Posted January 20, 2016 Report post Posted January 20, 2016 Can anyone tell me what Log or what reports to MDT to say successful... My images complete success but will not go to complete in mdt Quote Share this post Link to post Share on other sites More sharing options...
jdd12 Posted January 20, 2016 Report post Posted January 20, 2016 I have a Run Command Line task named "Completed Successfully" as the last step in my TS that reports that status to my MDT Monitoring. cscript "%deployroot%\scripts\ztidone.wsf" Quote Share this post Link to post Share on other sites More sharing options...
