Install the JumpCloud Agent with a Template or System Image

A template or system image can be used to efficiently set up multiple devices that include the JumpCloud agent and are all configured exactly the same way. This uniformity is helpful when troubleshooting technical issues.

After you customize the OS, applications, drivers, and settings on a single computer (the imaging host), pre-install the JumpCloud agent before creating the image and deploying it to other computers.

Any device deployed from the template or image has a unique device record in your JumpCloud organization.

Considerations:

  • Pre-installing the agent on a template or image doesn’t create any JumpCloud user account associations. You must associate users with devices after the unique device record is created because the template isn’t a unique record. You can automate user associations with JumpCloud’s API.

Warning:

Do not reboot the device or restart the agent after removing the files in Step 4 of the following procedure. The agent is configured to start on boot. When the agent starts, it recreates the files and creates a unique device record in your organization. Deploying from an image with certificates and configuration files in place results in duplicate device records.

To pre-install the agent on a template or system image:

  1. Before proceeding with installing the agent on a Windows imaging host, ensure that you do not have automatic enrollment enabled on Windows 10 & 11 devices:
    1. Log in to the JumpCloud Admin Portal.
    2. Go to DEVICE MANAGEMENT > MDM.
    3. Click the Windows tab.
    4. Ensure that the Automatically enroll all Windows 10 & 11 devices into Windows MDM checkbox is disabled.

Note:

After you have completed creating or updating the system image, you can re-enable this option.

  1. On the imaging host, install the agent from the Admin Portal or the command line.
  2. Stop the agent on the imaging host in one of the following ways:
    • Windows: sc stop jumpcloud-agent
    • Linux: service jcagent stop
      • For newer Linux devices with systemd, you can also use systemctl: systmctl stop jcagent
  3. Remove the following files: ca.crt, client.crt client.key, and jcagent.conf.
    • Use one of these methods to remove the files:
      • Windows – Open the following folder and remove the files: C:\Program Files\JumpCloud\Plugins\Contrib
      • Linux – Run the following command: sudo rm -f /opt/jc/ca.crt /opt/jc/client.crt /opt/jc/client.key /opt/jc/jcagent.conf
  4. Remove the device record created for this template in the Admin Portal, otherwise this device is orphaned. All operating systems use these steps: (You can also use the JumpCloud API.)
    1. Log in to the JumpCloud Admin Portal.
    2. Go to DEVICE MANAGEMENT > Devices.
    3. Select the checkbox next to the imaging host.
    4. Click delete.
  5. Configure the template or image to set unique network parameters such as hostname, IP, MAC, before the agent starts. This forces the agent to use the details for the specific device when it checks in with JumpCloud rather than using those assigned to the template.
  6. Without rebooting the imaging host, create the template or image.
  7. Associate users with devices in the Admin Portal or JumpCloud API.
    • Admin Portal:
      1. Log in to the JumpCloud Admin Portal.
      2. Go to DEVICE MANAGEMENT > Devices.
      3. Select a device.
      4. Select the Users tab.
      5. Select the checkbox for the user’s account.
      6. Click save device.
    • JumpCloud API:

Notebook IconLearn More

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case