SCCM oddities / domain joining randomness

Caporegime
Joined
26 Aug 2003
Posts
37,508
Location
Leafy Cheshire
Here's a bit of an odd one that I can't fathom (mainly due to SCCM not showing any errors in the logs).

I've got a few task sequences that either install Win7 or Win8 Ent, and are supposed to join the domain and install software based on the task sequence shown.

If I run this on a VM, either from my machine (VMware workstation 9), or hosted on our hypervisors (Hyper-V Server 2012), the task sequences run absolutely fine, the machines install the OS, join the domain, install CCMCLIENT and proceed to install the software packages defined in the task sequence.

If I run this on a physical machine, the OS installs, and thats it. No errors shown, but no domain join (and therefore no subsequent software installation).

I've checked and double checked the obvious things like the task sequences are correct and that they are published the same to both unknown computers and known ones, but so far, I'm unable to find the cause.
 
In addition to the above, does it reboot the PC? Does a computer account get created for the machine?
 
I've watched this (by keeping the F8 cmd window open for the duration). The machine is always connected to the network (and always has an IP), all drivers seem to install fine (nothing outstanding in devmgr once the machine has finished the task sequence), if the machine is Unknown to SCCM/AD then no, no account gets created. If the machine is known, obviously the container still exists in AD.

EDIT: The task sequence does restart the machine, twice, during the process.
 
smsts.log shows that it completed "apply network settings" successfully, the unattend.xml file in %windir%\panther\unattend\ shows the correct script, but yet the workstation itself is still in a workgroup (WORKGROUP).

I'm really confused how the same task sequence is working fine on VMs. :confused:
 
Please can you check the setupact.log in %windir%

Absolutely nothing of note at all. I can post up a whole log of you like, but there is nothing in there that even looks remotely suspect :(

When the machine finishes installing and ends up in workgroup, is it all fine, i.e. NIC drivers installed etc, but just not finished the TS?

Yep, it's all fine other than the fact that the machine has not joined the domain nor run the application installers that happen after domain join.

Does the work station get assigned DNS addresses?

You mean DHCP? They can't register in DNS as they aren't joining the domain.
 
How exactly are you trying to join the PC to the domain? Are you using the Apply Network Settings step? You mention a script, but if there is a problem with this it won't necessarily report it in any of the SCCM logs. You might need to write some error handling or log file creation in the script itself.

If you haven't already, you should build in some steps that copy all the logs to a share if there is an error. Like this
 
Back
Top Bottom