We're running a build process on around 30 PCs at a time using SCCM 2007 SP2 R2 OSD initiated over PXE. In a given run we typically see one system that will hang during "Applying System Settings". When looking at the setupact.log it show the last command is:
DJOIN.EXE specialize
That then leads me to look at the setupact.log under the unattendedGC folder which again shows that DJOIN.EXE is the last command issued, but it never errors outs. I've seen posts pointing towards a debug setting in the unattend.xml but that only shows something if there is an error.
I then came across C:\Windows\Debug\Netsetup.log to which I see the following repeat over and over every 20 seconds at the end of the log:
NetpGetLsaPrimaryDomain: status: 0x0
Now some useful or useless data, not sure. The PC object does get created in the domain. Only difference I've seen between a successfully built system and one that fails is that the AD object's last modified date of a failed system is the same as the create date. Seems that when a system successfully gets past this step the modified date is newer by about 2 minutes. Issue is new to the process. We recently started imaging the Dell OptiPlex 9020 and that involved using an updated boot WIM.