Migrate Desktops to Horizon Cloud

Use this information to migrate a tenants dedicated full-clone pools to Horizon Cloud using the desktop migration tool. The migration tool is an AlmaLinux appliance, which includes the Rundeck job orchestrator. The OVA needs to be deployed in the vCenter. Download the OVA (Horizon on vSphere Edge Migration Tool) from the Horizon DaaS Downloads page. The migration tool utilizes Rundeck jobs to perform the dedicated desktop pool’s migration for the tenant.

Before migration, you must complete onboarding, prerequisite validation, and pre-migration validation. After migration, there are post-migration validations and Day 2 activities to complete and consider.

Onboarding

You must complete onboarding to the Horizon Cloud platform before migrating. After completing onboarding, the following components should be deployed and working:

• Horizon vSphere Edge

• Pair of Horizon UAGs

• IDP configured for user entitlements

Validate Horizon Cloud Readiness

After onboarding is complete, create at least one dedicated full-clone desktop pool in the Horizon Universal console. Doing this validates the customers’s Horizon Cloud environment readiness for migration.

Validation activities include successful:

• Image creation

• Full-clone pool with desktop creation

• PoolGroup creation with user entitlements

• Launch of a desktop using the Horizon Cloud app blast and Horizon Client

• Eexecution of operations (power on, power off, shutdown, restart, or delete) on the pool desktops

Pool Migration Prerequisites

The following prerequisites should be validated on the pool to ensure it's eligible for migration.

• The required Horizon DaaS platform version on the tenant is 9.2.5

• All AD users and user groups that are part of the pool being considered for migration should be mapped and configured on the Workspace ONE Access for the active directory domain to which the pool is mapped

• The pool should be in online state at the time of migration

The following are prerequisites for each desktop in the pool being migrated.

• Minimum HAI version 24.4.0.13707842402 installed on the desktop with instant clone enabled

• Minimum one user assigned to the desktop

• No ongoing sessions on the desktop

• Desktop should be in powered on state

• Desktop should have an Active agent status

• Partner needs to have a scheduled downtime for the tenant to initiate migration/commit operations on the dedicated desktop pools of the tenant

Horizon Cloud Cloud Pre-Migration Validation

This Rundeck job validates the partner's Cloud setup.

1. Enter the following information for the job.

   • Tenant's Primary Appliance IP Address - The tenant (master appliance’s) IP address.

   • Horizon Cloud Next-Gen OrgId - The Horizon Cloud Organization ID can be obtained from Organization Settings in the CSP portal on Omnissa Connect.

   • Horizon Cloud Next-Gen Org Refresh Token - The generated refresh token. To generate the token, in the CSP portal in Omnissa Connect. Navigate to Account Settings > API Tokens > Generate API Key.

     Note: - Be sure to select all the required roles.

   • Horizon Cloud next-gen Org Edge name - The name of the deployed Horizon Cloud vSphere edge.

   • vCenter Desktop Pool Datastore Name - The name of the datastore from the tenant’s vCenter being used for desktops.

   • vCenter Desktop Pool VM Folder Name - The name of the vm folder from tenant’s vCenter.

   • vCenter Desktop Pool Resource Pool Name - The name of the desktop pool resource pool name from tenant’s vCenter.

   • VCPP Tenant's Cluster of vCenter Server - The name of vCenter cluster used by tenant for desktop provisioning.

   • VCPP Tenant's Datacenter of vCenter Server - The name of vCenter datacenter used by tenant.

2. Click Run job now. The pre-migration validation screen displays.

3. After successfully completing the job, continue to the migration job.

Migrate to Horizon Cloud

1. Enter the following information for the job.

   • Tenant's Primary appliance IP Address - The IP address of the primary appliance of the tenant.

   • Tenant's Desktop vCenter FQDN - The tenant’s desktop vCenter FQDN.

   • Tenant's Desktop vCenter Username - The tenant’s desktop vCenter username.

   • Tenant's Desktop vCenter Password - The tenant’s desktop vCenter password.

   • Tenant's AD Netbios Name - The tenant’s active directory Netbios name.

   • Tenant's AD Admin Username - The tenant’s active directory admin username.

   • Tenant's AD Admin Password - Tthe tenant’s active directory admin password.

   • Tenant's dedicated desktop Pool ID - The ID of the pool considered for migration.

   • Tenant's Networks - The pool’s network considered for migration.

2. Click Run job now.

3. After completing the job, go to the Horizon Cloud Console for the Horizon Cloud platform and validate the pool in the pool’s section.

Commit or Rollback to Horizon Cloud

This job finalizes the migration of pool to Horizon Cloud.

1. Enter the following information for the job.

   • Operation Type - Select Commit to finalize the migration to Horizon Cloud.

   • Pool ID on Which the Selected Operation Needs to be Performed - Enter the pool’s ID which is already migrated.

   • Tenant's Primary Appliance IP Address - Enter the IP address of the master tenant appliance.

2. Click Run job now.

Post Migration Validation

Verify the following entities and operations.

Important: Once a pool is successfully migrated to Horizon Cloud and the validations are completed, the pool should be committed to Horizon Cloud within 24 hrs.

Entities Created for Migrated Pool in Horizon Cloud Console

• Pools - Contains the pool information, its desktops, and assigned users.

• Pool Groups - Contains the pool’s users/user groups, power policy, and desktops.

Operations Allowed fom Horizon Cloud Console

Partner admin is advised to complete the below listed validations within 12 hrs from the time of successful migration.

1. Validate desktop launch from Horizon Cloud app-blast or Horizon Cloud client.

2. Do not perform any power operation (power-on, power-off, restart or shutdown) on any of the desktop of the migrated pool.

3. Do not launch the desktop from the DaaS app-blast or user portal as it will cause anomalies.

Notes:

• To avoid potential issues, limit operations on a migrated pool to only those explicitly listed. Avoid testing or attempting other actions, as they may cause anomalies.

• Post validation of pool from the Horizon Cloud console, consider opting for committing the pool to the Horizon Cloud platform.

Post Commit Validation

Once the migration is successful and the post migration validations are complete, commit the pool to Horizon Cloud. Once the commit operation is successful, complete the following:

1. Validate a desktop launch from Horizon Cloud app-blast or Horizon Cloud client.

2. Perform the power operations on the desktops of the pool after a period of 30 mins from the time of successful commit operation on the pool.

   Note: Desktops in the pool will no longer be accessible from DaaS.

Partner Day 2 Activities

Expanding or adding desktops to the migrated pool is not supported.

If admin wants to create new pools using the existing image of the pool, it can only be done after the pool is committed to Horizon Cloud. The image needs to be repurposed to meet Horizon Cloud platform requirements.

Platform Requirements

• If the local admin account image is Administrator, then a second local admin account should be created on the image with maximum privileges. The same should be used at the time of pool creation from the Horizon Cloud console.

• The Omnissa OS Optimization Tool (OSOT) should be executed to optimize the image.

• Execute the following PowerShell commands on the image VM:

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Agent\Configuration" -Name "Broker"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Agent\Identity" -Name "Bootstrap"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Agent\Identity" -Name "LastMachineId"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Agent\Identity" -Name "MachineId"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Node Manager" -Name "Broker Public Key"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Node Manager" -Name "Broker SSL Certificate Thumbprint"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Configuration" -Name "Broker"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Identity" -Name "Bootstrap"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Identity" -Name "LastMachineId"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Identity" -Name "MachineId"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Node Manager" -Name "Broker Public Key"

  Remove-ItemProperty -Path "HKLM:\SOFTWARE\VMware, Inc.\VMware VDM\Node Manager" -Name "Broker SSL Certificate Thumbprint"

  Set-ItemProperty -Path "HKLM:\SOFTWARE\Omnissa\Horizon\Node Manager" -Name "MS Transport" -Value "MQTT"

Important: See the Horizon Cloud Service for on-premises capacity – limited availability for Omnissa customers announcement for information on our cloud-managed DaaS solution that extends to their on-premises vCenter infrastructure, allowing them to simplify their DaaS implementation, lower cost of maintenance, and manage multiple sites and capacity types from a single console.