In this article:
The Unidesk Operating System (OS) Layer contains the Windows Operating System that is assigned to any Unidesk Layered Images you create using that OS Layer. Once created, you can use the OS Layer to build as many Layered Images as you need.
The OS Layer is created using a virtual machine in your infrastructure and the Windows Operating System that you want to use for your Layered Images. You can import the OS from your Azure environment or from the Network File Share attached to the Unidesk ELM.
Note: The OS image must be created from a Microsoft ISO, rather than an existing template.
To create an OS Layer, you create a virtual machine in Azure, prepare the OS in Azure, and then import the resulting OS Disk into Unidesk to create the OS Layer.
In the Microsoft Azure portal, create a new VM from the "Windows Server Remote Desktop Session Host Windows Server 2012 R2" image (New > Compute > Virtual Machine > From Gallery > Windows Server Remote Desktop Session Host Windows Server 2012 R2).
Choose Resource Manager from the Select a deployment model option list and click Create.
Note: Unidesk for Azure does not support the Classic option from the Select a deployment model option list.
Complete the Create virtual machine wizard to create the OS machine.
After the new server machine has been successfully created, reboot the machine, and log into it remotely.
Turn off Windows Automatic Updates (Control Panel > System and Security > Windows Update > Change Settings).
From the new machine, open a web browser, navigate to the Unidesk Download Center and download the Unidesk OS Machine Tools.
Rename or delete the "Unattend.wsf" file in the C:\Windows\OEM directory.
Note: Do not use the Unattend.exe, as this is not needed and will cause issues with Azure.
On the new server machine, run the setup_x64.exe file to install the Unidesk drivers on the OS Machine.
Ensure that this machine is not joined to a domain.
Note: Session Hosts will join a domain when you provision them from a Layered Image.
Optionally, you can shut down the new OS machine.
Notes:
To import an OS disk into Unidesk:
In the Unidesk ELM, select Layers > OS Layers and click Create OS Layer in the Action bar. This opens the Create Operating System Layer Wizard.
In the Layer Details tab, specify a Layer Name and Version, both required values. Optionally, you can enter Descriptions of the Layer and Version, and change the Max Layer Size to accommodate the OS you are going to import. For details, see more about these values below.
In the Connector tab, choose a Connector Configuration for the platform where you'll be publishing your Layered Images. If the configuration you need is not listed, add a New one and select it from this list. For information about creating a new Platform Connector Configuration, see Create a Connector Configuration.
Note: Alternatively, if you have a *.vhd file of the OS disk in your Network File Share, you can select the file share instead of a Unidesk Connector.
In the Import Disk Details tab, enter the name of the Azure Resource Group that contains the OS disk and the name of the OS disk, both required values.
Note: If you specified a file share on the Connector tab, enter the name of the OS disk residing on that file share or click Browse to select it.
In the Icon Assignment tab, select an icon image to assign to this Layer.
In the Confirm and Complete tab, review the details of the OS Layer, enter a comment if required, and click Create Layer. If you enter comments, they appear in the Information view Audit History.
When the task completes, the new OS Layer in the Unidesk Management Console displays a "Deployable" status.
Version - (Required) This can be the version of the OS Layer or a version you assign to the Layer. This value is displayed in the Details view of the OS Layer. It may be useful to include the date in the version name. Version names can be from 1 to 100 characters in length.