Checking the ADVL Logs shows the following:
Invoke-Command -ComputerName '<HyperVServerName>' -Credential $hypervCredential -SessionOption (New-PSSessionOption -IncludePortInSPN) -Script { Get-VMHost }
Warn HyperVCmdletsRule.Check(): Unable to invoke Hyper-V cmdlet on <HyperVServerName>. Error: QuestSoftware.RecoveryManager.AD.Cloning.PowerShellException: [<HyperVServerName>] Connecting to remote server <HyperVServerName> failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer <HyperVServerName>. Verify that the computer exists on the network and that the name provided is spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic
Invoke-Command -ComputerName '<HyperVServerName>' -Credential $hypervCredential -SessionOption (New-PSSessionOption -IncludePortInSPN) -Script { New-VHD -Path 'D:\M\Hyper-V-config\1eydtp20.rgk\test.vhdx' -SizeBytes 3MB }
Aug 29 19:12:28.249 [0744:0022] Warn TargetMachineAccessR...CheckStorageAccess(): Cannot create test object on storage: QuestSoftware.RecoveryManager.AD.Cloning.PowerShellException: [<HyperVServerName>] Connecting to remote server <HyperVServerName> failed with the following error message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer <HyperVServerName. Verify that the computer exists on the network and that the name provided is spelled correctly.
Run the following command:
setspn -l <HyperVServerName>
Check to see if the following SPNs are missing:
http/<FQDN>:5985
http/<shortname>:5985
If the SPNs are missing, run the following commands to add them and then try verifying the settings again in ADVL:
setspn -a http/<FQDN>:5985 <HyperVServerName>
setspn -a http/<shortname>:5985 <HyperVServerName>