I actually just finished setting this up not too long ago-almost mentioned it in the thread with your DHCP migration question, as that is when I last used it =)
Our old single DHCP server was still WS03 R2-it had the last few printers that weren't Win7 compatible shared up until September when they finally went away, so was a really good candidate for our first 2012 server migration. Over time, I did the migration first of the old server to 2012 DHCP using netsh, had our network admin add the IP for the new server to all the DHCP relay settings on the networking side, then set up the second server and added failover with some test scopes, then went into production with a few scopes, then added the rest. We've been running it for a month or longer now with all scopes in failover and it's been working well so far. I can shut down either server (one at a time) and things will still run. I did sit through a 1 hour webinar offered through our Premier support that gave some good insights to what is going on and what does/doesn't replicate-there are still some things you have to manually push when making changes. If you have questions on specifics that you're not finding, I *might* know-I don't really know the Hot Standby option as we're not using it, but I don't think it's all that different. At this point, we have about 75 IPv4 scopes for various wired and wireless subnets in a load balance parternship between the two servers, which are both in the same AD site. We still have a separate server dishing out DHCP for our IP phones that is 2008 R2, and will probably do the same migration for that system at a later date, but might set one up on a physical server since it's for phones. The only gotcha that I ran into that I didn't find documented was that when I went to add failover to some scopes, the option simply wasn't there with a right-click. After not finding the answer online, I compared scope-by-scope to the ones that worked and found I had to disable BOOTP completely for it to show up. This actually makes sense to me as I learned in the webinar that the option for DHCP failover is not a "Microsoft" thing, but is based on an RFC for DHCP on IPv4, so doesn't apply to IPv6, and nor would it apply BOOTP. I had to hunt down just a few devices (mostly printers) that were configured for BOOTP and get them changed to DHCP before we could configure failover on those scopes. There are also a few changes you make in the interface that you do have to manually push when changed as they are NOT covered by the RFC, and ARE a "Microsoft thing" that they added for ease of use. There is also no protection from your pushing a change in the wrong direction, so know where you are. -Bonnie From: Michael B. Smith [mailto:[email protected]] Sent: Friday, February 15, 2013 7:08 AM To: NT System Admin Issues Subject: RE: Server 2012 failover DHCP I've set it up in the lab, and plan on deploying it at a client in late March. But I don't have a real-world implementation yet. From: David Lum [mailto:[email protected]] Sent: Friday, February 15, 2013 10:03 AM To: NT System Admin Issues Subject: Server 2012 failover DHCP Is anyone running a pair of Server 2012 DHCP servers with a high availability set up? http://blogs.technet.com/b/teamdhcp/archive/2012/06/28/ensuring-high-availability-of-dhcp-using-windows-server-2012-dhcp-failover.aspx We are looking to add some HA to our DHCP configuration, as currently we're not even running an 80/20 setup. David Lum Sr. Systems Engineer // NWEATM Office 503.548.5229 // Cell (voice/text) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
