Support Center

JumpCloud Agent Compatibility, System Requirements, and Impacts

This document details operating system compatibility and associated system impacts of the JumpCloud agent. 
 

Mac
Windows
Linux

 

Mac

Note: Legacy installations of the JumpCloud Agent on 10.12 are supported, however functionality may be limited. JumpCloud Support will recommend upgrading to 10.13.6 or higher for issues found to be related to 10.12.  

 
Supported Versions 10.12, 10.13.6, 10.14
Installer Filename jumpcloud-agent.pkg
LaunchDaemon com.jumpcloud.darwin-agent
Primary install directory /opt/jc/
Installation and service logs
 
/var/log/jc*, /opt/jc/*.log
Location of the JumpCloud Mac App tray log ~/Library/Logs/JumpCloud
Custom Login Window /Library/Preferences/com.apple.loginwindow.plist, /Library/Security/SecurityAgentPlugins/jumpcloud-loginwindow.plist
When enabled, TOTP key files are stored on a per user basis at this path  /etc/ssh/jumpcloud/totp/${USER}
JumpCloud manages this based on users having uploaded public keys to JumpCloud
/Users/${USER}/.ssh/authorized_keys
JumpCloud appends sudo users to /etc/sudoers.d
Disk Usage ~14 MB
Memory Usage ~5 MB

Additional Considerations
 
 

Windows

 
Notes:

International versions of Windows are supported, however, certain international character sets may cause cosmetic issues in the Systems detail views and/or adverse results in Command execution in the Admin Console.

Installation of the JumpCloud Agent is currently supported for Windows Home versions, however JumpCloud Policies are currently unsupported.  

 
Supported Versions 7, 8, 8.1, 10 (32 and 64 bit) 
Server: 2008 R2 (64 bit), 2012 R2, 2016 (64 bit), 2019
Dependencies MS Visual C++ 2013 Redistributable package (x86_64)
Installer Filename JumpCloudInstaller.exe
SERVICE-NAME jumpcloud-agent
Primary location of jcagent for 64 bit C:\Program Files\JumpCloud
Primary location of jcagent for 32 bit C:\Program Files (x86)\JumpCloud
Service log C:\Windows\Temp\jcagent.log
Installation log C:\Users\user\AppData\Local\Temp\jcagent.log
Disk Usage ~47 MB (incl. dependencies)
Memory Usage ~6 MB

Registry: 
  • HKEY_LOCAL_MACHINE\SOFTWARE\JumpCloud\JumpCloud Agent\ConfigFile
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{96542816-DAD1-4D02-8363-CA4121E5CAE7}_is1

Additional Considerations
 
 

Linux


Supported Versions: 
 
OS Requirements
Amazon Linux 2013.09-2018.03 chkconfig coreutils curl glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux yum sudo dmidecode psmisc redhat-lsb-core
Amazon Linux 2 chkconfig coreutils curl glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux yum sudo dmidecode psmisc redhat-lsb-core
CentOS 6, 7 chkconfig coreutils curl findutils gawk glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux which yum sudo policycoreutils psmisc redhat-lsb-core
RHEL 6, 7, 8 chkconfig coreutils curl findutils gawk glibc-common grep initscripts lsof net-tools rpm shadow-utils tar util-linux which yum sudo psmisc redhat-lsb-core
Debian 8 (64 bit), 9 (64 bit) apt-rdepends apt-show-versions coreutils curl dpkg grep hostname libc-bin lsb-release lsof mawk passwd procps sysv-rc sysvinit-utils tar libpam-runtime libpam-modules sudo psmisc gdebi-core
Ubuntu 14.04 apt-rdepends apt-show-versions coreutils curl dpkg grep hostname libc-bin lsb-release lsof mawk passwd procps sysv-rc sysvinit-utils tar sudo gdebi-core
Ubuntu 16.04 (64 bit), 18.04 (64 bit) apt-rdepends apt-show-versions coreutils curl dpkg grep hostname libc-bin lsb-release lsof mawk passwd procps sysvinit-utils tar sudo gdebi-core

File and System Impacts
 
Installer Filename jcagent-os-version-arch.pkg
Installed services jcagent, agent-monitor (init.d systems)
Primary install directory /opt/jc/
service control scripts /etc/init.d/jcagent, /lib/systemd/system/jcagent.service
The Google auth pam plugin is the OS and arch lib dir, for example: /lib, /lib64, etc. /security/pam_google_authenticator.so
Installation and service logs /var/log/jc*, /opt/jc/*.log
JumpCloud appends a local host address (127.0.0.1:14028) when enabling Syslog for the Events API (logging user events).  For more information, refer to our KB for JumpClouds Events API /etc/rsyslog.d/jumpcloud.conf
One or more of the following parameters: [PermitRootLogin, PasswordAuthentication, UsePAM, PubkeyAuthentication, ChallengeResponseAuthentication]. Other config management systems may cause a conflict if it also tries to manage this file. /etc/ssh/sshd_config
JumpCloud adds the pam_google _authenticator.so plugin line to one of these files depending on your Linux distro. Existing installations of this library may cause a conflict. /etc/pam.d/sshd, /etc/pam.d/system-auth, /etc/pam.d/password-auth
When enabled, TOTP key files are stored on a per user basis at this path /etc/ssh/jumpcloud/totp/${USER}
 
JumpCloud enables sudo users by creating a file per user in  /etc/sudoers.d/USERNAME-jumpcloud
JumpCloud manages this based on users having uploaded public keys to JumpCloud /root/.ssh/authorized_keys, /home/ .ssh/authorized_keys
Installation and service logs /var/log/jc*, /opt/jc/*.log
Disk Usage ~20 MB
Memory Usage ~5 MB


Additional Considerations
 

Last Updated: Aug 15, 2019 12:58PM MDT

Related Articles
desk-forwarding@jumpcloud.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete