• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3466
  • Last Modified:

Remove an Exchange 2007 CCR Cluster


I am preparing for a migration from Exchange 2007 running on Windows Server 2008 to Exchange 2010 running on Windows Server 2008 R2 and one of the things we are going to do is implement Database Availability Groups (DAG) instead of CCR.
In preperation for this we will need to figure out how to properly destroy/remove our CCR cluster without causing any damage to the overall arcitecture.  We would like to remove the CCR portion and rebuild one of the current CCR machines as a 2010 Database Server.  In order to sucessfully complete this we will need the other member of the CCR cluster to remain functional while we move mailboxes.

Has anyone done this yet?  Does anyone have any suggestions on the best way to accomplish this?

I found the following Technet Artcle but I am wondering if anyone has any other articles/suggestions before we proceed: http://technet.microsoft.com/en-us/library/bb885058(EXCHG.80).aspx

Not sure on the exact steps&

1. Use the Exchange Server 2007 SP1 Setup Wizard to remove the passive clustered mailbox role from a node in a CCR environment (http://technet.microsoft.com/en-us/library/bb124756(EXCHG.80).aspx)

2. Then what?  It would seem that I would still have a CCR cluster that is utalizing the File Share Witness to operate.  How do you remove the cluster completely but maintain a functional enviroment?

Thank you for any help you can give,
  • 2
2 Solutions
brownmattcAuthor Commented:
But once you evict a node don't you still have a functioning cluster using the node that is still in place and the File Share Witness (FSW)?

After one node is gone what is the process for removing the cluster service from the second node?  Will that return a CCR configuration to a standard configuration with only one mailbox server?

The whole idea is to move the orginization to a point where there is no CCR cluster.  Just like CCR was never in place.

you cannot,

When you installed exchange you installed a cluster, there is not way to "convert" your installation to a non-clustered configuration . you could

1) Install your exchange 2010 DAG on new servers, move all mailboxes to it and then uninstall/remove the exchange cluster
2) remove the passive node as explained in the technet article, use this node as the first 2010 cluster, move mailboxes finish removing the 2007 cluster

brownmattcAuthor Commented:
Here are the steps I did to complete this successfully:
1. How to Remove the Passive Mailbox Role from a CCR Environment - I did this with Add/Remove programs - http://technet.microsoft.com/en-us/library/bb124756(EXCHG.80).aspx
2. Joined the machine to a workgroup in order to completely remove it from the domain.
3. Reinstalled the same box with Windows Server 2008 R2.  Added machine to domain.
4. Installed Exchange 2010 Mailbox Role.
5. Moved all user mailboxes to Exchange 2010
6. How to Remove the Active Mailbox Role from a CCR Environment - As I wanted to remove the CMS and the Active Role I did this through Add/Remove Programs - http://technet.microsoft.com/en-us/library/bb123940(EXCHG.80).aspx
7. Joined the machine to a workgroup to completely remove it from the domain.
8. Removed the CMS from Active Directory.
9. Verified that the Exchange CMS and Mailbox servers were not showing in the Exchange Management Console on both 2007 and 2010.
10. Verified that the Exchange 2007 Database was not showing on the Exchange 2010 Console.

Other tasks to keep in mind to decommission your Exchange 2007 Environment
1. Uninstall Exchange Management Tools from all machines (Domain Controllers, Workstations, etc.)
2. Uninstall Exchange 2007 from Hub Transport and Client Access servers.  Remove those servers from the domain.

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now