Unable to add computer to domain when account pre-created

[ITGURU]

I've inherited a network and carrying out a migration due to all systems being out of date

when adding a new computer via the 'network ID' wizard, I can successfully complete the wizard and the new computer account will be created in the computers container.

However if i pre-create the computer account, the wizard comes up saying an account is found, do i want to use it.

If i i say yes, it then fails with the following.

 

can anyone help please?

thanks

 

The domain name "domainname" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "domainname":The error was: "DNS name does not exist."(error code 0x0000232B RCODE_NAME_ERROR)The query was for the SRV record for _ldap._tcp.dc._msdcs.domainnameCommon causes of this error include the following:- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:ip of dc 1ip of dc 2- One or more of the following zones do not include delegation to its child zone:domainname. (the root zone)

[HobGoblin]

Do you have DHCP/DNS features enabled on your router?

[ITGURU]

Do you have DHCP/DNS features enabled on your router?

 

Not sure, its a bearer circuit provider who provided the cisco router which I have no access to. However on my original site we don't have this issue and that also has a cisco router provided by the line provider.

 

I've also assigned static IP and DNS servers to the client but the same issue occurs so not related to DHCP

[MatthewL]

What account are you trying to join the computer to the domain with?

[ITGURU]

What account are you trying to join the computer to the domain with?

 

I tried both the main domain administrator account as well as another account which I chose when I pre-created the account as having permission to join the computer to the domain.

 

if I don't pre-create the account either of the same 2 users will add the computer to the domain without any issues

[Fazza]

Never been able to make use of a pre-created computer account. I tried again the other day as I had a batch of laptops that I had already labelled up with their 'Staff-Lap' number so pre-created the accounts in AD Users and Computers so no one else used them by mistake but I have to delete them before putting one of the laptops on to the domain as it just wont use the ones I have manually created.

[ITGURU]

that's odd as at my primary location that I've been at for the last 15 year's I've always been able to pre create accounts and use them.. only since taking on the second school they don't seem to like it. may build a new domain at some point see if that resolves it.

[Duke5A]

Try staging them in Power Shell.

 

Something I found on the net a long time ago and have been using.

 

   # V3.0
   # Changes:
   #    No longer relies on Quest AD Snap in
   #    No longer uses the kludgey Test-XADObject to validate the existence of computers in AD
    
   import-module activedirectory
    
   import-csv "c:\namescsv" | foreach-object{ #imports CSV containing Name and MAC headings
    
       $name = $_.Name
       $MAC = $_.Mac  
      
       $CheckExists = get-adobject -Filter {(ObjectClass -eq "computer") -and (Name -eq $name)}  #Will be $NULL if this is a new computer
      
          
       if ($CheckExists -eq $NULL){
           [guid]$nbGUID = "00000000-0000-0000-0000-$MAC"  #casts 0s + MAC into a GUID, which is required for the netbootGUID property
           new-adcomputer -Name $name -SamAccountName $name -OtherAttributes @{'netbootGUID'=$nbGUID}        
           write-host $name " - " $nbGUID
         }
         else {
           write-host "$name already exists."
           }
          
   }

[ITGURU]

After doing some test VMs it turns out that it's a bug in Windows 10 build 1803.. You need the September cumulative update on to resolve the issue as it's stated in the changes as an issue. Determined this when i tried to add an 1803 to my other network which replicated the issue, and had always been ok on the other site as i deployed build 1709.