Move users Exchange 2003 to 2010 - EV9.0.1

[lukassc]

I have users in my actual EV enviorment and we planning to migrate some of them to Exchange 2010. How is the procedure concerning the VSA. Remember that both Exchange 2003/2010 must be active and archiving to the same time.

Eventualy we just use Exchange 2010. Do I need another VSA, mailbox, etc?

Another question: What is the recomendation to Upgrade version to 9.0.2? First add the new Exchange or not?

Thx!!!

[JesusWept3]

Upgrade to 9 sp3 instead of 9 SP2, doesn't matter if you upgrade before or after, personally though I would do it before, after that, move the VSA mailbox to 2010 (or create it if one doesn't exist) and then run the powershell scripts to set permissions and throttling policies That's pretty much it, you don't need two evadmins

[lukassc]

At the moment I have VSA mailbox running on Exchange 2003, so you said that I need to move it. But doing this, it will get any problems with my users on 2003?

• VSA (I have it)
• VSA mailbox (I have it) But do I need one mailbox per Exchange?

I don’t understand this “Upgrade to 9 sp3 instead of 9 SP2” I have 9.0.1 and we want to upgrade 9.0.2 (this last one its what you call sp2?).

Thx!!

[TonySterling]

Moving the VSA mailbox to Exch 2010 will not cause any problems with Exch 2k3 users.

You will need a new system mailbox for the Exch 2010 server(s).

JW2 is suggesting you upgrade to EV 9 sp3 instead of EV 9 sp2.  Why upgrade to a SP that is already out of date?

[lukassc]

Do you know any pappers to do this, step by step?

Thx!

[TonySterling]

You could review this:

How to configure EV 9 with Exchange 2010 Technical Whitepaper - Enterprise Vault 9 Archiving from Exchange 2010.pdf (703 kBytes)

If you are still uncomfortable with the process I would recommend engaging a consultant to assist you.  I would be worth the $$ having someone with experience step through the process with you.

[lukassc]

What about if I have 3 Exchange servers 2010? The mailbox of the VSA, do I have to move it on every exchange to assign permissions?

[TonySterling]

Did you read the document I posted?  No, you would not have to move the VSA to every server but you would need an archive task and system mailbox for each Exchange Server.

[lukassc]

I have one doubt.

If I have 3 Exchange 2003 and 1 Exchange 2010. Every server must have one account, different of the VSA, right? With the mailbox and system mailbox.

Exchange 1 ----> User: VaultUsr1 // mailbox1 and system mailbox

Exchange 2 ---->User: VaultUsr2 // mailbox2 and system mailbox

Exchange 3 ---->User: VaultUsr3 // mailbox3 and system mailbox

VSA: use by the Ev Console. On "logon" option on the exchange 1 y must use the user VaultUsr1.

This is correct? I don't know if I made myself clear.

Thx!!

[TonySterling]

No, that is not correct.  You don't mess with the logon options, leave them the VSA.

Give this a read as well:

How to add Exchange 2010 to an existing Enterprise Vault environment

Article: TECH165220

|

|

Article URL http://www.symantec.com/docs/TECH165220

[lukassc]

Let me see if I understand.

• Use VSA for all the exchange servers.
• Give VSA the proper permissions on each server (Powershell, throttling,etc)
• With Outlook on the EV server I must connect on each server as well with the VSA.

In the article that you send me, its say

If there is already an existing VSA on an existing Exchange 2007/2003 server in the same site, make sure that you move the VSA to the Exchange 2010 server, and grant it necessary permissions on the Exchange 2010 server.

I don't understand that part "Move the VSA to the Exchange 2010 server".

[TonySterling]

Move the VSA is referring to the VSA mailbox, it has to be on one of the Exchange 2010 servers.  Both JW2 and myself have told you this previoulsy.

[lukassc]

And if I have 3 Exchange server, what mailbox must move? From what exchange?

[TonySterling]

Did you read the documents?

Simply put, the VSA must have a mailbox on anyone of your Exchange 2010 servers, it doesn't need one on each, just one of them.

[lukassc]

What happend if I create one mailbox for Exchange 2010 and I used on the VSA.

This is what I going to do.

1. Create a mailbox for vsa in the exchange 2010

2. Grant permissions on the VSA

3. Add the exchange 2010 on the vault console.

4. Open Outlook with the VSA in the Vault Server and syncronize with Exch2010.

5. Move SOME of the mailbox of the user from 2003 to 2010.

6. Run the provisioning task, and the archiving task.

What do you think?

[lukassc]

What happend

What happend if I create one mailbox for Exchange 2010 and I used on the VSA.

This is what I going to do.

1. Create a mailbox for vsa in the exchange 2010

2. Grant permissions on the VSA

3. Add the exchange 2010 on the vault console.

4. Open Outlook with the VSA in the Vault Server and syncronize with Exch2010.

5. Move SOME of the mailbox of the user from 2003 to 2010.

6. Run the provisioning task, and the archiving task.

What do you think? 

[JesusWept3 · Accepted solution]

so it should be

1. Create a mailbox for the EVAdmin if one doesn't exist, and place it on Exchange 2010
2. If the mailbox does already exist, simply move it from Exchange 2003 to 2010
3. Run the Throttling and permissions scripts through Powershell
4. Create a System Mailbox (not the EVAdmin) for each Exchange 2010 server and place it on the Exchange 2010 server
5. Add the Exchange 2010 servers in the Vault Admin Console and when it creates the task, specify the system mailbox you created for that server in step 4
6. Move a single enabled mailbox from Exchange 2003 to 2010
7. Run Provisioning Task and then a synchronization via the Exchange 2010 Task
8. Open outlook for the mailbox logged in as that mailboxes owner
9. Ensure that you can open items first, then try restore and archve of the items
10. Also ensure that there is not a duplicate archive for that user created

It is possible when moving mailboxes from exchange server to another that duplicates are created if Exchange doesn't keep things like the LegacyExchDN or the MbxGUID, if you do end up with Duplicates you will need to run the SynchInMigrationMode registry key

[lukassc]

Perfect Answer, That is what I was looking for.

I will follow this steps, and I let you know the results.

Thx!!