FL shouldn't impact doing DHCP failover. The one thing that I did find when setting that up here was that any filters weren't being replicated. I had to setup a powershell task to do that. Apparently it was a known limitation.
-- There are 10 kinds of people in the world... those who understand binary and those who don't. ¯\_(ツ)_/¯ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Tuesday, December 5, 2017 11:03 AM To: [email protected] Subject: Re: [NTSysADM] Advice: physically moving a site, but not changing AD Site info ... On Tue, Dec 5, 2017 at 10:51 AM, Melvin Backus <[email protected]> wrote: > Moving DHCP shouldn't be as bad as you might think. If you're running 2012r2 > or later you can do failover, and either way you can export / import the > setup. The only real change would be the network guys having to add/replace > the DHCP helper IP setup in your routers/switches. Yes, all DCs are Win 2012 R2. (AD domain/forest level is still Win 2008 R2, but I think I can raise that, I believe all prerequisites have been met)
