You may receive Error ID: 5079 (000013d7) after uninstalling Double Take software

When you uninstall/remove Double Take software from your Windows Cluster you may receive the following error message when starting Cluster Administrator.

An error occurred attempting to read properties for the ‘Double-Take Source Connection’ resource type.

Error ID: 5079 (000013d7)

image

You can alway safely ignore this error message. However to get rid of it completely just remove the Double Take Resource type from the registry.

Open registry editor and take the backup of current registry.

Delete the following key:

HKEY_LOCAL_MACHINE\Cluster\ResourceTypes\Double-Take Source Connection

image

————End Of Document —————–

Tags: Clustering, Windows Server 2003

Published Date: 20080609

Advertisements

How to rename an Exchange Server running on a Windows Cluster

Though I would agree that is not a good idea to rename your Exchange server that is running on a Windows Server Cluster, however you may need to it for various reasons. I did test this in my test environment.

I had two tasks at hand:

  1. Rename the cluster name itself
  2. Rename the Exchange Virtual Server name

How to rename the cluster:

  • To Rename the Cluster right click on the cluster name and choose rename.

image

image

  • Type the new name of the cluster and you are done.
  • Check the properties of ‘cluster name’ resource to confirm the change of name.

image

  • Take the ‘cluster name’ resource offline and bring it back online.
  • DTC resource would also have gone offline. Bring it online as well.

How to rename the Exchange Virtual Server:

  • Bring all the Exchange resources off line including the network name (Exchange Virtual Server network name).
  • Rename the Exchange Virtual Server network name resource by choosing properties and editing the parameter of the resource.

image

image

  • Bring the Exchange Virtual Servername and Exchange Virtual Server IP address resources online.

image

  • Delete the Exchange Virtual Server System Attendant resource. It is necessary because a Windows Cluster server can only run a single instance of Exchange Virtual Server.

image

  • All other dependant resources should also be deleted. choose Yes to do so.

image

  • Move all the databases and log files to an alternate location. If you do not do so Windows will not let you create the System Attendant resource and will complain that the exchange data directory is not empty.

image

  • Create a new System Attendant resource and all other dependant resources would be created automatically.
  • Bring all the resources online once and check everything is fine in the cluster administrator.

image

  • Now open Exchange System Manager and you should see both the new and the old Exchange Servers listed.

image

  • If you try removing the old server, Exchange would complain that some users still exist on the server and you cannot remove the Exchange Server.

image

  • Use the following article to find all the users whose AD attributes for current mailbox server has not yet been update to the new server and rip off the Exchange attributes from all these users.

image

  • Put a check mark against the box "This database can be overwritten by a restore" found under Mailstore -> Properties -> Database tab. Do this for all the information stores in the new Exchange Virtual Server.

image

  • Take the System Attendant resource offline from the cluster.
  • Copy back all the exchange database and log files that you had copied earlier to an alternate location.
  • Bring back the System Attendant and all other resources online.
  • Check the Mailstore of the new Exchange Virtual Server and it should now list all the users who had their mailbox on this server.

image

  • Run the MailBox cleanup Agent Exchange System Manager.

image

  • Once you run the mailbox cleanup agent all the mailboxes would appear as disconnected.

image

  • Right click on each mailbox and reconnect them to the correct username in the AD.

Tempuser01 connected to old mailbox:

image

Tempuser01 with exchange attributes ripped off:

image

Tempuser01 connected to new mailbox

image

  • Purge all other mailboxes such as SMTP and System Attendant from the new Exchange Server.

image

  • Now remove the old server from Exchange System Manager

image

image

image

—————–End of Document————-

Tags: Clustering, Exchange Server, Windows Server 2003

Published Date: 20080609