Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

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

Posted on 07/07/202101/09/2023 IT Expert By IT Expert No Comments on 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
  1. Home
  2. Virtualization
  3. 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
Server connection error

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.

Understanding Unauthorized Access Error and Hyper-V Installation

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 unauthorized access. Kindly refer to this guide on how to install Hyper-V Server Core Mode: How to install a free Hyper-V Server on a VMware Workstation.

Virtual Machine Management service

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.

Server connectivity issues
Screenshot 2021 07 06 at 13.31.43 1
Authorization to connect
Screenshot 2021 07 06 at 14.15.16 1

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.

Server connection error
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:
Virtual Machine Management service

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.

Authorization to connect

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

Server connectivity issues

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.

Server connection error
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.

Virtual Machine Management service

If you connect from an arbitrary client to an arbitrary Hyper-V Server, you must 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.

Virtual Machine Management service

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

Authorization to connect

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

Server connectivity issues

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.

Screenshot-2021-07-06-at-16.36.45
Screenshot 2021 07 06 at 16.36.45
Screenshot-2021-07-06-at-16.37.25
Screenshot 2021 07 06 at 16.37.25
Screenshot-2021-07-06-at-16.37.47

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. Additionally, make sure the Virtual Machine Management service is running to ensure a successful connection. 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 on Virtual Machine Management service helpful. If you have any questions, please let me know in the comment session.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:Configure WinRM, errors, Hyper-V, hyperV, Hypervisor, Windows 10, Windows 11, Windows Server 2016

Post navigation

Previous Post: How to install free Hyper-V Server on a VMware Workstation
Next Post: Out-of-Band Security Update for PrintNightmare: Patch released for Windows Print Spooler Remote Code Execution Vulnerability

Related Posts

  • Delete Edit or Revert a Snapshot on vSphere
    Manage VMware Snapshots: Delete or Edit or Revert a Snapshot Virtualization
  • stuck
    Fix Hyper-V VM Stuck in Stopping State Virtualization
  • Machine does not support XSAve
    How to disable side-channel mitigations on VMware Workstation Virtualization
  • HyperV
    Unable to PXE boot a HyperV VM: F12 key does not work anymore Virtualization
  • Downgrade
    Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation Virtualization
  • Proxmox VM backup with VBR
    How to create a backup job for Proxmox VMs using VBR Backup

More Related Articles

Delete Edit or Revert a Snapshot on vSphere Manage VMware Snapshots: Delete or Edit or Revert a Snapshot Virtualization
stuck Fix Hyper-V VM Stuck in Stopping State Virtualization
Machine does not support XSAve How to disable side-channel mitigations on VMware Workstation Virtualization
HyperV Unable to PXE boot a HyperV VM: F12 key does not work anymore Virtualization
Downgrade Downgrade VMware Workstation: Fix the Processor does not support xsave on VMware Workstation Virtualization
Proxmox VM backup with VBR How to create a backup job for Proxmox VMs using VBR Backup

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • dfggg
    SimpleSAMLphp Setup on Windows Server [Part 1] Windows Server
  • changepsswd
    How to change your Windows Computer login Password Windows
  • powershell commands lede 1024x276 1
    Enable WinRM on Windows Servers and Windows PCs Scripts
  • Screenshot 2020 07 23 at 18.29.00
    Universal, Global, and Domain Local Group Scopes Differences Windows
  • fde container
    Full Disk Encryption with PBA or without PBA, UEFI, Secure Boot, BIOS, File and Directory Encryption and Container Encryption Security | Vulnerability Scans and Assessment
  • windows 10 s splash 100720578 large
    Open the location of a Program: How to search in Windows 10 to find a file, folder, or program in File Explorer Windows
  • ssh
    How to disable RC4 Cipher Algorithms support in SSH Server Linux
  • Featured image
    Domain Naming System: Enabling DNS over TLS in Windows 11 Network | Monitoring

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,801 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.