Using Workspot Templates

Robert Plamondon -


Starting with Control R11.3, you can create new Workspot desktop templates from a prepopulated list of Azure Marketplace images. These images can be turned into templates which you can modify and use in your Workspot desktop pools.

This document describes the process for creating and managing such templates.

Template Concepts

A Workspot template is a desktop image file that includes the Workspot Agent. In this document, we are concerned only with Azure-compatible templates.

  • Templates are configured for a specific virtual network and Azure region.
  • A template must have a local administrator account that you use to sign into the template to manage and customize it.
  • Templates can join an AD domain.
  • All these characteristics are inherited by desktops created from the template, and by other templates cloned from the parent template.

Template Workflow


Create the template. First you select one of the Azure Marketplace images available in your region. This will create a template in Draft mode, which launches the template VM, where it is ready for customization.

Customize the Draft-mode template. Next, you sign into the template using its local administrator account. Then you install your software and change system parameters until the template seems ready for your users.

Preview the template. From Draft mode, can optionally put the template into Preview mode, which powers it down and makes it available for selected Preview users. When you create a desktop pool from a Preview-mode template, the members of the Preview group receive desktop entitlements in that pool. A template in Preview mode can be returned to Draft mode if you need to make more changes.

Note: Only a single pool can use a given Preview-mode template.

Publish the template. Finally, you put the template into Published mode, which makes it available for use by ordinary users once you build or edit a pool to use the template.

Clone the template. Published templates can no longer be customized, but they can be cloned, creating a new template from the existing one. The clone is powered up and placed into Draft mode, ready for customization.

A clone starts out identical to its parent except for a new name, a different Notes field, and the option of selecting a different virtual network in the same region, if any.

Since cloning retains all the customizations of the parent template, this is the preferred way of creating a new template when changes aren’t too sweeping. For example, you would start with a clone if the only changes you wanted to make were to install updates.

Commands Allowed with Different Template Status

Different template states allow different commands. The Clone command is only available for Published templates, for instance. The complete matrix is shown below:


Draft Mode

Preview Mode

Published Mode













Creating or Cloning a Template

  • To create a brand-new template, you select an Azure Marketplace template and customize it.
  • To update an existing, customized template, you first clone it and then update the cloned template.

The two processes are similar. Cloning a template has fewer steps and prompts you for much less information since it inherits most of its configuration from the parent template.

The process below is for creating a new template. Follow the same procedure for cloning, but be aware that the process skips many of the steps below.

  1. Templates are created and cloned on a per-Cloud-Subscription basis, so the first step is to go to “Setup > cloudname.
    • For a new template, click the Build Template” button. This will pop up the “Build Template” page.
    • To clone a template, select "templatename > Actions > Clone."


templates-2.pngCreating a template via “Setup > cloudname > Build Template.”

  1. Fill in the “Build Template” form, as described below:


The Build Template page, shown filled in with typical parameters.

    • Region. Click the “Browse” button. This pops up a window that lets you select from the virtual networks defined for your Workspot network. Each virtual network is associated with an Azure region. Select one of these. Note: The search box is non-functional. Just click the “Browse” button.
    • OS Type. Select whether the “Image” pull-down menu will show Windows Desktop or Windows Server images.
    • Image. A pull-down menu that lists the images available in the selected region. These will generally be Azure Marketplace images. Select one of these.
    • Template Name. Enter a name for your template. Use printable ASCII characters.
    • Template VM. Click the “Select” button and choose the most appropriate VM from the list. This does not select a VM size for the desktops that will use the template. Instead, it selects the VM size for the template VM itself. It can be smaller than the eventual desktop VM, but it needs to be big enough to allow software to install successfully on the template.
    • Note. A text field that lets you include notes about the template for your own reference.
    • Setup Domain Join. If checked, you will be prompted (after clicking “Create Template”) for domain administrator credentials that will be saved in a secure wallet to allow the template (and desktops built from the template) to join your domain.
    • Create Template. Click “Create Template.” Control will prompt for domain administrator credentials, if selected, and credentials for a local administrative account. Afterwards it builds the template.
  1. Join the domain. If you have checked the “Setup Domain Join” box, you will be asked to join the domain via the “Domain Join” popup. Both the template and any desktops built from it will use these parameters to join the domain. Domain administrator credentials are stored in the VM’s secure wallet. Enter the appropriate domain name, OU string, and the credentials of a domain administrator’s account.


  1.  Create Local Admin Account. The “Create Local Admin Account” popup appears next. You will use this account to sign into and administer the template VM. Enter a login and password for an administrative account that will be created on your template VM (and all desktops built from the template).


The local admin account allows administrative access
to the template VM for customization.

  1. Wait for provisioning. Once the credentials are entered, the template begins provisioning. When provisioning is complete, its status will change to Draft.


Sign into the Template

To sign into your template VM, use a jump server on your Workspot virtual network. For example, the jump server can be your desktop in an existing Workspot desktop pool.

  1. Sign into the Workspot Client and launch your existing Workspot desktop.


Use an existing Workspot desktop as a jump server.

  1. Sign into the template VM. From your Workspot desktop, Use Remote Desktop Connection to sign into the template VM.
    • You can find the template VM’s IP address by expanding its entry on the “Manage Subscription” page.


Discovering the IP address of your template VM.

  • On the Workspot desktop, launch Remote Desktop Connection and sign into the template VM using the local administrator credentials you set earlier.


Connect to the template VM using Remote Desktop Connection.

  • You will see a Remote Desktop security warning, since the template VM uses a self-signed certificate. Accept the certificate to continue.


This certificate warning is expected.

  • You are now signed into your template VM as the local administrator.


Remote Desktop window after signing into template VM (will very with choice of template).

Customize the Template

Once you have signed into the template, you can install software and adjust system settings to match the needs of your users.

In the example screen capture below, the system default wallpaper has been changed and Firefox has been installed, plus other changes that aren’t visible in the screen capture, such as running Windows Update.

The Workspot Agent will update itself automatically after the template boots in Draft mode.


A template after installing Firefox and changing the default wallpaper system-wide.

Adjusting System Settings

See Workspot Desktop Templates: Recommended Optimizations for a list of recommended settings, most of which use the Group Policy Editor.

For example, with non-persistent desktop pools, setting appropriate session idle timeouts is essential to ensure that the desktops are returned to the pool after the user has finished with them.

Once the template VM is set up to your satisfaction, it can be shared with a pool of selected users by putting it into Preview mode.

Preview Mode

The next step is to put the template into Preview mode via “Setup > cloudname > templatename > Actions > Preview.” A template in Preview mode can be used to create a Preview pool, which will be shared with Preview users.


Placing a template into Preview mode.

Creating a Desktop Pool Using a Preview-Mode Template

This is the same as creating any other desktop pool, except that when selecting a template, check the “Preview” box and click the Search button to show the templates in Preview mode. Select the desired template.


Creating a desktop pool using  Preview template.

See Control: Desktop Pools for general instructions for creating desktop pools and Workspot Desktop Templates: Recommended Optimizations for recommended settings.

Note: Only a single pool can be created from a given Preview-mode template.

Preview Pool Group and Preview Users

On the “Users > Groups” page, the Preview Pool group defines which security policy, network policy, app policy, and VPN are used with Preview-mode desktops.


The Preview Pool Group determines who has access to Preview desktops.

The purpose of the Preview Pool Group is to allow selected users to test the new templates. To add users to the Preview Pool Group, change the group membership for the selected users via “Users > username > User Profile > Actions > Change Group > Preview Pool Group.”


Adding a user to the Preview Pool Group.

Members of the Preview Pool Group will see desktops on each of the Preview pools in the Workspot Client.


Preview pool desktops are shown in the Client for each user in the Preview Pool group.

Publishing the Preview Template

If changes need to be made to the Preview template, put it back into Draft mode via Setup > cloudname > templatename > Actions > Draft”  and customize it as before.

When it’s ready for ordinary users, put it into Published mode via Setup > cloudname > templatename > Actions > Publish.” After publication, you can assign the template to new desktop pools or to existing desktop pools using the “Resources > VDI Pools > poolname > Actions > Update Image”


Publishing a template.


Assigning a template to an existing pool via Update Image.

Updating Published Templates

A published template cannot be put into Draft mode. Instead, clone it via Setup > cloudname > templatename > Actions > Clone.” The clone will be placed into Draft mode and you can continue as with any other Draft template.

 Related Documents


Have more questions? Submit a request


Powered by Zendesk