|
Well seeing this discussion has started I would like to throw a curve ball.
In my environment I have chosen the route to train the junior lads into pre-creating the computer account into the relative OU.
I have delegated the following permission over "Computer Objects" to "Add and Remove computer objects"
The problem I am experiencing is that if the computer account already exists in the OU the error received is "access Denied"
Thanks in advance Yusuf
From: Sullivan, Kevin
[mailto:[EMAIL PROTECTED]
You don't need to give them account operator rights. You give them 'specific' delegated rights. There could be some complex solutions that involve automating the process of looking through the computers container and moving computer account to the appropriate container (that is if you know the appropriate container via a name designation or something). This can be automated and scheduled but if you are too understaffed I doubt you will be able to find the time to develop this kind of solution. To have full functionality to address some of the complexities of AD management easily you will probably want to evaluate third part administrative tools. (<plug>Oh, yeah, my company has one.</plug>)
Kevin Sullivan Aelita Software www.aelita.com
From: Chris Flesher
[mailto:[EMAIL PROTECTED]
I saw that out on Technet. That's great as long as there is a person/group to handle that. We are understaffed and are looking for the OU admins to take care of this without giving them Account Operator rights.
Chris Flesher The University of Chicago NSIT/DCS 1-773-834-8477
__________________________________________________________________________________________________________________________________
For information about the Standard Bank group visit our web site <www.standardbank.co.za>
__________________________________________________________________________________________________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___________________________________________________________________________________________________________________________________ |
Title: Message
- [ActiveDir] Adding machines to OU direc... Chris Flesher
- RE: [ActiveDir] Adding machines to... Rakes, Brandon A. NMIMC Contractor
- RE: [ActiveDir] Adding machine... Chris Flesher
- RE: [ActiveDir] Adding machines to... Sullivan, Kevin
- RE: [ActiveDir] Adding machines to... Sullivan, Kevin
- RE: [ActiveDir] Adding machines to... Mayet, Yusuf Y
- RE: [ActiveDir] Adding machine... Rick Kingslan
- RE: [ActiveDir] Adding machines to... Sullivan, Kevin
- RE: [ActiveDir] Adding machines to... Mayet, Yusuf Y
- RE: [ActiveDir] Adding machines to... Free, Bob
- RE: [ActiveDir] Adding machines to... Sullivan, Kevin
- RE: [ActiveDir] Adding machines to... Coleman, Hunter
- RE: [ActiveDir] Adding machines to... Sullivan, Kevin
- RE: [ActiveDir] Adding machines to... Wright, T. MR NSSB
- RE: [ActiveDir] Adding machines to... Ayers, Diane
- RE: [ActiveDir] Adding machines to... deji
