Skip to main content

Create a Self-Service User in VMM

By

A self-service user role enables users to create and manage their own virtual machines within a controlled environment by using the VMM Self-Service Portal or the Windows PowerShell VMM command shell. A self-service user cannot create or modify user roles and cannot perform administrative functions on hosts and library servers.

 

To create a Self-Service User, open System Center Virtual Machine Manager.

 

In the menu bar, click Go \ Administration.

 

In the menu bar, click Actions \ User Role \ New user role

clip_image001

 

Provide a name and a description for the user role.

 

In the User role profile: drop down menu, choose Self-Service User

 

Click Next

 

In the Add Members window, click Add…

 

Add in the users or groups that will be part of this role.

 

Click Next.

 

In the Select Scope window, select the host group that these users will be able to utilize for their virtual machines.

 

Click Next

 

In the Virtual Machine Permissions window, you have the ability to set what each of the users who are a part of this role can do. They can:

 

· Start virtual machines

· Stop virtual machines

· Pause and resume virtual machines

· Create and manage virtual machine checkpoints

· Remove virtual machines

· The can be granted local administrator rights on their virtual machines

· They can be allowed to remotely connect to their virtual machines

· Shut down virtual machines.

 

Check the appropriate boxes and click Next.

 

In the Virtual Machine Creation Settings you can determine if the users can create virtual machines. You can also provide them with a list of templates (Pre-created VMs) to choose from.

 

To limit the number of running VMs the users can have, check Set quota for deployed virtual machines:

 

VMs can have different quota values assigned to them. This quota system will help prevent a user from accidentally, or intentionally, create a Denial-of-Service situation on your host servers.

 

Click Next

 

The Share quota across user role members setting will set the quota for the role members as a group. In other words if the quota is 5 and one user has 5 VMs started, no other member of that group will be able to start a VM until a VM is shut down.

 

In the Library Share window, you can select which library will store the VMs and ISO files created by the users of this role.

 

Click Next.

 

Click Create.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more