This page describes items that are currently excluded from the self-service migration process for migrating first-generation Horizon Cloud on Microsoft Azure deployments to a Horizon Cloud tenant. This page also describes some special cases of first-generation deployments.
Note: This content is a living document. This information is updated as additional support becomes available.
Current Key Exclusions
Important: This content does not cite every possible exclusion. The items here are the large characteristics that are currently excluded from the migration process.
This first list states what is included, followed by the list of what is excluded.
Included as of January 16, 2025
As of this writing, a Horizon Cloud on Microsoft Azure pod that meets the following criteria can be migrated.
- Deployed in an Azure Commercial environment or deployed in Azure US Government (Azure regions
usgovvirginia,usgovtexas,usgovarizona). Note: Because Azure US Government subscriptions don't support Azure Private Link, when migrating pods in Azure US Government using the AKS deployment type, the resulting Horizon Edge will have network connectivity set to internet by default. - Has assignments within a single pod or which span multiple pods. (Migration of assignments which span multiple pods is supported as of January 16, 2025.)
- The Horizon Cloud on Microsoft Azure pod must be running a minimum pod manifest version, have a status of
Online(green) on the first-gen console's Capacity page, and the agents must be running a minimum version. For more details, see the section Ensure the Deployment and Agents are at Migration's Required Versions. - Internal gateway configurations that the first-gen pod deployer has provided for first-gen pods.
- External gateway configurations that the first-gen pod deployer has provided for first-gen pods.
- When a pod's subnets or VNet has conflicts with or overlap with what are called AKS-restricted IP ranges, the pod can be migrated as long as you either choose the Single Virtual Machine deployment type or implement the workaround of creating a new VNet and management subnet for the Horizon Cloud deployment. For more information about this scenario, refer to Determine Whether the Pod's VNet or Connected Networks Contain AKS-Restricted IP Addresses.
- Pods that are providing remote apps to the tenant's inventory are eligible for migration. Both auto-scanned remote apps and remote apps that were added to the inventory using the Manually from Farm option can be migrated at this time. As described in the first-gen documentation here, these remote apps are provided by application farms from the pod.
Note: If you had installed the manual apps directly on the first-gen farm VMs, even though their metadata is migrated as part of the migration process, such apps won't be installed by default on the Horizon Cloud environment's pool VMs. For such apps, you'll have to re-install them on the pool VMs in the exact specific paths where they were installed in the first-gen farm VMs.
For additional details about what the migrated application farms will look like in the Horizon Universal Console post-migration, see the section Remote Apps from First-Gen Farms in this migration guide.
- The proxy configuration settings that the first-gen service supports on first-gen pods. The migration process will configure the same proxy settings on the resulting Horizon Edge Gateway appliance.
Note: If you decide to migrate using the AKS deployment type and the first-gen pod is using an authenticated proxy, where its proxy settings include a user name and password for authentication, the migration process only copies the proxy URL itself to the Horizon Edge Gateway appliance. The reason for this is because the AKS type uses the Microsoft Azure Kubernetes Service (AKS), which does not support an authenticated proxy at this time.
For more information about deciding on which Horizon Edge Gateway deployment type to select when migrating, see Decide on Your Horizon Edge Gateway Deployment Type.
- If the first-gen tenant's pod fleet includes Horizon pods in addition to a Horizon Cloud on Microsoft Azure pod, as long as those Horizon pods are only using the subscription licensing and no other cloud-based services, then the Horizon Cloud on Microsoft Azure pod can participate in the self-service migration process.
In this scenario, you can use this guide's described self-service migration process to migrate the Horizon Cloud on Microsoft Azure pod to your Horizon Cloud environment. After the Horizon Cloud on Microsoft Azure pod is migrated, the Horizon pods remain in the first-gen tenant environment, receiving their subscription licensing through the first-gen tenant. A self-service migration process for Horizon pods is not yet provided.
- Horizon thin clients that are listed for Horizon Cloud in the Compatibility Guide are supported post-migration. When you have a use case where your end users are using Horizon thin clients, check the compatibility matrix between your Horizon thin client device and model and Horizon Cloud before proceeding with migration. Only Horizon thin clients that are listed as compatible with Horizon Cloud are supported post-migration.
The Horizon Thin Clients Compatibility Guide is located within Tech Zone's Technology Partner Hub - Compatibility Guides.
Note: Migration of the end-user desktop preferences set in the Horizon Client for each desktop is currently unsupported. To get their desired preferences after the migration, your end users can set those preferences again in their clients.
Excluded
The following scenarios are currently unsupported for migration:
- Situations that have a requirement for end users or their clients to use PCoIP with the Horizon Cloud on Microsoft Azure deployment.
Note: The automated self-service migration cannot detect if you have end users that want or require PCoIP. You and your VDI admins must verify whether this situation applies to your end users.
- Horizon thin clients that aren't in the Compatibility Matrix are unsupported for use post-migration. When you have a use case where your end users are using Horizon thin clients, check the compatibility matrix between your Horizon thin client device and model and Horizon Cloud before proceeding with migration. Only Horizon thin clients that are listed as compatible with Horizon Cloud are supported.
The Horizon Thin Clients Compatibility Guide is located within Tech Zone's Technology Partner Hub - Compatibility Guides.
Note: As described in KB article 91183, of June 30, 2023, historical dashboards and reports which were powered by the Cloud Monitoring Service (CMS) data are only available through Omnissa Intelligence. When you followed the KB article's steps prior to June 30, 2023, data for the first-gen Horizon Cloud on Microsoft Azure pod was initially available in the Intelligence console.
When the first-gen Horizon Cloud on Microsoft Azure pod is migrated to the Horizon Cloud environment, the time series type of data for that pod will continue to be available in Intelligence after the migration.
If the Horizon Cloud team has enabled your access to the Horizon Cloud migration wizard in the first-gen Horizon Universal Console, that wizard displays the set of features that are available in first-gen Horizon Cloud on Microsoft Azure but are not available after migration to Horizon Cloud.
Administrators should inform end users of the migration and that the Horizon Cloud user experience differs somewhat from that of first-gen Horizon Cloud on Microsoft Azure.
Does Your First-Gen Deployment Make Use of Features Selectively Provided to You or Enabled by Horizon Cloud Operations Team or Integrated with Omnissa Access?
Some features might have been selectively enabled for your first-gen deployment by the Horizon Cloud Operations Team. Some items might have been provided for your use under special conditions, such as private APIs.
Review in your team if your deployment involves any of these items.
- Is your tenant configured for single-pod brokering and Omnissa Access is integrated with that tenant and its pod? If you are not already in contact with the Horizon Cloud team for migrating your pod, please file a support request to reach out to the Horizon Cloud team for guidance.
- Is your tenant configured with Universal Broker and integrated with Access and Intelligent Hub Services? If you are not already in contact with the Horizon Cloud team for migrating your pod, please file a support request to reach out to the Horizon Cloud team for guidance.
- Have you requested enablement for any features that the first-generation documentation states are available when your tenant is explicitly enabled for use of such features on a per-request basis? Examples of such features are use of LDAPS when registering the Active Directory domain, moving individual VMs between assignments in the same pod, narrow scope permissions to desktop assignments and farms for the built-in predefined roles. If the answer is yes, please file a support request to reach out to the Horizon Cloud team for guidance.
- Have you developed scripts relying on APIs that the Horizon Cloud team provided for your use with the first-gen control plane? Those scripts or tools will need to be re-written using the Horizon Cloud control plane's APIs. See the Horizon Cloud API documentation for those APIs.
- Has your team or the Horizon Cloud Operations team on your behalf configured specific features or properties in the deployment's Unified Access Gateway configuration? Examples of such configurations are syslog, advanced RADIUS options, custom routing on the management or tenant subnets, changed default MTU sizes on the Unified Access Gateway instances. If the answer is yes, please file a support request to reach out to the Horizon Cloud team for guidance.
- Has the Horizon Cloud Operations team on your behalf configured specific properties related to the deployment's pod-manager instances? Examples of such configurations are changing the default user cache thread timeout value, disabling the Domain Join account permission validation. If the answer is yes, please file a support request to reach out to the Horizon Cloud team for guidance.
- Are there other items that the Horizon Cloud Operations team has configured for your deployment that are not described in the first-generation documentation as generally available or per-request features? If the answer is yes, please file a support request to reach out to the Horizon Cloud team for guidance.
Was this page helpful?