ºÚÁϺ£½Ç91Èë¿Ú

Install or Uninstall the ºÚÁϺ£½Ç91Èë¿Ú Agent

This article covers the manual ways to install or uninstall the ºÚÁϺ£½Ç91Èë¿Ú Agent via the ºÚÁϺ£½Ç91Èë¿Ú Admin Portal on various operating systems.

Prerequisites:​

Installing the Agent

Install the ºÚÁϺ£½Ç91Èë¿Ú Agent on a MacOS Device

  1. Log in to the .
  2. Go to DEVICE MANAGEMENT > Devices.
  3. Click + to add a device and click the Mac tab.
  4. Select the Install via Mac Agent option.
  5. If you are currently on the target system, click Download Mac Agent. If not, click Copy Download Link to copy the link URL and open the link in a browser on the target system.
  6. Copy the Connect Key.
  7. Run jumpcloud-agent.pkg
  8. Follow the installer and enter the Connect Key when prompted.

Install the ºÚÁϺ£½Ç91Èë¿Ú Agent on a Windows Device

  1. Log in to the .
  2. Go to DEVICE MANAGEMENT > Devices.
  3. Click + to add a device and click the Windows tab.
  4. Select the Install via MSI Download option.
  5. If you are currently on the target system, click Download Windows Agent. If not, click Copy Download Link to copy the link URL and open the link in a browser on the target system. 
  6. Copy the Connect Key.
  7. Run jcagent-msi-signed.msi.
  8. Follow the wizard and enter the Connect Key when prompted.
  9. For a step by step walkthrough, refer to ºÚÁϺ£½Ç91Èë¿Ú Agent Windows Installation Walkthrough.

Install the ºÚÁϺ£½Ç91Èë¿Ú Agent on a Linux device

  1. Log in to the .
  2. Go to DEVICE MANAGEMENT > Devices.
  3. Click + to add a device and click the Linux tab.
  4. Copy the displayed Install Command into the target system, or, if you already have your connect key, log in to the target machine as either sudoer or root and run the following:

curl --silent --show-error --header 'x-connect-key: YOUR_CONNECT_KEY' https://kickstart.jumpcloud.com/Kickstart | sudo bash

Tip:

For steps to install the Linux agent via automation tools (Ansible, Chef, and Puppet) see Install the Linux Agent.

Uninstalling the Agent

If you don't want ºÚÁϺ£½Ç91Èë¿Ú to manage a device, remove the following components:

  • The device’s record from the Admin Portal.
  • The agent from the local device.
  • Any ºÚÁϺ£½Ç91Èë¿Ú policies on the local device.

If a device is active, all of these components are automatically removed for you. You can find the status of a device in the Admin Portal in the Devices list. Depending on the device status, the agent's components are uninstalled in the following ways:

Component Uninstall Based on Device Status

Status Device Record Agent Policies
Active, System Reporting Removed Removed Removed
Inactive, System Not Reporting Removed Not removed Not removed

There are two methods to uninstall the agent:

  • Using the Admin Portal to Uninstall the Agent
  • Using the ºÚÁϺ£½Ç91Èë¿Ú API to Uninstall the Agent

Both of these tools can uninstall all agent components from Mac, Windows, and Linux devices.

Considerations:

  • In rare cases, policies aren’t removed automatically from Windows devices. If this happens, you can manually remove Windows policies.
  • Uninstalling the agent from a device should be used as a last resort if the device is no longer online or communicating with ºÚÁϺ£½Ç91Èë¿Ú.

Using the Admin Portal to Uninstall the Agent

When you remove the agent from a device, all associated policies, files, and directories are also removed. See the complete list in Agent Compatibility, System Requirements, and Impacts.

Considerations:

  • If you log on to a device and manually remove the agent first, a record remains in the Admin Portal. You can use these steps to remove only the device record if the device has a status of Inactive, System Not Reporting.

To uninstall the agent from the Admin Portal:

  1. Log in to the .
  2. Go to Device Management > Devices.
  3. Select the device you want to stop managing. To uninstall all ºÚÁϺ£½Ç91Èë¿Ú components associated with the device, make sure it has a status of Active, System Reporting.
  4. Click delete.

The device's record is removed from the Admin Portal.

  • If the device has a status of Active, System Reporting when it’s deleted from the Admin Portal, the ºÚÁϺ£½Ç91Èë¿Ú agent and policies are also automatically removed.
  • If the device has a status of Inactive, System Not Reporting when it’s deleted from the Admin Portal, you need to log in to that device and manually remove the agent and policies.
  • It can take up to two minutes for the agent and all associated files to be uninstalled from the local device.

Best Practice:

If you're removing the agent from a Windows device, verify the ºÚÁϺ£½Ç91Èë¿Ú policies have been removed by running this command as administrator:

gpresult /Scope Computer /v

If they remain, you need to manually remove policies from the Windows device.

Using the ºÚÁϺ£½Ç91Èë¿Ú API to Uninstall the Agent

Follow these steps to run a curl command to access the ºÚÁϺ£½Ç91Èë¿Ú API and uninstall the agent. The ºÚÁϺ£½Ç91Èë¿Ú API allows interaction with ºÚÁϺ£½Ç91Èë¿Ú resources such as commands, devices, and users.

Considerations:

  • Deleting a device through the ºÚÁϺ£½Ç91Èë¿Ú API can take up to a minute to complete.
  • When you remove the agent from a device, all associated policies, files, and directories are also removed. See the complete list in the Agent Compatibility, System Requirements, and Impacts article.
  • If you log on to a device and manually remove the agent first, a record remains in the Admin Portal. You can use these steps to remove only the system record if the system has a status of Inactive, System Not Reporting.

To uninstall the agent from the API:

  1. Review the API documentation to determine, based on your type of integration, which version of the ºÚÁϺ£½Ç91Èë¿Ú API to use.
  2. Use the following sample request, replacing SystemID and API_KEY with the values specific to the device you want to stop managing. For definitions of keys, path parameters, and headers, review the API documentation for .

curl -X DELETE https://console.jumpcloud.com/api/systems/{SystemID} \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-H 'x-api-key: {API_KEY}'

When the command completes successfully, the system's record is removed from the Admin Portal.

  • If the device has a status of Active, System Reporting when it’s deleted from the Admin Portal, the ºÚÁϺ£½Ç91Èë¿Ú agent and policies are also automatically removed.
  • If the device has a status of Inactive, System Not Reporting when it’s deleted from the Admin Portal, you need to log on to that system and manually remove the agent and policies.

Best Practice:

  • If you’re removing the agent from a Windows device, verify the ºÚÁϺ£½Ç91Èë¿Ú policies have been removed by running this command as administrator:

gpresult /Scope Computer /v

If they remain, you must manually remove policies from the Windows devices.

Manually Remove the Agent from an Inactive Device

You should use these steps only if you want to uninstall the agent from a device that has a status of Inactive, System Not Reporting in the Admin Portal.

Considerations:

  • If the device has a status of Active, System Reporting, you should remove all agent components automatically using either the Admin Portal or the ºÚÁϺ£½Ç91Èë¿Ú API.
  • If you log on to a device and manually remove the agent first, a record remains in the Admin Portal. You also need to remove the record using either the Admin Portal or the ºÚÁϺ£½Ç91Èë¿Ú API.

To manually remove the agent:
Use the steps in the following table for the OS on your system.

OS Uninstall Steps Notes
Mac
  1. Download the .
  2. Run the script:
    sudo sh remove_mac_agent.sh
  3. Approve Terminal access when prompted.

You need an administrator password to run the sudo command.

Windows
  1. Open the Control Panel.
  2. Click Programs and Features.
  3. Click ºÚÁϺ£½Ç91Èë¿Ú agent ("ºÚÁϺ£½Ç91Èë¿Ú v1.0").
  4. Click Uninstall.

For specific files, directories, and registry keys modified by the Windows Agent, see Changes Made to Your Windows Device During Installation.

 

Debian/Ubuntu
  1. Log on to the device as an administrator.
  2. Open a command prompt.
  3. At the prompt, type:
    service jcagent stop
    apt-get remove jcagent
    rm -rf /opt/jc
-
Amazon/CentOS/RHEL
  1. Log on to the device as an administrator.
  2. Open a command prompt.
  3. At the prompt, type:
    service jcagent stop
    yum remove jcagent
    rm -rf /opt/jc 
-

Manually Remove ºÚÁϺ£½Ç91Èë¿Ú Policies from a Windows Device

Follow these steps only after you have uninstalled the agent. If the ºÚÁϺ£½Ç91Èë¿Ú policies weren't automatically removed, you can manually remove them from the Windows device.

Warning:

When you clear the device's local Group Policy cache, you're removing not only ºÚÁϺ£½Ç91Èë¿Ú policies, but all other policies that have been applied, including Windows User and Group policies.

In these steps, you'll use the secedit command to clear the system's local Group Policy cache. The secedit command lets you configure the current device's security settings stored in a database.

To remove ºÚÁϺ£½Ç91Èë¿Ú policies from a Windows device:

  1. Log in to the device as an administrator.
  2. Verify ºÚÁϺ£½Ç91Èë¿Ú policies remain after an uninstallation by running this command:

gpresult /Scope Computer /v

  1. If group policies are listed, open a PowerShell terminal.
  2. At the prompt, type this command:

secedit /configure /cfg $env:windir\inf\defltbase.inf /db defltbase.sdb /verbose
Remove-Item $env:windir\System32\GroupPolicyUsers
Remove-Item $env:windir\System32\GroupPolicy
gpupdate /force

  1. After you run this command, you need to reapply any Windows User and Group policies that are required by your organization.

Device Status After Removing ºÚÁϺ£½Ç91Èë¿Ú

When you remove ºÚÁϺ£½Ç91Èë¿Ú from a device, either by deleting the device in the Admin Portal, or by manually removing the agent from the device, the following will occur:

  1. The ºÚÁϺ£½Ç91Èë¿Ú agent will be removed from the device.
  2. All users on the device will remain unaffected regardless of whether they were provisioned by ºÚÁϺ£½Ç91Èë¿Ú or were pre-existing and taken over by ºÚÁϺ£½Ç91Èë¿Ú. 
  3. All user data and permissions on the device remain as is.
  4. Any commands set up to run on that device via ºÚÁϺ£½Ç91Èë¿Ú Commands will no longer run, regardless of how those commands are launched (this means you’ll need to move any scheduled commands manually in cron or another scheduling tool).

Your Data In ºÚÁϺ£½Ç91Èë¿Ú

  1. Your account will remain intact, should you wish to use ºÚÁϺ£½Ç91Èë¿Ú in the future.
  2. If you remove enough users to get below 11, your charges will drop to $0 and your account will continue as is going forward.
  3. Any undeleted devices that go offline without being removed from the ºÚÁϺ£½Ç91Èë¿Ú Admin Portal will remain in the Portal indefinitely, or until ºÚÁϺ£½Ç91Èë¿Ú chooses to delete them.
Back to Top

Still Have Questions?

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

Submit a Case