Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Fail to recompose or provision due to stale VDI entries in the View ADAM database (57845)

Last Updated: 8/3/2023Categories: TroubleshootingTotal Views: 8035Language:
KoreanEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Linked Clones, Instant Clones keep coming back in deleting (missing) or Error (missing) state

Unable to find stale desktops to manually delete desktops if there are issues using viewdbcheck

The pool fail to recompose or create a new VM due to stale desktops in ADAM

Purpose

This article only provides additional steps for locating the virtual machine(s) for removal in this article:
Manually removing problem desktops and pools from Horizon (2015112)

Cause

When trying to initiate multiple tasks at a same time sometimes some of them stuck in the background thus affecting composer operation.

Impact / Risks

Take a complete backup of the ADAM before modifying or deleting entries in either database. Disable provisioning for the pool in View Manager. For more information, see Performing an end-to-end backup and restore for VMware View Manager (1008046).

Resolution

a) Connect to the View ADAM database. For more information on connecting to the ADAM database with ADSI Edit, see Connecting to the View ADAM Database (2012377).

b) Then,  Locate the virtual machine(s) for removal.

Right-click the Connection View ADAM Database [localhost:389], and click New > Query.
Provide a query name any name of your choice.
Under Root of Search, click Browse and select the Servers organizational unit.
Click OK.
In the Query String, paste the following search strings one by one:

(&(objectClass=pae-VM)(pae-VmState=deleting))

(&(objectClass=pae-VM)(pae-VmState=error))

(&(objectClass=pae-VM)(pae-VmState=cloningerror))

(&(objectClass=pae-VM)(pae-VmState=missing))

Click OK to create the query.
Click the query in the left pane. The virtual machines that match the search are displayed in the right pane.

Check the properties of the items returned by the query to confirm the correct virtual machine(s) were found, and delete the pae-VM object(s) to remove them from the ADAM database.

c) If it is Instant clones, then locate the machine in the vCenter and delete the machine from the vCenter such that delete from disk.

d) If Linked Clone, proceed with the rest of the steps in the article Manually removing problem desktops and pools from Horizon (2015112)  to complete the manual cleanup.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
KoreanEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon View

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant