Skip to main content

How to delegate Admin on an RODC.

Read Only Domain Controllers are a great option for sites with less then desierable security. When deploying RODCs, one thing to consider is a local administrator. Unlike traditional Domain Controllers, RODCs areable to have a local administrator. These local administrators do not have Domain Administrator rights. They can only work on their RODC. Some of the tasks they can perform are:
· Install hardware devices, such as network adapters and disk drives
· Manage disk drives and other devices
· Install software updates and drivers
· Stop and start Active Directory Domain Services (AD DS)
· Install and remove other server roles and features
· View logs in Event Viewer
Manage shares and other applications and services

How do you delegate the local administrator role for an RODC? If you are using the wizard, you can delegate this role to a user or group on the Delegation of RODC installation and Administration page. (See below)




You can also delegate after installation in one of two ways. By opening the RODC account property, you can specify the local administrator in the Managed by tab. Click Change and select the user or group you want to delegate to.






You can also do it using the commands ntdsutil local roles or dsmgmt local roles command. Delgation via command line is not recommended because it is stored locally, not in Active Directory.





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.

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 .