Why can all Domain Users seemingly launch the VMM 2012 R2 console and modify my VMs?

Greetings -

Folks, I've run into something that is very concerning to me in my new VMM 2012 R2 environment.  I've found that seemingly any domain user in my domain can launch the VMM 2012 R2 console (if installed on their machine of course), and they can not only connect to the VMM server but also modify properties of my VMs, start/stop them, etc.  They can't connect to the console session but at any rate, this is highly concerning from an RBAC perspective.

The only built-in RBAC group in VMM that I can see is "Administrators".  The membership of this group contains all the defaults (i.e. the VMM server computer account, service account, default action account, Domain Admins, etc.)  It does *not* however contain any groups that would include Domain Users or any broad global/universal groups.

So why anyone can launch the console and play with my VMs, I have no idea.  Where else should I be looking for access rights?  Aside from my server administrators, I don't want anyone to be able to launch the console and connect, let alone make any setting changes or even see any VMs for that matter.

Ideas?  What am I missing about VMM 2012 R2 versus the old VMM 2008 R2 world where this was seemingly simpler or at least more secure/functional?

Thanks in advance.

Edit - Additional Information:

My VMM environment is extremely simple at this point as it is in the early stages of configuration.  Only a few hosts, about 20 VMs, a single private cloud, single domain, nothing extravagant.  It is VMM 2012 R2 (Update Rollup 4) running on a fully patched Server 2012 R2 box.
amendalaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
In SCVMM what group of users are administrators (as far as SCVMM is concerned)
0
VB ITSSpecialist ConsultantCommented:
In VMM, click on Settings in the bottom left corner > expand Security > click User Roles > under User Roles in the right pane > click the Administrator user role > verify the members in this role in the bottom pane and remove members if necessary. If you have other custom roles then check the members for these roles also.
0
amendalaAuthor Commented:
Good morning -

I actually answer the questions in both comments above in my original post but I'll answer again here.

There are *NO* additional individual members or groups in my Administrator role in SCVMM above and beyond the defaults.  The only members are as follows (with specific naming redacted for security):

DOMAIN\Domain Admins
NT AUTHORITY\SYSTEM
DOMAIN\SCVMMSERVICES
DOMAIN\SCVMMACTION
DOMAIN\VMMSERVER$

And no, Domain Admins does not contain Domain Users, it contains only a small list of individual user accounts and no other groups.

This is what is so confusing to me.  VMM seems to be granting all Domain Users privileges when none above and beyond the action and service accounts, and domain admins, are explicitly configured.

Thank you.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

amendalaAuthor Commented:
I decided to create a role with "Read-Only" permissions that has access to no clouds or host groups and I added "Domain Users" as a member.

I've found that this restricts any users who are not explicitly part of a higher-permission RBAC group from making any changes or viewing anything.

This partially satisfies my goal but is so backwards that I feel as if something is wrong.

Firstly - it completely obliterates the concept of Least Possible Privilege by assuming everyone has all access until restricted.

Second - It violates the long-standing tenet in the Windows world that "Deny" permissions supersede "Allow" permissions.

Functionally, this solution does work.  If as a Domain Admin I open the console, because I'm part of a higher RBAC group, even though Domain Users (of which every Domain Admin is obviously a member) is in a read-only group, I am granted the permissions of the higher RBAC group.

The only thing this doesn't satisfy is why users are allowed to even connect to the VMM server AT ALL without being granted permissions.  As far as I'm concerned, unless explicitly granted permissions to an RBAC group in VMM, the console shouldn't even accept your connection or get past the splash screen.

Perhaps more on this later if I learn more but at this point, I think I've found my own solution.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VB ITSSpecialist ConsultantCommented:
Sorry amendala, completely missed that bit in your original post. If what you said above is true then that is deeply concerning. I'm going to try and install SCVMM 2012 R2 on my machine and run it under my user account (as I use a separate account for admin tasks) and see if what you say is true.
0
amendalaAuthor Commented:
By all means, I'd love to hear your results, let me know... I'll keep the question open.  If it restricts you, then I'm going to open a case with Premier Support to see if Microsoft has any good answers as to the behavior I'm seeing.

Thanks!
0
VB ITSSpecialist ConsultantCommented:
Sorry amendala, haven't had time to install SCVMM 2012 R2 on my machine as of yet. I'll let you know how I go once I get a chance regardless.
0
amendalaAuthor Commented:
I have found no alternatives either here or anywhere else, including Microsoft, regarding this behavior.  The solution I devised is apparently the manner in which to configure SCVMM if you want the console locked down - at least in 2012 R2.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.