After the virtual machine (VM) built on a Microsoft Windows 10 Enterprise multi-session operating system is imported and you have paired it to Horizon Cloud, but before converting it into a published image, you customize the guest operating system (OS) to install and configure all of the things you want to have in the RDSH VMs from which your end users' remote applications and session-based desktops will be provisioned. At this time, you install all of the third-party applications you want available in the session-based desktops or available for assignment as remote applications. Also at this time, you perform any other customizations in the Windows guest operating system, such as installing special drivers required by your organization's needs, applying wallpaper, setting default colors and fonts, configuring taskbar settings, and other such OS-level items. The VM prior to customization is sometimes referred to as an image or base image. After customization, the VM is sometimes referred to as a golden image.

Tip: As described in the Microsoft documentation FAQ, Microsoft Windows 10 Enterprise multi-session is a Remote Desktop Session Host (RDSH) type that allows multiple concurrent interactive sessions, which previously only Microsoft Windows Server operating systems could provide. Because Microsoft Windows 10 Enterprise multi-session is an RDSH type of operating system, it will appear in the Horizon Cloud RDSH-applicable workflows when your Horizon Cloud tenant account configuration provides for its use.

After the Imported VMs page indicates that your imported VM has its agent-related status as active, you connect to it using your RDP software and install the applications into the underlying operating system.

Prerequisites

If the imported VM is running one of the Microsoft Windows 10 Enterprise multi-session systems that includes Office 365 ProPlus by default, as part of customizing the operating system, you might have to configure that Office 365 ProPlus for shared computer activation as described in the Microsoft documentation topic Overview of shared computer activation for Office 365 ProPlus. Read that Microsoft documentation topic to determine how you want to configure Office 365 ProPlus for shared computer activation.

Verify the Imported VMs page indicates the agent-related status is active for the VM. To get that status, use the Imported VMs page's Reset Agent Pairing action on the VM. That action is located in the More drop-down list.

Obtain the VM's IP address as displayed on the Imported VMs page.

Tip: When using the Microsoft Remote Desktop Client as your RDP software to connect to the VM, ensure it is the most up-to-date version. The version must be version 8 or higher.

Verify you have at least one of the following credentials (user name and password) to log in to the VM's guest Windows operating system, according to how the VM was created.

How the VM was created Credentials to use to log in

Import Virtual Machine wizard, from the Imported VMs page.

The Import Virtual Machine wizard provides the option of either having the wizard-created VM joined to a specified Active Directory domain or not having the VM joined to the domain at the end of the creation process.

  • If the VM was created with the wizard's Domain Join toggle enabled, you can use either the credentials for a domain account in the specified Active Directory domain or use the local administrator account that was specified in the wizard.
  • If the VM was created with the wizard's Domain Join toggle turned off, you must use the local administrator account that was specified in the wizard. In this case, because the VM is not joined to the domain, the local administrator account is the only account that has access to log in.

Manual preparation steps in Manually Build and Import a Virtual Machine from Microsoft Azure into Horizon Cloud.

Typically you do not need to join the VM to your Active Directory domain when you manually build the VM. To log in to that VM, use one of the following:

  • The credentials for the local administrator account that was specified when the manually built VM was created in the Microsoft Azure portal.
  • If you manually joined that VM to an Active Directory domain, the credentials for a domain account in that domain.

Procedure

  1. Use the VM's IP address in your RDP software to connect to the VM's operating system.
    • If the VM was created with a public IP address, you can use that IP address in your RDP software
    • If the VM has a private IP address, you must RDP into it by one of these two methods:
      • Using another VM in your Microsoft Azure subscription that does have a public IP address and doing an outbound RDP into the imported VM.
      • Use your VPN and RDP into the VM over your corporate network
    Remember: When using the Microsoft Remote Desktop Client as your RDP software to connect to the VM, ensure it is the most up-to-date version. The version must be version 8 or higher.
  2. Log in to the Windows operating system using credentials (user name and password) as described in the prerequisites here.
    When using the local administrator account credentials that were specified in the Import Image wizard when the VM was created, enter the username as \username.
    Note: When the VM is a domain-joined VM, as described in the prerequisites here, and you want to use a domain account instead of the local administrator account, enter the user name as domain\username where domain is the name of the domain.
  3. When you are logged in to the operating system, install the third-party applications or drivers that you want available for your end users in the session-based desktops or to run as remote applications.
  4. In the operating system, install any custom drivers you want available in the RDSH hosts.
  5. Make any customizations or configurations you want to have in the session-based desktops, such as add a custom wallpaper, set default fonts or colors or themes, adjust the taskbar default settings, and so on.
  6. When you are done adding your finishing touches to the VM's guest operating system, sign out of the operating system.

What to do next

If the VM is based on one of the Microsoft Windows 10 Enterprise multi-session choices that includes Office 365 ProPlus by default, additional steps might be required. You might have to configure that Office 365 ProPlus for shared computer activation as described in the Microsoft documentation topic Overview of shared computer activation for Office 365 ProPlus. Read that Microsoft documentation topic to determine how you want to configure Office 365 ProPlus for shared computer activation and use the method appropriate for your situation.

Optimize the image based on your intended business scenario. See the guidance in Five Key Steps to Take with Your Golden Images to Get Optimal Remote Experience Performance from Horizon Cloud Farms and Desktops.

Follow the best practices to optimize the VM to prevent encountering sysprep or other errors during the process to convert the golden image to an assignable image in Horizon Cloud, also known as publishing or sealing the image. See Customize the Imported VM's Windows Operating System.

Convert the golden image to an assignable image, using the steps described in Convert a Configured Image VM to an Assignable Image in Horizon Cloud on a Per-Pod Basis.