Search the VMware Knowledge Base (KB)
View by Article ID

The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used (1000590)

  • 45 Ratings

Symptoms

When using VMware View with a pool set to refresh or delete the virtual machines after log off, you experience these symptoms:
  • VMware View virtual machines are unavailable.
  • The View Administrator console shows the status of virtual machine as:

    Already Used  or  Agent Disabled

Cause

If a desktop that is set to refresh or delete after log off is reset, the desktop goes into the Already Used state, or possibly the Agent Disabled state.

This security feature prevents any previous session data from being available during the next log in, but leaves the data intact to enable administrators to access the desktop and retrieve lost data or investigate the root cause of the reset. Administrators can then refresh or delete the desktop.

The View desktop can also go into the Already Used state if a virtual machine is powered on in another ESX host in the cluster in response to an HA event, or if it was shut down without reporting to the broker that the user had logged out.

Resolution

To resolve this issue, perform a refresh of the desktop using the View Administration console. For more information, see the VMware Horizon View Administration guide relevant to your version.

Alternatively, In View 5.1.2 and later releases, you can add a View LDAP attribute, pae-DirtyVMPolicy under OU=Server Groups, DC=vdi, DC=vmware, DC=int, and set the values below for the attribute.

The pae-DirtyVMPolicy values provide these options for the Refresh on logoff policy:
  • pae-DirtyVMPolicy=0: Mark virtual machines that were not cleanly logged off as Already used and block user access to them. This is the default behavior in View 4.6 and later releases.

  • pae-DirtyVMPolicy=1: Allow virtual machines that were not cleanly logged off to become available without being refreshed. View Client users can access these desktops.

  • pae-DirtyVMPolicy=2: Automatically refresh virtual machines that were not cleanly logged off. View Client users can access these desktops after the refresh operation is completed.
 
Notes:
 
To change the value of the pae-DirtyVmPolicy attribute using the ADSI Edit utility:
  1. Start the ADSI Edit utility on your View Connection Server host. For example, navigate to Start > Programs > ADAM > ADAM ADSI Edit.
  2. Select or type a Distinguished Name or connect to DC=vdi, DC=vmware, DC=int.
  3. Select or type a domain or server to localhost:389.
  4. Locate the OU=Server Groups for editing.
  5. Under the Server Groups OU, double-click CN=pool_name. This opens the properties of the CN.
  6. Click the pae-DirtyVmPolicy attribute and click Edit.
  7. Set the pae-DirtyVmPolicy attribute to the selected mechanism described above.

    Note: You must type an integer between 0 and 2

Note: When you are manually updating the ADAM database, the pae-DirtyVmPolicy attribute may not be visible if the properties filter is set to hide attributes without value. To find the attribute, change the filter to show all attributes irrespective of whether they have a value or not.

In View 5.1.2, to ensure that only a single Suspend operation is sent, you must configure a multivalued attribute in View LDAP:

  1. Start the ADSI Edit utility on any View Connection Server instance in a replicated group. For more information, see Connecting to the View ADAM Database (2012377).
  2. In the Connection Settings dialog box, select or connect to DC=vdi,DC=vmware,DC=int.
  3. In the Computer pane, select or type localhost:389 or the fully qualified domain name (FQDN) of the View Connection Server computer followed by port 389.
  4. On the object CN=Common, OU=Global, OU=Properties, select or create the pae-NameValuePair attribute.
  5. Add these values to the pae-NameValuePair attribute:

    cs-suspendpolltimeout=90000

    and

    cs-suspendpolltime=1000

    Note: These values are in milliseconds.

Tags

view-vm-session-fails  view-vm-status-already-used

See Also

Update History

01/20/2012 - Updated to include VMware View Manager 5.0 in product versions 08/20/2012 - Updated KB to say this can occur on delete after logoff 04/28/2013 - Update the Resolution section contain info about the properties filter showing all the attributes 05/05/2013 - Added the line in the Additional information section. 05/19/2013 - Added link to the KB article in the resolution and added information about taking back up before applying any change to ADAM database. 05/19/2013 - Also changed "ADSI EDIT" to Powercli in the Additional Information section. 05/19/2013 - Added view 5.1.2 to the second paragraph in Resolution section. 09/04/2013 - Added steps 5, 6 and 7 in Resolution section. 02/02/2014 - Merged in content from KB 2046638.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 45 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 45 Ratings
Actions
KB: