Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Vault Service Account in DAG

Created: 11 Apr 2013 • Updated: 05 May 2013 | 4 comments
This issue has been solved. See solution.


I need a solution. We've got a mixed mode Exchange environment with 2007 and 2010 DAG. We can put the 2010 DAG Service to the target list, but when we like to archive no mailbox is shown.

Is it neccessary to put the Vault Service Account also to the DAG or could it stay on the 2007 Service till the end of the migration

The Archiving System in Enterprise Vault 10.0.3

Thanks in advance

Operating Systems:

Comments 4 CommentsJump to latest comment

Advisor's picture

Yes you will need to create/move VSA mailbox on Exchange 2010 server first.

thpuck's picture


Vault Service Account is in the DAG, but never the less i can't archiv mailboxes that in the dag.

When I put the DAG Server to the Target everything works well. When I tried to archive a Mailbox (Reporting Mode or Archiving and Shortcutprocessing" I won't see any mailboxes

Thanks in advanced

Advisor's picture

Did you run the provisioning task before running the archiving task? Any events logged regarding archive task run?

JesusWept3's picture

typically it should be

1. Create a mailbox for the EVAdmin (if it doesn't exist) and move in to an exchange 2010 server
2. Run the Permissions powershell script as an exchange admin, specifying the EVAdmin account
3. Run the Throttling policy powershell script
4. Create regular mailboxes on each exchange server you wish to target for the system mailbox
5. Add the Exchange Servers as targets in EV, when you create the task, you then specify the system mailboxes you created

Now when you add the system mailboxes, it will show you a list of all the mailboxes on that exchange server, so you know at least that you have permissions to read from the GAL etc

6. Modify any provisioning groups if need be, as you may not target whole exchange organization, you maybe targeting DL's, or an LDAP query or a group etc which may not include the Exchange 2010 users
7. Run provisioning in normal mode and review the provisioning reports, make sure some Exch2010 users are being provisioned
8. Attempt to enable an archive

Another reason you may not be seeing anyone to enable is if the provisioning group is set to Automatically Enable an archive and then the Exchange 2010 task kicked off its normal archiving run, it would see these new users and then enable them as it processes the mailbox... and the reason you may not see anyone to enable is because they are already enabled

If that was the case though, you would see mailboxes listed when you try to do a manual Run Now or a manual synchronization etc