VMware vSphere® App HA — 1.1 Release Notes

VMware vSphere App HA 1.1 | 8 April 2014

Last Document Update: 24 April 2014

These release notes cover the following topics:

About vSphere App HA

vSphere App HA is a plug-in to the vSphere Web Client. vSphere App HA enables you to define high availability for the applications that are running on the virtual machines in your environment.

Key vSphere App HA Features

This version includes the following features:

  • vSphere App HA is now backward compatible with the vSphere Web Client 5.1 U2.
  • You can create a custom App HA service to manage non-default App HA services.
  • You can edit policies, including those that have already been assigned to services.

Accessing vSphere App HA Remotely

Access to a vSphere App HA VM can be made remotely using SSH protocol. To enable SSH, open the console on the VM and start the sshd service.

By default, you cannot log in remotely using root credentials. To enable root credential login, open the console on the VM and change the permitRootLogin entry in the sshd_config file to yes. Restart the sshd service.

Limitations and Known Issues

The following limitations and known issues affect this vSphere App HA release:


  • The vSphere App HA license is configured at ESX level. As long as you have a vSphere App HA license feature on one of your ESX servers, it applies to the vCenter environment.
  • You can only install one vCenter Hyperic server on one vCenter server with one vSphere App HA plug-in installed (1:1:1).
  • vSphere App HA has a scale limitation of 400 agents.


  • When you apply Reset VM remediation to a service, verify that service starts automatically when the operating system is booted. If the service is not already configured to start automatically at system reboot, you must configure it to do so.
  • When you power off or suspend a virtual machine, during the first minute of the process the vSphere HA protection is disabled remediation limitation is displayed instead of the VM is powered off or suspended limitation.
  • When you put a service in maintenance mode, the process takes up to a minute to be fully applied, even though the Application Availability table already shows that the service is in maintenance mode. During this time, remediation actions might still be triggered.
  • If you configure a Reset VM action on a virtual machine that is not part of a cluster and you then move it to a cluster, the action does not work if the action was triggered while the machine was outside the cluster.
  • If you apply Reset VM remediation to two or more services on a virtual machine and one of the services requires a reset virtual machine action, the other services are determined to be stopped or unstable, and a reset loop might be created.
    Only apply this remediation action to one service on a virtual machine.
  • You cannot assign a remediation policy to a service whose availability is unknown. However, in the case in which the service is unknown because of configuration issues, you can create a policy with correct configuration properties and assign it.


  • In the vSphere Web Client, under the vCenter Solutions Manager, the vSphere App HA plug-in is listed with unknown status, regardless of the health of the plug-in.
  • Occasionally, a #1010 internal error appears in the Applications Availability tab. You can safely ignore the message.
  • On virtual machines running a Windows operating system, occasionally you might see two instances of Apache HTTP Server displayed in the Availability tab although there is actually only one instance. Check that the path to the instances are identical to verify that there is only one instance of the server.
  • If the clock of a vCenter Hyperic agent is not synchronized with the vCenter Hyperic server clock, the information that is retrieved from the vCenter Hyperic server is inaccurate. As a result, vSphere App HA actions are unreliable.