Microsoft Deployment Toolkit
Documentation Library Step 6-4: Start the Target Computer with the Task Sequence Bootable Media |
Start the target computer (WDG-CLI-01) with the task sequence bootable media created earlier in the process. This medium starts Windows PE on the reference computer and initiates the MDT process. At the end of the MDT process, Windows 7 is deployed on the target computer.
Note You can also initiate the MDT process by starting the target computer from Windows Deployment Services.
To start the target computer with the task sequence bootable media
1. Start WDG-CLI-01 with the task sequence bootable media created earlier in the process.
Windows PE starts, and then the Task Sequence Wizard starts.
2. Complete the Task Sequence Wizard using the information in Table 36. Accept the default values unless otherwise specified.
Table 36. Information for Completing the Task Sequence Wizard
On this wizard page |
Do this |
Welcome to the Task Sequence Wizard |
In Password, type P@ssw0rd, and then click Next. |
Select a Task Sequence |
In the list box, select Windows 7 Target Deployment, and then click Next. |
To monitor the reference computer deployment process using the Deployment Workbench
1. On WDG-MDT-01, click Start, and then point to All Programs. Point to Microsoft Deployment Toolkit, and then click Deployment Workbench.
2. In the Deployment Workbench console tree, go to Deployment Workbench/Deployment Shares/MDT Deployment Share (C:\DeploymentShare$)/Monitoring.
3. In the details pane, view the deployment process for WDG-CLI-01.
4. In the Actions pane, periodically click Refresh.
The status of the deployment process is updated in the details pane. Continue to monitor the deployment process until the process is complete.
5. In the details pane, click WDG-CLI-01.
6. In the Actions pane, click Properties.
The WDG-CLI-01 Properties dialog box is displayed.
7. In the WDG-CLI-01 Properties dialog box, on the Identity tab, view the monitoring information provided about the deployment process as described in Table 37.
Table 37. Monitoring Information About the Deployment Process
Information |
Description |
ID |
Unique identifier for the computer being deployed. |
Computer Name |
The name of the computer being deployed. |
Deployment status |
The current status of the computer being deployed; the status can be one of the following: · Running. The task sequence is healthy and running. · Failed. The task sequence failed, and the deployment process was unsuccessful. · Completed. The task sequence has finished. · Unresponsive. The task sequence has not updated its status in the past four hours and is assumed to be nonresponsive. |
Step |
The current task sequence step being run. |
Progress |
The overall progress of the task sequence. The progress bar indicates how many task sequence steps have been run out of the total number of task sequence steps. |
Start |
The time the deployment process started. |
End |
The time the deployment process ended. |
Elapsed |
The length of time the deployment process has been running or took to run if the deployment process has finished. |
Errors |
The number of errors encountered during the deployment process. |
Warnings |
The number of warnings encountered during the deployment process. |
Remote Desktop |
This button allows you to establish a remote desktop connection with the computer being deployed using the Windows Remote Desktop feature. This method assumes that: · The target operating system is running and has remote desktop support enabled · mstsc.exe is in the path Note This button is always visible but may not be able to establish a remote desktop session if the monitored computer is running Windows PE, has not completed installation of the target operating system, or does not have the Remote Desktop feature enabled. |
VM Connection |
This button allows you to establish a remote desktop connection to a VM running in Hyper-V. This method assumes that: · The deployment is being performed to a VM running on Hyper-V · vmconnect.exe is located in the %ProgramFiles%\Hyper-V folder Note This button appears when ZTIGather.wsf detects that Hyper-V integration components are running on the monitored computer. Otherwise, this button will not be visible. |
DaRT Remote Control |
This button allows you to establish a remote control session using the remote viewer feature in the Diagnostics and Recovery Toolkit (DaRT). This method assumes that: · DaRT has been deployed to the target computer and is currently running · DartRemoteViewer.exe is located in the %ProgramFiles%\Microsoft DaRT 7\v7 folder Note This button appears when ZTIGather.wsf detects that DaRT is running on the monitored computer. Otherwise, this button will not be visible. |
Automatically refresh this information every 10 seconds |
Check box that controls whether the information in the dialog box is automatically refreshed. If the check box is: · Selected, the information is refreshed every 10 seconds · Cleared, the information is not automatically refreshed and must be manually refreshed using the Refresh Now button |
Refresh Now |
This button immediately refreshes the information displayed in the dialog box. |
8. In the WDG-REF-01 Properties dialog box, click OK.
9. Close the Deployment Workbench.
To monitor the reference computer deployment process using the Get-MDTMonitorData cmdlet
1. On WDG-MDT-01, click Start, point to Administrative Tools, and then click Windows PowerShell Modules.
The Windows PowerShell Modules command prompt opens.
2. Create a PowerShell drive that uses the MDT PowerShell provider by running the New-PSDrive cmdlet as shown in the following example:
New-PSDrive -Name DS001 -PSProvider mdtprovider -Root d:\DeploymentShare$
3. View the MDT monitoring process by running the Get-MDTMonitorData cmdlet as shown in the following example:
Get-MDTMonitorData -Path DS001:
This command returns the monitoring data collected by the MDT monitoring service running on the same computer that hosts the deployment share as shown in the following example output:
Name : WDG-REF-01
PercentComplete : 96
Settings :
Warnings : 0
Errors : 0
DeploymentStatus : 1
StartTime : 6/7/2012 6:45:39 PM
EndTime :
ID : 1
UniqueID : 94a0830e-f2bb-421c-b1e0-6f86f9eb9fa1
CurrentStep : 130
TotalSteps : 134
StepName : Gather
LastTime : 6/7/2012 8:46:32 PM
DartIP :
DartPort :
DartTicket :
VMHost : XYL-DC-02
VMName : WDG-REF-01
ComputerIdentities : {}
Name : WDG-CLI-01
PercentComplete : 26
Settings :
Warnings : 0
Errors : 0
DeploymentStatus : 1
StartTime : 6/7/2012 3:07:13 AM
EndTime :
ID : 2
UniqueID : 94a0830e-f2bb-421c-b1e0-6f86f9eb9fa1
CurrentStep : 49
TotalSteps : 134
StepName : Capture Network Settings using MDT
LastTime : 6/7/2012 3:08:32 AM
DartIP :
DartPort :
DartTicket :
VMHost :
VMName :
ComputerIdentities : {}
4. Close the Windows PowerShell console.
If any problems occur during the deployment, consult the MDT document Troubleshooting Reference. When successfully completed, the target computer is running a Windows 7 operating system configured like the reference computer.