Unidesk App Layers, Image Templates, and Publishing

Last Modified: Jan 28, 2017 @ 3:49 pm

Navigation

Create App Layer

  1. In the Unidesk ELM Management Console, go to the Layers tab.
  2. Right-click in the grey, and click Create App Layer.
  3. In the Layer Details page, give the layer a name and version. Since the App Layer is tied to the OS Layer, it’s a good idea to include the OS Layer name in the App Layer name.
  4. Give the layer a Max Size. The layer disk created for the vSphere Packaging Machine is Thick Provisioned. Click Next.
  5. In the OS Layer page, select an OS Layer. An App Layer created for one OS Layer cannot be used with another OS Layer. Click Next.
  6. In the Prerequisite Layers page, you can select additional layers to include in your packaging machine. If there are no dependent layers, just click Next.
  7. In the Connector page, select a vSphere connector, and click Next.
  8. In the Platform Layer page, if you are creating the App Layer on a different hypervisor than originally used for the OS Layer, you can select the Platform Layer for the new hypervisor. If the hypervisor has not changed, just click Next. The hypervisor can also be changed when publishing the Image Template later.
  9. In the Packaging Disk page, give the .vmdk file a name, and click Next.
  10. In the Icon Assignment page, select an icon, or upload a new one, and click Next.
  11. In the Confirm and Complete page, click Create Layer.
  12. At the bottom of the page, open the Tasks panel.
  13. Click the information icon next to the running task.
  14. Eventually the task will finish deploying the Packaging Machine.
  15. In vSphere Web Client, find the new Packaging Machine (in the PackagingVMs folder in the Unidesk VM folder), open its console, and install your app normally. See Layering Recipes for some application install instructions.
  16. When you are done installing your app, double-click the Shutdown for Finalize icon on the desktop.
  17. It will tell you any issues it finds. After correcting them, double-click the icon again to shutdown the machine.
  18. After the machine is shutdown, in Unidesk ELM Management Console, go to Layers > App Layers.
  19. Right-click the Layer that is currently being Edited, and click Finalize.
  20. In the Script Path page, if you embedded any scripts in the layer, specify the path. Otherwise, just click Next.
  21. In the Confirm and Complete page, click Finalize.
  22. You can view the running tasks in the bottom window pane.
  23. It will eventually finish and say Deployable.

Image/Template

  1. In the Unidesk Management Console, go to the Images tab.
  2. Right-click in the grey, and click Create Template.
  3. In the Name and Description page, give the Template a Name that indicates the OS Layer, Platform Layer, and App Layers. Then click Next.
  4. In the OS Layer page, select an OS Layer, and click Next.
  5. In the Application Assignment page, select zero or more applications. Any App Layer you select here will be merged into the machine pre-boot. Elastic Layers are assigned later. Click Next.
  6. Note: if you find that App Layers are conflicting with each other, you can adjust the App Layer priority by using the Unidesk 4 Layer Priority Utility — Experimental tool.
  7. In the Connector page, select a Connector for the platform you want to push this image to. If publishing to MCS, select a vSphere Connector, and click Next.
  8. If you are publishing to PvS, and if you don’t have a PvS Connector, click New.

    1. From Connector Configuration & Optional Script (PVS) at Unidesk.com.
    2. In the Choose a Connector Type window, select Citrix PVS, and click New.
    3. A new tab opens.
    4. Give the Connector a name. This Connector points to one PvS server, and one vDisk store, so the name should reflect that.
    5. The Console field contains the list of registered Unidesk Agents running on PvS Servers.
    6. Enter credentials of a service account that is an administrator in PvS. Click Check Credentials.
    7. Scroll down. Use the drop-downs to select the vDisk store and other vDisk settings. Click Test.
    8. On the bottom, click Save.
    9. Then click Close.
    10. Back in the Connector page, select the PvS connector, and click Next.
  9. In the Platform Layer page, select one Platform Layer, and click Next. For PvS, make sure the Platform Layer includes both VDA and PvS Target Device Software.
  10. In the Layered Image Disk page, give the .vmdk file a name, specify a size, and decide if you want Sysprep to run or not. You typically don’t need to Sysprep the image if you’re using MCS, PvS, Composer, or Instant Clone.
  11. If you wish to enable Elastic Layering, select it here. Assignment of Elastic Layers to users is described later. Click Next.

    1. Notice that PvS does not have a SysPrep option.
  12. In the Confirm and Complete page, click Create Template.
  13. The Image is then displayed as Publishable.

Publish Image

  1. Right-click a publishable image, and click Publish Layered Image.
  2. In the Confirm and Complete page, click Publish Layered Image.
  3. Open the Tasks pane, and click the information icon to view details of the running task.
  4. If publishing to MCS (vSphere):
    1. In the vSphere Web Client, you’ll find the Template VM under the TemplateVMs folder under the Virtual Machine folder you selected for the Connector.
    2. Citrix MCS creates VMs in the same Folder as the Master Image. You might want to move the Template VM to a different virtual machine folder.
    3. If you edit the VM’s hardware, you’ll see that the disk is Thick Provisioned.
    4. Power on the machine.
    5. If doing Citrix Machine Creation Services, there is no need to join it to the domain. Some other provisioning platforms might require the machine to be joined to the domain, which you can do now.
    6. Shut down the Template VM.
    7. For MCS, in Citrix Studio, create a Machine Catalog using the Template VM as the Master Image.
    8. Notice that MCS creates VMs in the same Virtual Machine folder as the Master Image.
  5. If publishing to PvS:
    1. The image is uploaded to the vDisk Store as a .VHD file (not .VHDX).
    2. And it’s automatically added to the vDisk Store in the PvS Console. You can now assign it to your Target Devices.

Elastic Layers

  1. In the Unidesk Management Console, go to Layers > App Layers.
  2. Right-click a Deployable App Layer, and click Add Assignments.
  3. In the Select Version page, select an App Layer version, and click Next.
  4. In the Image Template Assignment page, don’t select anything. This page lets you assign this App Layer to a Image Template for pre-boot merging. For Elastic merging/mounting, just click Next.
  5. In the Elastic Assignment page, note any issues that Elastic Fit discovered that would prevent the app from merging elastically correctly. If you’re OK with the issues, click the Assign Elastically button.
  6. Search for a user group you want to assign this Layer to, and check the box next to the group. Click Next when done.
  7. In the Confirm and Complete page, click Assign Layer.
  8. Open the Tasks pane to see the progress while it copies the App Layer to the remote SMB share.
  9. When it’s done, go to the SMB share to see the files it uploaded, including the .json files that contain Layer assignments.
  10. To enable Elastic Layers in machines created from a Unidesk Image Template, edit the Template (Images), and make sure Elastic Layers is enabled in the Layered Image Disk page.

  11. Note: if you find that App Layers are conflicting with each other, you can adjust the App Layer priority by using the Unidesk 4 Layer Priority Utility — Experimental tool.

Update Layers

  1. Right-click an App Layer, and click Add Version.
  2. In the Version Details page, enter a new version, and click Next.
  3. In the OS Layer page, click Next.
  4. In the Prerequisites Layers page, click Next.
  5. In the Connector page, select a Connector, and click Next.
  6. In the Platform Layer page, click Next.
  7. In the Packaging Disk page, click Next.
  8. In the Confirm and Complete page, click Add Version.
  9. The task details shows the current progress.
  10. When the Packaging Machine is deployed, you can connect to its console and perform any desired updates. When you are done performing updates, double-click the Shutdown for Finalize icon on the desktop.
  11. When done updating the Packaging Machine, right-click the App Layer that is marked as Editing, and click Finalize.
  12. In the Script Path page, click Next.
  13. In the Confirm and Complete page, click Finalize.
  14. View the task details to see the current progress.
  15. To confirm that you have a new version, right-click the App Layer, and click Delete Versions.
  16. You can only delete versions that are not assigned to any Image.
  17. There are two methods of assigning a new version: one image at a time, or multiple images.
  18. To edit one image:
    1. Go to the Images tab. Right-click an Image, and click Edit Template.
    2. Click the Application Assignment page.
    3. Click the plus arrow next to a Layer and select the new version. Then complete the wizard.
  19. To update multiple images:
    1. Right-click the updated layer, and click Update Assignments.
    2. In the Select Version page, select the version you want to assign, and click Next.
    3. In the Image Template Assignment page, select the templates you want to update, and click Next.
    4. In the Elastic Assignment page, if this App Layer is assigned to users, you can update them too. Click Next.
    5. In the Confirm and Complete page, click Update Assignments.
  20. Once an image has a new version assigned, you must republish it.

3 thoughts on “Unidesk App Layers, Image Templates, and Publishing”

  1. Carl, how have you been defining the PVS device collection with overflow disks? Previously you would create a master target, attach a D drive for overflow/persistent folder structure, and then use a PVS device wizard to spin off X total PVS targets using a template based off of the master target. I think when you do publish image #2 operation from the Unidesk console, that new PVS vDisk file has no knowledge of a D drive and pointers to it for persistent folder locations like D:\EventLogs, etc.

  2. Spot on as always. Thanks 🙂 When you have published an updated image, you have to go in to Citrix Studio and change machine in machine catalog manually there, correct?

Leave a Reply