It has been too long since I wrote anything but here comes a small update. Hopefully I get more time to blog all things I’ve been wanting to share soon.

I have just updated my MDT Monitor Tool to version 1.5 (Download), this version adds the “Start Time” column. So if you have many deployments ongoing or finnished you can now sort on start time.



New in v1.5:

  • Added Start Time as a value in the columns so you can sort on when a deployment was started
  • Removed the empty column to the left.


New in v1.4:

  • Fixed bug where Dart Remote Viewer didnt work
  • Option to show client local time instead of UTC, edit config.xml to enable/disable


New in v1.2:

  • Fixed Dart Remote Viewer not connection to full ip Issue: 1222


New in v1.1:

  • Added timers for autorefresh of webservice info
  • Added some better errorchecking and cleaned up the code a bit


For more info see my original post:


I can’t take all the credit for thinking up this tool, but I’ll take the credit for making it cool! At my previous job, one of the guys there wrote a script to do the following:

Run the silent install of an application -> Wait for it to complete -> Copy log files to a network share -> Revert VM to previous snapshot and test the next application

They could start this script and test a lot of apps overnight. I recently came across a problem where I wanted to test all the applications just created to make sure they installed correctly. We knew the silent install scripts worked outside of ConfigMgr, but the application objects were not tested. Instead of doing the work manually, I decided to write a new and improved version of the script to work with Hyper-V. Here’s the setup for the script:

1) Deploy all applications you want to test as Available to a Hyper-V VM
2) Run this script on the computer/server running Hyper-V
3) Put in the computer name (what you ping) and VM name (what you see in Hyper-V)
4) Select the applications you want to install (if you don’t see them, do machine policy updates)
5) Select if you want logs gathered and/or checkpoints made
6) Click start!

What does the script do? I made this nice flow chart to explain!


Each step is logged to the same directory of the script to a file called ApplicationInstalls.log. This log file is in CMTrace format, so make sure you open it with trace!


If you choose to save checkpoints and are testing a lot of apps, make sure you have space! I used this to test 40 apps earlier today and saved a check point after each install. It ate up about 100GB of space and I had only 8GB left when the script ended!

Things to add later: Option to test uninstall after installing.

If you want this script, you can download it here on Technet.

If you want to contribute any code to the script, check it out in my toolbox repo on GitHub. It’s called “Test Applications in HyperV.ps1″