Integrating DaRT with MDT and enable DaRT Remote Control

Deployment

Integrating DaRT into MDT will allow you to remotely view running deployments. Pretty handy for remote deployments that you are having trouble with.

For this I presume you already have a fully functional MDT Deployment Workbench server/workstation and I also presume you already downloaded MDOP (Microsoft Desktop Optimization Pack). MDOP is a must for this to work because it has a tool that we need and is called DaRT (Diagnostic and Recovery Toolset). Unfortunately to be able to download MDOP you need a Microsoft Software Assurance subscription.

First install DaRT. From the Microsoft Desktop Optimization Pack, look in the DaRT folder for the latest version (in the screenshots using Dart 10 x64).

Install DaRT using the default or recommended options

 

 

 

Once installed, navigate to C:\Program Files\Microsoft DaRT\v8.1 and copy the Tools64.cab and Tools86.cab to the appropriate Tools folder in your Deployment Share.

Open your MDT Deployment Workbench, right-click your Deployment Share and choose Properties. In the Properties page, click the Windows PE tab, and then click the Features tab. Down at the bottom you should now see the Microsoft Diagnostics and Recovery Toolkit (DaRT) check box. Check this box, then do the same for the 64 bit platform. Change the platform from the Platform drop-down-box at the top.

  

Before you close this, you need to make sure monitoring is enabled for the Deployment Share, or you will get the bellow error message when viewing the Monitoring section:

No monitoring data is available because monitoring is not enabled for this deployment share

To verify this just hit the Monitoring tab on the MDT Deployment Share Properties window. Make sure the Enable Monitoring for this deployment share check box is checked. By enabling monitoring a new service, the Microsoft Deployment Toolkit Monitor Service is installed on the system which receive events from the computers being monitored.

Update the Deployment Share.

“When this is done, make sure you update all your boot images from your WDS server (for those of you that are using WDS to boot clients for deployment)”

If you boot a client with the new boot image, you should have DaRT at the Welcome screen and if you click Run DaRT tools, the tools window will open. The one that we are interested right now is the Remote Connection application. By launching this you can then remote into this session of WinPE from a computer with DaRT installed (by using the DaRT Remote Connection Viewer).

Once in the WinPE environment is up you should see the Remote Connection application (minimized) waiting for a connection.

To see this session remotely, open your MDT Deployment Workbench and click the Monitoring folder. All computers that are in a deployment process are listed here. They are kept in the list for three days, then they are automatically deleted so the MDT database will not get too big.

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Deployment
MDT – Joining a Computer to a Domain Using PowerShell

Using PowerShell scripts within a task sequence provides more flexibility than using the CustomSettings.ini file to join a computer to a domain. The parameters of the CustomSettings.ini file are common to any deployment you perform. That’s why creating a custom PowerShell script to join your domain will be customize to …

Deployment
Task Sequence Tasks Explained

This document explains the tasks that you will find in standard task sequence. Initialization > Gather local only – gathers deployment configuration settings from local sources that apply to the target computer [ZTIGather.wsf] Validation > Validate – verifies that the target computer meets the specified deployment requirement conditions. Such as …

Deployment
How MDT uses XML to install Applications

Have you ever thought about what actually happens when you import applications into your MDT environment? How does the task sequence know what application to install? How does it know what command-line arguments to specify during the application install process? Technically, as a user, all that is required of us …