SD Support
DE EN
Article

One article from the knowledge base, shown in full. You can read it without signing in, and nothing on this page is sent to the service desk or changes a ticket of yours.

Settings on this page

All articles
The button next to the article title takes you back to the article list, the same page as Knowledge base in the top bar. That list has a search box, a category filter and a language filter.
New ticket
In the top bar. Opens the form for raising a new ticket, with fields for your email address, a subject and your message.
Log in
In the top bar, for seeing your own tickets. Reading articles needs no account. Once you are signed in, the bar shows your email address and a Log out button instead.
EN / DE
Switches the language of the portal and keeps you on this article. The choice is remembered for your next visit. The article text itself does not change with it.
Light / Dark
Chooses the bright or the dark colour scheme. The portal starts dark. Your choice is stored in this browser only and applies to every page of the portal.

Reading the results

The article text
The whole article on one page, with its headings, lists, steps and links as they were written. Nothing is shortened and there is no next page to open.
Language of the article
Each article is written in one language, which may differ from the language you are reading the portal in. The article list shows your language by default and offers an All languages option.
Reading an article opens no ticket and notifies nobody. If it does not solve your problem, use New ticket and say which article you read and what you already tried.
 Log in

Hyper-V Manager can't connect to the host server - WinRM or permission errors

All articles

Symptoms

  • Hyper-V Manager stuck on 'Connecting to Virtual Machine Management service...' or shows no VMs.
  • WinRM/Kerberos errors such as 0x80090311 when connecting.
  • VMConnect console fails ('Cannot connect to the virtual machine') from some machines.

Fix it yourself

  1. Verify the Hyper-V Virtual Machine Management service (VMMS) is running on the host; restart it if hung.
  2. Confirm the connecting user is a member of Hyper-V Administrators (or Administrators) on the host, and Remote Management Users where applicable.
  3. Enable remoting on the host: 'Enable-PSRemoting'; for workgroup/cross-domain management also 'Enable-WSManCredSSP -Role server' on the host and '-Role client -DelegateComputer ' on the management machine.
  4. On the management machine, add the host to WinRM TrustedHosts: 'Set-Item wsman:localhost\client\trustedhosts <host FQDN/IP>'.
  5. Check firewall ports: TCP 2179 must be open for VMConnect console access, and LDAP 389 to domain controllers for authentication; enable the Hyper-V/Remote Management firewall rule groups.
  6. Check DNS and Netlogon health - failed domain controller discovery breaks Kerberos for remote management.
  7. If the console remains broken, test the same operations via PowerShell (Get-VM against the host) to isolate GUI vs. connectivity.

If that did not help

Attach the exact error, whether PowerShell remoting to the host works, the user's group memberships on the host, WinRM configuration (winrm get winrm/config), and firewall state for ports 2179/5985.