This page describes the process typically used in the Horizon Universal Console where the console's Imported VMs page lists single-pod-based VMs that are in your tenant's Horizon Cloud on Microsoft Azure deployments, and then you want to instead make them into multi-pod images.
Important: To be supported for use in first-gen Horizon Cloud on Microsoft Azure deployments, all imported base images must be built from Windows-based VMs that are sourced from the Azure Marketplace. Even if you try an image obtained from other origins and the console does not prevent you from using it within the console's workflows, use of such images is unsupported.
If the image is running a Windows 11 operating system, in addition to the requirement to be directly sourced from the Azure Marketplace, the image cannot have been subsequently processed for it to be validly supported in first-gen Horizon Cloud on Microsoft Azure deployments. Importing Windows 11 VM from any other sources such as Shared Image Gallery (SIG), Azure Managed Images, Azure VM snapshot, and the like is currently unsupported.
For additional considerations about supported combinations of Gen-1 and Gen-2 machines for the image-related workflows with first-gen Horizon Cloud on Microsoft Azure deployments, which OSes are supported for which machine generation, refer to Support for Images Sourced from Pods on Microsoft Azure.
The console's Imported VMs page lists single-pod-based VMs by design. A single-pod-based VM gets listed on the page as an outcome from two scenarios. One scenario is when you manually import a base VM from the Azure Marketplace into a specific Horizon Cloud pod. The other scenario is when a base VM is created in a specific pod using the single-pod Import VM from Marketplace workflow on that Imported VMs page.
The console's Imported VMs page provides two options for publishing imported VMs as sealed golden images:
- Publish to Images - This option publishes a VM as a single-pod assignable image on the Images page.
- Move to Multi-Pod Images - This option moves a VM to the Multi-Pod Images page where you can then publish it as a multi-pod image.
This topic describes the Move to Multi-Pod Images option.
In the Move to Multi-Pod Images flow, the system retains the size of the VM that is being moved.
CAUTION:
The console only makes this Move to Multi-Pod Images action available when the VM has the agent software installed and the VM is already paired with its source pod.
However, as described in Horizon Cloud - Publish an Image, when the agent software is already installed, then the Publish Image wizard does not allow for enabling the wizard's Install Horizon Agent toggle.
When the Publish Image wizard's Install Horizon Agent toggle is not enabled for publishing the image, then additional agents such as the App Volumes Agent will not be configured correctly in the published image.
Therefore, after you use Move to Multi-Pod Images and move the image to the console's Images - Multi-Pod page, you must take additional steps to ensure IMS performs the appropriate agent configurations. Those steps are described in the following procedure. The move will create version 1.0 of the image, which you will take through the publishing workflow, after which then you create a version 2.0 and publish that version with the Install Horizon Agent toggle selected and your agent options selected.
Then the resulting version 2.0 of the published image can be used in desktop assignments.
Prerequisites
- This procedure is only available for desktop VMs.
- For your Horizon Cloud on Microsoft Azure deployments, this feature is only available if all those pods are at the manifest version specified in First-Gen Tenants - IMS System Requirements.
- Before moving a VM to the Multi-Pod Images page, confirm that you have installed and paired the correct Horizon Agent on the VM.
Attention: For images created and published in the past on individual pods in Microsoft Azure without using the Image Management Service (IMS), you must first duplicate the image on the Images page. This creates a duplicate VM on the Imported VMs page that you can then move using the steps below. For information about duplication, see Actions You Can Perform on Published Images from Horizon Cloud Pods in Microsoft Azure.
Procedure
-
To move the VM from Imported VMs to Images - Multi-Pod, navigate to Inventory > Images, select the VM and click Move to Multi-Pod Images.
-
In the displayed window, specify options as described in the following table.
Option Description Image Name Enter a name for the image. Important: Do not enter a name that was previously used for an image in your Horizon Cloud environment. Due to a known issue, the VM creation process fails silently if you reuse a name that is already listed on the Multi-Pod Images page. The system will not create the VM in Microsoft Azure, however, an error message does not appear in the administrative console. When selecting a name, confirm that the name you are using does not already appear as an image name on either the Multi-Pod Images page or the Images page. The name must adhere to the following rules: - It cannot contain an underscore character (_).
- It can have only alphanumeric characters and the hyphen.
- The name must start with an alphabetic character (not a number).
- The name cannot end with a hyphen (-).
Description Enter an optional description for the image. Markers Important: You must assign at least one marker to have the image later available for creating assignments in the console's Create Assignment workflow. If you do not assign at least one marker now, the image will not appear in the UI as a choice in the assignment creation workflow later. Ensure you have at least one string displayed in this box before you click Import. Use this UI box to define one or more reference markers that you want to associate with the image. The markers will be associated with version 1.0 of the image. As you type in characters, those characters appear in both the UI's box and in a blue row below the box. Important: After typing in characters, you must complete the addition of the marker to this UI box. Either press your Enter key or click the string displayed in the blue row below the box. After the string is fully added to the UI box, the box will display the characters with a curved outline around them and a little x for removing it. If you do not see the string displayed in the box with a curved outline around it, then the marker is unsaved. The marker needs to be saved for the image to be used in assignments. Include GPU Enable this toggle to specify a GPU-enabled multi-pod image as the result of the move. - This option is not supported for the Windows 7 operating system. Therefore, you will not see this wizard option if you selected a Windows 7 operating system.
- If this toggle is dimmed, that means your Microsoft Azure subscription in the selected pod's region does not support GPU hardware.
Username Type the admin name that you want for the VM's local administrator account. This local administrator account is created in the VM during the process. This name is used for the local admin account to access the VM's operating system. This name can be a maximum of 15 characters in length, must not end in a period ("."), and must not be one of the admin names that are not allowed when creating a VM in Microsoft Azure. Note: The user name you enter must meet the Microsoft requirements for acceptable user names for creating a VM in Microsoft Azure. For the list of requirements, see username requirements in the Microsoft documentation. Important: Ensure you can remember this local administrator account information (this name and the password that you specify in the Password text box), or that you write it down so you can retrieve the information later. You need these credentials to add any third-party applications to this base image. Password Type the password that you want for that administrator account. The password must adhere to the Microsoft Azure password rules: - Must not be one of the admin account passwords that are not allowed when creating a VM in Microsoft Azure
- Must be from 12 through 123 characters in length and meet three out of the following four complexity requirements:
- Contain a lowercase character
- Contain an uppercase character
- Contain a digit
- Contain a special character, such as (!@#$%/^&*)
Verify Password Retype the password. -
Click Move.
Horizon Image Management Service imports the image into the catalog and creates a new image in the list on the Images - Multi-Pod page. This is version 1.0 of the image and has status of Deployment Complete.
The following screenshot illustrates this result for the image named
manualtest1.
-
Navigate to the Images - Multi-Pod page (Inventory > Images - Multi-Pod).
-
Click on the image name to navigate to see the version 1.0 of the image with its status of Deployment Complete.
-
Publish that image by selecting that version 1.0 and clicking the more ( ... ) button, select Publish from the menu.
Because the agent software is already installed on this image, the Publish Image wizard prevents selection of theInstall Horizon Agent toggle and has switched off that toggle by default. As a result, IMS is prevented from installing the agent software and applying the appropriate configuration parameters that additional agents such as App Volumes Agent require.
The following screenshot illustrates how in the scenario of a VM moved from the Imported VMs page this Install Horizon Agent toggle is switched off by default and it is unavailable for being switched on.
However, the desired goal is to have IMS install the Horizon agent and all of the additional agent software to ensure the configuration is validated for use with the pods in the tenant.
The reason for this step and the next step of publishing the version 1.0 image in this state is to allow for you to create a second version, version 2.0, from the published version 1.0. Then publishing that version 2.0 allows IMS to install the agent software.
-
Type in a company name (Company Name) and click Publish to publish this version 1.0.
-
Wait for the version 1.0 to achieve the status Available, and then select that version 1.0 so that you can access the New Version action.
It might take up to 20 minutes for the version 1.0 image to achieve the status Available.
The following screenshot illustrates the selected version 1.0 with Available status and the New Version action.
-
Click New Version to create a new version of the image.
You will publish this second version and have IMS install the Horizon Agent into this new, version 2.0 of the image. Publishing of the second version ensures IMS can perform the appropriate agent configurations, for all of the image replicas in the destination pods.
The following screenshot illustrates the UI after New Version is clicked and after filling out the information.
Important: Remember to input a marker and click Enter to ensure the marker is displayed in the Markers field before submitting this window. If a marker doesn't exist for the version, you will not be able to successfully complete the final step of updating the floating VDI desktop assignment to use this new image version.
Click Submit to complete creation of this new image version, version 2.0.
The system will being deploying the underlying VM for this version 2.0.
-
When the UI indicates the version 2.0 is Deployment Complete on the image versions page, select that version 2.0 and click Publish.
Now in the Publish workflow, the Install Horizon Agent toggle is available and switched on where it was inaccessible when publishing the version that was moved from the Imported VMs page.
Important: Ensuring the Install Horizon Agent toggle is switched on for this new image version is critical to ensuring IMS installs the agent software and configures it appropriately in the published image.
-
From this point you can follow the steps described in Publish an Image steps, selecting the destination pods and enabling the agent features that you want installed to use in the VDI desktops.
For a description of the Publish Image UI's fields, see Publish an Image steps.
Questa pagina è stata utile?