Machine Template

A Machine Template provides a standardized way to onboard and manage Robility Runner deployments across multiple host machines using a single template configuration. Instead of performing machine-by-machine setup, each Runner instance uses the template configuration to register and establish connectivity with Robility Manager automatically.

Machine Templates are recommended for golden image deployments, pooled or auto-scaled VMs, VDI/Citrix environments, and other scenarios where machines are frequently created, refreshed, or replaced.

Automation executes on available/online machines associated with the template. If a machine is unavailable, execution will start when a compatible machine becomes available.

Pre-requisites

1. A Machine Template must be created in Robility Manager.
2. The generated Machine Template XML must be downloaded.
3. The XML must be placed in the required folder under the Robility Runner installation path.

Limitations

1. Machine Template support adding up to 200 users per template from the Resource page in Robility Manager.

Key Features

1. Centralized template configuration: Define connection and execution settings once in Robility Manager and apply them across multiple machines.
2. Scalable onboarding: Enable rapid provisioning for pooled or dynamically created machines without per-machine setup.
3. Automatic registration and connection: Robility Runner reads the Machine Template XML from the standard location and connects to Robility Manager automatically.
4. Resilient connectivity: Runner supports periodic reconnect attempts when connectivity is interrupted or the Runner state changes.
5. Standardized provisioning: Ensures a consistent Runner setup across multi-user and multi-machine environments.

Where Machine Templates Apply

Machine Templates are recommended for environments where machines are shared, frequently recreated, or non-persistent, and you need consistent unattended onboarding without per-machine configuration.

1. VDI/Citrix-hosted environments: Where Runner instances run on centrally hosted machines and must be provisioned consistently across sessions.
2. Pooled / auto-scaled / non-persistent VMs: Where machines are frequently created, refreshed, or replaced and require repeatable onboarding.
3. Multi-user Windows servers: Where Runner instances run under separate Windows accounts to maintain isolation and permissions.
4. Unattended automation deployments: Where Runner instances must run reliably without interactive user login.

Step 1 — Create a Machine Template in Robility Manager

1. Log in to Robility Manager. 
2. In the left panel, go to Resources.
3. Click + Add and select Machine Template.
4. Provide the following details:
           a. Machine Template Name: Enter a unique name
               (example: Invoice_Automation_Template).
           b. Domain: Specify the domain where machines and bot users are registered.
           c. User Accounts: Add the bot execution user(s) (example: Bot_admin).
           d. Password: Enter the password required for unattended execution
               (as applicable).
5. To add additional bot users, click the + (Add) icon and enter the usernames and passwords.
6. Click Save.

After saving, Robility Manager generates the Machine Template XML for Runner onboarding.

Step 2 — Configure the Machine Template on Robility Runner (Golden Image / Host Machines)

2.1 Download the XML from Robility Manager  

1. In Robility Manager, locate the created Machine Template.
2. Download the XML shown next to the template.

2.2 Copy the XML to the Runner installation path  

1. Navigate to the Robility Runner installation path using one of the following methods:
         a.Right-click the Robility Runner shortcut and select Open file location
            OR
         b. Open the path directly using Run: C:\Program Files (x86)\RobilityRunner
2. Create a folder named exactly: MachineTemplate
3. Copy the downloaded XML file and paste it into: 
    …\RobilityRunner\MachineTemplate\
4. Restart Robility Runner (recommended).

Runner detects the XML and connects successfully within ~60 seconds.