The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used (1000590)
- VMware View virtual machines are unavailable.
- The View Administrator console shows the status of virtual machine as:
Already Used or Agent Disabled
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.
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.
- When the Suspend power policy is set for a desktop pool, View sends multiple Suspend operations to the same virtual machines, causing vCenter Server to log multiple error messages.
- For detailed instructions on using ADSI Edit to connect to the View ADAM database, see Connecting to the View ADAM Database (2012377).
- Ensure to take a backup of the ADAM database before proceeding. For more information, see Performing an end-to-end backup and restore for VMware View Manager (1008046).
- Start the ADSI Edit utility on your View Connection Server host. For example, navigate to Start > Programs > ADAM > ADAM ADSI Edit.
- Select or type a Distinguished Name or connect to DC=vdi, DC=vmware, DC=int.
- Select or type a domain or server to localhost:389.
- Locate the OU=Server Groups for editing.
- Under the Server Groups OU, double-click CN=pool_name. This opens the properties of the CN.
- Click the pae-DirtyVmPolicy attribute and click Edit.
- 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:
- 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).
- In the Connection Settings dialog box, select or connect to DC=vdi,DC=vmware,DC=int.
- 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.
- On the object CN=Common, OU=Global, OU=Properties, select or create the pae-NameValuePair attribute.
- Add these values to the pae-NameValuePair attribute:
Note: These values are in milliseconds.