Funny, this came up internally last week as well when one of our testers hit the exact same issue. We confirmed it's by design with unattended domain join, you can't specify a container, just an OU. If you want it to join the computers container, don't specify anything. We did file a UI bug so that we can better filter the list that's provided so that it's only OUs.
Aaron From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Johns, Damon (DoJ) Sent: Tuesday, March 25, 2014 1:25 PM To: 'mssms@lists.myitforum.com' Subject: RE: [mssms] machine fails to join domain I'm pretty sure you can't use a container in a domain join step with Config Mgr. Had a similar problem from memory years ago with 2007. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeremy Sihassen Sent: Wednesday, 26 March 2014 4:09 AM To: mssms@lists.myitforum.com Subject: Re: [mssms] machine fails to join domain What did you insert in your SCCM Task Sequence for the Domain OU? If you want to build computers and that they enter the Default "Computers" container then this box should be empty and you shouldn't select any OU. 2014-03-25 15:21 GMT+01:00 Stephen Owen <sre...@gmail.com<mailto:sre...@gmail.com>>: Looks like this is the root cause. Try using an OU instead. On Tue, Mar 25, 2014 at 9:24 AM, Hun boy <hun....@outlook.com<mailto:hun....@outlook.com>> wrote: The default one is CN Not the OU Sent from iPhone....sorry for typos On 25-Mar-2014, at 6:53 pm, "Stephen Owen" <sre...@gmail.com<mailto:sre...@gmail.com>> wrote: Shouldn't that be "OU=Computers,DC=Comany,DC=Com"? You're using CN, which I"m not sure is suported. On Tue, Mar 25, 2014 at 9:19 AM, Stephen Owen <sre...@gmail.com<mailto:sre...@gmail.com>> wrote: 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 <mcdonald...@hotmail.com<mailto:mcdonald...@hotmail.com>> 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: dratl...@humana.com<mailto:dratl...@humana.com> To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>; mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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 [mcdonald...@hotmail.com<mailto:mcdonald...@hotmail.com>] Sent: Monday, March 24, 2014 05:06 PM Eastern Standard Time To: mdt...@lists.myitforum.com<mailto:mdt...@lists.myitforum.com>; mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> 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. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
