<div>
Are the TCP/IP properties on the members interfaces set to register this computer in DNS? &nbsp;Do you have any domains you are appending? &nbsp;Are you setting the &quot;connection specific&quot; dns registration?<br />
<br />
A screenshot of the DNS tab under IPV4 in TCP/IP properties would help
</div>


<div>
The NIC's are set to 'Register this connection's addresses in DNS', and yes there is also GPO which configures the primary connection suffix, and appends additional domains to suffix search list. This all works properly, just with ADMT it does not work fast enough...<br />
<br />
Once the computer account is migrated, it is a 50/50 chance the A record is registered on the target domain, until we do a second reboot manually. What I am looking to do here is force DNS registration on the target domain after computer is online, or script / automate a second reboot in conjunction with ADMT.<br />
<br />
Note; Please expect delayed response on this thread.
</div>


<div>
Thanks Manesh, I cannot change DNS on the DHCP scope because it would effect all clients, and we are migrating only groups at a time but thanks for the idea. <br />
I understand what is happening and why, but was hoping for a way to force a second reboot from the ADMT process; but this is not possible so we are scripting the reboots.
</div>


<div>
<div class="content wysiwyg-content">
We are migrating thousands of computers via ADMT to a new domain. We have an issue where ADMT migrates the computer accounts, performs the reboot, but the computers often do not register DNS on the new domain until we perform a second reboot. ADMT performs one reboot automatically, and I cannot find a way for ADMT to perform two reboots. <br />
<br />
I have also tried startup scripts to run ipconfig /registerdns for example, but this was not working either. The only way I am seeing successful migrations are with two reboots. <br />
<br />
By successful migrations, I mean ADMT is reporting a success. Even with the one reboot from ADMT, the computer accounts do migrate to the new domain successfully, however ADMT will not report a success until the comptuers register DNS. I need to rely on ADMT letting me know if the migrations are successful due to the amount of computers in play here. <br />
<br />
Any ideas on how to get ADMT to reboot the PCs twice, or how to force the computers to register DNS without a second reboot?
</div>
</div>


We are migrating thousands of computers via ADMT to a new domain. We have an issue where ADMT migrates the computer accounts, performs the reboot, but the computers often do not register DNS on the new domain until we perform a second reboot. ADMT performs one reboot automatically, and I cannot find a way for ADMT to perform two reboots. 

I have also tried startup scripts to run ipconfig /registerdns for example, but this was not working either. The only way I am seeing successful migrations are with two reboots. 

By successful migrations, I mean ADMT is reporting a success. Even with the one reboot from ADMT, the computer accounts do migrate to the new domain successfully, however ADMT will not report a success until the comptuers register DNS. I need to rely on ADMT letting me know if the migrations are successful due to the amount of computers in play here. 

Any ideas on how to get ADMT to reboot the PCs twice, or how to force the computers to register DNS without a second reboot?

ADMT DNS registration issues

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.