RE: How to prevent some specific Domain Admin Accounts from creating U



Hello Carl,

Have a look here from MVP Laura Hunter, found in another posting:

LauraEHunterMVP:
kamleshqwalani is incorrect - if you add a user to the Built-In Administrators group on a domain controller, that user becomes an administrator on all domain controllers in your domain, and by extension a Domain Admin. (kamleshqwalani is correct about local Administrator membership on workstations and member servers, but not DCs.)

The difference between making a user a member of Administrators on a DC versus making them a Domain Admin is an implementation detail - for example, Domain Admins are members of the local Administrators group on each domain-joined workstation and member server, BUILTIN\Administrators are not, and BUILTIN\Administrators is a Domain Local group whereas Domain Admins is a global group. So making a user a Domain Admin will automatically profer certain rights to domain-joined workstations and servers that BUILTIN\Administrators does not...but at the end of the day a member of BUILTIN\Administrators on a DC still has the effective rights of a Domain Admin, and so a determined user could figure out how to grant themselves whatever rights they don't have by default on workstations/member servers.

From a security perspective, BUILTIN\Administrators membership should be
treated as the security equivalent of Domain Admins, even though there are certain implementation details that may differ.
Accepted Solution


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

I've done this before. (or something similar to this.)

If the groups only needs to administer the DCs, they don't need to be
in the domain admins group. They only need to be in the Built-in
Administrators group.

The process to do this is slightly different between a 2000 forest and
a 2003 forest.

Create 2 groups. (i.e.- DCAdmins and DenyAD. This are mode up
groups. call them whatever you want.)

Nest the DCadmins in the Administrator group (this gets your account
the ability to administer the DC.) Next, add the DCadmins group in
the DenyAD group.

The next piece is tricky since it requires denies. I have to find my
old doc on how it was done. BUT IT IS NOT a blanket deny over the
DOmainNC, configuration, and Schema. the account that is logging into
the DC needs to be able to read a n attriute so that it knows it is
allow to login to the machine (this is for 2003 forests.)



.



Relevant Pages

  • RE: Windows 2000 to Windows 2003 Upgrade!
    ... Admins group was removed from Local Administrators group. ... Windows 2000 to Windows 2003 Upgrade! ... my VBScript logon script will not run for this reason(Seems WMI ... if I am logged on as a domain admin I should be able to access ...
    (microsoft.public.windows.server.migration)
  • Re: Admin accounts for Run As purposes only
    ... the approach to grant your folks only local admin rights won't work... ... > Administrators group of each server that needs to be managed. ... is this just as strong as a Domain Admin or is it more limited ...
    (microsoft.public.windows.server.active_directory)
  • Re: True difference between Domain Admin grp and Administrators Group
    ... is a member of the domain "administrator" group by default. ... The domain admin group not only has local administrator ... group is automatically added to the local "administrators" group. ... Members of this group have full control of the domain. ...
    (microsoft.public.windows.server.general)
  • Re: System Admin - Tomasz
    ... Delegation of rights allows a user or group to manipulate objects in the ... To be able to properly install software, he would need to be a member of the ... local administrators group at any machine on which you want him to be able ... You do not have to make him a domain admin for this. ...
    (microsoft.public.win2000.active_directory)
  • Re: Server Security
    ... In my opinion you want accountability for administrators and each administrator ... "The" administrator account should not be used and given a very long ... make sure that if there is sensitive information on that server, ... > name with domain admin rights on each. ...
    (microsoft.public.win2000.security)