Delegate Control to rename and add/remove computer from domain

From: "Flash3200" <Flash3200@xxxxxxxxx>
Date: 27 Feb 2007 13:05:31 -0800

I want to delegate control to our Desktop Support group to be able to
add computers to the domain and also be able to rename computers
already on the domain. It is as easy as just giving them the rights
to create objects and delete objects for the computer objects? There
are a ton of possibilities of what they can do to computer objects but
most don't appear to apply. Anyone gone through this already?

Thanks

.

Follow-Ups:
- Re: Delegate Control to rename and add/remove computer from domain
  - From: Roger Abell [MVP]

Prev by Date: Group Policy without Active Directory
Next by Date: daylight saving time (DST)
Previous by thread: Group Policy without Active Directory
Next by thread: Re: Delegate Control to rename and add/remove computer from domain
Index(es):
- Date
- Thread

Relevant Pages

RE: Joining to the Domain - Question
... "Luiz" wrote: ... I must do that or can I do also by GPO? ... You have to give the Create Computer Objects to a user for the Computers ...
(microsoft.public.windows.server.active_directory)
RE: Joining to the Domain - Question
... You have to give the Create Computer Objects to a user for the Computers ... On the Security tab, ... I created a user, helpdesk, to join machines in my domain. ...
(microsoft.public.windows.server.active_directory)
RE: Joining to the Domain - Question
... "Luiz" wrote: ... I must do that or can I do also by GPO? ... You have to give the Create Computer Objects to a user for the Computers ...
(microsoft.public.windows.server.active_directory)
RE: Joining to the Domain - Question
... You have to give the Create Computer Objects to a user for the Computers ... From the Active Directory Users and Computers snap-in, ... Right-click the Computers container, ...
(microsoft.public.windows.server.active_directory)
Re: User and Computer OUs
... I have left all the domain controllers in the default Domain Controllers OU, ... but all our member servers are still in the default Computers container - ... >> someone explain why computer objects and user objects should be ...
(microsoft.public.win2000.group_policy)