<div>
Go ahead and do that<br />
There is nothing wrong in that did not impact any<br />
U r simply changing Scavenging trigger server and not Scavenging duration
</div>


Go ahead and do that
There is nothing wrong in that did not impact any
U r simply changing Scavenging trigger server and not Scavenging duration

sagdoc

<div>
Would it be possible to provide an update. Thanks.
</div>


Would it be possible to provide an update. Thanks.

<div>
<div class="content wysiwyg-content">
We have an old 2008 domain controller\AD DNS server that is also set as the scavenging server. &nbsp;It's been this way for years without issue. &nbsp;We now want to change the scavenging server to a new DC running 2016 but it has been so long since we have had do deal with this, we could use some advice on the change.<br />
<br />
1. &nbsp;The current scavenging server is set using all the period defaults. &nbsp;It runs every Wednesday at around 7:45PM. &nbsp;<br />
2. &nbsp;Should we make the change to set the new domain controller as the DNS scavenger just after step one completes. &nbsp;Our thinking is this will prevent any issues scavenging records that it should not and it will maintain the same time period. &nbsp;<br />
3. &nbsp;Is there any other steps that need to be performed other than just unchecking 'Enable automatic scavenging of stale records' on the old server and checking the same setting on the new server?<br />
<br />
Thanks
</div>
</div>


We have an old 2008 domain controller\AD DNS server that is also set as the scavenging server.  It's been this way for years without issue.  We now want to change the scavenging server to a new DC running 2016 but it has been so long since we have had do deal with this, we could use some advice on the change.

1.  The current scavenging server is set using all the period defaults.  It runs every Wednesday at around 7:45PM.  
2.  Should we make the change to set the new domain controller as the DNS scavenger just after step one completes.  Our thinking is this will prevent any issues scavenging records that it should not and it will maintain the same time period.  
3.  Is there any other steps that need to be performed other than just unchecking 'Enable automatic scavenging of stale records' on the old server and checking the same setting on the new server?

Thanks

Help changing the AD\DNS scavenging server

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

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.