cancel
Showing results for 
Search instead for 
Did you mean: 

Migrate Exchange 2010 Archived Mailboxes to O365

Itegral
Level 6

One of our clients are migration their Exchange 2010 archived mailboxes to O365. The concern is that when the users are migrated, it will break the link (stub) between legacy EV and destination mailbox (on Exchange online) which will leave the users unable to access the historical data.

Is there a way for users to have access to their legacy archives while the mailbox is being migrated to O365?

  1. What are the migration options to maintain the stubb connection intact?
  2. Speaking to one 3rd party professional, he suggested that stubs lose connection will depend how the users are migrated from Exch to O365. What method people follow to ensure continuity of legacy EV system?
  3. Any document to support the above discussion would be appreciated.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Rob_Wilcox1
Level 6
Partner

How Outlook connects to EV for retrieval of archives items, via the shortcut, is governed to some extent by a hidden message in the mailbox. So, provided the mailbox is moved to Office 365 along with hidden messages (rules are stored as hidden messages too) then TECHNICALLY the retrieval will work... so long as the user still has access to the source environment. Supported, is a different story.  Most folks migrating mailboxes to Office 365, will want to also migrate the archived data... and (slightly biased) Archive Shuttle can do that for you..  as well as other third party products/tools.

Working for cloudficient.com

View solution in original post

10 REPLIES 10

Rob_Wilcox1
Level 6
Partner

How Outlook connects to EV for retrieval of archives items, via the shortcut, is governed to some extent by a hidden message in the mailbox. So, provided the mailbox is moved to Office 365 along with hidden messages (rules are stored as hidden messages too) then TECHNICALLY the retrieval will work... so long as the user still has access to the source environment. Supported, is a different story.  Most folks migrating mailboxes to Office 365, will want to also migrate the archived data... and (slightly biased) Archive Shuttle can do that for you..  as well as other third party products/tools.

Working for cloudficient.com

Itegral
Level 6

Thanks Rob, Yes the archives are going with Mailboxes as well. However, once the mailboxes are migrated, I suppose users will not be able to access their historical archives until the archives are not fully ingested at destination. Now the question is, you said "so long as the user still has access to the source environment" - how? What the mechanism that needs to be in place to achieve it so that users from destination could pull the archived data from the source?

WiTSend
Level 6
Partner

We're facing a similar scenario. I see the best option would be to use EV-IMAP to allow the users full access and functionality to their archives.  This is fully independent of any action taken on the mail systems or mailboxes.

Itegral
Level 6

So for that you would require EV 11?

Once EV server is enabled for IMAP and Provisioning Group created and mailbox added to the provisioning group, how would you make it public facing? I know you would require SSL certificate but obviously some IIS settings to make it public might require.

What configuration is required on Exchange side?

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

IMAP could be an option, unless you want to stop paying for EV Support.  Here is some additional info and link to the deploying guide.

Licensing and support considerations

In order to provide IMAP Access to an Exchange Archive, the Exchange Mailbox Archiving license is required. For Internet Mail Archives the Per Terabyte license is required.

A step by step guide for configuring IMAP Access is provided in the document Setting up IMAP.pdf, found in the product media Documentationfolder. For more details and best practices on IMAP and SMTP configuration refer to the whitepaper “Deploying IMAP Access to Enterprise Vault”, available at http://www.veritas.com/docs/000004014

Itegral
Level 6

Having spoken with the customer, they are not under support by Symantec as about to move to O365. So the IMAP option is not pragmatic.

Now the question is, what are their options in order to keep the links maintained between the migrated mailboxes and source archives (while the archives are being ingested at destination).

If continuity is not possible, as above, what are their alternatives in order to have the legacy archives available to their users while the archives are being ingested at destination?

All I can think of is, export the archives in PST and and link it with the outlook at local machine... problem is the number if users... probably 100s!!

Itegral
Level 6

Any thoughts would be appreciated..

WiTSend
Level 6
Partner

The shortcuts are simply URL links to the EV platform and as long as the users' accounts stay the same and you are still on the same network they shortcuts should continue to function.  The users also should continue to have the ability to connect via the WebApp.  If you are planning on migrating the archives to O365 as well then the best option is to use one of the 3rd party migration tools/services.  The local option of export to PST and import into the O365 mailbox is also possible either by the admin or by the user.

Itegral
Level 6

I agree but dont forget users will be on Exchange online after the migration, with Archives left behind in legacy environment. For users accounts to remain the same and communicate back with local AD from O365 environment, we would require ADFS, correct? Otherwise I am not seeing any way to recieve the authentication betweent the source and destination environments.

Michael_Bilsbor
Level 6
Accredited

Hi,

 

At TransVault, most of the customers I see migrating to Office365 do so with ADFS.  So they have a hybrid environment.  Users are able to double click on shortcuts in their mailboxes to access archived items whilst the data is migrated.  Everything works smoothly.

 

Yours,

Mike