JumpCloud vs. Tools4ever UMRA

JumpCloud is least suited in situations where you have few devices, but lots of users. JumpCloud heavily focuses on the "One-User-One-Device" type of use, and does lack some of the features things like Active Directory is better suited for when having multiple users accessing one machine. Their Powershell APIs are fantastic and getting only more powerful. Lots of features are hidden behind these APIs, so admins not as familiar with Powershell would have more issues leveraging these tools. BYOD deployments are amazing, especially for macOS devices that are using Apple Business Manager and can leverage Zero Touch deployments. It is especially good at handling mixed systems, whereas other options, such as Jamf, are really suiting only for macOS, or Intune is more suited for Windows; JumpCloud managed to handle both systems well.

It is very well suited for tying multiple systems and services together, allowing for exchanges of information and account management. I'm not sure of instances that it is not well suited since solution was recommended by folks in education. With that being the case it suited our needs quite well.

• User Management - The ability to control our users and set password/polices is made easy in the JC console
• Device Management - Using JC each user is assigned to their own device with only the rights to do their job - When elevated rights are required, this is done simply via the JC console for the period of time required
• SSO - Using JC's SAML SSO integrations we are building out our SSO offering and this is making for a much simpler daily user experience

Incentivized

• Imports students and staff into our Active Directory and email system.
• It manages those same accounts, disabling accounts for folks who have left, and creating "Windows" when accounts should be enabled.
• It interacts with our Microsoft AD and our student management software seamlessly. Once accounts are in our AD environment, our student management and other systems create new email accounts automatically for us.

• SSO via OpenID - Opening up their SSO from just SAML to including OpenID (OAuth) would allow us to make more use of the service and to also incorporate it into some internal testing suites
• Time Limited User Elevation - The ability to time limit a users elevation of privileges would be a great addition
• Extending device management to include LPA - Least Privilege Access is becoming a bigger ask from our external auditors - Being able to do this via JC would be amazing

Incentivized

• We have been attempting to get single sign on for students, so they have the ability to change their passwords on their own. The documentation of this process is very dated, and often support isn't even aware that their site issues/ references those older documents.
• During the initial buildup of our server Tools4ever UMRA support was a bit hit and miss, but I will say our ongoing support has been very good.
• Some integration tools had to be custom created.

It's simple. I like how JumpCloud keeps things simple. Similar to Apple's ecosystem, they give you what you want with some extra features and bells and whistles but it doesn't take a large instruction manual to use it. They have the support system and KB articles to back up their product and learn about a feature and how to implement it

Incentivized

I have rarely contacted support. When I have, the responses were within expected time frames, and easy to access. Community support is incredible, both from the JumpCloud representatives, and the user base community at large. The support pages on the website also are typically very well written and strike a nice balance between having the technical information needed, and also being easy to understand for the small business types that might not have as much of a technical background as an IT Admin.

Being responsible for choosing the product after a POC and pilot we found the process to be simple and effective

Incentivized

Incentivized

Some features would make more sense for us to be bundled by machine, instead of the user. We have fewer machines, and multiple users log into one machine, so doing something like paying per user for services like Patch Management are difficult to warrant the cost. I also feel a more complete package that includes common addon features; Patch Management and Password Manager, would be an improvement. It would also be nice if we could change packages, addons, and other billing services via self-service instead of reaching out to our account manager.

services and professional team and support teams are good

Incentivized

• Very easily add, or disable employee logins
• Reduce "password fatigue" by being able to reduce password expiration requirements, and having single sign on
• Higher security and visibility of security issues
• Reduced onboarding time from days to minutes
• Enabled easy reassignment of user accounts to another user via groups when employees leave
• Quick securing of terminated users, or otherwise compromised accounts
• Reduced user disablement time from previous manual methods requiring days, to literal minutes

• We save considerable work hours by a multitude of staff having the system manage and generate accounts for us on a daily basis.
• We have some peace of mind knowing accounts for staff and students who leave our district can no longer gain access to our systems because it automatically disables those accounts.
• Because of the way the system interacts with input that is put in, it automatically creates logical positions which dictate different levels, meaning it automatically sets up when staff gain access and lose access depending on the position they are filling.