Introducing an Exchange 2010 into an existing EV 9 environment
Hello, I have upgraded an EV 8.0 SP2 server to EV 9.0, and now I need to add two Exchange 2010 SP1 DAG servers into the archiving environment. The process of adding a new server seems straightforward, but I was wondering how to best provision the Vault system mailbox. Page 63 of the installing and configuring PDF says to move the mailbox to the Ex2010SP1 server to run the necessary management script for disabling throttling, but since the Exchange 2003 SP2 servers will be around for a couple of weeks, I don't want to "break" archiving for the users while they live on the old EX servers during the transition. What is the best way to proceed? Am I wrong to assume that the Vault system account, needs to be the owner of the vault system mailbox?
Comments
The VSA needs send as
The VSA needs send as permissions on the mailbox. It can be any mailbox on the server, so rather than moving one you can simply create a new mailbox on the Exchange server
Does the VSA need to be moved
Does the VSA need to be moved to an Exchange 2010 database before we can archive from a 2010 server?
I'm struggling to find any documentation specifically surrounding coexistence.
No, the VSA doesn't need to
No, the VSA doesn't need to be moved and actually doesn't need to have a mailbox at all. The VSA connects to the Exchange server via the EV system mailbox that you create on the Exchange server. It needs send as permission on this mailbox to be able to carry out all of the required operations. The installation and configuration documentation goes through all of this if you are getting stuck
Nick, Is that correct? I was
Nick,
Is that correct? I was under the impression that the account that runs against the task needs a mailbox (This is generally the VSA but does not necessarily have to be). The reason being due to throttling hence why we have to disable it via the powershell script and to do that the user needs a mailbox. From the Installing and Configuring guide:-
Exchange Server 2010 has a default throttling policy which restricts user accounts
to no more than 20 open connections to the server. This restriction on the Vault
Service account would cause failures of the Enterprise Vault tasks that run under
the account.
To prevent these failures, you must remove the restriction from the Vault Service
account when you archive from Exchange Server 2010. Enterprise Vault includes
a PowerShell script which creates a new policy and assigns it to the Vault Service
account to remove the restriction.
The script must be run against an Exchange 2010 mailbox so you must create a
mailbox for the Vault Service account before you can run the script. If your Vault
Service account already has a mailbox on Exchange Server 2007 or earlier, you
must first move the mailbox to Exchange 2010.
EV Backline Technical Support Engineer APJ Region
Good point Paul. I forgot
Good point Paul. I forgot that it changed for 2010. The VSA needs a mailbox for Exchange 2010 but not for Exchange 2000/2003/2007. The VSA's mailbox should not be used as the system mailbox though.
Thanks for spotting my mistake! :)
E2010 Migration
Hello,
Is there a valid document available detailing the coexistence scnearios of E2k3 & E2k10 ? we have upgraded to EV 9.0 & E2010 (from E2k3/EV8.0.3)and now planning to conduct additional testing. E2k10 setup include DAG. What are the points to consider before we can migrate the mailboxes to E2010 ? Any documents available explaining this procedure ?
Hello, You can follow the
Hello,
You can follow the below steps,
1. Move the VSA to Exchange 2010 server.
2. Set proper rights for VSA,
Log on to Exchange 2010 server with the accounts which has right on exchange servers and run below poweshell script,
Set-Mailbox <VSA> -ApplyMandatoryProperties
3. Configure the Exchange 2010 throttling policy on the VSA.
From exchange server 2010, copy the powershell script 'SetEVThrottlingPolicy.ps1' to local system for example to 'c:\temp'
Note: The Exchange 2010 PowerShell scripts are in the PowerShellScripts subfolder of the Enterprise Vault installation folder (normally c:\Program Files\Enterprise Vault)
Go to Exchange powershell and run this script, example: Set-Mailbox saEV –ApplyMandatoryProperties
4. Assign Exchange Server permissions to the Vault Service account.
Copy the powershell script 'SetEVExchangePermissions.ps1' to Excahnge server same as in step 3
Go to Exchange Powershell and run Example: SetEVExchangePermissions.ps1 –user <Domain>\saEV
5. Add the Exchange server into the EV as following normal porcess.
Ameen.
Hi Ameen , do i have to move
Hi Ameen , do i have to move the VSA, what about the exchnage 2003 users? they will still able to access the archived items
Yes you have to move the VSA
Yes you have to move the VSA mailbox to Exchange 2010 and run the throttling configuration. Exchange 2003 users will still be able to access their archived items.
Make sure you are moving the VSA mailbox and not the system mailbox associated with the Exchange 2003 tasks.
Regards
Karl
Thank you ameen, i tried
Thank you ameen, i tried adding my exchange 2010 server through following the below and it worked. The steps made my life easier.
Regards,
Kitchu.
DAG
Hi Ameen,
Thanks for your response. i am still not clear how do we treat an enviornment with DAG ?
For ex. in a env with 1 DAG 3 DB copies ( 2 Active & 1 Passive MB role srv), does it require one VSA for each server?
Thanks ,
RG
RG No you do not need a
RG
No you do not need a separate VSA (Vault Service Account) for each server.
In the VAC you will need to add each member server of the DAG and configure a Mailbox Archiving task for each server.
Where you will struggle is that when it comes to configuring the task for the passive server you will need to temporarily failover the DB containing the EV system mailbox (not to be confused with VSA) to the passive node to complete the configuration. After this is done you can move the DB back to the Active node.
Thanks
Karl
Hi RG, Nothing to worry,
Hi RG,
Nothing to worry, you just create task for your mailbox servers and EV 9 will take care the DAG related things, EV 9 is a Exchange 2010 aware software.
Since you are totaly confused, i would suggest you to set up Proof of Concept/LAB and experience the same.
Hope it will help!
Regards,
Ameen
@ Ameen
Dear Ameen,
I have tried to run the script but its not running. every thing is fine when i run Deployment Scanner i get the error of perimission.
as u mention above i tried to run the script to assing the permission to VAS but unable to do so.
Can u plz help me.
Regards
Saqib Alam
Saqib Alam|Senior Systems Engineer|Symantec Technical Specialist|
Correction to a post
Correction to a post above..
You can follow the below steps,
1. Move the VSA to Exchange 2010 server.
2. Set proper rights for VSA,
Log on to Exchange 2010 server with the accounts which has right on exchange servers and run below poweshell script,
Set-Mailbox <VSA> -ApplyMandatoryProperties
3. Configure the Exchange 2010 throttling policy on the VSA.
From exchange server 2010, copy the powershell script 'SetEVThrottlingPolicy.ps1' to local system for example to 'c:\temp'
Note: The Exchange 2010 PowerShell scripts are in the PowerShellScripts subfolder of the Enterprise Vault installation folder (normally c:\Program Files\Enterprise Vault)
Go to Exchange powershell and run this script, example: Set-Mailbox saEV –ApplyMandatoryProperties
** The command here is ./SetEVThrottlingPolicy.ps1 -user VSA **
4. Assign Exchange Server permissions to the Vault Service account.
Copy the powershell script 'SetEVExchangePermissions.ps1' to Excahnge server same as in step 3
Go to Exchange Powershell and run Example: SetEVExchangePermissions.ps1 –user <Domain>\saEV
5. Add the Exchange server into the EV as following normal porcess.
Again On the same subjet
hi , i have the same case in my envirnoment, my question is ? do i have to move the VSA mailbox from the exchange 2003 which i have now to the exchamge 2010 server .and what about the current users on the exchnage 2003 , do they will still have access to the archived items during the users mailboxs transfer.
do the mailboxs taskes for the exchange 2003 will keep running
please help me.
Would you like to reply?
Login or Register to post your comment.