Embedded Files
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
Additional MacOS Considerations:
For all supported macOS versions, a native Administrator service account is created, and credentials are required during installation for support with secure token in conjunction with FileVault.
Syncing login passwords with Apple’s iCloud service is not supported, and attempting to turn it on may result in undefined and unsupported behavior.
JumpCloud is proud to natively support Apple silicon Macs.
Windows
Windows
Supported Windows Versions:
10 (64 bit)
11
Server: 2012 R2
Server: 2016 (64 bit)
Server: 2019
Server: 2022
Considerations:
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 June 16, 2023, the JumpCloud agent will not be updated past version 1.115.1 on 32-bit devices.
As of June 16, 2023, the JumpCloud tray application will not be updated past version 1.32.0 on 32-bit devices.
As of February 18, 2022, JumpCloud no longer supports Windows 8.1.
Beginning on May 11, 2021, we only support Windows 10 build 1909 and above. Learn more: Windows 10 Release Information.
As of June 30, 2020, we don’t support the JumpCloud agent on 32-bit devices.
As of June 30, 2020, we don’t support the JumpCloud agent on Windows 8.
As of April 14, 2020, we don’t support the JumpCloud agent on Windows 7 or Windows 2008 + R2.
International versions of Windows are supported. However, certain international character sets may cause the following issues:
Cosmetic issues in the Devices detail views
Adverse results in Command execution in the Admin Portal
Non-English locales aren’t supported by JumpCloud policies
Home versions of Windows are supported in the following ways:
The JumpCloud agent can be installed
Conditional access is supported
JumpCloud policies and security commands are currently unsupported
Enhanced Security Configuration on Windows Server 2019 blocks our ability to auto-select the certificate in Internet Explorer and certain versions of Edge; disable Enhanced Security Configuration for users so that they aren’t prompted when accessing JumpCloud-managed resources.
Release Candidate (RC) versions of O/S releases are not supported.
The JumpCloud agent is not compatible with Duo System Agent Authentication for Windows.
The JumpCloud agent does not support Windows ARM devices.
Note: PowerShell is required for Windows agent functionality.
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.
Linux
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
Linux Installation Requirements
Changes Made to Your Linux Device During Installation
Additional Linux Considerations:
For Linux account takeover to complete successfully, the /home/directory must exist for that user.
If it’s not already installed by default, an admin will need to install OpenSSH server for the specific case where they intend to require MFA to log in via SSH. If MFA is desired over SSH, ensure openssh-server is installed before installing the agent.
Page updated
Report abuse