Manually Remove JumpCloud Policies from a Windows Device<\/h2>\n\n\n\n

Follow these steps only after you have uninstalled the agent. If the JumpCloud policies weren’t automatically removed, you can manually remove them from the Windows device.<\/p>\n\n\n\n

<\/p><\/div>

Warning:<\/strong> \n

When you clear the device’s local Group Policy cache, you’re removing not only JumpCloud policies, but all other policies that have been applied, including Windows User and Group policies.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n

In these steps, you’ll use the secedit<\/strong> command to clear the system’s local Group Policy cache. The secedit<\/strong> command lets you configure the current device’s security settings stored in a database.<\/p>\n\n\n\n

To remove JumpCloud policies from a Windows device<\/strong>:<\/p>\n\n\n\n

\n
1. Log on to the device as an administrator.<\/li>\n\n\n\n
2. Verify JumpCloud policies are removed after an uninstallation by running this command:<\/li>\n<\/ol>\n\n\n\n
   \n

   gpresult \/Scope Computer \/v<\/p>\n<\/div><\/div>\n\n\n\n

   \n
   1. If group policies are listed, open a PowerShell terminal.<\/li>\n\n\n\n
   2. At the prompt, type this command:<\/li>\n<\/ol>\n\n\n\n
      \n

      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<\/p>\n<\/div><\/div>\n\n\n\n

      \n
      1. After you run this command, you need to reapply any Windows User and Group policies that are required by your organization.<\/li>\n<\/ol>\n\n\n\n

         Device Status After Removing JumpCloud<\/h2>\n\n\n\n

         When you remove JumpCloud from a device, either by deleting the device in the Admin Portal, or by manually removing the agent from the system, the following will occur:<\/p>\n\n\n\n

         \n
         1. The JumpCloud agent will be removed from the system.<\/li>\n\n\n\n
         2. All users on the system will remain unaffected regardless of whether they were provisioned by JumpCloud or were pre-existing and taken over by JumpCloud. <\/li>\n\n\n\n
         3. All user data and permissions on the system remain as is.<\/li>\n\n\n\n
         4. Any commands set up to run on that system via JumpCloud 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).<\/li>\n<\/ol>\n\n\n\n

            Your Data In JumpCloud<\/h3>\n\n\n\n

            \n
            1. Your account will remain intact, should you wish to use JumpCloud in the future.<\/li>\n\n\n\n
            2. Any undeleted devices that go offline without being removed from the JumpCloud Admin Portal will remain in the Portal indefinitely, or until JumpCloud chooses to delete them.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

               If you don’t want JumpCloud to manage a device, remove the following components: If a device is active, all of […]<\/p>\n","protected":false},"author":206,"featured_media":0,"template":"","meta":{"_acf_changed":false,"_oasis_is_in_workflow":0,"_oasis_original":0,"_oasis_task_priority":"","inline_featured_image":false,"footnotes":""},"support_category":[2923,2852],"support_tag":[],"coauthors":[2842],"acf":[],"yoast_head":"\n