You can find this issue on many other sites, but this just happened to us when upgrading a domain controller from 2016 to 2019, that also had the DHCP server role installed. First before upgrading, we demoted the DC to a regular domain server. Then we upgraded to 2019, and re-promoted the machine to a domain controller. Lo and behold in DHCP, it looked like everything was working fine but the Server IP (for itself) was a 169.254.x.x address. Sure enough when we disabled all unused network adapters, the issue was instantly resolved (without reboot). Hope this helps anyone else out there – “not sure why MS hasn’t fixed this yet” since it looks like its been a problem since 2012.
Hyper-V 2019 Failover and Replication Tips
We recently performed a Hyper-V 2019 failover for a customer and wanted to share some insights. Non-clustered environment, simply 2x 2019 Hyper-V
