Delegating renaming a computer account

From: Jerame (anonymous_at_discussions.microsoft.com)
Date: 08/05/04


Date: Thu, 5 Aug 2004 12:50:52 -0700

I have delegated the right to add and delete computer
objects for our helpdesk to a particular OU in our Win2K3
domain.

I am told that they can not rename a computer that has
already been added to the domain. I have verified this to
be true. They do have local admin access to the
workstation.

Doing some research, I've read that you need to delegate
rename rights to the computer objects. I have been
unsuccessful in finding this.

I also came across a ms document that stated giving a
user "add computer rights to the domain" automatically
gave them rename rights, and that that was a problem and
going to be fixed in Windows 2000 SP3.

Can someone point me in the right direction?

TIA,
Jerame



Relevant Pages

  • Re: Cant anyone help me with this?
    ... What I have done is to delegate the change password and reset password ... permission to our helpdesk. ... password or the option to unlock an account is simply grayed out. ...
    (microsoft.public.windows.server.migration)
  • Re: Cant anyone help me with this?
    ... check on the ACL of that user object. ... Make sure that your helpdesk really ... > What I have done is to delegate the change password and reset password ... > password or the option to unlock an account is simply grayed out. ...
    (microsoft.public.windows.server.migration)
  • Re: Delegate permission to unlock AD accounts
    ... then you can also delegate the control to the OU where your Helpdesk people are located. ... unlock AD user accounts - that is fine. ... to unlock thier own accounts. ...
    (microsoft.public.windows.server.active_directory)
  • Delegation Account Unlock to Users
    ... I have delegated the Account Unlock function to my helpdesk but I'm ... I noticed that my helpdesk is unable to unlock fellow helpdesk ... I'd like to enquire if anyone has managed to succesfully delegate the ... Account Unlock function to work on the above 2 scenarios, ...
    (microsoft.public.win2000.security)