Windows Server - command to add node to existing cluster

Asked By snazz on 05-Nov-07 09:53 AM
In trying to run the wizard to add a node to a existing cluster, the message
that the service already exists appears.  This is Windows 2003 Server which
has the Cluster service installed by default.  I have run the command;
cluster node mycluster /forcecleanup, to insure that the cluster node is
removed.  It removes itself successfully.  Is there a command to manually add
this node to the cluster?  I believe the wizard is getting hung up when it
tries to create a service name called "Cluster" and it cannot since it
already exists.




Rodney R. Fournier [MVP] replied on 05-Nov-07 09:58 AM
The second, third, forth, etc. nodes join the cluster. The first one creates
it. Are you running Cluster Administrator Add a node wizard?

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
snazz replied on 05-Nov-07 10:29 AM
Yes, I am running cluster Admin to add the node?  Is there another way?
Rodney R. Fournier [MVP] replied on 05-Nov-07 10:40 AM
Yes, you can use cluster.exe from the command prompt.

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
John Toner [MVP] replied on 06-Nov-07 09:25 AM
Did the cluster node /forcecleanup remove the "Cluster Service" from this
node? If not, then the cleanup didn't quite work out and you should try
again. If needed, you might want to hack this out of the registry.

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

message
which
add
Edwin vMierlo [MVP] replied on 06-Nov-07 10:29 AM
I agree with John, but reading the origianal post it seems (or could be)
that the syntax used "cluster node mycluster /forcecleanup" was wrong. It
seems it was run for a node called "mycluster" which possibly is not a node
name, but a cluster name.

Please run the following command

cluster node /forcecleanup

and check if the cluster service is removed