06-24-2013 09:30 AM
We've been getting event id 35 from discovery accelerator trying to sync the AD account for an employee who left the company. I'm not, however, seeing where I can deactivate this account. I understand that I cannot delete him the account to preserve the chain of evidence but I would really like to stop this error from being logged constantly throughout every day.
Solved! Go to Solution.
06-25-2013 01:20 PM
Since you don't have Custodian Manager set up, those errors are caused by at least one role assignment that the account has. How many Cases do you have where that user account could have been granted a role assignment? If only a few, just go into each Case, click on the Role Assignments sub-tab, locate that user and remove any roles. This also needs to be done at the Application level if that user was granted any application level roles.
If you can't locate where this user was granted any role assignment(s), please contact the Symantec Enterprise Vault Support to open a case with one of our DA Technical Support Engineers so we can assist you in finding and clearing all role assignments for that account.
06-24-2013 11:11 AM
You can deactivate the synch in Custodian Manager:
Article:HOWTO31603 | | | Created: 2010-09-23 | | | Updated: 2012-06-27 | | |
Article URL http://www.symantec.com/docs/HOWTO31603 |
You access CM via the web page, http://server_name/virtual_directory
For example:
http://server2/EVBACustodianManager
You can also change the number of days CM tries to synch before automatically marking the account as deactivated:
Article:HOWTO31609 | | | Created: 2010-09-23 | | | Updated: 2012-06-27 | | | Article URL http://www.symantec.com/docs/HOWTO31609 |
The number of days that Custodian Manager should wait before it marks as deactivated a custodian for whom no Active Directory or Domino LDAP directory account is available.
06-25-2013 01:08 PM
Apparently they never set up the Custodian Manager. How do I need to set up the SQL database?
06-25-2013 01:20 PM
Since you don't have Custodian Manager set up, those errors are caused by at least one role assignment that the account has. How many Cases do you have where that user account could have been granted a role assignment? If only a few, just go into each Case, click on the Role Assignments sub-tab, locate that user and remove any roles. This also needs to be done at the Application level if that user was granted any application level roles.
If you can't locate where this user was granted any role assignment(s), please contact the Symantec Enterprise Vault Support to open a case with one of our DA Technical Support Engineers so we can assist you in finding and clearing all role assignments for that account.