Deploying the JumpCloud Agent using a Template or System Image
The JumpCloud agent can be pre-installed on any supported OS to be used on a template or image for rapid system deployment.
- Any system deployed from the template will result in a unique system record in your JumpCloud organization.
- Preinstalling the agent on a template does NOT allow for automatically carrying over any user bindings made to the image. Binding users to systems needs to be done after the unique system record is created, by design, the template is not a unique record. Automating user binding can be done via the API.
- IMPORTANT: DO NOT reboot the system or restart the agent after removing the files listed below. The agent is configured to start on boot. When the agent starts, it recreates the files and also creates a unique system record in your organization. Deploying from an image with certs and conf files in place will result in duplicate system records where only the most recent to check in will show active.
- Recommended: On deploy, the template should be configured to set a unique hostname, IP, MAC, etc.. BEFORE the agent starts, so when the agent scans for system details, it will check in to JumpCloud with those unique attributes, rather than those assigned to the template.
- Install the agent as usual, whether from the command line (Linux, Mac) or its GUI installer (Mac).
- Stop the agent on the imaging host, and run the following:
Linux / Mac
sudo rm -f /opt/jc/ca.crt /opt/jc/client.crt /opt/jc/client.key /opt/jc/jcagent.conf
Remove the files of the same name above, but found in the path:
C:\Program Files (x86)\JumpCloud\Plugins\Contrib
- Remove the system record from your organization created for this template, it will be orphaned if left in place.