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

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

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...

Apple iPhone Text responses go to wrong country code

A user wrote: Recently I went to Portugal and when I was there I bought a sim card and put it in my iPhone 11 Pro, with my primary e-sim still in it. When I got home to Australia, I deactivated the Portugal sim-card, deleted it and took the sim card out. Now when someone call me I respond with text, my iPhone changes the calling numbers country code to +31. I had the same problem. Despite turning "Dial assist" on/off, checking Country, Language and all the suggested stuff it did not work for me. What I did at the end was deleting country prefix from contact numbers --> Save --> Added country prefix again . It works now.