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

edits

Browse Source
This commit is contained in:
Greg Lindsay 2020-02-25 16:11:26 -08:00
parent bb0d2f2255
commit c08a29c306
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/deploy-windows-mdt/build-a-distributed-environment-for-windows-10-deployment.md
View File

@ -233,9 +233,9 @@ Like you did in the previous topic for MDT01, you need to add the MDT Production
1. On MDT02, using the WDS console, right-click **Boot Images** and select **Add Boot Image**. 1. On MDT02, using the WDS console, right-click **Boot Images** and select **Add Boot Image**.
2. Browse to the **D:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim** file and add the image with the default settings. 2. Browse to the **D:\\MDTProduction\\Boot\\LiteTouchPE\_x64.wim** file and add the image with the default settings.
## Deploy the Windows 10 client to the remote site ## Deploy a Windows 10 client to the remote site
Now you should have a solution ready for deploying the Windows 10 client to the remote site, Stockholm, connecting to the MDT Production deployment share replica on MDT02. Now you should have a solution ready for deploying the Windows 10 client to the remote site, Stockholm, connecting to the MDT Production deployment share replica on MDT02. Deployment to the remote site can be tested using the following procedure. Note: In order to use the remote site server (MDT02) the VM must be assigned a default gateway corresponding to that which was entered in the Boostrap.ini file.
1. Create a virtual machine with the following settings: 1. Create a virtual machine with the following settings:
1. Name: PC0006 1. Name: PC0006