cancel
Showing results for 
Search instead for 
Did you mean: 

Transitioning From Exchange 2007 Sp3 To Exchange 2010 Sp1, With EV9.3

SamChougule
Level 4

Greetings:

We are transitioning  from exchange 2007 sp3 to exchange 2010 sp1. Introduced exchange 2010 sp1 servers, now want to add them to EV 9.3

So far I have done these steps:

  1. Vault Service Account already exists , since we are already archiving on exchange 2007
  2. Created System Mailbox for each of the exchange 2010 servers ( in DAG, all servers active)
  3. Ran .\SetEVExchangePermissions.ps1 –user Domain\EVServiceAccount
  4. Ran .\Set-Mailbox EVServiceAccount -ApplyMandatoryProperties
  5. Ran .\SetEVThrottlingPolicy.ps1 -User Domain\EVServiceAccount
  6. Ran Add-ADPermission –Identity <SystemMailbox> -User < EVServiceAccount > -AccessRights ExtendedRight –ExtendedRights “Send As”

Do I need to these following and Am I missing anything that i need to take care before moving mailboxes from exchange 2007 to exchange 2010.

Add the exchange 2010 CAS servers to C:\Program Files\Enterprise Vault\ExchangeServers.txt and run owauser.wsf

Add SynchInMigrationMode registry value under HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Agents , while moving mailboxes from exchange 2007 to exchange 2010.

Thanks,

Sam

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
Ok so for the mailbox, you have to create or move the vault admin accounts mailbox to 2010 In exchange 2007 and 2003 you never needed a mailbox for the vault admin, but for the powershell scripts you do need a mailbox for it that will be placed on the 2010 servers As for the IP addresses for the CAS servers, you can either place them in the exchangeservers.txt and run the script or you can just place the IP addresses in the ip restrictions part in IIS As for synchInMigrationMode, it doesn't hurt to put that on but maybe unnecessary if the mbxguid and pegacyexchangedn's are going to be the same Worst case scenario is if you don't have it on you may end up with duplicate archives for each iser
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

4 REPLIES 4

JesusWept3
Level 6
Partner Accredited Certified
Not sure what the question is, but everything you listed seems fine, really the only thing you have to make sure is that the EVAdmin account has a mailbox on the exchange2010 server and then run the permissions and throttling scripts You may also need to give the EVAdmin account Send On Behalf As rights to the system mailboxes you've created so that you can send enablement/disablement messages Run a deployment scanner for good measure to make sure t doesn't complain about the permissions and versions for outlook, and also try connecting to a random mailbox on exchange 2010 and ensure that it doesn't prompt for a username and password, if it does the. You may need to apply the permissions script again
https://www.linkedin.com/in/alex-allen-turl-07370146

SamChougule
Level 4

Hi JesusWept2 : may be i was not een clear on my questions, here they are:

should I add the exchange 2010 CAS servers IP addreseses to C:\Program Files\Enterprise Vault\ExchangeServers.txt and run owauser.wsf ,

On the EV servers should I add SynchInMigrationMode = 1 in the registry under HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Agents , while moving mailboxes from exchange 2007 to exchange 2010. I am looking at this technote http://www.symantec.com/business/support/index?page=content&id=TECH48928

Also you mentioned "make sure is that the EVAdmin account has a mailbox on the exchange2010 server". currently the mailbox is on exchnage 2007 server, if I move it exchange 2010 server, will archiving still work on exchange 2007 server ?

Thanks for your time.

JesusWept3
Level 6
Partner Accredited Certified
Ok so for the mailbox, you have to create or move the vault admin accounts mailbox to 2010 In exchange 2007 and 2003 you never needed a mailbox for the vault admin, but for the powershell scripts you do need a mailbox for it that will be placed on the 2010 servers As for the IP addresses for the CAS servers, you can either place them in the exchangeservers.txt and run the script or you can just place the IP addresses in the ip restrictions part in IIS As for synchInMigrationMode, it doesn't hurt to put that on but maybe unnecessary if the mbxguid and pegacyexchangedn's are going to be the same Worst case scenario is if you don't have it on you may end up with duplicate archives for each iser
https://www.linkedin.com/in/alex-allen-turl-07370146

SamChougule
Level 4

Thank you once again for your time on the questions. I have marked your suggestions as solution. THANKS

I will move the current evadmin mailbox from ex2k7 to ex2010. and add the synchInMigrationMode  in reg  , just to be on safe side.