ConfigMgr Task Sequence Monitor

ConfigMgr Task Sequence Monitor is a GUI application that makes use of the task sequence execution data in the ConfigMgr database to review or monitor ConfigMgr task sequences.  It is particularly useful for monitoring OS deployment task sequences step by step in near real-time.

4.5 Star
20,515 times
Add to favorites
System Center
E-mail Twitter Digg Facebook
Sign in to ask a question

  • LastStatusMsgName Filter
    2 Posts | Last post April 20, 2017
    • Hi, I've just found this today and I'm loving the feed back its giving me. Would it be possible to filter the returned events so I could prevent any 'Skipped an action because its condition was evaluated to be false'?
      Maybe a filter button under 'Generate Reports' which could have a list of check boxes against status messages so show or hide?
    • That's a good idea. I will try to work some additional filtering into the next release.
  • Identifying Unknown Computers
    6 Posts | Last post March 16, 2017
    • Thanks for this tool Trevor, it's been extremely helpful in developing our OSD task sequences.  The one enhancement that I feel would be useful is to make the unknown computer names unique somehow.  I know you're limited to what's in the database ... are the minint name there?  If not maybe just append the last few digits of the client GUID when the name equals unknown?  Anything to differentiate them in the machine drop down.
    • Hi Bryan, thanks for the feedback.  Are you using MDT integration?  Because integrating with MDT allows the application to link the task sequence data in the ConfigMgr database with MDT via the GUID, and MDT will at least use the unique "MININT" name, then later the actual computer name, depending on where in the task sequence you set that.  If you don't use MDT integration, then you are right, the computer name does not appear in the ConfigMgr database until nearer the end of the deployment, or after it, for bare-metal builds so it only appears as "UNKNOWN" in the application during deployment.
    • I have MDT integrated into SCCM to get the additional TS steps but I'm not running MDT task sequences.  In this case is there a possibility of adding something to the UNKNOWN machine names to differentiate them?
    • Yes I'm sure that can be done.  I will make a note for a future release!
    • Hi Trevor,
      As per Bryan's request, it would be great if you could add something to differentiate unknown computers. It could be a default gateway, a IP address or anything...
      Thanks in advance.
    • Hi, I hear you. I'll try to get this done soon.
  • Wrong Error Status
    2 Posts | Last post February 08, 2017
    • It's an awesome tool, Trevor. thanks!
      But you don't get the correct error codes specified on the "success codes:" field of a task sequence step. what I'm meaning is, I get false positive errors like this:
      "The task sequence execution engine successfully completed an action"	ErrorCode 3
      this step is then listed as an error, but it's successfully, because I set the Success codes to "0 1 3 3010" as it is necessary from the command I'm running. Of course, I can change the command or the script, but this is npot what I want to do. 
      So as I understand, the tool checks only for errorcode 0 and 3010, can you please add the correct success codes from the TS steps directly then it will be perfect, as it is nearly today ;-)
    • Hey Stefan, thanks for the feedback. If you are using non-standard exit codes to indicate success obviously this will display incorrectly in the tool. I will note for a future version to include an option to specify custom exit codes to be interpreted as success.
  • MDT Portion no longer working with 1610?
    3 Posts | Last post February 08, 2017
    • First off this tool is awesome! Wish I had installed it earlier. I am getting all the steps for the computers except the MDT portion is not being filled out. 
      I know the URL is correct as I can see the xml data and it looks good. Could there have been a change in CB 1610 or earlier that cause this not to work anymore? 
      Thanks again!
    • The MDT portion is getting data from the MDT monitoring webservice like this:
      $Data = Invoke-RestMethod -Uri $MDTURL
      Check that works for you. It also uses Invoke-Command to get the UTC date from the MDT server itself, so you need to have PSremoting enabled and permission to run Invoke-Command against that server.
    • Wish I could still use this. Sourcefire just noticed its W32.8D9216DCA1-100.SBX.VIOC and on every launch it tries to reinstall and then fails. Gonna be a hard sell to the Security team to let this by.
      Anyway you can fix this?
  • Flagged as Malware
    1 Posts | Last post February 01, 2017
    • I tried to download this msi. Symantec EndPoint Protection is flagging this as WS.Malware1
  • This program appears to have a trogen in it.
    3 Posts | Last post January 02, 2017
    • I scanned the installer and the extracted .EXE file and found a trogen.  I would caution anyone installing this.  To the author, Do you have a trogen on your system that is inserting code or did you reuse some code that may have added this?  I love the idea of this program but I can't use it if there is a trogen.  Fix it as soon as you are able.
      Virustotal Results
      Avira (no cloud)	TR/Dropper.Gen2	20161114
      Baidu	Win32.Trojan.WisdomEyes.16070401.9500.9926	20161111
      CrowdStrike Falcon (ML)	malicious_confidence_85% (D)	20161024
      Invincea	backdoor.msil.bladabindi.b	20161018
      Qihoo-360	HEUR/QVM03.0.0000.Malware.Gen	20161114
    • I'm seeing this issue too, with McAfee Endpoint Security. It would be nice to see this fixed as this tool is really great!
      Action taken		Delete
      Threat category		Malware detected
      Threat detected on creation	No
      Threat name		Artemis!7B832EB88994
      Threat severity		Critical
      Threat timestamp	2/1/2017 10.47
      Threat type		Trojan
      Source URL Task Sequence Monitor.msi
      Source URL rating code	Green
      Source URL web category	Technical/Business Forums
    • Hi guys, thanks for this information. I'm pretty sure that's a false positive. According to, only 7 out of 55 virus engines currently report a suspected virus, and the exe file is the suspect. 
      They report it as a suspected 'trojan dropper' which is probably because the exe file extracts and then runs a PowerShell script. I have scanned all the files with my own AV - Kaspersky - and it reports clean on everything. I have been using this tool myself from the same installer file since its release with no virus issue on my system, as I'm sure is the case for many others.
      For McAfee, you could report it as a false positive using their standard procedure:
  • No task sequences appear.
    4 Posts | Last post September 16, 2016
    • Hi Trevor,
      This tool sounds awesome, but I can't get it to show any Task Sequences.
      I entered our SQL server and DB in the settings, and I get "Connected to SQL Server database.  Select a Task Sequence." in the action output window, but there are no Task Sequences in the drop down box at all.
      Powershell 4
      .NET 4.5
      User account has db_datareader rights on the SCCM DB
      Any idea why it's not working?
    • Hi Stuart, that's interesting.  I assume you have some task sequences that you have deployed?
    • Yep. Three TS deployed to several collections, soon several more.
      I do not have MDT installed if that matters.
    • Do you get results if you run the following SQL query against your ConfigMgr database from the same machine? 
      SELECT DISTINCT summ.SoftwareName AS 'Task Sequence'
              FROM vDeploymentSummary summ
              WHERE (summ.FeatureType=7)
              ORDER BY summ.SoftwareName
      You can find a script for running a SQL query with Powershell on my blog:
  • EDT Break MDT
    2 Posts | Last post July 18, 2016
    • Hi,
      When I set Display Date/Time to "Eastern Daylight Time" MDT Monitoring break with Error:"could no connect to MDT web service". When I set it back to "UTC" MDT Monitoring works fine. I'm using 1.4. Any ideas?
    • Mmmm it's possible you are not getting the date from the MDT server.  Powershell "Invoke-command" gets that info with the following command:
      Invoke-Command -ComputerName $MDTServer -ScriptBlock {
      Check that you have permission to run that command.
  • Where is the server/db info stored in the registry?
    2 Posts | Last post June 22, 2016
    • I'm trying to deploy this app to a few of our tool servers and would like to pre-populate the regkeys needed so it does not need to be run as admin initially.
    • On a 64-bit system, the registry keys are found here:
      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SMSAgent\ConfigMgr Task Sequence Monitor
      These are the keys themselves (all string values)
      DTFormat (Date-time format, use "UTC" as default or [System.TimeZone]::CurrentTimeZone from Powershell)
  • Status text is omitted (possible missing)
    3 Posts | Last post February 22, 2016
    • Hi again TrevorJones,
      It seems like some of the Action Output text is being omittet or somehow missing text.:
      It's not a big deal, but i'm guessing it's not intended.
      [This is first line in a Install Update step (see the ... 9 (it's like somthings missing))]
      ... 9-41db-9b21-734ea9558bdf:version=205'.
      [789] Added/updated setting 'ccm_civersioninfo:modelname=site_e41a98bf-4d39-4aec-a950-
      [.... TEXT OMITTET BY ME AS]
      ProcessID = 3348;
      ThreadID = 3352;
      uccessfully submitted event to the Status Agent. [In this line "s" is omittet]
      End TS policy evaluation
      Policy evaluation initiated
      [Install Application Step, same behavior first line 3 dots and some text missing]
      ... essID = 3288;
      ThreadID = 3672;
      uccessfully submitted event to the Status Agent. [After space "s" is missing]
      End TS policy evaluation
      [Another install application step]
      ... tedConfig for source CcmTaskSequence successfully
    • Hi, this is not an issue with the application but it is how ConfigMgr stores the data in the database.  As far as I've been able to tell, the action output is a snippet from the smsts.log relating to that action, but it does not contain every entry in the log.  Basically whatever is in the database will be displayed by the tool, even missing first letters!
    • allright, just seemed odd.. :)
21 - 30 of 35 Items