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

expand guidance

Browse Source
This commit is contained in:
Greg Lindsay
2020-02-26 15:53:39 -08:00
parent e3edaa6e19
commit 5219d18bf6
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
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 ### Upgrade (refresh) a Windows 7 SP1 client
>[!IMPORTANT] >[!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 previous computer object will be orphaned. In the current guide, computer objects should be located in Contoso > Computers > Workstations. >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.
1. On PC0001, sign in as **contoso\\Administrator** and start the Lite Touch Deploy Wizard by opening **\\\\MDT01\\MDTProduction$\\Scripts\\Litetouch.vbs**. 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: 2. Complete the deployment guide using the following settings:
@ -108,6 +108,8 @@ Starting the computer refresh from an online Windows 7 SP1 client.
![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.
## Related topics ## Related topics