Video Screencast Help

Moving Mailboxes to a new Exchange server

Created: 15 Aug 2013 • Updated: 19 Sep 2013 | 18 comments
This issue has been solved. See solution.

We currently have one EV server and configured with one Exchange server, We are going to add another Exchange server and then move some mailboxes from the old exchange server to the new ones. Other than adding the new exchange server in the directory – Target area are there any other configuration that I should be aware.

Operating Systems:

Comments 18 CommentsJump to latest comment

Ben Watts's picture

Yep, you must use the SyncInMigrationMode registry key to ensure the new mailboxes are assigned to the existing Archives.

SyncInMigrationMode  -  http://www.symantec.com/docs/TECH48928

Other than that, so long as you have setup archiving from the new Exchange server and tested this with a test account, all should go smoothly.

Using the above key will ensure EV associates the 'New' (In EVs eyes) mailbox with the existing entries in the EV SQL DBs.

GabeV's picture

Just add the SynchInMigrationMode, as Ben suggested, with a value of 1:

SynchInMigrationMode
http://www.symantec.com/docs/HOWTO32318

Description
Specifies whether, when migrating mailboxes from one Exchange Server to another, Enterprise Vault automatically assigns migrated mailboxes to existing archives. SynchInMigrationMode affects only the association between user mailboxes and archives; it does not affect the association between journal mailboxes and their archives.

1 - Makes Enterprise Vault assign new or moved mailboxes to existing archives if the legacyMbxDN values match.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

EVRocks's picture

thank you chaps,

The fact that we have carried out Exchange migration in the past this mentioned reg key is already exists in the registry. it looks like I don't need to make any changes. But still concern that I might end up EV creates new archive account for the moved mailboxes.

Ben Watts's picture

Hi EV,

So long as that regkey is in there you wont get duplicated archives.

EVRocks's picture

Since GabeV mentioned journaling. would the journal mailbox cause any issue when I start moving it to a new Exchange server.

GabeV's picture

For journaling, the process is a little bit different. I wouldn't move the journal mailbox. When you setup journaling in EV initially, you need to create the journal archive manually, create the journaling task and then setup the journal mailbox under the Exchange server. In this last step, you need to select the journal mailbox from Exchange, the journal archiving task, journal policies, retention and which archive you want to use to archive it.

In this case, you can just create a new journal mailbox in the new Exchange Server and setup a new task and a new Journal Mailbox in EV under the new Exchange Server and point it to the same archive you were using before.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

EVRocks's picture

Hi Gabe,

Currently I have one Exchange server (Exch01) and the plan is to build two more servers Exch02 and Exch03 then decomm Exch01. So I will have to move all mailboxes from Exch01 eventually.

Form Exchange point of you I can have one Journal mailbox but then I assume from EV point of you I should be able to have one journal archive for both Exch servers. is this possible and performance point of you is this recommended.

 cheers

GabeV's picture

If that's the case, you can configure a new journal mailbox in the new server, redirect journaling to the new mailbox and configure EV to archive this new journal mailbox. Then, once the 'old' EV journaling task archives all the data from the old journal mailbox, you can delete the mailbox from Exchange and decommission the server. You can have two journaling tasks archiving to the same journal archive. With only one EV server, you shouldn't have any performance issues if you keep your SQL DBs fragmentation low.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

EVRocks's picture

Gabe,

For what I read is that I need to add new exchange server as a new target, add journal, PF and then create new journal and mailbox archive tasks.

I noticed that when I tried to add the new target it prompt me to associate a system mailbox for the new exchange server. is this mean that I have to create a new system mailbox for each new target.

on the new exchange server I have yet got no mailboxes and in EV environment I only have one EV service account and I don't want to have multiple service/system mailboxes.

JesusWept3's picture

You have to have a system mailbox per exchange server (not per database or per EV environment)

It's been a pre-requisite since the beginning of EV, I think even BES requires a system mailbox per exchange server

EVRocks's picture

Well I have been using one account (EV service account) for all EV pre-req. I think you are right about BES requirement as well which require MAPI profile.

Pradeep_Papnai's picture

The information about move mailbox in exchange & EV related setting can be found in TN http://www.symantec.com/docs/TECH48928

Before moving the mailbox, exchange server must be added to EV task & associated task must be created. For exchange 2007/2010, refer following tech articals.

Exchange 2010 http://www.symantec.com/docs/TECH165220
Exchange 2007 http://www.symantec.com/docs/TECH68422

We should have mailbox for VSA (vault service a/c) if exchange is 2010 (should be hosted on e2k10 server only) and additionally each exchange server should have system mailbox.

System & VSA should not be same, refer following tech notes for each EV a/c require for it's operation.
Enterprise Vault Accounts and Permissions http://www.symantec.com/docs/TECH76700
 

SOLUTION
EVRocks's picture

EV-Counselor

With regards of step1 - Exchange permission. this is failing on me despite of running the provided PS1 script to set permision. the VSA is still have no SendAs and ReceiveAs permission on the new Exchange server.

The deployment scanner is failing on exchange permission.

Using PS on Exchange I am seeing these results when I compare the old and new exchange server for permisioning VSA. exch003 is the new Exchange server

Get-ExchangeServer exch003 | Get-ADPermission -User sv-enterpr

Identity             User                           Deny  Inherited     Rights
--------                 ----                           ----     ---------       ------
EXCH003            PROD\sv-enterpr... True  False     Send-As
EXCH003            PROD\sv-enterpr... True  False     CreateChild, Delet...
EXCH003            PROD\sv-enterpr... True  False     Receive-As

EXCH003            PROD\sv-enterpr... False False     GenericAll
EXCH003            PROD\sv-enterpr... False True      Receive-As
EXCH003            PROD\sv-enterpr... False True      ms-Exch-Store-Visible
EXCH003            PROD\sv-enterpr... False True      ms-Exch-Store-Admin
EXCH003            PROD\sv-enterpr... False True      ms-Exch-Store-Crea...
EXCH003            PROD\sv-enterpr... False True      ReadProperty, Gene...

Get-ExchangeServer exch001 | Get-ADPermission -User sv-enterpr

Identity                User                       Deny  Inherited Rights
--------                 ----                          ----     ---------   ------
EXCH001            PROD\sv-enterpr... False False     GenericAll
EXCH001            PROD\sv-enterpr... False True      Receive-As
EXCH001            PROD\sv-enterpr... False True      ms-Exch-Store-Visible
EXCH001            PROD\sv-enterpr... False True      ms-Exch-Store-Admin
EXCH001            PROD\sv-enterpr... False True      ms-Exch-Store-Crea...
EXCH001            PROD\sv-enterpr... False True      ReadProperty, Gene...

I have tried to remove those additional permsion but it does not let me due to not been present.

Any ideas...!!!

GabeV's picture

Is the VSA member of any Exchange Admin group?

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

EVRocks's picture

Yes. the VSA is a member of Exchange Server Administrator for both Exchange servers and also is a member of View Only Administrator (Organisation Wide).

GabeV's picture

If I remember correctly, those groups have send as and receive as permissions denied. Use ADSIEdit.msc to explore the permissions in the Exchange containers. Also, double check the permissions requirements for the VSA since I think the VSA doesn't need to be a member of those groups. The powershell scripts should assigned the permissions over the Exchange containers.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

henrikwalther3's picture

Move Exchange Mailbox to New Server can differ approach according time and current condition.

Mutate Offline/Unmounted EDB file to Outlook PST file formate from Old Server then Import outlook PST into New MS Exchange Server or relocate old database then recovery exchange database and point it.

You can also use PowerShell Export/Import Request commands.

"New-MailboxExportRequest" and "New-MailboxImportRequest". ..

For More Information, Visit here -  http://exchangeservermigration.blogspot.com/2013/07/how-to-move-exchange-server-2007.html

EVRocks's picture

Thank you Gentleman your input greatly appreciated.