deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 22:07:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
Greg Lindsay 2016-12-20 12:35:49 -08:00
parent a3a1d7493c
commit 48b379af45
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deploy/windows-10-poc-mdt.md
View File

@ -129,6 +129,7 @@ A reference image serves as the foundation for Windows 10 devices in your organi
- Summary: click **Next** - Summary: click **Next**
- Confirmation: click **Finish** - Confirmation: click **Finish**
12. Edit the task sequence to add the Microsoft NET Framework 3.5, which is required by many applications. To edit the task sequence, double-click **Windows 10 Enterprise x64 Default Image** that was created in the previous step. 12. Edit the task sequence to add the Microsoft NET Framework 3.5, which is required by many applications. To edit the task sequence, double-click **Windows 10 Enterprise x64 Default Image** that was created in the previous step.
13. Click the **Task Sequence** tab. Under **State Restore** click **Tatto** to highlight it, then click **Add** and choose **New Group**. 13. Click the **Task Sequence** tab. Under **State Restore** click **Tatto** to highlight it, then click **Add** and choose **New Group**.
@ -207,13 +208,13 @@ A reference image serves as the foundation for Windows 10 devices in your organi
26. Open a Windows PowerShell prompt on the Hyper-V host computer and type the following commands: 26. Open a Windows PowerShell prompt on the Hyper-V host computer and type the following commands:
<pre style="overflow: auto;"> ```
New-VM –Name REFW10X64-001 -SwitchName poc-internal -NewVHDPath "c:\VHD\REFW10X64-001.vhdx" -NewVHDSizeBytes 60GB New-VM –Name REFW10X64-001 -SwitchName poc-internal -NewVHDPath "c:\VHD\REFW10X64-001.vhdx" -NewVHDSizeBytes 60GB
Set-VMMemory -VMName REFW10X64-001 -DynamicMemoryEnabled $true -MinimumBytes 1024MB -MaximumBytes 1024MB -Buffer 20 Set-VMMemory -VMName REFW10X64-001 -DynamicMemoryEnabled $true -MinimumBytes 1024MB -MaximumBytes 1024MB -Buffer 20
Set-VMDvdDrive -VMName REFW10X64-001 -Path c:\VHD\LiteTouchPE_x86.iso Set-VMDvdDrive -VMName REFW10X64-001 -Path c:\VHD\LiteTouchPE_x86.iso
Start-VM REFW10X64-001 Start-VM REFW10X64-001
vmconnect localhost REFW10X64-001 vmconnect localhost REFW10X64-001
</pre> ```
The VM will require a few minutes to prepare devices and boot from the LiteTouchPE_x86.iso file. The VM will require a few minutes to prepare devices and boot from the LiteTouchPE_x86.iso file.
@ -231,6 +232,7 @@ A reference image serves as the foundation for Windows 10 devices in your organi
- Capture the installation to a Windows Imaging (WIM) file. - Capture the installation to a Windows Imaging (WIM) file.
- Turn off the virtual machine. - 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**. 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**.
## Deploy a Windows 10 image using MDT ## Deploy a Windows 10 image using MDT
@ -243,6 +245,7 @@ This procedure will demonstrate how to deploy the reference image to the PoC env
- **Deployment share description**: MDT Production - **Deployment share description**: MDT Production
- **Options**: accept the default - **Options**: accept the default
2. Click **Next**, verify the new deployment share was added successfully, then click **Finish**. 2. Click **Next**, verify the new deployment share was added successfully, then click **Finish**.
3. In the Deployment Workbench console, expand the MDT Production deployment share, right-click **Operating Systems**, and then click **New Folder**. Name the new folder **Windows 10** and complete the wizard using default values. 3. In the Deployment Workbench console, expand the MDT Production deployment share, right-click **Operating Systems**, and then click **New Folder**. Name the new folder **Windows 10** and complete the wizard using default values.
@ -263,6 +266,7 @@ This procedure will demonstrate how to deploy the reference image to the PoC env
![custom image](images/image.png) ![custom image](images/image.png)
### Create the deployment task sequence ### Create the deployment task sequence
1. Using the Deployment Workbench, right-click **Task Sequences** under the **MDT Production** node, click **New Folder** and create a folder with the name: **Windows 10**. 1. Using the Deployment Workbench, right-click **Task Sequences** under the **MDT Production** node, click **New Folder** and create a folder with the name: **Windows 10**.