Creating a Template Image for Horizon Instant Clones

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

How to create Template Image for use with Horizon Instant Clones

Environment

• App Control Server: All Supported Versions
• App Control Agent: All Supported Versions
• Omnissa Horizon Instant Clone Desktop Pool

Resolution

PLEASE NOTE: Use of Agent version 8.10.2+ with Horizon Instant Clones is suggested to avoid an issue due to the Omnissa rebrand. Reverting the Golden Image to a previous Snapshot will cause the Server to see this as a new Instant Clone and the Unlink process will be required. Updating the Template Image should follow this same process, always use the original Golden Image. Do not use a Clone of a Template.

1. Install all required software before installing the App Control Agent (for new installs).
2. In the Console > Assets > Computers > relevant Computer (Golden Image) > open the Details > Verify:
   • No Parent Template Computer is listed on the page (Computer is not a Clone). If necessary, unlink it from the old Template Computer.
   • Initialization is Complete.
   • Synchronization is 100%.
3. Shutdown the Golden Image.
4. In the Console > Computer Details page > right hand menu > Advanced > Create Template Image.
   • After clicking OK to the Warning the Template Details page will load for the new Template Computer.
   • At this time, initiate a Snapshot of the Golden Image in the VSphere Console & Redeploy the Pool using the new Snapshot.
5. Return to the Console and from the Template Details page specify the:
   • Template Name
   • Clone Inventory settings
   • Clone Cleanup
6. The defaults for Internal Template should be used:

   Internal Template: Standard
   Check the box if Clones are joined to an Active Directory domain
   Prefix: IT
   Suffix: Leave blank
   Which characters may exist between the prefix and suffix?
   Check the box for "Numbers (0-9)" only

7. Internal Template Tests: this is used to verify the Instant Clone VM names don't accidentally match the Internal Template name. If they do, this would cause the App Control Clone process to fail.
   • Horizon's default Internal Template name pattern looks like "it1234567", it is very uncommon that this was changed
   • App Control requires the Internal Template name be input in capitals. Example: "it123567" to "IT1234567"
   • For example if the Instant Clones are named as "IT1,IT2..." this will match the pattern of the Internal Template name "IT1234567" and the test will fail
   • To pass the test enter a sample Internal Template name and a sample Instant Clone VM name example:

     Internal Template: DOMAIN\IT12345667
     Clone Machine: DOMAIN\MYCLONE-1

8. A sample Template Configuration will look like this:
   
9. Save the Template.

Additional Information

• Template Image option should only be used for Horizon Instant Clones.
• Template Computer option should but used for all other Clone types, and should no longer be used for Instant Clones.
• The Golden Image may get removed from Assets > Computers due to Old Computer Cleanup. This will not impact the Template Computer or the Clones.
• When the Golden Image is booted again, it should show in Assets > Computers again.
• Unlinking the Clone in Step 2 will require a new Initialization and File Synchronization.
• Many customers choose the Clone Inventory option, "New and modified files" for Non-persistent environments for performance reasons.
• More details can be found in the App Control User Guide chapter, "Managing Virtual Machines".