From 57583442a931b101dac22398d8dfe9f9414f80c4 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 20 Dec 2016 16:25:18 -0800 Subject: [PATCH] trying --- windows/deploy/windows-10-poc-mdt.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deploy/windows-10-poc-mdt.md b/windows/deploy/windows-10-poc-mdt.md index f17dc17b46..abe4fb20bc 100644 --- a/windows/deploy/windows-10-poc-mdt.md +++ b/windows/deploy/windows-10-poc-mdt.md @@ -235,6 +235,7 @@ A reference image serves as the foundation for Windows 10 devices in your organi - Capture the installation to a Windows Imaging (WIM) file. - Turn off the virtual machine. + This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. The image is located in the C:\MDTBuildLab\Captures folder on your deployment server (SRV1). The file name is **REFW10X64-001.wim**. @@ -424,8 +425,10 @@ This procedure will demonstrate how to deploy the reference image to the PoC env 7. On SRV1, in the Deployment Workbench console, click on **Monitoring** and view the status of installation. Right-click **Monitoring** and click **Refresh** if no data is displayed. 8. OS installation requires about 10 minutes. When the installation is complete, the system will reboot automatically, configure devices, and install updates, requiring another 10-20 minutes. When the new client computer is finished updating, click **Finish**. You will be automatically signed in to the local computer as administrator. + ![finish](images/deploy-finish.png) + This completes the demonstration of how to deploy a reference image to the network. To conserve resources, turn off the PC2 VM before starting the next section. ## Refresh a computer with Windows 10