09-23-2013 07:58 AM
We are just implementing Exchange Mailbox Archiving with EV 10.0.4, We have been using journal archiving for some time. I had a couple of user's who left, and was testing a procedure for moving the contents of their mailboxes to EV and then deleting them from Exchange and AD. However, after doing so I am receiving a warning event #3454 during the archiving run and the archiving report is showing a "Warning not Provisioned" error for both mailboxes. Here is the procedure I followed to get where I am. The mailboxes were not already enabled for archiving.
Provisoning, synchronization and archiving tasks have been running normally for the last few days, with the exception of the above errors.
I would appreciate any advice on both how to tell EV to stop trying to archive these mailboxes and on how to modify my procedure so that this doesn't happen in the future.
I appreciate any input.
Solved! Go to Solution.
09-23-2013 08:24 AM
Rob article is fantastic!
When you run the provisioning task, it writes the provisioned users information in Exchangemailboxentry table under Enterprisevaultdirectory database. So once you remove them from provisioning group also try cleaning the Exchangemailboxentry table.
09-23-2013 08:05 AM
Here is something that might be helpful:
https://www-secure.symantec.com/connect/articles/processing-company-leavers
09-23-2013 08:24 AM
Rob article is fantastic!
When you run the provisioning task, it writes the provisioned users information in Exchangemailboxentry table under Enterprisevaultdirectory database. So once you remove them from provisioning group also try cleaning the Exchangemailboxentry table.
09-24-2013 07:31 AM
Manually removing the entries from Exchangemailboxentry table does eliminate the errors during the archiving run. However, it seems that whenever I disable a mailbox for archiving and remove it from all provisoning groups, an entry for that mailbox is left in the Exchnagemailboxentry table and must be manually removed. This doesn't seem normal to me. Are there any ideas on how to avoid this?
Thanks.