Compliance of a cluster is checked based on various factors, depending on if you have HA enabled, DRS enabled or both!

• FT logging NIC speed is at least 1000 Mbps.
• At least one shared datastore exists.
• FT logging is enabled.
• VMotion NIC speed is at least 1000 Mbps.
• All the hosts in the cluster have the same build for Fault Tolerance.
• The host hardware supports Fault Tolerance.
• VMotion is enabled.

• Read more ...

Recently I found myself looking at an error which I've seen many times before with different customers View environments in which they are unable to connect to desktops getting the following error..

"The connection to the remote computer ended"

Read more ...

There is an issue with a Guest OS of either Windows Server 2008 R2 or Windows 7 running on VMware ESX/ESXi 4.x with VMware Tools installed. The display driver SVGA-II freezes intermittently and sometimes permanently requiring reset of the VM.

Read more ...

There are numerous reasons to use vSphere host profiles, namely to ensure all your ESXi hosts within a cluster are configured identically.

Storage of course is an important part of this, as we need to ensure all hosts can see the same datastores, the same pathing policy configured etc.

If not we want an alert to tell us this so we can correct - even perhaps automagically with host profiles!

However local SAS drives within the ESXi server can be detected as remote storage devices, which as you can imagine can cause an issue with this compliance checking.

If this is the case the local SAS drive "naa.xxxxx ID" needs to be presented to each ESXi server to tick the compliance box, but thats not possible as it's a local disk.

Read more ...