JumpCloud policies and security commands are currently unsupported.Home versions of Windows are supported in the following ways:.Non-English locales aren’t supported by JumpCloud policies.Adverse results in Command execution in the Admin Portal.Cosmetic issues in the Devices detail views.However, certain international character sets may cause the following issues: International versions of Windows are supported.As of April 14, 2020, we don’t support the JumpCloud agent on Windows 7 or Windows 2008 + R2.As of June 30, 2020, we don’t support the JumpCloud agent on Windows 8.As of June 30, 2020, we don’t support the JumpCloud agent on 32-bit devices.Learn more: Windows 10 Release Information. Beginning on May 11, 2021, we only support Windows 10 build 1909 and above.As of February 18, 2022, JumpCloud no longer supports Windows 8.1.As of June 16, 2023, the JumpCloud tray application will not be updated past version 1.32.0 on 32-bit devices.As of June 16, 2023, the JumpCloud agent will not be updated past version 1.115.1 on 32-bit devices.JumpCloud is proud to natively support Apple silicon Macs.Syncing login passwords with Apple’s iCloud service is not supported, and attempting to turn it on may result in undefined and unsupported behavior. See OS X: User Password Does Not Update with iCloud Account.See Managing Users with High Sierra, FileVault, and APFS. 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.Note: OS query is only installed when System Insights is enabled. As of April 14, 2020, we don’t support the JumpCloud agent on macOS Sierra 10.12.As of June 30, 2020, we don’t support the JumpCloud agent on Debian 8 systems.As of November 30, 2020, we don’t support the JumpCloud agent on macOS High Sierra 10.13.As of December 15, 2021, we will no longer support the JumpCloud agent on macOS Mojave 10.14.Furthermore, functionality may or may not work as intended and may be hindered based on future product releases: If the JumpCloud agent is installed on an unsupported version, JumpCloud neither ensures nor provides guarantees full or even partial functionality of device management.Pre-release or Release Candidate (RC) versions of OS releases are not supported.See Granting Full Disk Access Permissions to the JumpCloud Agent for MacOS. 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.Intel and Apple Silicon devices are supported.For more information, see Enrolling iOS Devices in MDM. I'm using macOS Mojave 10.14.6 on a 2015 MacBook Pro.Įdit: It just happened again, so I took some screenshots and attached them below.JumpCloud supports iOS devices, such as iPhones, iPads, and Apple TVs, but the JumpCloud agent is not installed on those devices. I'm not able to reproduce the issue when I want, but it happens regularly every or every-other day. This has happened many times over the past 6 months, over many different Edge versions (I'm always using the latest stable version). When I relaunch it and re-open the web pages I was using, it works fine (until later that day or the next day, when the process repeats).ĭoes anyone know how I can troubleshoot this so I can file a useful bug report? If I Quit the application, all the windows close but it doesn't fully quit I have to do command-option-esc to open the Force Quit window (where it says "Microsoft Edge (not responding)" and then I'm able to Force Quit it. According to the Task Manager, it is the "Browser" thread that is using this CPU. After using Edge for a few hours, it will begin using 100% CPU. I'm reporting a problem I've experienced with Edge since I began using it six months ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |