So we finally got to do this yesterday afternoon. The TechNet article laying out the process isn't going to win any awards for clarity, but we did get it done. Because we installed DHCP on the Win2012 server ourselves (to create the custom DHCP options for our phones), we did have to do the Import-SmigServerSetting command with the -Force option.
But it looks all good now. Soon we'll set up DHCP failover, once we get another machine to do so, for redundancy and for DR purposes, etc. On Tue, Mar 10, 2015 at 1:44 PM, Michael Leone <[email protected]> wrote: > On Tue, Mar 10, 2015 at 12:54 PM, Miller Bonnie L. > <[email protected]> wrote: >> Only issue I've ever had with moving over the IP from the old to new DHCP >> server is that sometimes you have to reauthorize the new one. Just make >> sure all of your DNS (and WINS if in use) records update correctly at each >> step in the IP changes before you move to the next. >> >> Only other catch on the import/export is if you've added any custom options >> you can get some weird/unknown errors when you try to import. You have to >> create those options again on the new server prior to import, then it will >> go through. For example, we have a few custom options added for phones. > > > That last is good to know. We, too, have custom options for phones ... > > Thanks! > >> -Bonnie >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Michael Leone >> Sent: Tuesday, March 10, 2015 9:10 AM >> To: [email protected] >> Subject: [NTSysADM] Advice: migrating DHCP from Win 2008R2 DC to Win2012 >> non-DC, then decommision Win2008R2 >> >> So we've been having massive DHCP problems, the service just becomes >> unresponsive until we reboot the server. So the boss has decided to migrate >> the DHCP to a new Win2012 R2 VM. And he wants to do it today ... >> >> So here's what I have: all Win2008 R2 DC (forest and domain at Win2008 >> R2 levels) - 7 DCs in total, 3 here at headquarters, 4 out at other sites. >> >> We want to migrate DHCP from #2 DC here at HQ. This DC does DNS and DHCP (no >> FSMO roles). We want to migrate DHCP to the new Win2012 R2 member server. >> Then we want to decommission the DC entirely, and re-use it's IP address >> (because all our switches use that IP as DHCP helper addresses). >> >> Now, we have "Migrate DHCP Server to Windows Server 2012 R2" doc, and it >> seems relatively straightforward. Export using the migration tools, import >> using the migration tools. >> >> Here is my concern - because I need to keep the same IP address, I need to >> decommission the existing DC, so I can re-use it's IP. Where in this process >> do I do this? >> >> Do I: change the IP on the DC *first*; migrate to new Win2012 R2; change >> it's IP to match the old IP of #2; decommission the old DC entirely and shut >> it down? >> >> I realize that change the IP on the existing DC means that DHCP will break >> (in the sense that the switches won't be able to do DHCP helping). But I >> just think that this is easier and safer. >> >> Thoughts? >> >>
