1 Check DHCP scope has option 66 with the SCCM server name set as the value.
2 WDS service is installed and running.
3 Under site Systems select the SCCM server and make sure "ConfigMgr PXE service point" role is installed
3.1 For a lab environment. Enable "Allow this PXE... to repond to incoming PXE requests" and "Respond to PXE request on all network interfaces".
4 Create a Collection called "Bare Metal OSD deployment"
5 Click on "Computer Asscocation" > "Import computer Information" > Import single computer
5.1 Enter Computer name and MAC address to define system > Add to "Bare Metal OSD deployment" collection
6 Under the node OSD in SCCM click on "Task Sequence"> Select the TS you want to deploy to the collection > Right click and "Advertise", specify the "bare metal OSD deployments".
6.1 Set as mandatory assignemtn. Tick "Ignore maintenance windows when running program and "Allow system restart outside maintenance Window.
6.2 Select "access content directly from a DP ...."
Setup WDS, DHCP scope, PXE point service, Advertised Task Sequence, Imported system via MAC address and added to collection. SCCM is ready next step is to restart the computer defined for a network boot, typically F12.
The computer will advertise that it is looking for a PXE service, the DHCP server will point it to the SCCM server that will then pick up the computer and push a Win PE image following the TS options.
7 While SCCM WinPE is deploying the WIM file it is possible to press F8 to bring up a DOS window and exam the SMSTSLog directory.
\\Map network drive: enter credentials
x:\> net use z: \\sccm\c$\tempsmslog
\\Copy all logs files to z:\
x:\> copy z:\ *.log
Now on your SCCM server\c$\tempsmslog folder you will find a smsts.log file. Open with trace32 to troubleshoot.
7.1 Alternatively within SCCM select the Reporting Node and run the "Deployment status of all task sequence advertisements". This report details the last action, exit code and Action output.