Now that Exchange Server 2010 has had its first birthday, it's a good time to remind folks about the built-in features for high availability, site resilience and disaster recovery in Exchange 201...
Published Dec 16, 2010
Version 1.0
Blog Post
Hi Exchange
Thanks for the info about upgrading CAS servers - if you only have two in the array, and you do this out of hours, I guess you can skip the drain stop part ? We have upgraded with no ill effects.
I thought I would return the favour and provide a step by step deployment when you are running ForeFront for Exchange. I have fully tested this so it is based on successful experience. Obviously for the HT/CAS, your procedure can now substitute that which I used.
Procedure for installation
1. Move all MailboxDatabases to a desired alternative target server**
2. Ensure both Copies and Search indexes are in Healthy state, that there are zero logs to be copied, and the latest copy timestamp is current.**
3. Run the following script to put the server into Maintenance mode :-
“C:Program FilesMicrosoftExchange ServerV14ScriptsStartDagServerMaintenance.ps1”**
(Note that you may receive a warning that this will only run when there are multiple copies of the MailboxDatabase – ignore this and continue running the script)
4. Disable CRL checking (Internet ExplorerToolsInternet OptionsAdvancedSecurityCheck for Publisher’s Certificate Revocation – untick box)
5. Stop ForeFront services . Open command prompt with elevated Administrator privileges.
Exchange HT/CAS
Path to “C:Program Files (x86)Microsoft Forefront Protection for Exchange Server”
Run fscutility /disable
At prompt, run Net Stop FSCController
Again run fscutility /disable
There will be a warning then confirmation that the MSTransport service link has been removed – Forefront is now disabled correctly
Exchange MBX
Path to “C:Program Files (x86)Microsoft Forefront Protection for Exchange Server”
Run fscutility /disable
At prompt, run Net Stop MSExchangeIS
Again run fscutility /disable
At prompt, run Net Stop FSCController
Again run fscutility /disable
There will be a warning then confirmation that the MSExchangeIS service link has been removed – Forefront is now disabled correctly
6. Copy rollup pack to local machine (this should have been done in advance – location on each machine is “C:SPs_PatchesUpdate_Rollups<Rollup_Number>”)
7. Open cmd with administrator elevated privileges or reuse Window already opened
8. Install update –next assumes this installs without any problems
9. (Optional but recommended) Reboot
10. Check event logs
11. Check services started correctly (Test-ServiceHealth)
12. Restart ForeFront services (fscutility /enable)
13. Re-enable CRL checking
14. Run the following script to take the server out of Maintenance mode :-
“C:Program FilesMicrosoftExchange ServerV14ScriptsStopDagServerMaintenance.ps1”**
15. Check MailboxDatabaseCopyStatus is normal **
16. Check event logs
17. Failover MailboxDatabases to this server (optional)**
18. Monitor for any issues
** DAG Members only
Thanks for the info about upgrading CAS servers - if you only have two in the array, and you do this out of hours, I guess you can skip the drain stop part ? We have upgraded with no ill effects.
I thought I would return the favour and provide a step by step deployment when you are running ForeFront for Exchange. I have fully tested this so it is based on successful experience. Obviously for the HT/CAS, your procedure can now substitute that which I used.
Procedure for installation
1. Move all MailboxDatabases to a desired alternative target server**
2. Ensure both Copies and Search indexes are in Healthy state, that there are zero logs to be copied, and the latest copy timestamp is current.**
3. Run the following script to put the server into Maintenance mode :-
“C:Program FilesMicrosoftExchange ServerV14ScriptsStartDagServerMaintenance.ps1”**
(Note that you may receive a warning that this will only run when there are multiple copies of the MailboxDatabase – ignore this and continue running the script)
4. Disable CRL checking (Internet ExplorerToolsInternet OptionsAdvancedSecurityCheck for Publisher’s Certificate Revocation – untick box)
5. Stop ForeFront services . Open command prompt with elevated Administrator privileges.
Exchange HT/CAS
Path to “C:Program Files (x86)Microsoft Forefront Protection for Exchange Server”
Run fscutility /disable
At prompt, run Net Stop FSCController
Again run fscutility /disable
There will be a warning then confirmation that the MSTransport service link has been removed – Forefront is now disabled correctly
Exchange MBX
Path to “C:Program Files (x86)Microsoft Forefront Protection for Exchange Server”
Run fscutility /disable
At prompt, run Net Stop MSExchangeIS
Again run fscutility /disable
At prompt, run Net Stop FSCController
Again run fscutility /disable
There will be a warning then confirmation that the MSExchangeIS service link has been removed – Forefront is now disabled correctly
6. Copy rollup pack to local machine (this should have been done in advance – location on each machine is “C:SPs_PatchesUpdate_Rollups<Rollup_Number>”)
7. Open cmd with administrator elevated privileges or reuse Window already opened
8. Install update –next assumes this installs without any problems
9. (Optional but recommended) Reboot
10. Check event logs
11. Check services started correctly (Test-ServiceHealth)
12. Restart ForeFront services (fscutility /enable)
13. Re-enable CRL checking
14. Run the following script to take the server out of Maintenance mode :-
“C:Program FilesMicrosoftExchange ServerV14ScriptsStopDagServerMaintenance.ps1”**
15. Check MailboxDatabaseCopyStatus is normal **
16. Check event logs
17. Failover MailboxDatabases to this server (optional)**
18. Monitor for any issues
** DAG Members only