cancel
Showing results for 
Search instead for 
Did you mean: 

dsacls command not working

Jim_Hellewell
Level 4
Partner

Hi all,

We have Windows Server 2003 Domain Controllers, the Forest Functional level is also 2003; we have deployed Exchange 2010, and EV 10.0.4 into production. before we turn on Journal archiving and use Discovery Accelerator in production, we are trying to test it first in our labs.

As one of the pre-requistites for DA, we are running the following dsacls command:-

dsacls "CN=Deleted Objects,DC=domain,DC=com" /takeownership

this generates the following error "Parameter /takeownership was unexpected"

My questions are:-

1) Do we really need to issue this command (we get a warning about it later in the istallation process) ?

2) Any ideas what is wrong with the command.. is it to do with the Domain Controllers being on Windows Server 2003 ?

Any help is much apreciated

regards

Jim

1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you seen this?

Assigning the required Active Directory permissions to the Custodian Manager synchronization account

Article:HOWTO107877  |  Created: 2015-01-09  |  Updated: 2015-01-09  |  Article URL http://www.symantec.com/docs/HOWTO107877

It needs the permissions on the Deleted Objects container for this reason:

Without these permissions, it is not possible to deactivate any custodians and custodian groups whose Active Directory details have been moved to the Deleted Objects container.

For the Windows 2003 part of you question, I would refer to this: http://support.microsoft.com/kb/281146

View solution in original post

1 REPLY 1

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you seen this?

Assigning the required Active Directory permissions to the Custodian Manager synchronization account

Article:HOWTO107877  |  Created: 2015-01-09  |  Updated: 2015-01-09  |  Article URL http://www.symantec.com/docs/HOWTO107877

It needs the permissions on the Deleted Objects container for this reason:

Without these permissions, it is not possible to deactivate any custodians and custodian groups whose Active Directory details have been moved to the Deleted Objects container.

For the Windows 2003 part of you question, I would refer to this: http://support.microsoft.com/kb/281146