none
MDT 2012 - unable to join domain

    Question

  • My customsettings.ini is working in all senses so i figured i would add computers to the AD and OU based on Type, i e Desktop models should be added to the OU=PC, DC=name, DC=local

    so here is the layout of my additions:

    [Settings]
    Priority=ByType,ByVMType,Default
    Properties=MyCustomProperty
    
    [Default]
    SkipBDDWelcome=YES
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipTaskSequense=NO
    SkipAdminPassword=YES
    AdminPassword=P@ssw0rd
    SkipComputerName=NO
    ComputerName=Datornamn_here
    SkipDomainMembership=YES 
    JoinDomain=name.local
    DomainAdmin=joindomain
    DomainAdminDomain=name.local
    DomainAdminPassword=JoinDomain
    MachineObjectOU=OU=Computers,DC=NAME,DC=local
    
    [ByType]
    SubSection=Laptop-%IsLaptop%
    SubSection=Desktop-%IsDesktop%
    
    [Laptop-True]
    MachineObjectOU=OU=Laptop,DC=NAME,DC=local
    
    [Desktop-True]
    MachineObjectOU=OU=PC,DC=NAME,DC=local

    Now i don't get any of my computers added to the AD and the ZTIDomainJoin.log tell me only this:

    JoinDomain_error_log

    Even in NetSetup.log i can find the corresponding error:

    NetSetup_error_log

    What is it i am not seeing here? Where is the error i need to correct?

    As soon as the TS is done i get the error from the computer saying it has tried to may times to join the domain, but i can at this point manually add the computer to the domain with no issues (other than that it ends up in the COMPUTER-OU)...

    I have  found similar posts here but no definitive answer to the question. I can and will provide more information about this if needed.

    Anyone?

    Friday, March 22, 2013 12:46 PM

Answers

  • so we have now migrated our older DHCP and DNS from physical 2003-servers to virtual 2008r2-servers and raised the funcitonal levels

    since this i have less issues with this and also think i will need to reopen this topic if we have any further issues

    this means that we have no solution to the issue in order to help others, nevertheless i set this to solved and close it down

    Wednesday, April 10, 2013 9:09 AM

All replies

  • It can't see your Domain Controller. Check your IP and DNS settings on that client.

    Also, try running this test and post back the results(less sensitive data):

    nltest /dsgetdc:mydomain.local
               DC: \\DC1.mydomain.local
          Address: \\10.0.0.55
         Dom Guid: 0000000-0000-0000-0000-00000000000
         Dom Name: mydomain.local
      Forest Name: mydomain.local
     Dc Site Name: HeadQuarters
    Our Site Name: HeadQuarters
            Flags: GC DS LDAP KDC WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE
    The command completed successfully


    Blog: http://scriptimus.wordpress.com

    Friday, March 22, 2013 1:42 PM
  • I hope this helps.

    This is from a machine that does not join the domain:
    DC: \\utb-dc3.Utb.local
          Address: \\172.16.12.103
         Dom GUID: 850af93d-db37-4357-a07d-b23c2a4a4de8
         Dom Name: Utb.local
      Forrest Name: Utb.local
     DC Site Name: Centralt
    Our Site Name: Centralt
            Flags: DS LDAP KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE
    The command completed successfully

    This is from a machine that does join the domain:
    DC: \\utb-dc.Utb.local
          Address: \\172.16.12.201
         Dom GUID: 850af93d-db37-4357-a07d-b23c2a4a4de8
         Dom Name: Utb.local
      Forest Name: Utb.local
     Dc Site Name: Centralt
    Our SIte Name: Centralt
            Flags: PDC GC DS LDAP KDC TIMESERV GTIMESERV WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE



    EDIT: we have added DC3 as GC now that we found that out...
    Monday, March 25, 2013 7:49 AM
  • Have you verified your IP and DNS settings?

    Blog: http://scriptimus.wordpress.com

    Wednesday, March 27, 2013 8:58 PM
  • i have and they differ at best...

    i have a desktop that usually is added to domain and a laptop that never is added to the domain
    according to logs from both they do have issues finding the correct DC (as i see it, we have 2 as you can see by the c'n'p above)

    they do get correct IP and everything, but the laptop seldom or never find the UTB-DC but generally only find UTB-DC3 and tries to use this information to add itself to the domain. i manually compared the logs and found this:

    netsetup_log_compare

    do you see anything that could help me out?
    the machines are connected through the same router, standing next to eachother.

    the laptop directly connects to the domain if done manually as soon as the error message from the TS shows, no restart or anything prior.

    none of us here see any reason for this to happen. i belive it to be some random issue in regards of DHCP/DNS somehow...

    any thoughts?

    Thursday, March 28, 2013 9:21 AM
  • so we have now migrated our older DHCP and DNS from physical 2003-servers to virtual 2008r2-servers and raised the funcitonal levels

    since this i have less issues with this and also think i will need to reopen this topic if we have any further issues

    this means that we have no solution to the issue in order to help others, nevertheless i set this to solved and close it down

    Wednesday, April 10, 2013 9:09 AM