Skip to main content

Create a Delegated Administrator in VMM

A Delegated Administrator has the ability to perform all the functions of an administrator in VMM, but is limited to only certain groups of hosts or library servers.

 

To create a Delegated Administrator, 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 Delegated Administrator

 

Click Next

 

clip_image002

 

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, check the hosts, hosts groups, and library servers that this group will have administrative control over for VMM.

 

Click Next.

 

clip_image003

 

In the Summary window, click Create.

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