Video Screencast Help

Migrating to new Active Directory Domain

Created: 29 Jun 2014 • Updated: 05 Sep 2014 | 8 comments
This issue has been solved. See solution.


A portion of our business has been sold and is required to be migrated to a brand new domain. We are planning on using the Dell/Quest Migration tools to migrate users and mailboxes to the new domain and exchange org.

We use Enterprise Vault 10.0.4 to archive both mail and files. Due to storage issues it would be desirable to continue archiving email (file archiving not necessary) during the migration period.

Is it possible to migrate the existing Enterprise Vault infrastructure to the new domain and maintain archiving for email?

What would be the recommended general steps to achieve this?

In regards to the users who are not moving to the new domain, we plan to inflate their archives or migrate them to another archiving solution.

Thanks in advance!


Operating Systems:

Comments 8 CommentsJump to latest comment

RahulG's picture

You may refer the folowing document

You may export the existing archived data to PST files for the user whom you dont want to move to the new domain. You can perfrom this operation using the export wizard in Vault admin console.

You may also consider the Move archive utility which can be used to move users from one EV server to Another Ev server.

karmakoma's picture

Thank you very much!

The migration steps look reasonably straight forward. We will have the issue with email shortcuts using links and I have read the RestoreShortcutBody process takes a lot of processing power. Will adding an additional EV server help?

RahulG's picture

The RestoreShortcutBody process mostly affects exchange as the shortcuts in all the mailbox would get updated thus increasing  the transaction logs .

AndrewB's picture

hi karmakoma, are you looking to split up a single EV environment to two different companies while maintaining archiving for the parent company and minimizing user impact? just want to make sure we're not overlooking something here because in the scenario you describe it sounds like you might require a migration tool. any additional information you'd like to provide about your requirements  and the size of the existing environment would help us help you. this is something we do all the time for our customers. happy to help you figure this out together.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner |

karmakoma's picture

Hi Andrew,

Thanks for your reply. Yes, probably best to explain my situation better as, like them all, it's unique.

Ok so Company_A has sold part of it's business to a new entity. Included in the sale is the IT infrastructure so the new entity (call them Company_B) owns the EV infrastructure.

Company_B are moving to a new domain and plan on continuing to use EV for mail and file. Company_A may or may not continue using EV.

There are approx 500 users. 400 moving across with Company_B and the remaining 100 to stay with Company_A

I don't have exact figures on vault archive storage but the total amount of archive storage (mail and file) is 8.1Tb (inflated).

Company_B's work data has already been extracted/inflated to a new file server and is not being archived. Company_B's user personal files and email is still archived.

Company_A's work data, user personal files and email is still archived.

So we are looking for a solution with minimal user impact to setup EV in the new domain.

A solution which involves building a new EV environment in the new domain and copying across Company_B file and data which then leaves Company_A with the original EV infrastructure and archives would be ok too.


AndrewB's picture

you should be able to run a report and see the size of all the mailbox archives. login to the EV server with the EV service account, launch Internet Explorer, go to http://localhost/EnterpriseVault/usage.asp and from there you can click on the vault store(s) where the mailbox archives reside and see the data. you can save the report to tsv or whatever and manipulate it in excel.

for the least impactful approach (to either side) you could build a new EV server for Company_B, configure archiving etc, and use move archive for the 400 archives. however, if that proves too slow and cumbersome and ultimately unreliable it's worth looking into migration tools and help.

in particular, if the archived data is used for legal, compliance, eDiscovery, etc purposes you need detailed records of where it's been, what was done to it, and where it ended up (and also if anything failed to migrate keep track of that too) and migration tools provide that for you. we call it "chain of custody"

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner |

karmakoma's picture

Hi Andy,

Thanks for the reminder re: reports. There are a large number of mailbox archives (over 1000) and 100 over 20Gb in size with over 80K items.

I think with that number of items, the RestoreShortcutBody process is going to result in too long an outage for users and that is going to make migrating the existing EV infrastructure to the new domain a no go.

Using the Move Archive tool might work but Symantec say it is purpose is not a mass migration tool so I think a migration tool is what's required.

Using a tool such as ArchiveShuttle in conjunction with Quest/Dell Migration manager for Exchange what would be the recommended process?

1. Migrate users and mailboxes to new domain.

2. Enable mailbox archiving on new EV infrastructure in new domain

3. Migrate old archives in old domain to new domain EV infrastructure

Is it possible to merge old archives into new?


AndrewB's picture

agreed and yesir, that's how it would be done with ArchiveShuttle. part of the initial setup/config lets you map the source archive (old company EV) to the destination archive (new company EV) so it's exactly how you describe. all the while, the users can maintain access to their data and you can continue archiving.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner |