Skip to main content

Upgrading a Single Copy Cluster to Exchange 2007 SP1

Upgrading the Exchange 2007 single copy cluster requires a bit changed steps than in previous Exchange Server's releases. You still have to work on a passive node tough :)))

I suggest that you run Microsoft Update on all nodes prior to Exchange SP1 install. The most important part is .NET Framework 2.0 SP1 update, since Exchange is .NET Framework application!

The change from previous versions is that there is no GUI for updating the cluster. You have to do the upgrade from command prompt.

Let's presume that our nodes are named NODE1 and NODE2. Steps are as follows:

On NODE2

  1. Move all cluster groups to NODE1 if they are not already active on NODE1
  2. Put Windows Firewall/Internet Connection Sharing (ICS) service to manual and then START IT, since Setup will add Windows Firewall exceptions for Exchange services
  3. Stop any services that have open handles to performance counters (Performance Logs and Alerts and any Microsoft Operations Manager agents), since performance counters are changed during setup
  4. Stop, and then restart the Remote Registry service
  5. In command prompt navigate to Exchange 2007 SP1 files and run (files must be available locally):
Setup /m:upgrade
  1. Restart NODE2 after setup completes
  2. Open Cluster Administrator and take Exchange Server's Group OFFLINE !!!
  3. Move all Groups to NODE2 (THIS SERVER)
  4. In command prompt navigate to Exchange 2007 SP1 files and run:
Setup /upgradecms
  1. After this completes Exchange Services on NODE2 are started and you are ready to move to NODE1

On NODE1

  1. Put Windows Firewall/Internet Connection Sharing (ICS) service to manual and then START IT, since Setup will add Windows Firewall exceptions for Exchange services
  2. Stop any services that have open handles to performance counters (Performance Logs and Alerts and any Microsoft Operations Manager agents), since performance counters are changed during setup
  3. Stop, and then restart the Remote Registry service
  4. In command prompt navigate to Exchange 2007 SP1 files and run (files must be available locally):
Setup /m:upgrade
  1. Restart NODE1 after setup completes
  2. Move all cluster groups back to your preferred active node

On NODE1 and NODE2

  1. Stop and disable the Windows Firewall/Internet Connection Sharing (ICS) service on both nodes.

Comments

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.