Verify that the recovery cloud contains at least one host running a compatible version of Windows with Hyper-V Replica enabled. Then, try to enable protection for the virtual machine again.
Usage: DRConfigurator.exe /r /friendlyname value /proxyaddress value /proxyport value /proxyusername value /proxypassword ...
User role (%UserRoleId;) can't be found. User roles set on primary site virtual machines must also exist on the recovery ...
Validate the IP address and port and check connectivity between the host and process server. If the issue persists contact ...
Verify network connectivity between the process server and target servers. Check that there's adequate bandwidth to enable ...
Verify that the recovery cloud contains at least one host running a compatible version of Windows with Hyper-V Replica enabled. ...
Verify that the script exists in the required path. Check that exceptions are being handled correctly using try-catch blocks. ...
Verify that the VMM service can access the import or export path. If the path is shared, ensure that the VMM service account ...
Verify the replication state for the virtual machine in the Microsoft Azure Site Recovery vault, and retry the operation. ...
Verify the virtual machine state, check that the VMM/Hyper-V server is available, and retry the planned failover. Or perform ...