#Adding images to wallpaper wizard windows#

For steps, see Create a Base Virtual Machine Automatically from the Microsoft Azure Marketplace and Pair it with Horizon Cloud on a Per-Pod Basis. From the console's Inventory page, start the workflow by clicking Import.

#Adding images to wallpaper wizard windows#

In this configuration, the workflow also provides options for optimizing the VM, which can prevent Microsoft Windows Sysprep errors from occurring. In the default tenant configurations, the automated workflow configures the VM to conform to the Horizon Cloud environment's requirements, including installing and configuring the appropriate agent-related software. Using the automated workflow automates building the virtual machine (VM).

The recommended and standard way is to use the administrative console's automated workflow to create the base VM using one of the supported VM configurations from the Microsoft Azure Marketplace.

You create a base VM either using the automated workflow or manually. First, Create a Base Virtual Machine (VM) In the Horizon Universal Console, the label Publish is used for the console's workflow to seal the image.Ĭreating a golden image which can be sealed and then used to provision RDS farms or VDI desktops involves the following high-level sequence. That assignable image is an image that has successfully completed the Horizon Cloud sealing process and it can be used to provision farms (in the case of RDS-based images or multi-session images built on Windows Enterprise multi-session) or single-session VDI desktops (in the case of client-based images). Sealing that golden image results in the assignable image that can be used in your tenant's farms and single-session VDI desktop assignments. Customizing that base VM creates the golden image. Such deployments have reached end of general support, perįor Horizon Cloud on Microsoft Azure deployments, you first import a base VM from the Azure Marketplace. Note: As of July 2022, content related to pods of unsupported manifests has been removed from this page. For details on multi-pod images, see the guide Managing Horizon Images from the Cloud and its subtopics. In addition to the sequence described here, when your tenant is configured to use Universal Broker, the features of the Horizon Image Management Service and multi-pod images are available to you.

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.įor 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.

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. 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. Horizon Cloud on Microsoft Azure deployments, all imported base images must be built from Windows-based VMs that are sourced from the Azure Marketplace.

Important: To be supported for use in first-gen