Proxmox/Hyper-V/VMware

An error occurred while attempting to connect to the server: Check if the Virtual Machine Management service is running or you are not authorized to connect to this server

HyperV-1

Microsoft Hyper-V, codenamed Viridian lets you create and run a software version of a computer, called a virtual machine. Each virtual machine acts like a complete computer, running an operating system and programs. When you need computing resources, virtual machines give you more flexibility, help save time and money, and are a more efficient way to use hardware than just running one operating system on physical hardware. You may also want to see Why does the legacy PXE not does work on Generation 2 VM, How to set up a VM via PXE boot on a Generation 1 VM, Generation 2 VM: How to set up a Hyper-V Virtual Machine through PXE boot, how to install Windows Server 2022 on VMware Workstation, how to install Windows Server 2016 Operating System on VirtualBox, and how to install Windows Server 2019 on Virtualbox.

The following error below can be attributed to a whole lot of issues. But as you can see from the error description (image below), this is also as a result of an unauthorized access. Kindly refer to this guide on how to install Hyper-V Server Core Mode: How to install free Hyper-V Server on a VMware Workstation.
Screenshot-2021-07-06-at-13.30.04

As you can see below, the management service is running. Also the WinRM is configured, yet the remote connection to the server isn’t possible.

Reason: The following error is because you are connecting to the Hyper V Manager NOT as an Administrator that wasn’t defined in the Hyper-V Manager Administrators group in AD or Hyper-V Administrators group on the HyperV server. The below image might help you see what you are doing wrong.

Screenshot-2021-07-06-at-13.26.05
Solution: You must run Hyper-V Manager using an account that is in the Administrators group or Hyper-V Administrators group on the target server. Otherwise, you won’t even be able to connect to the Hyper-V host. If your management workstation’s administrator account does not have those capabilities, hold down [Shift] while right-clicking the Hyper-V Manager shortcut, and then choose Run as different user:
Screenshot-2021-07-06-at-14.42.25-1

You will be prompted to enter your username and password as shown below. This user account is part of the Local Administrators User Group on the HyperV server.

Screenshot-2021-07-06-at-14.42.44-1

Click on Connect to Server, enter the server name when prompted and click on Ok.

Screenshot-2021-07-06-at-14.43.17-1

As you can see below, you should be able to connect to the server. That is all that needs to be done to correctly connect to the HyperV server remotely from a Windows 10 device.

Screenshot-2021-07-06-at-14.43.31-1
Other suggestions you could try: If you are having further issues and this isn't part of a Domain joined device, please perform the steps below.

If you are connecting from an arbitrary client to an arbitrary Hyper-V Server, you will need to configure winrm before you can connect. On the Windows 10 client, you will need to configure WinRM. Open PowerShell as Administrator and run the command in the image below.

Screenshot-2021-07-06-at-13.31.43-1

Add the IP address or servername of our Hyper-V Server to your WinRM client Trusted Hosts list as shown below.

Screenshot-2021-07-06-at-14.07.12

Kindly save the Administrator and password credentials for our Hyper-V Server (substituting the IP address or server name with your information as needed).

Screenshot-2021-07-06-at-14.13.30-1

DCOMCNFG is a Windows NT 4.0 utility that allows you to configure various DCOM-specific settings in the registry. DCOM is a programming construct that allows a computer to run programs over the network on a different computer as if the program was running locally. DCOM is an acronym that stands for Distributed Component Object Mode.
– Run the dcomcnfg from the command prompt or Windows search and expand the Component Services
– Computers
– My Computer in it. Right-click here, select Properties and go to COM Security 
Access Permissions 
– Edit Limits. In the next window check Remote Access permissions for everyone.

As you can see, everyone has Remotte Access permission.

Screenshot-2021-07-06-at-16.38.11-1

If you aren’t using an IP Address to connect, and you aren’t using DNS and you wish to connect using the server name, please create a host file record. Edit the host file with notepad (++) or any of the editors of your choice. I will not be demonstrating these steps as these are just added suggestions.

C:\Windows\System32\drivers\etc\hosts

Add a line with the “IP of your Microsoft Hyper-V Server 2012” followed by the “name of your Hyper-V server”. Then click on File and Save.

Screenshot-2021-07-06-at-16.41.31

You may also want to see the steps highlighted by Microsoft on how Remotely manage Hyper-V hosts with Hyper-V Manager. I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x
Kindly subscribe to TechDirectArchive
This is default text for notification bar