If you are adding a new node to an existing cluster that is being managed by System Center Virtual Machine Manager 2008 (SCVMM), or if you had to rebuild a node of a cluster and need to add it back, here are the steps that are required:
First, here is the existing cluster:
We will add one more node so that we have nodes:
Next go to the SCVMM server and run a refresh:
Once the refresh is done we will see the new node in a pending state:
Next, right-click on the node and select "add to host cluster":
Once the node is added you will see both nodes\hosts back in SCVMM console as a cluster:
Note that when we add the host to SCVMM it installs the agent remotely onto it automatically. For Windows Server 2008 (except Core) we can install the client from the GUI manually if required. See http://technet.microsoft.com/en-us/library/bb740757.aspx for more details. If you are using Windows Server 2008 Core you will need to follow the method below to install the SCVMM agent:
1. Install the VC Redist first, which is located on the SCVMM disk at : [DVD]\prerequisites\VCRedist\
2. Install the SCVMM agent by launching the following MSI command:
For 64-bit OS, msiexec.exe –I [DVD drive]\amd64\msi\Agent\vmmAgent.msi; For 32-bit OS, msiexec.exe –I [DVD drive]\i386\msi\Agent\vmmAgent.msi;
For 64-bit OS, msiexec.exe –I [DVD drive]\amd64\msi\Agent\vmmAgent.msi;
For 32-bit OS, msiexec.exe –I [DVD drive]\i386\msi\Agent\vmmAgent.msi;
Dhaval M Bhadeshiya | System Center Support Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode The System Center Essentials Team blog: http: http://blogs.technet.com/b/systemcenteressentials The Server App-V Team blog: http: http://blogs.technet.com/b/serverappv
Actually, when we use the steps you outline here, all the VMs go into the "Unsupported Cluster Configuration" status when the second node is added. While in this status, no management of the VMs are possible.
This is due to the fact that the networks defined on the first Hyper-V Host are not configured yet on the second Hyper-V Host.
We have found it preferably to:
1. Add the new host to VMM
2. Define all networks on the new host the same as the other hosts in the cluster.
3. Add the new host to the cluster using Failover Cluster Manager
VMM automatically moves the host from a standalone host as now being part of the cluster, and the VMs doesn't end up with the "Unsupported Cluster Configuration" status.
@Kare you say all of the VM's go into the Unsupported Cluster Configuration?
Are you adding a new node? Or are you re-adding a node that has VM's on it.
I would assume that before you added it to either SCVMM or to the cluster you would have to have everything exactly the same as the other nodes, networks etc.
I just want to know which way is recomended or if it does not matter are there any things NOT to do.
This method ensures there is quick synchronicity between the configuration state in both Hyper-v and Failover clustering and the VMM datastore (which is is where the console pulls from initially and updates based upon state changes in the environment.