replace done

This commit is contained in:
Greg Lindsay 2020-03-02 13:36:50 -08:00
parent eb43e22550
commit 0c5fe64fdd
5 changed files with 20 additions and 9 deletions

View File

@ -31,6 +31,8 @@ For the purposes of this article, we assume that MDT02 is prepared with the same
Computers used in this topic. Computers used in this topic.
>HV01 is also used in this topic to host the PC0006 virtual machine.
## Replicate deployment shares ## Replicate deployment shares
Replicating the content between MDT01 (New York) and MDT02 (Stockholm) can be done in a number of different ways. The most common content replication solutions with Microsoft Deployment Toolkit (MDT) use either the Linked Deployment Shares (LDS) feature or Distributed File System Replication (DFS-R). Some organizations have used a simple robocopy script for replication of the content. Replicating the content between MDT01 (New York) and MDT02 (Stockholm) can be done in a number of different ways. The most common content replication solutions with Microsoft Deployment Toolkit (MDT) use either the Linked Deployment Shares (LDS) feature or Distributed File System Replication (DFS-R). Some organizations have used a simple robocopy script for replication of the content.
@ -235,9 +237,9 @@ Like you did in the previous topic for MDT01, you need to add the MDT Production
## Deploy a 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, using the MDTProduction deployment share replica on MDT02. You can test this deployment with the following procedure. Now you should have a solution ready for deploying the Windows 10 client to the remote site: Stockholm, using the MDTProduction deployment share replica on MDT02. You can test this deployment with the following optional procedure.
>To use the remote site server (MDT02) the VM must be assigned a default gateway that matches the one you entered in the Boostrap.ini file. >For demonstration purposes, the following procedure uses a virtual machine (PC0006) hosted by the Hyper-V server HV01. To use the remote site server (MDT02) the VM must be assigned a default gateway that matches the one you 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

View File

@ -35,6 +35,8 @@ For more details on the setup for this topic, please see [Prepare for deployment
The computers used in this topic. The computers used in this topic.
>HV01 is also used in this topic to host the PC0007 virtual machine for demonstration purposes, however typically PC0007 is a physical computer.
## Prepare for the computer replace ## Prepare for the computer replace
To prepare for the computer replace, you need to create a folder in which to store the backup and a backup only task sequence to run on the old computer. To prepare for the computer replace, you need to create a folder in which to store the backup and a backup only task sequence to run on the old computer.
@ -104,13 +106,17 @@ On **PC0002**:
The new task sequence running the Capture User State action on PC0002. The new task sequence running the Capture User State action on PC0002.
4. On MDT01, verify that you have an USMT.MIG compressed backup file in the **E:\\MigData\\PC0002\\USMT** folder. 4. On **MDT01**, verify that you have an USMT.MIG compressed backup file in the **D:\\MigData\\PC0002\\USMT** folder.
![The USMT backup](../images/mdt-03-fig04.png "The USMT backup") ![The USMT backup](../images/mdt-03-fig04.png "The USMT backup")
The USMT backup of PC0002. The USMT backup of PC0002.
### Deploy the PC0007 virtual machine ### Deploy the replacement computer
To demonstrate deployment of the replacement computer, HV01 is used to host a virtual machine: PC0007.
On **HV01**:
1. Create a virtual machine with the following settings: 1. Create a virtual machine with the following settings:
@ -119,8 +125,9 @@ On **PC0002**:
* Generation: 2 * Generation: 2
* Memory: 2048 MB * Memory: 2048 MB
* Hard disk: 60 GB (dynamic disk) * Hard disk: 60 GB (dynamic disk)
* Install an operating system from a network-based installation server
2. Start the PC0007 virtual machine, and press **Enter** to start the Pre-Boot Execution Environment (PXE) boot. The VM will now load the Windows PE boot image from the WDS server. 2. Start the PC0007 virtual machine, and press **Enter** to start the Pre-Boot Execution Environment (PXE) boot. The VM will now load the Windows PE boot image from MDT01 (or MDT02 if at a remote site).
![The initial PXE boot process](../images/mdt-03-fig05.png "The initial PXE boot process") ![The initial PXE boot process](../images/mdt-03-fig05.png "The initial PXE boot process")
@ -128,16 +135,18 @@ On **PC0002**:
3. After Windows Preinstallation Environment (Windows PE) has booted, complete the Windows Deployment Wizard using the following settings: 3. After Windows Preinstallation Environment (Windows PE) has booted, complete the Windows Deployment Wizard using the following settings:
* Password: P@ssw0rd
* Select a task sequence to execute on this computer: * Select a task sequence to execute on this computer:
* Windows 10 Enterprise x64 RTM Custom Image * Windows 10 Enterprise x64 RTM Custom Image
* Computer Name: PC0007 * Computer Name: PC0007
* Applications: Select the Install - Adobe Reader XI - x86 application. * Move Data and Settings: Do not move user data and settings.
* User Data (Restore) > Specify a location: \\\\MDT01\\MigData$\\PC0002
* Applications: Adobe > Install - Adobe Reader
4. The setup now starts and does the following: 4. Setup now starts and does the following:
* Partitions and formats the disk.
* Installs the Windows 10 Enterprise operating system. * Installs the Windows 10 Enterprise operating system.
* Installs the added application. * Installs the application.
* Updates the operating system via your local Windows Server Update Services (WSUS) server. * Updates the operating system via your local Windows Server Update Services (WSUS) server.
* Restores the USMT backup from PC0002. * Restores the USMT backup from PC0002.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 252 KiB

After

Width:  |  Height:  |  Size: 360 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 45 KiB

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 2.9 KiB