Server 2016r2 dhcp not updating dns

This, of course, means you won’t be able to utilize the newest functionality and enhancements, but it will allow you to move the VM back to a 2012 R2 host.This is certainly interesting when you work in migration scenarios or want to use Rolling Hyper-V Cluster Upgrade, which I’ll cover later.With Windows Server 2012 R2, the current configuration version is 5, and surprisingly, it won’t be 6 in 2016 — TP3 gave us version 6.2 and TP4 shows 7 — unless something changes, of course.There is a difference compared to earlier versions: For instance, when you move or import a VM that comes from WS 2012 R2 to 2016, you’ll notice that the configuration version will remain at 5.Power Shell Direct allows you to use a simple cmdlet (Enter-PSSession -VMName VMName) and connect to the virtual machine (VM) through a host connection.

However, the VMs in that cluster should remain at version 5 (see above), and all of the new functionality and features cannot be used until it becomes a full 2016 Hyper-V cluster.Once you decide not to let your VM go back to an older version, you’ll need to update the VM to the latest configuration, which you can do by using Power Shell again (Update-Vm Configuration Version vmname or Update-Vm Configuration Version vmobject).The newer version also has a new configuration file.VMs running Linux (generation 2 VMs) will be able to use the Secure Boot option now. I assume that more distros will be added to this list later on.Windows Server 2016 will give you the ability to add and remove network adapters on the fly, without downtime.