About Me

My photo
This blog has been created to share technical information, interesting innovations that I notice on daily basis and Architectural/Consulting overview of various technologies. My areas of interest, on which I would be blogging, are VMware, Microsoft and Citrix Technologies. I hope you will enjoy this blog and share your experience with me.

How to Manually Uninstall Windows 2003 Cluster

First try Microsoft KB http://support.microsoft.com/kb/282227/en-us but if that fails, you can perform the following using all or some of the following steps where applicable. The example below is where no eviction or force cleanup has taken place. This is the last remaining node in a cluster.

1.) Unload the cluster hive via the Registry Editor --> Select HKLM\Cluster --> Menu Bar --> File --> Unload Hive
2) Delete HKLM\System\CurrentControlSet\Services\clusnet and clussvc keys
3.) Change the Clusdisk startup type to "disabled" in the Device Manager --> View --> Show Hidden Devices --> Non Plug and Play --> Cluster Disk Properties --> Driver Tab

HKLM\System\CurrentControlSet\Services\clusdisk\
  Value 1
  Name:            Start
  Type:            REG_DWORD
  Data:            0x4

Also delete all but the HKLM\System\CurrentControlSet\Services\clusdisk\ and it's security subkey. The registry text export looks like the following example taken from a standalone Windows 2003 EE node where cluster wasn't installed:

Key Name:          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk
Class Name:        <NO CLASS>
Last Write Time:   6/19/2006 - 3:20 PM
Value 0
  Name:            Type
  Type:            REG_DWORD
  Data:            0x1

Value 1
  Name:            Start
  Type:            REG_DWORD
  Data:            0x4

Value 2
  Name:            ErrorControl
  Type:            REG_DWORD
  Data:            0x1

Value 3
  Name:            Tag
  Type:            REG_DWORD
  Data:            0x7

Value 4
  Name:            ImagePath
  Type:            REG_EXPAND_SZ
  Data:            system32\DRIVERS\ClusDisk.sys

Value 5
  Name:            DisplayName
  Type:            REG_SZ
  Data:            Cluster Disk Driver

Value 6
  Name:            Group
  Type:            REG_SZ
  Data:            Filter

Key Name:          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Security
Class Name:        <NO CLASS>
Last Write Time:   6/19/2006 - 3:20 PM
Value 0
  Name:            Security
  Type:            REG_BINARY
  Data:           
00000000   01 00 14 80 b8 00 00 00 - c4 00 00 00 14 00 00 00  ....¸...Ä.......
00000010   30 00 00 00 02 00 1c 00 - 01 00 00 00 02 80 14 00  0...............
00000020   ff 01 0f 00 01 01 00 00 - 00 00 00 01 00 00 00 00  ÿ...............
00000030   02 00 88 00 06 00 00 00 - 00 00 14 00 fd 01 02 00  ............ý...
00000040   01 01 00 00 00 00 00 05 - 12 00 00 00 00 00 18 00  ................
00000050   ff 01 0f 00 01 02 00 00 - 00 00 00 05 20 00 00 00  ÿ........... ...
00000060   20 02 00 00 00 00 14 00 - 8d 01 02 00 01 01 00 00   ...............
00000070   00 00 00 05 04 00 00 00 - 00 00 14 00 8d 01 02 00  ................
00000080   01 01 00 00 00 00 00 05 - 06 00 00 00 00 00 14 00  ................
00000090   00 01 00 00 01 01 00 00 - 00 00 00 05 0b 00 00 00  ................
000000a0   00 00 18 00 fd 01 02 00 - 01 02 00 00 00 00 00 05  ....ý...........
000000b0   20 00 00 00 23 02 00 00 - 01 01 00 00 00 00 00 05   ...#...........
000000c0   12 00 00 00 01 01 00 00 - 00 00 00 05 12 00 00 00  ................

4.) Ensure the following files are the only ones in c:\windows\cluster.

TIP: You can move clusdb or any files or logs to another folder if you want to reference them to view old configuration data.
        If you prefer, just delete the other files and leave the remaining.

clusfolder

5.) Make sure the following registry key is present with the following values:

NOTE: The key should be present already with 2 values but just delete the extra ones and change the ClusterInstallationStage value to 1.

Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Cluster Server
Class Name:        <NO CLASS>
Last Write Time:   9/8/2006 - 8:53 PM
Value 0
  Name:            ClusterInstallationState
  Type:            REG_DWORD
  Data:            0x1

Value 1
  Name:            ClusterInstallationDirectory
  Type:            REG_SZ
  Data:            C:\WINDOWS\Cluster

6.) Restart the node.
7.) Double-check your modifications to make sure they didn't change from the reboot or you overlooked anything.
8.) You will now be able to access your old quorum, so move or delete the MSCS folder.
9.) You should now be able to install cluster (new cluster or add node to cluster).
10.) If you are installing a new cluster (or adding a node back to a cluster) with the same name as the pre-existing one, you should see passing checks for the analyzing configuration section of the cluster install wizard:

newwiz

Don’t forget to leave your comments :)

Thanks,
Aresh

1 comment:

Unknown said...

Areash, this did work fine. I was trying to correct some errors left over from when my server was actually part of a cluster but I am repurposing it. Everything runs fine now and I bet I could reconfigure a cluster if I wanted. But like I said, the best part is that my server is COM+ and DTC and Cluster error free.

My Blog List