much more added here

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

@@ -64,6 +64,10 @@ On **MDT01**:
 
    The Deployment Workbench with the MDT Build Lab deployment share.
 
+### Optional: Enable monitoring
+
+To monitor the task sequence as it happens, right-click the **MDT Build Lab** deployment share, click **Properties**, click the **Monitoring** tab, and select **Enable monitoring for this deployment share**.
+
 ### Configure permissions for the deployment share
 
 In order to read files in the deployment share and write the reference image back to it, you need to assign NTSF and SMB permissions to the MDT Build Account (MDT\_BA) for the **D:\\MDTBuildLab** folder
@@ -646,6 +650,13 @@ 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.
     7. Turns off the virtual machine.
 
+If you enabled monitoring, you can check the progress of these tasks.
+
+   ![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$).
+
 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.
 
 ## Related topics