Phase 3: Templatize

After a successful build, templatizing saves the current state of all your VMs as a reusable template. This template is what students actually deploy — each deployment gets a fresh copy of the templated VMs.

Note

This phase unlocks after completing a successful build with zero errors. If your build has errors, resolve them first using Redeploy.

Before You Templatize

Take a moment to verify your build is correct:

1. Open the Infrastructure panel in the left dock to see all your VMs
2. Click on VMs to open them in a new window
3. Log in and confirm services are running, configurations are applied, and the scenario works as intended

This is your last chance to catch issues before the template is created. Anything wrong with the VMs will be baked into the template.

Creating the Template

1. Click Templatize Build in the top-right control panel
2. The system snapshots all VMs and converts them into a template
3. The status badge shows Converting with a task countdown while this runs

The conversion process takes a few minutes depending on the number and size of your VMs. Once complete, your template is saved and ready for the next phases.

What Templatizing Does

• Snapshots every VM in its current state
• Packages them as a template that can be deployed repeatedly
• Enables the Publish phase — you can’t publish without a template

Each time a student deploys your scenario, they get a brand-new copy of these templated VMs. Your original build remains untouched.

Updating a Template

If you need to make changes after templatizing:

1. Go back to the canvas and modify your design
2. Use Redeploy to rebuild from the last checkpoint
3. Verify the updated build
4. Click Templatize Build again to create a new template version

The previous template is replaced with the updated one.