I´m really thankful with your great article but this is a full Windows Server 2008 cluster and not just MS SQL Server Cluster as informed on the title.

Tks as well and Best Rgds

Comment updated:

Hi Bora,

Kindly disrespect my first comment (on part 2) and sorry about the mistake. All my doubts was explain on part 3.

Tks again

Thanks for all your comments and compliments. I am sure these comments will help anyone that faces such problems. They add great value to the article.

Thank you again and keep support :)

I would like to add some additional info that is important when installing on VMware.

The following issues may potentially come up when the cluster is created and the Cluter Validation tests are run.

It’s an area that causes a lot of frustration for a lot of people.

a. Validate Windows Firewall Configuration test fails.

When (ESX) cloning the 2nd server, the NICs may have the same GUIDs. If that is the case, validation will show a failure with the “Windows Firewall Configuration” (and probably a few other network related issues).

To resolve this, use this PowerShell command to identify the GUIDs.

Get-WmiObject Win32_NetworkAdapter | fl Name,GUID

(this is simply a WMI call -nothing fancy)

If they are the same, then, using Device Manager, uninstall both NICs on one of the servers, reboot that server and retest. Validation should pass the Network tests this time.

b. Validate SCSI-3 Persistent Reservation fails

This is most likely attributed to the fact that both nodes of the Windows Cluster are on the SAME ESX host.

Separating them to different hosts usually resolves this problem (HOWEVER….read on)

Setting a VMWare DRS affinity rule to keep the VMs separate will work, BUT, not if the machines are already on the same host and powered up.

If the rule is set up after the VMs are powered and on the same host and DRS is executed, the rule will fail with this error.

“Virtual Machine is configured to use a device that prevents the operation: Device ‘SCSI controller 1; is a SCSI controller engaged in bus-sharing.”

(to see this message, do a manual Migrate)

To successfully move one of the nodes to another ESX host you will need to power down one of the VMs and then migrated it. After power up the DRS rule will work.

Again, many thanks for the article. It is great to see all the steps detailed out!