Please do...been troubleshooting last few days with no resolution.

Any other ideas?

From: [email protected]
To: [email protected]
Subject: RE: [MDT-OSD] JoinDomain Issues with MDT 2012 U1
Date: Thu, 24 Oct 2013 17:30:36 +0000









I believe I ran into this same issue not that long ago. IIRC, it had to do with 
the timing during setup passes between the naming of the computer and the domain
 join action.  I don’t recall what the resolution was, but if I find it I’ll 
send it your way.
 
-Phil
 
_________________________________________________________________
Phil Schwan |
 Technical Specialist, Enterprise Windows Services
Project Leadership Associates
|
2000 Town Center, Suite 1900, Southfield, MI 48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net
Lead
 with Strategy. Leverage Technology. Deliver Results.
 
 
 
 
 
 


From: [email protected] [mailto:[email protected]]
On Behalf Of Brian McDonald

Sent: Thursday, October 24, 2013 1:17 PM

To: [email protected]

Subject: [MDT-OSD] JoinDomain Issues with MDT 2012 U1


 

I am having issues joining machines to the domain using MDT 2012 Update 1.



My CustomSettings.ini is as follows:



JoinDomain=MyDomain

DomainAdmin=My.Account

DomainAdminDomain=MyDomain

DomainAdminPassword=MyPassword



Here is the error in the ZTIDomainJoin.log

JoinDomain Failure: The account *may* already exists in a different OU. 
Retrying without the specified OU.



And the error in the NetSetup.log

NetDsGetDCName: failed to find a DC having account "account name": 0x525, last 
error is 0x0

NetspCreateComputerObjectInDS: NetspGetComputerObjectDN failed: 0x534

NetspProvisionComputerAccount: LDAP creation failed



I'm not sure if this is an MDT issue or account at this point?



Thanks,



Brian







PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are 
privileged and confidential and intended solely for the use of the individual 
or entity to whom they are addressed. If you have received this email in error 
please notify the sender.
 If you are not the named addressee you should not disseminate, distribute or 
copy this e-mail or any of its attachments.
 

                                          

<<inline: image001.jpg>>

<<inline: image002.jpg>>

<<inline: image003.jpg>>

<<inline: image004.jpg>>

Reply via email to