Create a Self-Service User in VMM

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

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.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

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...

Jason Yoder, MCT

Search This Blog