cancel
Showing results for 
Search instead for 
Did you mean: 

Confusing documents Purpose of reg. keys SkipChecks and DoNotChangeAnonymousPermissions.

Raul_Kivi
Level 3

Confusing documents Purpose of reg. keys SkipChecks and DoNotChangeAnonymousPermissions.

I have Windows 2003 SP1 and EV 6.0 SP3. I had some DCOM errors and started to look solution from KB.

Document http://support.veritas.com/docs/279962 introduces reg. key DoNotChangeAnonymousPermissions

In document http://support.veritas.com/docs/279588 is written that SkipChecks reg. key should be used.

Third document -EV help file registry_values.chm tells that SkipChecks have completely different purpose - nothing connected with DCOM permissions:

„Controls whether the Enterprise Vault Admin Service performs memory and disk space checks when it starts. If any check fails the Admin Service does not start and thus the other Enterprise Vault services do not start”

Does anybody know what exactly these regkeys do?

Message Edited by Raul Kivi on 08-08-200701:33 PM

1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Looking at the bottom of http://support.veritas.com/docs/279588 you see SP1 (Fixed) so that key should not be needed any longer.  :)
 
For the DoNotChangeAnonymousPermissions the release notes have the following:
 
The Admin Service checks the default Anonymous Logon permissions each time it starts, modifying them if necessary. If your corporate security policy does not permit this automatic softening of security permissions, do the following:

View solution in original post

1 REPLY 1

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Looking at the bottom of http://support.veritas.com/docs/279588 you see SP1 (Fixed) so that key should not be needed any longer.  :)
 
For the DoNotChangeAnonymousPermissions the release notes have the following:
 
The Admin Service checks the default Anonymous Logon permissions each time it starts, modifying them if necessary. If your corporate security policy does not permit this automatic softening of security permissions, do the following: