If you encounter problems, view SCCM’s message and log files for help. Additional troubleshooting tips include the following:
- If you have a problem with PXE, open the collection and clear the last PXE advertisement, as Figure 5 shows. You can then retest the computer with the full advertisement.
- If you have a problem with WinPE, try enabling the command prompt in the boot images. Navigate to Site Database, Computer Management, Operating System Deployment, Boot Images, then right-click the boot image and select Properties. On the Windows PE tab, select the Enable command support option. After you update the boot images, be sure to refresh their distribution points.
- If WinPE fails to partition or format the disk, use the DiskPart utility (diskpart.exe) to partition and format the disk from the command line, then try deploying the OS again. This action will create the log file smsts.log, which will store failure information. I initially had problems accessing the SMSPXEIMAGES$ share, because the network access account lacked permission. When I tried to use the Net Use command on the \\sccm server\SMSPXEIMAGES$ share, the command failed.
Hands Off
Now that you have an environment capable of deploying an OS contained in a WIM file, you can build on it to perform more automated OS configuration, services and application deployment, patch deployment, and driver deployment. Once SCCM is fully configured, you have a complete zero-touch deployment solution.