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

troubleshooting section added

Browse Source
This commit is contained in:
Greg Lindsay
2020-01-27 16:14:58 -08:00
parent 474ba7acc0
commit 07929c2005
2 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image.md
View File

@ -650,12 +650,15 @@ The steps below outline the process used to boot a virtual machine using an ISO
6. Captures the installation to a Windows Imaging (WIM) file. 6. Captures the installation to a Windows Imaging (WIM) file.
7. Turns off the virtual machine. 7. Turns off the virtual machine.
If you enabled monitoring, you can check the progress of these tasks. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep, located in the D:\\MDTBuildLab\\Captures folder on your deployment server. The file name is REFW10X64-001.wim.
## Troubleshooting
If you enabled monitoring, you can check the progress of the task sequence.
![monitoring](../images/mdt-monitoring.png) ![monitoring](../images/mdt-monitoring.png)
>[!TIP] If there are problems with your task sequence, you can troubleshoot in Windows PE by pressing F8 to open a command prompt. There are several [MDT log files](https://docs.microsoft.com/configmgr/mdt/troubleshooting-reference#mdt-logs) created that can be helpful determining the origin of an error, such as BDD.log. You can copy these logs from the client to your MDT server for viewing with CMTrace (ex: copy *.log \\\\mdt01\\logs$).
>If there are problems with your task sequence, you can troubleshoot in Windows PE by pressing F8 to open a command prompt. There are several [MDT log files](https://docs.microsoft.com/configmgr/mdt/troubleshooting-reference#mdt-logs) created that can be helpful determining the origin of an error, such as BDD.log. You can copy these logs from the client to your MDT server for viewing with CMTrace (ex: copy *.log \\\\mdt01\\logs$).
After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep, located in the D:\\MDTBuildLab\\Captures folder on your deployment server. The file name is REFW10X64-001.wim. After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep, located in the D:\\MDTBuildLab\\Captures folder on your deployment server. The file name is REFW10X64-001.wim.

4
windows/deployment/deploy-windows-mdt/prepare-for-windows-deployment-with-mdt.md
View File

@ -156,7 +156,9 @@ This will create an OU structure as shown below.
To use the Active Directory Users and Computers console (instead of PowerShell): To use the Active Directory Users and Computers console (instead of PowerShell):
1. On DC01, using Active Directory User and Computers, in the contoso.com domain level, create a top-level OU named **Contoso**. On **DC01**:
1. Using the Active Directory Users and Computers console (dsa.msc), in the contoso.com domain level, create a top-level OU named **Contoso**.
2. In the **Contoso** OU, create the following OUs: 2. In the **Contoso** OU, create the following OUs:
1. Accounts 1. Accounts
2. Computers 2. Computers