I've not had to pre-create objects in AD when I specify a "Domain OU" on the "Apply Network Settings" step. As I understand it if no OU is specified it tries to place the computer object in the default Computers OU in AD which in my case no one has rights to. So I either have to pre-create AD computer objects or specify the target OU.
In my TS I have taken to building bare metal machines and placing them in a default build OU and moving them manually when finished. And using the same TS if the object already exists it is joined to the existing object during the build. Isaac From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Monday, March 24, 2014 5:05 PM To: [email protected]; [email protected] Subject: [MDT-OSD] machine fails to join domain I am attempting to join a bare metal machine to the domain using an SCCM 2012 R2 TS. The machine fails to join to the domain. The NIC driver is injecting properly as part of the installation process. The SMSTS.log doesn't tell me much other than the fact that the Apply Network Settings step executed. In our previous SCCM 2007 environment we always had to create the computer object in the domain before imaging. That was the only way we could make t join during OS deployment process. Is this mandatory? I have a service account setup to join PCs to the domain. I have validated the password and permissions. Am I missing something here? Seems nuts to have to put the computer in AD before machines will join to the domain as part of OSD. I appreciate any input. Thanks, Brian
