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

Migration Recommendations and Restrictions for Horizon VDI Desktops (57368)

Last Updated: 7/22/2022Categories: How toTotal Views: 54701Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Purpose

Horizon View supports use cases which require Persistent and Non-Persistent desktops, utilizing both Dedicated and Floating Assignment VMs based on several different technologies.  Please review the information regarding the steps to migrate different VDI workloads, should the need arise.

Note that for Non-persistent desktops, the workflow will involve the VMs being deleted and recreated in their new configuration.  For Persistent desktops, the workflows involve two steps: one to change the existing VMs and one to change new VMs going forward.

Resolution

Migrating Networks
In your environment, you will have many VLANs setup.  They will be assigned to different DVS, NSX-t, or Standard Switches.  You can change where your VMs are connected using the following steps.  Ensure the VMs have a reliable connectivity path to the Horizon Connection Servers.

In a Linked Clone Pool, Edit Settings on the golden image VM in vSphere Web Client and change the network which the vNIC is attached to.  OK out and create a new snapshot on the VM.  Recompose the pool in Horizon Administrator.  For additional information, see https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-63C1BE4D-4B6E-446D-9E6D-1DA016B4B944.html

In an Instant Clone Pool, you have two choices.  You can change the golden image as mentioned above, or you can change the pool in Horizon Console.  In Horizon Console, Edit the pool, go to the vCenter Settings tab, and click Browse next to the Network entry.  Typically the box is checked to, “Use network from current parent VM image."  Uncheck this box and select the available networks you would like to use.  As VMs are destroyed at logoff, they will be recreated on the newly specified network segment.

In an Automated Full Clone Desktop Pool, convert the Template VM to a Virtual Machine from within vSphere Client.  Change the vNIC assignment and convert the VM back to a Template.  New VMs will now provision to the newly specified network segment.  For existing VMs, you can change their vNIC assignment in vSphere Client.

In a Manual Desktop Pool, Edit the VMs in vSphere Client and change them to be on the newly specified network segment.

Migrating Storage
The datastores where the VMs reside can be changed.  This may be required when redistributing IOPS load across multiple locations or when vacating a SAN is it can be decommissioned.

In an Instant Clone or Linked Clone Pool, Edit the pool in Horizon Console and go to the vCenter Settings tab.  Click Browse next to the Datastores entry.  Select the new location(s) and optionally unselect the old location(s).  OK out of the Edit page.

For Linked Clone Pools, perform a Rebalance operation.  For additional information, see https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-B498C846-C7FE-4D37-9899-7857BA7C706B.html

For Instant Clone Pools, VMs will remain on the old datastore until a user logs on and then logs off, or you manually remove the VM by going to the Inventory tab for the pool using the Remove button.  Horizon will create the replacement VM on the new datastore.  Note that you should allow additional time for the first clone to appear, as new cp-replica and cp-parent VMs will need to be created.  For additional information, see https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-A2D1B8DF-9F6D-4C9F-937A-F454031F7472.html

In an Automated Full Clone Pool, Edit the pool in Horizon Console and go to the vCenter Settings tab.  Click Browse next to the Datastores entry.  Select the new location(s) and optionally unselect the old location(s).  OK out of the Edit page.  New desktops will now provision to the newly selected datastore.  For existing VMs, use the Migrate option in vSphere Client as seen below.

In a Manual Desktop Pool, use the Migrate option in vSphere Client.  For additional information, see https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-A15EE2F6-AAF5-40DC-98B7-0DF72E166888.html

Migrating Compute
The location where VMs are run from, different hosts and clusters managed by the same vCenter Servers, can be changed.  If the pool needs to be moved to a new vCenter Server, the pool will need to be recreated.  Pools being moved to or from a vSAN datastore will also need to be recreated.

For an Instant Clone or Linked Clone Pool, Edit the existing pool in Horizon Console, go to the vCenter Server tab, and to point to a new Cluster, Resource pool, Datastore, and (if necessary) Network under the Resource Settings section.  If moving to a new vCenter Server, copy the primary VM to the new environment and recreate the pool using the previously used settings.

For an Automated Full Clone Pool, disable provisioning, edit the pool settings to point to the new cluster and template.  In vSphere Client, move the existing VMs to the newly specified location.  Re-enable provisioning and increase the size of the pool in Horizon Console by one VM to confirm the desired results are seen.

Alternatively, recreate the Automated Pool in the new location.  Then, migrate the existing machines to the new location, and create a new “static” Manual Pool for existing users to reside, as seen below.

In a Manual Desktop Pool, the desktop VMs are managed by vCenter Server or some other source.  The machines (typically Full clone Agent VMs but also physical machines) can be removed from the pool in Horizon Administrator (select the option Remove VMs from View Manager only) and then migrated manually to a new location, such as a new cluster under a new vCenter, using new storage and new networking.  From there, they can be added to a new or existing Full Clone Manual pool and re-assigned to the appropriate user.

Note: If the VM remains in the status “Agent Unreachable” or "Waiting for Agent" after being added to the new pool, then rebooting or uninstalling and reinstalling the Horizon Agent will be required.  For additional steps, see Troubleshooting Agent Unreachable status in VMware Horizon View/VDI (2083535)

References:

Create an Instant-Clone Desktop Pool
https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-F5C53552-F6C8-4BE8-B486-9D172CA1F5CD.html

Creating Linked-Clone Desktop Pools
https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-CE05F77C-1121-444A-8C02-40BA874CFCD7.html

Creating Automated Desktop Pools That Contain Full Virtual Machines
https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-29866633-23DF-4CBB-9642-333E1384F1EF.html

Creating Manual Desktop Pools
https://docs.vmware.com/en/VMware-Horizon-7/7.13/horizon-virtual-desktops/GUID-85352734-3AC3-45B0-AA10-5E632D0C1824.html

Related Information

See, Migrating from vCenter Windows Server to vCenter Service Appliance with VMware Horizon 7.x (51154).

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
•
Download and Install VMware Fusion (2014097)

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 View

VMware Horizon View

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7.x

VMware Horizon 7

VMware Horizon 6

Take Our Survey

Support Assistant