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

Post a Comment

Popular posts from this blog

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center
Post a Comment
Read more

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.
Post a Comment
Read more