You can create Image Templates to publish Layered Images to your target platform where you can then use the Layered Image to provision servers on your chosen publishing platform. An Image Template stores your Layer assignments, along with a Layer icon and description. You can easily edit an Image Template and use it to publish new versions of your Layered Images.
To create an Image Template you need:
- A Platform Layer containing the software required for your environment.
- The Platform Layer you choose must have the same hardware settings as the OS Layer you are using. (The hardware settings are chosen when you deploy the VM for the OS and Platform Layers.)
- The Platform Layer you choose must contain the software required for your environment, including for your hypervisor, and for any provisioning service and connection broker.
Create an Image Template
To create an Image Template:
- In the App Layering Management Console (UMC), select the Images module, then click Create Template. This opens the Create Template wizard.
- In the Name and Description tab, enter a Name for the template and notes in the Description field, so you can identify the template when choosing one for publishing a Layered Image.
- In the OS Layer tab, select one of the Available OS Layers. If there is more than one Layer Version, the most recent version is selected by default. You can choose an older version by expanding the Layer and choosing a different one.
- In the App Assignment tab, select the App Layers to include in the Layered Images that you publish using this template.
On the Connector Configuration tab, select the Network File Share.
On the Platform Layer tab, you can select a Platform Layer that contains the tools and hardware settings that you need to publish Layered Images to the location defined in the Connector Configuration.
On the Layered Image Disk tab:
- Layered Image Disk File name. (Optional) You can change the default Layered Image Disk File name.
- Layered Image Disk Format. Select the Disk Format appropriate for the environment where your servers are running. For example, select VHD when publishing images to Azure or Hyper-V environments. Select VMDK when publishing images to vSphere or PVS, for example, when streaming the images to vSphere servers. Or, select QCOW2 or VHD when publishing to Nutanix AHV.
- Layered Image Disk Size. The default disk size of 100 GB is recommended.
- Sysprep. If your Platform Target is a Network File Share, this option lets you choose the method for generalizing the Layered Image. Select the method that is appropriate for your connection broker.
- Not Generalized - Does not generalize the Layered Image nor join a domain. Machines created from this image will be identical to the OS Disk from which they are created. Machines created from this image will be identical to the OS Disk they are created from.
- Generalize Offline - Generalizes the Image using Unidesk code, and without booting the VM. Machines created from this image will be unique, and will run unattend.xml to join a domain.
- Elastic Layering - Select the Application Layering option to enable Elastic Layering on this Layered Image.
- User Layer - (Labs feature) When enabled in System Settings, you can select the Office 365 option to save the settings and data for users assigned an Office 365 App layer. Similarly, the Full option saves the settings and data for users assigned any other App Layer (exclusive of Office 365.)
- On the Confirm and Complete tab, enter any comments you would like for this layer, and click Create Template.
The new Template icon appears in the Unidesk Images module.