ct and all descendant objects
Create Computer objects Allow
Delete Computer objects Allow
From: Jon Harris [mailto:jk.har...@gmail.com]
Sent: Friday, July 29, 2011 8:50 PM
To: NT System Admin Issues
Subject: Re: Delegation of Control in Windows 2008 R2 DFL/FFL questions
I went with
ects Allow
Delete Computer objects Allow
From: Jon Harris [mailto:jk.har...@gmail.com]
Sent: Friday, July 29, 2011 8:50 PM
To: NT System Admin Issues
Subject: Re: Delegation of Control in Windows 2008 R2 DFL/FFL questions
I went with putting a group into the default domain GPO that was able to add
, August 01, 2011 2:36 AM
To: active...@mail.activedir.org; NT System Admin Issues
Subject: RE: [ActiveDir] Delegation of Control in Windows 2008 R2
DFL/FFL questions
You don't have to pre-create the computer account in a particular OU, if
you use tools like NETDOM to join the computer,
ctive...@mail.activedir.org; NT System Admin Issues
Subject: RE: [ActiveDir] Delegation of Control in Windows 2008 R2
DFL/FFL questions
Computers don't have to be joined via the default computers container.
You can pre-create the computer account in its final destination, then
perform the d
I went with putting a group into the default domain GPO that was able to add
machines. I did that originally because I had been told that the office
manager needed to add machines as they arrived. Shortly after that I
management told me never mind the office manager did not want the extra
work.
To the list,
Been reading up on delegation of control wizard, and it seems that it
can be customized as per
http://support.microsoft.com/kb/308404
And there are additional templates in the following document:
Best Practices for Delegating Active Directory Administration Appendices
http:
