Workspot made the creation of a template simple through the Build Template option in Control. On each cloud environment (Azure, GCP, AWS, On-Prem) the actual steps for creating and cloning templates will differ. At a high-level the following steps are involved to build a new template.
Example of a Windows Template:
Install Workspot Agent
Provide domain joined details through Workspot Configuration Editor
Requires a service account with appropriate permissions to create and delete computer object in an OU in AD
Optional
In case there is a need to add users or Groups to VM local group, provide the details. We recommend our customer to use group policy to manage user & group memberships.
In case there is a need to execute any script before domain Join, WSCompleteSetup can be used.
In case there is a need to execute any script after domain Join, WSRunOnce can be used.
In case there is a need to execute any script at every reboot or Agent restart, WSCustomeStartup can be used.
For more details, Please refer to
Most of our customers use non-domain joined templates to provision VMs. However, if the need to use a domain join Template you can install the Workspot Agent in the template which provides the renaming the cloned template and joining.
For non-domain joined templates:
Workspot recommends that administrators clone the existing template. Then make the changes before publishing the template and assigning it to a pool.
For domain Joined Templates: During the VM provisioning administrators can utilize the Workspot Agent to remove the VM from the domain and based on the desktop name, rename the VM and rejoin the VM with the new desktop name.
Snippet from the Desktop Agent Log file:
When a template is cloned from Control (support for only Cloud environment) Control and the Workspot Agent will complete the registration process of new template. However, when a customer clones a template at a hypervisor level, Control will be unaware of the clone. So for hypervisor level clones the process works like this. Again it will vary based on cloud provider.
VMWare Hypervisor example:
Clone the existing Template.
If the source template is domain joined a few extra steps, we need to consider:
Domain Joined template.
When powering on the first time, make sure NIC is disconnected. Thus, the VM should not communicate to AD. Else, the cloned VM change the SID in the AD as a result the first machine (template) won’t be able to communicate with AD.
Login to the Cloned template and change from Domain to Workgroup
Reboot the VM
Connect the NIC back. (MAC address should not be same, as Agent registration is closely affiliated with MAD id)
Join the clone VM to the domain with a unique Computer Name.
Uninstall the Desktop agent from the Cloned VM
Reinstall the Desktop Agent in the Clones VM with details to register with Control as a Template.