deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 10:53:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

edits

Browse Source
This commit is contained in:
Greg Lindsay
2020-02-26 16:10:03 -08:00
parent 5219d18bf6
commit ea8a53197a
1 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
windows/deployment/deploy-windows-mdt/refresh-a-windows-7-computer-with-windows-10.md
View File

@ -81,7 +81,7 @@ It is also assumed that you have a domain member client computer named PC0001 in
### Upgrade (refresh) a Windows 7 SP1 client
>[!IMPORTANT]
>Domain join details [specified in the deployment share rules](deploy-a-windows-10-image-using-mdt.md#configure-the-rules) will be used to rejoin the computer to the domain during the refresh process. If the Windows 7 client is domain-jonied in a different OU than the one specified by MachineObjectOU, the domain join process will initially fail and then retry without specifying an OU. If the domain account that is specified (ex: MDT_JD) has [limited permissions](deploy-a-windows-10-image-using-mdt.md#step-1-configure-active-directory-permissions) then the domain join will ultimately fail and the client computer object will be orphaned. In the current guide, computer objects should be located in Contoso > Computers > Workstations. Use the Active Directory Users and Computers console to move computer objects if needed. To diagnose MDT domain join errors, see C:\Windows\Temp\DeploymentLogs\ZTIDomainJoin.log on the client computer.
>Domain join details [specified in the deployment share rules](deploy-a-windows-10-image-using-mdt.md#configure-the-rules) will be used to rejoin the computer to the domain during the refresh process. If the Windows 7 client is domain-jonied in a different OU than the one specified by MachineObjectOU, the domain join process will initially fail and then retry without specifying an OU. If the domain account that is specified (ex: MDT_JD) has [permissions limited to a specific OU](deploy-a-windows-10-image-using-mdt.md#step-1-configure-active-directory-permissions) then the domain join will ultimately fail, the refresh process will proceed, and the client computer object will be orphaned. In the current guide, computer objects should be located in Contoso > Computers > Workstations. Use the Active Directory Users and Computers console to move computer objects if needed. To diagnose MDT domain join errors, see **ZTIDomainJoin.log** in the C:\Windows\Temp\DeploymentLogs directory on the client computer.
1. On PC0001, sign in as **contoso\\Administrator** and start the Lite Touch Deploy Wizard by opening **\\\\MDT01\\MDTProduction$\\Scripts\\Litetouch.vbs**.
2. Complete the deployment guide using the following settings:
@ -92,6 +92,9 @@ It is also assumed that you have a domain member client computer named PC0001 in
>[!NOTE]
>Skip this optional full WIM backup. The USMT backup will still run.
* Select one or more applications to install: Install - Adobe Reader
![Computer refresh](../images/fig2-taskseq.png "Start the computer refresh")
4. Setup starts and does the following:
* Backs up user settings and data using USMT.
@ -100,13 +103,9 @@ It is also assumed that you have a domain member client computer named PC0001 in
* Updates the operating system using your local Windows Server Update Services (WSUS) server.
* Restores user settings and data using USMT.
![Computer refresh](../images/fig2-taskseq.png "Start the computer refresh")
5. You can monitor progress of the deployment using the deployment workbench on MDT01. See the following example:
Starting the computer refresh from an online Windows 7 SP1 client.
5. If desired, monitor progress of the deployment using the deployment workbench on MDT01. See the following example:
![monitor deployment](../images/monitor-pc0001.png)
![monitor deployment](../images/monitor-pc0001.png)
6. After the refresh process completes, sign in to the Windows 10 computer and verify that user accounts and settings were migrated.