showing posts tagged with 'vsphere'
by lunarg on May 8th 2017, at 14:32
A very common practice when setting up SAN storage on a VMWare cluster is to configure the storage path policy to be set to "Round Robin" to properly benefit from MPIO in addition to standard failover. However, if the cluster consists of many nodes or there are many volumes, this can take up quite a lot of time if you configure this using the (Web)GUI. A better way to adjust the setting for the entire cluster is through PowerCLI.

The one-liner:

Get-VMHost <Cluster-or-Host> | Get-ScsiLun -LunType "disk" | Where {$_.MultipathPolicy -ne "RoundRobin"} | Set-ScsiLun -MultipathPolicy RoundRobin

The cmdlet selects a cluster or host, gets all LUNs which are of   ...
by lunarg on February 6th 2017, at 16:30
A list with direct links to VMware vSphere clients. Saves you a lot of time when you need to (re)install many different versions.

Starting with 6.5, the vSphere client is no longer available.

VMware vSphere Client 6.0 Update 2a: VMware-viclient-all-6.0.0-4437566.exe

VMware vSphere Client 6.0 Update 2: VMware-viclient-all-6.0.0-3562874.exe

VMware vSphere Client 6.0 Update 1: VMware-viclient-all-6.0.0-3016447.exe

VMware vSphere Client 6.0: VMware-viclient-all-6.0.0-2502222.exe

VMware vSphere Client 5.5 Update 3d: VMware-viclient-all-5.5.0-3705931.exe

VMware vSphere Client 5.5 Update 3: VMware-viclient-all-5.5.0-3024345.exe

VMware vSphere Client 5.5 Update 2: VMware-viclient-all-5.5.0-1  ...
by lunarg on October 26th 2015, at 14:00
When attempting to unmount or delete a VMFS datastore on a cluster, you may get the message that the resource is still in use, even though all the VMs have been moved off the datastore, or that Storage I/O Control (SIOC) is enabled on it (usually when attempting to unmount).

To circumvent the issue, temporarily stop SIOC, unmount/delete the datastore, then start SIOC again. If an unplanned Permanent Device Loss (PDL) is invoked when Storage IO control enabled on a storage device (iSCSI device or FC), the ESX host cannot remount the VMFS datastore, and also the steps below are then also required in order to be able to remount the datastore.

On each of the ESX hosts (if there's more than one  ...
by lunarg on August 21st 2015, at 10:23

If your vCenter server has a self-signed certificate, you will get a warning about this when connecting to it from vSphere PowerCLI. You can disable this warning through PowerCLI with the Set-PowerCLIConfiguration cmdlet.

  1. Start an elevated vSphere PowerCLI (right-click, Run as Administrator).
  2. Enter the following cmdlet:
    Set-PowerCLIConfiguration -InvalidCertificateAction Ignore
    Press Enter again to confirm the change.

After making the change, new connections to the vCenter server will no longer produce a warning about the certificate.

by lunarg on July 7th 2015, at 11:54
When you enable the ESXi Shell or SSH on a particular host in a vSphere cluster, a warning will appear on a ESX host:

ESXi Shell for the host has been enabled

or SSH for the host has been enabled

This is normal behaviour, but you can turn off these warnings for each of the hosts.

Note that prior to vSphere 4.1 Update 2, it is not possible to suppress the warnings.

Open vSphere Client.

Select the ESX host. From the Configuration tab (right pane), click Advanced Settings.

Navigate to UserVars → UserVars.SuppressShellWarning.Set its value to 1.

Click OK to confirm. The warning will disappear immediately.

Log on to vSphere Web Client.

Select vCenter from the Home menu. Select Host  ...
by lunarg on July 3rd 2015, at 15:39
The vSphere Web Client may display the following error:

Failed to verify the SSL certificate for one or more vCenter Server Systems: https://vCenter-Server-FQDN:443/sdk


Could not connect to one or more vCenter Server Systems:https://vCenterFQDN:443/sdk

Additionally, objects such as hosts or VMs are not displayed in the vSphere Web Client.

These errors usually occur with a re-installation or upgrade of vCenter Server, where the vCenter Server is registered to the same vSphere SSO more than once.

The faulty registration needs to be resolved by unregistered all duplicate vCenter Server instances from vSphere SSO, so only the correct registrations remain.

You will have to unregister al  ...
by lunarg on May 20th 2015, at 16:45
After configuring HA for a vSphere 5 cluster, you may encounter the following warning on each ESX host:

Configuration Issues
The number of vSphere HA heartbeat datastores for this host is 1, which is less than required: 2

vSphere 5 introduces datastore heartbeats in addition to network hearts, which allows to distinguish between a network-isolated host and a crashed host. In order for datastore heartbeats to work properly, vSphere requires at least 2 shared datastores available on every host in the cluster. If there's less than 2 shared datastores, datastore heartbeats will not function properly, resulting in the configuration issue message.

If you only have one shared datastore and wish   ...
by lunarg on May 6th 2015, at 09:20

You may have noticed that running the VMWare vSphere client on a display with higher DPI settings causes problems with the mouse cursor alignment when working inside a VM. This is because of a mismatch between the DPI settings of the VM and the DPI settings of your computer.

To resolve, right-click the shortcut to the client, go to the Compatibility tab, and enable Disable display scaling on high DPI settings.

The downside of this method is that there will be misalignment of some parts in the client, but it is still workable and moreover, it solves the mouse issue in a VM.

by lunarg on April 20th 2015, at 15:42
There are two methods of uninstalling vSphere Replication from your vcenter, depending on whether or not the replication appliance is still present and accessible.

Unregister the appliance from vCenter, then turn off and delete the appliance.

If not turned on, turn on the replication appliance.

Stop all replications in both directions.

Disconnect any open connections to other replication sites.

Connect to the VAMI of the appliance through web: https://vr-appliance-address:5480

From the Configuration tab, click Unregister from vCenter server.

In the vSphere Web client, power off and delete the replication appliance. The plug-in will be uninstalled automatically.

by lunarg on November 26th 2014, at 10:19

You can use the Guided Search Wizard for VMWare Compatibility Matrix to figure out if a certain version of ESX or feature is supported by a certain server or hardware platform:

by lunarg on August 14th 2014, at 14:17
In certain cases when deploying machines from a template using deployment customization, parts of this process may fail. As a result, upon each reboot, the system may try to re-run the customization process, and the following message is displayed at each startup:

VMware Image Customization in progress

To remove any pending sysprep customization routine, you can manually remove the reference to it by editing the Windows Registry

Start regedit.exe.

Navigate to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\.

Change the value of BootExecute. Remove the part that says sysprepDecryptor.exe. Leave the other parts of the value as they were (so only remove the one w  ...
showing posts tagged with 'vsphere'