In some cases it’s good to replicate a virtual machine in and outside a clustered system.
I tried this the very first time but after setting up the replication broker role in the failover cluster manager I got an error.
After researching a while whats going on I got a solution.
The Cluster Role couldn’t write a computer object.
Usually you set up an OU where the Hyper-V Servers belongs to and there is the Cluster Role (actually a computer account created during the installation) as well.
The Cluster (machine account) has to get writable access to this OU and after that… The Replica Broker is working. 🙂
More informations about that:
On my testing lab I ran into a problem as I tried to get vPro access remotely via Direct Access based on Server 2012 R2.
It turned out that there is a problem if I used the virtual network of the Direct Access Server on the same port as the built in network port.
I couldn’t get access to the vPro interface on the Hyper-V Host where the DA Server is running as virtual machine.
Reasearching the problem I could see If I’m switching to another vNet on an other port on the same Host the vpro webinterface appears.
In best practise the Host System shouldn’t communicate during the same network port as the virtual machines anyway but with limited ressources I ignored that.
The vPro/AMT Stuff works on a shared base with the first network port on Intels Q Chipsets.
I could reproduce this with a Q77M chip and Intel 82579LM and a Q87M with I217LM as well.
Some smaller or older servers have these kind of shared remote ports as well but in most cases the remote port is independent (HPs iLO is mostly a 100Mbit port for example).
The Preview is still out there and the first impressions were made.
Since R2 hits the TechNet i’m on my way to explore more and more stuff I really like.
- Tiered Storage Spaces
- incredible fast (Windows) updates
- dedup for CSVs
- shared virtual disks (makes it a lot easier to build Cluster in a Cluster Environments –> guest clustering)
- online VHDX resizing (Gen2 only)
But there are some Points missing.
A graphical view of hot spots on dedup’d File Servers or something to see what kind of data can dedup’d pretty well and what kind doesn’t.
Quick upgrade/migrations paths for existing Gen1 Hyper-V machines to Gen2.