JumpCloud Agent Compatibility, System Requirements, and Impacts

This article includes details about OS compatibility, installation requirements, and changes made to your device during installation of JumpCloud’s agent. Use this information to perform these tasks:

• Make sure you’re using a supported OS before you install the agent.

• Find the files and directories used during installation to troubleshoot issues.

• Verify files and directories are installed correctly before you contact Support.

You can review our prospective end of support timelines in Prepare Now for End of Support.

Note: JumpCloud supports iOS devices, such as iPhones, iPads, and Apple TVs, but the JumpCloud agent is not installed on those devices. 

Mac

Supported macOS versions

• Big Sur 11.x

• Monterey 12.x

• Ventura 13.x

• Intel and Apple Silicon devices are supported.

Considerations

• For Macs running macOS Monterey and later, the JumpCloud Agent requires Full Disk Access permissions to enable communication with the authentication controls on the device. 

• Pre-release or Release Candidate (RC) versions of OS releases are not supported.

• If the JumpCloud agent is installed on an unsupported version, JumpCloud neither ensures nor provides guarantees full or even partial functionality of device management. Furthermore, functionality may or may not work as intended and may be hindered based on future product releases:

• As of December 15, 2021, we will no longer support the JumpCloud agent on macOS Mojave 10.14.

• As of November 30, 2020, we don’t support the JumpCloud agent on macOS High Sierra 10.13.

• As of June 30, 2020, we don’t support the JumpCloud agent on Debian 8 systems.

• As of April 14, 2020, we don’t support the JumpCloud agent on macOS Sierra 10.12.

Note: If an unsupported device is assigned to the JumpCloud MDM server in Apple Business Manager (ABM), it will attempt to install the agent, which will generate an error and cause the device to hang at the install screen. The device will need to have the JumpCloud MDM server unassigned in ABM. This can be done by removing the JumpCloud MDM server from the Default Device Assignment under Device Management Settings or by changing the Device Management settings for the individual device.

Warning: Do NOT release the device from ABM. Devices released from ABM will need to be re-enrolled using Apple Configurator for iOS. See the Apple Configurator User Guide.

Changes Made to Your MacOS Device During Installation

Changes Made to Your Windows Device During Installation

Additional Windows Considerations

• After you create a JumpCloud account for a user and the account is active, you can associate the user with a JumpCloud-managed Windows device. When you bind a user to a device, we add the user’s account to the following local groups:

  • Standard User Windows Local Groups (for user accounts with no local administrator permissions):

    • Users

    • Remote Desktop Users

  • Administrator User Windows Local Groups(for user accounts with local administrator permissions):

    • Administrators

    • Users

    • Remote Desktop Users

  • If you manually remove a user account from one of these groups, the agent on the Windows device restores these associations when you save any changes in the Administrator Portal.

• Windows Live! isn’t supported. 

• See JumpCloud agent Port Requirements.

• See Adding the JumpCloud agent to an allow list.

Linux

Core packages are central to the running of a Linux distribution because they contain files for functionality, such as connecting to the Internet, managing and repairing file systems, and the system setup process (e.g. openssh). The packages you’re required to install for the JumpCloud agent to work varies by OS version and are listed in the following table.  

Considerations

• Release Candidate (RC) versions of O/S releases aren’t supported.

• If the JumpCloud agent is installed on an unsupported version, JumpCloud neither ensures nor provides guarantees full or even partial functionality of device management. Furthermore, functionality may or may not work as intended and may be hindered based on future product releases:

  • As of December 2022, we don’t support the JumpCloud agent on the following systems:

    • CentOS 8

    • Fedora 35

  • As of September 2022, we don’t support the JumpCloud agent on the following systems:

    • Debian 9

    • Fedora 34

    • Mint 18

    • Ubuntu 21.04

  • As of August 8, 2022, we don’t support the JumpCloud agent on Amazon Linux 2013 – 2018.

  • As of April 30, 2021, we don’t support the JumpCloud agent on Ubuntu 16.04.

  • As of November 30, 2020, we don’t support the JumpCloud agent on the following systems:

    • CentOS 6

    • RHEL 6

    • Ubuntu 19.04

  • As of June 30, 2020, we don’t support the JumpCloud agent on Debian 8 systems.

Supported Linux Versions