<div>
If I remember correctly the setting for GPO will not work on a server OS. (it may have changed in recent version though) <br>Last time I did this was via PowerShell script but I would also make sure you do a verification that it applies correctly. <br>I have seen cases where the script updates the value but it didn't actually apply on a few of the machines. <br>It also depends on how many servers your talking about a few hundred obviously do a script but if it is only 20 or so just update the settings manually.&nbsp;
</div>


<div>
Thanks for your input, yeah, we have hundreds.&nbsp; I found this and ran manually on one system via powershell, worked, so now just figuring out how to deploy.<br><br>Set-DNSClientServerAddress –interfaceIndex 12 –ServerAddresses (“10.0.0.1”,”10.0.0.2”)<br><br>Thanks<br><br>
</div>


<div>
If you have a list of the servers then you could do a remote execution of the command.<br>Using Invoke-command you could iterate through the list of servers and run the command.<br>Just be aware the interfaceindex may not always be 12.<br><pre><code class="code-10 nolinks" id="code-20-43296946-1"><span>$servers = get-content -path "c:\temp\serverlist.txt"</span>
<span>$Log = "C:\temp\log.txt"</span>
<span>&nbsp;ForEach ($server in $servers) { </span>
<span>$server</span>
<span>&nbsp; &nbsp; Try {</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; $error.Clear()</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; Invoke-Command -ComputerName $computer -ScriptBlock {</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Set-DNSClientServerAddress –interfaceIndex 12 –ServerAddresses (“10.0.0.1”,”10.0.0.2”)</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; }</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; if ($error.Count -gt 0) {</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $ERRMSG = "Server: " + $server + " ERROR " + $error[0]</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Add-content $log $ERRMSG</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; }</span>
<span>&nbsp; &nbsp; }</span>
<span>&nbsp; &nbsp; Catch {</span>
<span>&nbsp; &nbsp; &nbsp; &nbsp; Add-content $log $server + " Was not available" </span>
<span>&nbsp; &nbsp; }</span>
<span>&nbsp; &nbsp;</span>
</code></pre><br><br>&nbsp;
</div>


<div>
How about just re-IP'ing the new DCs so that they have the same IPs as the old DCs? Then you don't have to worry about changing DHCP options or your static hosts.<br />
<br />
If for some reason you can't do that, then scripting using PowerShell Remoting would be my choice.
</div>


<div>
Thanks in advance for your comments. &nbsp;We're going to try to push the simple powershell script via Blade Logic. &nbsp;Currently it's just a matter of getting the job setup correctly in BladeLogic to push out.
</div>


<div>
<div class="content wysiwyg-content fr-view">
We recently migrated our FSMO roles to new Windows 2016 servers and would like to demote our Windows 2008 R2 Servers. &nbsp;The question is our member servers on their NIC's point to the existing Windows 2008 R2 servers for DNS. &nbsp;These are static since these are member servers. &nbsp;Member servers are running Windows 2008 R2, Windows 2012 R2 and Windows 2016.<br><br>What is the best way to update the DNS on the NIC's to the new DC's? &nbsp;I would image that this should be more than a manual process. &nbsp;All I've been finding are the recommendations to use DHCP which doesn't' work on statically assigned IP's and info on Member Servers.<br><br>Thanks in advance.
</div>
</div>



We recently migrated our FSMO roles to new Windows 2016 servers and would like to demote our Windows 2008 R2 Servers.  The question is our member servers on their NIC's point to the existing Windows 2008 R2 servers for DNS.  These are static since these are member servers.  Member servers are running Windows 2008 R2, Windows 2012 R2 and Windows 2016.
What is the best way to update the DNS on the NIC's to the new DC's?  I would image that this should be more than a manual process.  All I've been finding are the recommendations to use DHCP which doesn't' work on statically assigned IP's and info on Member Servers.
Thanks in advance.

Powershell or GPO - which works best to update the Primary &amp; Secondary DNS server on Member Servers

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

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.

Powershell or GPO - which works best to update the Primary &amp; Secondary DNS server on Member Servers

Powershell or GPO - which works best to update the Primary & Secondary DNS server on Member Servers