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

Horizon Instant Clones fail with ForkParentNotEnabledOnSource after an upgrade from vCenter 6.0 to 6.5 (52573)

Last Updated: 12/28/2023Categories: TroubleshootingTotal Views: 12730Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After upgrading from vCenter 6.0 to 6.5, the Instant Clone virtual machine  provisioning operation fails with an error:

The operation is not allowed in the current state.  ForkParentNotEnabledOnSource

Purpose

This article provides guidelines for upgrading from vSphere 6.0 to 6.5 when Horizon View has Instant Clone pools deployed. These steps apply to the VDI Cluster, not the Management Cluster.
If you do not follow these steps, the following error will be seen in vSphere when Instant Clones attempt to provision:

VirtualMachine.createForkChild.label Target cp-parent-xxxx.. The operation is not allowed in the current state.  ForkParentNotEnabledOnSource.

Resolution

Due to changes in forking technology between vCenter 6.0 and vCenter 6.5, choose the upgrade option which is most conducive to your environment.

Option 1:

Upgrade vCenter Server to 6.5

Upgrade all ESXi hosts to 6.5

Update Golden image/ Main virtual machine as needed (example, updated virtual HW and VMtools) and create a new snapshot.

Push the updated Image to the pool to reprovision the desktops.

Note: These steps should all be performed in the same maintenance window.

Option 2:

Step 1:

Upgrade vSphere and ESXi to 6.0 P06

Update main VM (Example: load Windows Updates if this hasn’t been done recently) and create a new snapshot.

Push Image the pool to reprovision the desktops.

Step 2:

Upgrade vCenter to 6.5.

Create a new snapshot on the main VM (no changes needed).

Push Image the pool to reprovision the desktops.

Step 3:

Upgrade ESXi hosts to 6.5.  For large, multi-cluster environments, each cluster can be done one at a time.

Update main VM as needed (Example: updated virtual HW and VMtools) and create a new snapshot.

Push Image the pool to reprovision the desktops.

Note: Each step can be done in a separate maintenance window.

Related Information

Upgrade vCenter to 6.7 or later, see Upgrade Instant-Clone Desktop Pools.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Horizon 和第三方外围设备兼容性列表 (71062)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 7.x

VMware Horizon 7

Take Our Survey

Support Assistant