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

Disabling automatic recovery when View linked clones are repeatedly deleted and recreated (2030311)

  • 3 Ratings


In a large linked-clone pool, if a desktop is in an Error state, the automatic recovery mechanism attempts to power on the linked clone, or shut down and restart the linked clone. If the linked clone fails to power on after a certain number of attempts, View Manager deletes the clone.

If the pool size settings require View Manager to create a new linked clone, the new clone is provisioned, often with the same desktop name as the original desktop. If the new clone is provisioned with the same error, that clone is deleted.

In this situation, a linked-clone desktop is created in an Error state, deleted, and recreated in an Error state. The cycle keeps repeating.

Note: If automatic recovery attempts fail for a linked clone, View Manager deletes the clone only if it is a floating desktop or a dedicated desktop that is not assigned to a user. Also, View Manager does not delete clones when pool provisioning is disabled.

For more information, see Troubleshooting Desktops That Are Repeatedly Deleted and Recreated section in the VMware Horizon View Administration Guide.
Note: View automatic recovery mechanism is introduced in View Manager 5.1 and applies to all Automated pools, full or linked clones.


The troubleshooting topic in the View Administration document directs you to examine and correct errors in the parent virtual machine and create a new snapshot for creating linked-clone desktops.

Alternatively, you can disable the automatic recovery mechanism on the pool using these steps:
  1. Start the ADSI Edit utility on the View Connection Server host.
  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 host followed by port 389.

    For example: localhost:389 or

  4. In the ADSI Edit navigation pane, select OU=Server Groups.
  5. Select the object CN=pool name, where pool name is the pool on which you intend to disable automatic recovery.
  6. Set the pae-RecoveryDisabled attribute to 1.

    A value of 1 disables the automatic recovery feature.
Note: Instead of editing the ADAM database manually, you can run the ConfigPoolAutoRecovery.bat script attached to this article on the Connection Server to achieve Steps 1 to 6.

Additional Information

For translated versions of this article, see:

Update History

09/05/2012 - Added the script ConfigPoolAutoRecovery.bat 12/10/2014 - Added View 6.0.x, per doc bug 1366891


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.


  • 3 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.
  • 3 Ratings