VMM 2019 Permissions Set

Simon G 26 Reputation points

Hi All

Apologises if this sounds like a daft question but have deployed VMM 2019 in our environment (All Hyper-V 2019 hosts) and we are looking at setting permissions within VMM and the some VM's for a team outside of my own.

I am trying to avoid using GP's to push out permissions for RDP and local admin but when I enable these options within Settings > User Roles and assign them to a user group for example - the RDP fails to launch advising access denied. Does the user group or user need to be added locally to each server and the permissions set in here only applies to the console rather than the VM's the console hosts.

Hope this makes sense.


A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,562 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 39,411 Reputation points

    Hi @Simon G

    I see that you are wanting to see some fixes about the RDP permissions, I can help you with that.

    Please try the following steps;

    Go to


    2-click computer configuration

    3-click windows settings

    4-then to security settings

    5- click local policies

    6- click security options

    7- then disable the function with name "limit local account to use blank passwords "

    8- logout and re login and try again ....hope you will be connected

    Also, I would suggest you to check the suggestions provided in the section "Why can’t I connect using Remote Desktop Connection?" in this article:


    You may also refer to this link; https://answers.microsoft.com/en-us/windows/forum/all/remote-desktop-password-incorrect-windows-10/0720c735-196e-4550-9704-41d17b3551b3?page=3

    Did I resolve your issue today? If so, that would be great.

    --If the response is helpful, please click "Accept Answer" and upvote it--

    0 comments No comments

  2. Alex935 6 Reputation points

    Hi Simon,

    yes that are two separate parts, the one is the VMM permission set, which allows you to steer who sees which parts and how many rights they have..

    ...when opening an RDP connection to a VM from VMM then you have to authenticate and authorize to the system explicitly again. - So either you add the corresponding users locally to the systems or via GPO as you said.

    small hint:
    In case the users need to open VMM with different credentials as they are logged on, I remember there was a small bug when first time opening a remote connection via VMM it would say access is denied, but on the second try it would work...

    best regards,

    0 comments No comments