The steps for upgrading an Exchange 2007 CCR to SP2 is different from the procedure that we follow for non clustered servers. Check my article for upgrading non clustered exchange servers to SP2.
Note: The procedure to upgrade Exchange 2007 CCR is the same whether you have a CCR without any service pack, with SP1 or with SP1 and any update rollups.
You can only upgrade CCR nodes by using the shell. The command to be run is Setup.com /mode:upgrade (Setup /M:Upgrade in short). You cannot upgrade CCR nodes by using the GUI.
The process in a nutshell is to upgrade the passive node first, restart, move CMS to the passive node, upgrade the CMS which makes the node the active one & then upgrade the initial active node and restart.
My lab has two CCR nodes, CCR2 (active) and CCR1 (passive). The CMS name is MBX and windows cluster is CCRCLUSTER. Both nodes have SP1 installed with Update Rollup 9. You don’t have to delete the update rollups manually.
1. Upgrade The Passive CCR Node:
Log into the passive node (CCR1 in my case) with an admin account. Make sure to stop any monitoring services which are running on the server like MOM agents. You can also put the server in maintenance mode for 30 minutes so that email alerts doesn’t fill your inbox. This is very important in a large organization as you will have a dedicated monitoring team.
Launch a command prompt window and navigate to the exchange 2007 sp2 installation directory / dvd drive. Run the command Setup.com /Mode:Upgrade
Setup runs the exchange pre-requisites check for the mailbox role.
Once the checks are completed, the following happens in order.
- Preparing the SP2 setup
- Removing the exchange files on the system
- Starts copying files from the dvd / installation folder.
- Installs the mailbox server role.
- Installs management tools
- And finalize the setup.
Restart the server once the command completes successfully.
2. Upgrade the Clustered Mailbox Server
Once the passive server gets restarted and is back online, it will be running Exchange 2007 SP2. Do note that the active node is still online and serving the users. We need to upgrade the Clustered Mailbox Server (CMS) now, before we upgrade the present active node.
Before upgrading the CMS, we need to stop the CMS that is running on the active node and then move it to the passive node (upgraded server). This step will result in exchange server becoming unavailable for CMS users and hence has to be done out of hours.
Log into the passive node, launch the exchange shell and run the following command to stop the CMS. You can also do it from the console if you prefer to do so.
Stop-ClusteredMailboxServer MBX –StopReason “SP2 Upgrade”
Confirm the step by pressing “Y”.
Make sure that the cluster status is Offline.
Once the cluster is stopped, move the CMS to the passive node from the console or by running the following command from the shell.
Move-ClusteredMailboxServer MBX –TargetMachine CCR2 –MoveComment “SP2 Upgrade”
Confirm the step as well.
Navigate to the exchange 2007 sp2 installation folder /dvd and upgrade the CMS by running the following command. You can’t use the console for this step.
Setup.com /UpgradeCMS
Setup runs a pre-requisite check before upgrading the CMS.
Once the setup was completely successfully, it brought the stopped cluster online & now we have an upgraded CCR running on one node. You can check the status of the cluster using Failover Cluster Management tool. Users can start connecting to the cluster from now on.
3. Upgrade The Initial Active Node (Now Passive)
Login to the present passive node (initial active node) with an admin account. Launch a command prompt window and navigate to the exchange 2007 sp2 installation directory / dvd drive. Run the command Setup.com /Mode:Upgrade
Setup runs the pre-requisite check and installs the service pack.
Restart the server and now you have an Exchange 2007 SP2 CCR.
Tweet This!
59 comments:
Good post.. very helpful..
Thanks Deepak.
Great post, very helpful... got a few questions....
We are running Exch 2007 sp1 in a CCR envirnoment.
We have 6 Exch servers in total (2 cas, 2, hub and 2 mailbox) One of each server type in located in our "active datacenter" and the other in our DR site.
1. Can we move the cluster from active to passive using the GUI wizard in SP1 ?
2. we have our CAS and hub roles on different servers, what is the process for upgrading these servers in a CCR envirnoment ?
Great site, keep up these great blogs.
Thanks
Liam
Hi Liam,
1. Yes. You can move the clusteted mailbox server from one node to another from the console.
2. The order of SP2 installation is as follows. CAS - UM - HUB - EDGE - MAILBOX. So, install SP2 on your CAS and HUB servers & CCR at the end.
Rajith.
Hi Liam,
In case you want the path to manage CMS from EMC, navigate to Server Config -> Mailbox -> Select your CMS Server, right click & select "Manage Clustered Mailbox Server". It will open a wizard and give you options to start/stop/move cluster.
Rajith, thank you so much for these great responces, I apprecate your help, keep up posting these great blog. I have learned a deal from your blog over the past 2 days. Thank you.
Good to know that you like my articles.
Thanks.
Really Thank You. Very good article. I followed your instructions and all went fine.
Oscar Soto
MVP Directory Services
Glad to hear that the article helped you Oscar.
Does need to re-apply the edge subscription after upgrading to sp2 the edge servers?
Thanks,
Noah
Hi,
is it necessary to run the sp2 on the domain controllers too? If yes, which is the preferred order, before or after upgrading the exchange environment?
Great site!
Thanks,
Peter
Hi Peter,
SP2 is for Exchange servers only. So, if you have your exchange running on a DC (single server environment), then you need to install exchange SP2 on the DC, otherwise NO!
Exchange SP2 extends the AD schema, but the setup will take care of it and hence doesn't have to be run seperately (although you can). But, that process is different to running the actual SP2 setup.
Rajith.
Hi Rajith,
thanks a lot for the quick response.
This is a really useful blog.
Peter
Thanks Peter.
Rajith, One more question.. I just discovered that we were still on UR5, do we need to update to UR9 before installing SP2 or does sp2 contain all necessary updates.
Thanks
Liam
Hi Liam,
The procedure is the same whether you have an exchange 2007 ccr without any service packs, with SP1 or with SP1 and any update rollups.
Thanks,
Rajith.
Wonderful thank you as always... I am loving all the exch 2010 blogs as well, keep the coming.
Thanks
Liam
Good to know that you are following my blog Liam. Let me know if you want me to write about a specific topic.
Thanks,
Rajith.
My 2003 64bit SP2 CCR cluster worked fine in the SP2 upgrade at first. Passive node went fine, upgradecms went fine and the mail server is happy on Node B. However every time I try to run setup /m:upgrade on Node A it fails with the error:
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
Exchange Server setup encountered an error.
Nothing in the logs. Any ideas?
Got the fix - strangely enough powershell was the issue. Running the setup.com /m:upgrade froma command prompt made it all work.
I wasn't around for two days. Good to know that you have sorted the issue Giasone.
Hi Rajith,
Is there any specfic steps that needs to be followed for upgrading forefront for exchange SP2 in a CCR environment.
Regards
Birju Ashramath
Hi Birju Ashramath,
Use Fsutility (command line) to disable the forefront security during the sp2 upgrade and enable it afterwards. Fsutility /disable and Fsutility /enable. Check http://support.microsoft.com/kb/929076 for more info.
Couple of questions...
First, approx how long did it take for the /upgradecms step? I know the time will vary depending on size and number of mailboxes but I'm just looking for a ballpark so I know how early I need to come in ;)
Second, we run both CCR and SCR. CCR is in our server room with the SCR configured with a D/R site. If I run all of these steps in the CCR, do I need to run /upgradecms for the SCR also or would /upgradecms during the CCR install take care of that?
Thanks for any advice you can offer!
My /upgradecms was against a CCR cluster with 400 users and took about 20 minutes. My nodes are quad-core with 12GB of RAM each - not sure if that changes the timing or not.
Hi,
The upgrade process shouldn't take that long, like long hours. I would suggest to do the work in the weekend (friday evening being the best) rather than coming early on a weekday and finding out that the upgrade is still running while your staff starts to come in.
Thanks Giasone for your input.
Rajith,
This was a great post, thanks for the hand. Just one change you may want to consider is to run the following on CCR2 (Previously passive now active node): Navigate to the exchange 2007 sp2 installation folder /dvd and upgrade the CMS by running the following command. You can’t use the console for this step.
Setup.com /UpgradeCMS
Thanks again!
-Aaron
Thanks Aaron.
Its good post but we are facing a problem below:
[PS] E:\Exchange SP2\E2K7SP2EN64>.\setup /prepareschema
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
Organization Checks ......................... COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema
Progress ......................... FAILED
Active Directory server CCRMBQSI.exqsi.com is not available. Error message:
The LDAP server returned an unknown error.
The Exchange Server Setup operation did not complete. For more information, visi
t http://support.microsoft.com and enter the Error ID.
Exchange Server setup encountered an error.
Help me too to resolve thi problem.
Deepak Khandelwal said...
Good post.. very helpful..
02 September 2009 15:40
Rajith Jose Enchiparambil said...
Thanks Deepak.
03 September 2009 19:43
Anonymous said...
Great post, very helpful... got a few questions....
We are running Exch 2007 sp1 in a CCR
giasone said...
My /upgradecms was against a CCR cluster with 400 users and took about 20 minutes. My nodes are quad-core with 12GB of RAM each - not sure if that changes the timing or not.
06 October 2009 20:42
Rajith Jose Enchiparambil said...
Hi,
The upgrade process shouldn't take that long, like long hours. I would suggest to do the work in the weekend (friday evening being the best) rather than coming early on a weekday and finding out that the upgrade is still running while your staff starts to come in.
Thanks Giasone for your input.
07 October 2009 08:44
Aaron said...
Rajith,
This was a great post, thanks for the hand. Just one change you may want to consider is to run the following on CCR2 (Previously passive now active node): Navigate to the exchange 2007 sp2 installation folder /dvd and upgrade the CMS by running the following command. You can’t use the console for this step.
Setup.com /UpgradeCMS
Thanks again!
-Aaron
15 October 2009 13:52
Rajith Jose Enchiparambil said...
Thanks Aaron.
23 October 2009 15:20
Ravinder said...
Its good post but we are facing a problem below:
[PS] E:\Exchange SP2\E2K7SP2EN64>.\setup /prepareschema
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
Organization Checks ......................... COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema
Progress ......................... FAILED
Active Directory server XXXXXX.DOMAIN.com is not available. Error message:
The LDAP server returned an unknown error.
The Exchange Server Setup operation did not complete. For more information, visi
t http://support.microsoft.com and enter the Error ID.
Exchange Server setup encountered an error.
Help me too to resolve thi problem.
This was a great post, thanks for the hand. Just one change you may want to consider is to run the following on CCR2 (Previously passive now active node): Navigate to the exchange 2007 sp2 installation folder /dvd and upgrade the CMS by running the following command. You can’t use the console for this step.
Setup.com /UpgradeCMS
Thanks again!
-Aaron
15 October 2009 13:52
Rajith Jose Enchiparambil said...
Thanks Aaron.
23 October 2009 15:20
Ravinder said...
Its good post but we are facing a problem below:
[PS] E:\Exchange SP2\E2K7SP2EN64>.\setup /prepareschema
Welcome to Microsoft Exchange Server 2007 Unattended Setup
Preparing Exchange Setup
No server roles will be installed
Performing Microsoft Exchange Server Prerequisite Check
Organization Checks ......................... COMPLETED
Configuring Microsoft Exchange Server
Extending Active Directory schema
Progress ......................... FAILED
Active Directory server XXXXXX.DOMAIN.com is not available. Error message:
The LDAP server returned an unknown error.
The Exchange Server Setup operation did not complete. For more information, visi
t http://support.microsoft.com and enter the Error ID.
Exchange Server setup encountered an error.
Help me too to resolve thi problem.
Great post, very helpful... got a few questions,
1. CMS upgrade should be done via Exchange Shell.
2. The Distributed Transaction Coordinator serivce must be started before setup can continue
3. Forefront should be disabled prior to upgrade.
Please clarify...
Hi Anonymous,
Answers below.
1. True. It can only be done using shell.
2. DTCS service will be running as normal. Doesn't have to pay much attention to it.
3. The original release (RTM) version of Forefront Security for Exchange Server is incompatible with Exchange 2007 SP2.
You must either remove Forefront Security for Exchange Server or upgrade it to a later version before you can upgrade to Exchange 2007 SP2. The Exchange 2007 SP2 Setup program does not pass prerequisites if the computer is running the RTM version of Forefront Security for Exchange Server.
If you are running the latest version of Forefront Security for Exchange Server, you must stop all Forefront services before you run the Exchange 2007 SP2 Setup program.
Hi Rajith Jose,
Thanks for the quick response. the DTCS service is not running on our mailbox servers. it has been disabled. we are running Forefront version 10.1.0746.12. I hope we don't have to remove it before upgrade to SP2.
The Exchange 2007 SP2 Setup program does not pass prerequisites if the computer is running the RTM version of Forefront Security for Exchange Server.
So, run and see if you are not sure about the version of Forefront.
Hi Rajith Jose,
I would like to add one more prerequisit. Windows Installer 4.5 should be installed before upgrading to SP2.
Yes, that is right Anonymous. I will add it. Thanks.
Hello! :)
Any difference here if one is using windows server 2003 or windows server 2008 on the CCR-servers?
Hi Anonymous,
The process is the same.
Hi
We have Exchange 2007 CCR with Sp1, 2 Hub Server , One Edge all with Sp1. can anyone suggest which server we should update first with Sp1. Step to install sP1 is same for Sp2.
Thanks in advance
Can anyone confirm estimated downtime when upgrading to SP2? Is it the number of mailboxes or the size/number of the mailboxstores that determin the downtime? What are you guys experiencing? :)
Hi Anonymous,
The order to install SP1/SP2 is CAS, HUB, EDGE, Mailbox/CCR.
Namestay Rajith,
Thanks for the info. I am getting an error on the Mailbox check due to the account NOT being an enterprise admin OR Org admin. I have an environment where the Exchange 2007 servers have been delegated for installation. I have had no problem installing Sp2 on non-ccr servers that were provisioned in the same manner.
Please advise why this happens with command-line version and CCR upgrade.
Hi All,
This is a great manual. But there's a problem with the servicepack regarding the backup plugin on the 2nd node (it's not being installed)
see http://social.technet.microsoft.com/Forums/en-US/exchangesvravailabilityandisasterrecovery/thread/1e296b90-c959-4e73-ac2c-213192f11eae
I've written a solution for this issue.
greets
Thanks Greets.
In regards to downtime, the downtime is not huge - it's probably been on the order of 15 minutes tops for every server I've done.
It goes like:
Passive Node: Down 15 minutes then reboot.
CMS: Down 5 minutes, tops. (This is a complete downtime though, no service during this time!)
Former Active Node: Down 15 minutes then reboot.
Now, a real stinker here is that the SP2 install CAN, in some cases, be too much downtime for your CCR to handle. In one cluster I've upgraded recently, there were 2 days of backed up logfiles (yes, someone hadn't checked the backup server) and between that and the various downtimes the CCR decided that the databases were too far out of sync, and I had to do a complete reseed of 500GB of mail. Not fun.
Thanks for the info Gurm42.
before you upgrade, do you have to stop the shipping of log files from the active to the passive? or do you just let it stop on its own and let the cluster figure out that the other node is down?
thanks,
markB
Hi Anonymous,
You upgrade the passive node first & restart. Then move the cluster to the restarted passive node and stop the cluster.And continue...
You don't have to manually stop the log shipping.
Thanks for this great post. I'm just wondering about rolling back a failed upgrade. I understand that SP2 cannot be removed. Let's say the node 1 upgrade has been successful and the CMS upgrade fails. No upgrade has been started on node 2 at this point. Do you know what will be upgraded during the CMS upgrade and what we would do if this fails?
Hi, great article and well described, when I try to apply SP2 on my CCR cluster I receive an error at the point of "Removing Exchange Files", the full error is as follows:
Unable to remove product with code 24b2c164-de66-44fe-b468-a46d9d5e6b31. Fatal error during installation. Error code is 1603. Last error reported by the .msi package is "Could not open key:UNKNOWN\Components\6f949e36cb3004c50af18c3b9b1a1ee8\461c2b42ggedef444b864ad6d9e5b613. Verify that you have sufficient access to that key, or contact your support personnel.
The 2 nodes are running Windows Server 2008 SP2, have you ever seen anybody with this error before? I have the DOS screen shot of the error if you need to take a look.
Many thanks.
Hi Stephen,
Does the account you are using have Domain admin and Exchange Org Admin rights? Have you successfully updated your CAS and HUB to SP2?
Do you have enough space on the server? Any AV locking the files?
Hi Rajith, thanks for getting back to me. I'm using the administrator account and I checked it is a member of the groups above, SP2 installed without any issues on my CAS & HUB servers. The server has 5Gb free and no AV running.
Thanks.
Stephen,
Are you trying to install SP2 on the passive CCR? Or was that a success?
I'm trying on the passive node first and this is where I got the initial failure.
Hi Stephen,
Make sure that the account you are using has local admin rights on this passive node. Check the "Local users and groups" on this server and see the "Administrators" group. Is this account you are using listed there?
Just checked and the Domain Admins group is in there which my account is a member of.
Post a Comment