Some environments will not allow you to domjoin and create a new object at the same time. Can you check with your AD team and see if thats the case?
Also, make sure you have the right OU specified. On Tue, Mar 25, 2014 at 9:14 AM, Brian McDonald <[email protected]>wrote: > The netsetup.log file shows the following: > > 03/24/2014 13:43:47:786 NetpCreateComputerObjectInDs: > NetpGetComputerObjectDn failed: 0x2 > 03/24/2014 13:43:47:786 NetpProvisionComputerAccount: LDAP creation > failed: 0x2 > > The thing that is interesting is that it doesn't like the OU I am > specifying. In fact, it doesn't think it's an OU. Does the joindomain > process not working with the default Computers OU in AD? > > 03/24/2014 17:09:56:364 NetpGetComputerObjectDn: Specified path > 'CN=Computers,DC=MyCOMPANY,DC=com' is not an OU > > Thanks, > Brian > ------------------------------ > From: [email protected] > To: [email protected]; [email protected]; > [email protected] > Subject: RE: [mssms] machine fails to join domain > Date: Mon, 24 Mar 2014 21:15:08 +0000 > > > Take a look at setupact.log and setuperr.log in the ccm folder. > > -Daniel Ratliff > > -----Original Message----- > *From: *Brian McDonald [[email protected]] > *Sent: *Monday, March 24, 2014 05:06 PM Eastern Standard Time > *To: *[email protected]; [email protected] > *Subject: *[mssms] 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 > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > >
