I've two running VM-Hosts based on Hyper-V Server 2019. These hosts are accessable using Hyper-V-Manager and vmconnect.exe on Windows 10 and Windows Server 2012R2. But on newer Windows Versions (Windown 11 and Windows 2022) neither Hyper-V-Manager nor vmconnect.exe are able to connect. Both applications show the identical error:
The operation on computer 'DEP-VMHOST01' failed: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer DEP-VMHOST01.local. Verify that the computer exists on the network and that the name provided is spelled correctly.
(Original error is in german, this is the english translation) Original error in german:
Fehler beim Vorgang auf Computer 'DEP-VMHOST01': Die Anforderung kann von WinRM nicht verarbeitet werden. Der folgende Fehler ist bei Verwendung der Kerberos-Authentifizierung aufgetreten: Der Domputer 'DEP-VMHOST.local' konnte nicht gefunden werden. Stellen Sie sicher, dass der Computer im Netzwerk vorhanden ist und dass der angegebene Namen richtig geschrieben ist.
The connection is tested using Hyper-V-Manager and vmconnect.exewith the following command: vmconnect.exe DEP-VMHOST01 linux01 [linux01 is a running virtual machine on the host]
I'm confused about DEP-VMHOST01.local, I would expect here: DEP-VMHOST01.example.com or [email protected] (Computer name with the domain behind)
The used Windows Domain is structured as following:
Computer name in ActiveDirectory and on the VM-Host: <Department acronym>-<Name>
DNS-Name: <Name>.<Department acronym>.example.com
E.g. Computer Name: DEP-VMHOST01, DNS: vmhost.dep.example.com
All used computers and the VM Host are in the same IPv4 subnetwork and have joined the same domain and the logged in Domain-User has administrator privileges.
Kerberos and winrm Authentication are working (without entering the password again) and have been tested with the following commands:
Enter-PSSession DEP-VMHOST01 -Authentication Kerberos
Open a remote power shell without
winrs -r:DEP-VMHOST01 powershell Get-VM
Lists the remotely running virtual machines
Accessing the VM-Host with other tools from the Microsoft Management Console is also possible (tested with the Computer Management addin).
Copy a working vmconnect.exe to Windows Server 2022 does not work, as the application crashes on startup (complaining about a missing file in the windows event log). The vmconnect-Application from C:\Program Files\Hyper-V\6.3 (or 6.2) on Windows Server 2022 does complain that it is only compatible with Hyper-Versions newer than Windows Server 2012. Running the applications form C:\Program Files\Hyper-V\6.2 on Windows Server 2012 does work.
Does anyone know, how the Kerberos-Parameters are acquired in the Hyper-V management applications?
