Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
mdt 2012 - W8 - join domain issues

Answered mdt 2012 - W8 - join domain issues

  • Tuesday, January 29, 2013 6:31 PM
     
     
    Sign In to Vote
    0

    hi

    Am seeing the following when running a deployment of W8x64.

    I haven't really set up much of the cs.ini file.. just standard settings..

    I can't find any info in c:\windows\debug\netlogon.log .. that file hasn't been updated since 2011 :-|

    I followed this:

    http://www.sysadminlab.net/windows/deploy-windows-8-with-mdt

    to fix a few errors.. but other than that.... nothing.. the domain - join account is the same as I use for W7, which I've never had problems with.. The computer isn't joined to the domain already either..

    Ideas?

    Kindest regards, Martin

     

All Replies

  • Tuesday, January 29, 2013 6:41 PM
     
     Proposed Answer
    Sign In to Vote
    0

    I believe C:\Windows\debug\NetSetup.log is actually the file you want to look at if you are having domain join issues.  Are you able to join it manually after MDT ends?

    Also, note the error about USMT 4.  For Windows 8, you'll need to update to USMT 5 which is found in the new ADK (Assessment and Deployment Kit: http://www.microsoft.com/en-us/download/details.aspx?id=30652).

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Proposed As Answer by tk.421 Tuesday, January 29, 2013 7:16 PM
    •  
     
  • Tuesday, January 29, 2013 9:44 PM
     
     
    Sign In to Vote
    0

    hi

    I'll look into the usmt 5.. thx..

    C:\Windows\debug\NetSetup.log was what I meant.. and it's empty... entries are from 2011..

    Kindest regards, Martin

     
  • Tuesday, January 29, 2013 9:48 PM
     
     Answered
    Sign In to Vote
    0
    Fix USMT and see if you still have the domain join issue.  It may have been a red herring.  If it persists after you swap to USMT 5, try doing it manually and then check the log.  If it's empty, I would believe that it never even ran the domain join command (and hit an error pre-execution).  Any sign of anything in bdd.log?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    • Marked As Answer by Martin Rask Wednesday, January 30, 2013 4:20 PM
    •  
     
  • Wednesday, January 30, 2013 4:20 PM
     
     Answered
    Sign In to Vote
    0

    fixed the usmt issue (i really just installed the newer adk tools)

    I still had the problem...

    After feeling like a complete twat I went to my ad, checked the OU variables and copy/pasted the ldap path to the ou..

    I then noticed...

    Old:

    MachineObjectOU=Windows 7,OU=Arbejdsstationer,OU=Computere,DC=hef,DC=dk

    New:

    MachineObjectOU=OU=Windows 7,OU=Arbejdsstationer,OU=Computere,DC=hef,DC=dk

    the OU= was missing in the machineObjectOU

    *sigh* I'm an idiot.!

    Kindest regards, Martin

    • Marked As Answer by Martin Rask Wednesday, January 30, 2013 4:20 PM
    •  
     
  • Wednesday, January 30, 2013 4:21 PM
     
     
    Sign In to Vote
    0

    a side note..

    on my mdt server the: C:\Windows\debug\NetSetup.log

    is still not updating at all.. last entry was in 2011..

    Kindest regards, Martin

     
  • Wednesday, January 30, 2013 4:37 PM
     
     
    Sign In to Vote
    0
    But it is joining the domain now after the MachineObjectOU was fixed?  If it still isn't and NetSetup.log isn't being updated, can you see what happens if you try to manually join it after imaging and see if it a) joins correctly and b) updates NetSetup.log?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek