Skip to main content

How to set Quota Points for VMs in VMM

In System Center Virtual Machine Manager, you can create a quota point system to restrict how many VMs your self service users can run at any one time.  By using the quota points, you can prevent your users from accidentally, or intentionally creating a Denial-of-Service attack on your host servers.
We all know that virtual machines do not have to be created equally.  In other words, they may consume more or less resources than other VMs.  For this reason, you can assign a different quota point value to different virtual machines.  That way a single user, or group of users will not fire up resource intensive VMs and bring your hosts to their knees.

To do this, open System Center Virtual Machine Manager.

On the menu bar, click Go \ Virtual Machines

Right click the VM that you want to change the default quota point value for. Click Properties

Click the Settings tab.

Notice the default value for the Quota is 1.  For VMs that are resource intensive, you may want to increase this number. 

Click OK when you are finished.

image

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

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.

How to run GPResult on a remote client with PowerShell

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.

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