Skip to main content

How to delegate out permissions to rename user accounts

This question came from one of my Active Directory classes. To find the solution, I installed RSAT on a Windows 8 client.  I also created a user named JYoder who is not a member of any special group. I also had to do a little bit of detective work to figure out a small piece of this puzzle.

The first real big problem is that I noticed the Last Name field is missing from the Delegate Control Wizard. We are missing the SN attribute which is the last name.  Here is where the fun starts.  On the client that you are using to delegate rights, Open dssec.dat  You will find it in %Systemroot%\System32.  Make a copy of this first and then open it in Notepad.

Now, scroll close to the bottom.  You will notice that the file is divided into object types.  Close to the bottom, you will find the User object.  Look for the SN field in the user object.  Make sure, you are in the user object.

image

Now, look for SN=7.  Change this to SN=0.  Save the changes

Now, close and re-open Active Directory Users and Computer.

Right click the OU that you want to delegate permissions to and select Delegate Control…

Click Next 

Click Add

Select the user whom you want to delegate permissions to and click  Check Names, and then OK

Click Next.

Click Create a custom task to delegate and click Next.

Select Only the following objects in the folder and then place a check by User objects.

Click Next

Uncheck General and check Property-specific

In the permissions list, place a check by:

  • Write: AccountNameHistory
  • Write: Display Name
  • Write: First Name
  • Write: Initials
  • Write: Last Name
  • Write: Logon Name
  • Write: Logon Name (Pre Windows 2000)
  • Write: Middle Name
  • Write: msDS-LastKnownRDN
  • Write: name
  • Write: Name

Click Next

Click Finish

 

Log on to the client as the user you have delegated rights to.

Open Active Directory Users and Computers.

Inside the OU where you delegated this user the rights to rename an account, right click a user account and select Rename.

Type the display name for the new user and press Enter.  This will open a Rename User box.

image

Change the necessary fields and click OK

To show that I cannot use the RSAT tools to perform actions that I am not allowed to do, I simple right click the Sales OU.  I can see that under all tasks, I am limited:

image

Also try some other functions to see that the Delegate Control Wizard did not give out more than you ask for.

Comments

Andy Fuhr said…
This trick is amazing. Can this same concept be used for other attributes like, Office, City, etc ?

Thanks
Andy,
Go in the DSSEC file. I do not have one in front of me, but I believe you will find what you are looking for.

I'm glad this helped you out.

Jason
Unknown said…
ms-DSlastknownrdn is also not visible

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