Figure 7.9 Service retry actions
Consider that if a service fails three times consecutively, it’s unlikely that restarting it
a third time would result in a different outcome. Clustering can be configured to
perform the action that is known to fix any problem and reboot the virtual machine on
the existing host. If the virtual machine is rebooted by clustering and the service fails
a subsequent time inside the virtual machine, then clustering will move the virtual
machine to another host in the cluster and reboot it.
For this feature to work, the following must be configured:
Both the Hyper-V servers must be Windows Server 2012 or above, and the guest
OS running in the VM must be Windows Server 2012 or above.
The host and guest OSs are in the same or at least trusting domains.
The failover cluster administrator must be a member of the local administrator’s
group inside the VM.