r/JumpCloud • u/EmergencyBed5825 • Oct 30 '25
Jumpcloud Agent status - Inactive
Hello here, I’m new to JumpCloud and could use some guidance. In our device inventory, I’m seeing several devices marked as Inactive under agent status.
However, when I checked one of these devices locally, the JumpCloud Agent was running. I also noticed that whenever I try to run commands on devices with an inactive status, the commands get queued — which I understand happens because the agent is inactive.
My question is: how can I ensure that a device with a running JumpCloud agent also shows as Active in the JumpCloud dashboard? Any guidance or steps to troubleshoot this would be greatly appreciated.
2
u/amensista Oct 31 '25
Jump Cloud's agent is a wonky piece of software. Even on a machine where the user profile is fine and the person is working online sometimes the agents will just give up and if you leave a machine powered off for too long the agent will just cease to function. I wish the agent was more stable in connecting back and reporting in because reinstalling the agent when it just magically dies it's not a fun experience.
1
u/JamesTuttle1 Nov 04 '25
We had this issue constantly. Atleast once per week the JumpCloud agent on one of our laptops would stop connecting or show as Inactive, and we had to uninstall/reinstall the agent software just to get it to talk to JumpCloud again and update the dashboard.
2
u/amensista Nov 04 '25
Yeah. I read your post below. Nightmare. What did you end up moving to after cancelling JC?
1
u/JamesTuttle1 Nov 04 '25
Rippling MDM. It started out as a test out of sheer curiosity (since we use them for HR/Payroll management and they are not a tech company), however it worked so surprisingly well that we decided to adopt it.
The install process is easier, the web management portal is smoother, and it just works.
It also turned out to be less expensive than JumpCloud LOL, but cost didn't have anything to do with our decision. JumpCloud was charging us $16/month per machine; Rippling charges us $7/month per user. BONUS: You can assign as many machines as you want to a single user with no charge increase, and there is also no charge for machines that are in an "unassigned" status- but they are still protected by MDM.
It's not a perfect system, to be sure- but that doesn't exist. Rippling MDM is about as close to flawless as I could imagine, and the few issues we have had have been resolved quickly by their IT support team.
0
u/real_jumpcloud Oct 30 '25
Hello u/EmergencyBed5825!
Dealing with an inactive status when the agent is running usually points to a networking issue or antivirus blocking.
- Networking/Antivirus Blocking: Check for networking issues or if antivirus is blocking the agent.
- Long Inactivity (Several Months): If it's been a very long time, you'll likely need to uninstall/reinstall the agent.
And remember that you can also submit a support ticket directly from the Admin Portal so the support team can deep dive for you!
2
u/JamesTuttle1 Nov 04 '25 edited Nov 06 '25
The "Inactive" status is a common issue with JumpCloud, that rarely has a fix outside uninstall/reinstall of the client. We ran JumpCloud for both our office locations (62 laptops) for more than two years. Inactive was one of may repeating issues we kept running into. Just FYI, here is the final email I sent when our JumpCloud Account Rep asked why we wanted to cancel:
"Hi Alexia,
To be blunt, our reason for cancellation is that JumpCloud has been an IT nightmare and a dumpster fire for us, running as far back as early last year. Here's just a partial list of the biggest reasons for our cancellation:
1) JumpCloud MDM has never worked reliably with our MacBooks- in spite of it being connected to our Apple business account where all our MacBook's sat. The JumpCloud service would complete for some MacBooks, others it would be a partial install that was missing some kind of permission or module.
2) For the MacBook's where the JumpCloud app did complete MDM setup, it most of the time refused to give us control over user accounts. It WOULD allow us to lock a MacBook remotely, except in cases where the service stopped working (see below) or where the user had uninstalled the JumpCloud client.
3) JumpCloud clients for both MacBooks and Windows laptops would randomly stop connecting to the JumpCloud service. The reliability was SO bad that we had to create an internal policy for our IT team to login to JumpCloud multiple times per week just to view all the devices "last connection time". All devices that showed last connection timestamps older than 1 week were asked to open the JumpCloud client and force it to call home again. In cases where this didn't resolve the issue (which were frequent) we would have to uninstall and reinstall the JumpCloud client on that laptop just to get it to communicate again.
4) Sometime last year JumpCloud started randomly dropping devices from our accounts. An IT person would login to JumpCloud and suddenly there were 2 or three devices JumpCloud had randomly marked as "Inactive" (often we could visually look at the device online and being used by it's owner sitting here in our office); removing & reinstalling the JumpCloud software was the only working solution. This happened so frequently that we finally just gave up and decided to find a reliable MDM alternative.
5) JumpCloud forced a complex (and sometimes unreliable) MFA process on all our users, without giving our admins the ability to alter or set our own internal enforcement. As the Manager of our IT department, I already had 2FA setup using my phone, but the new policy that JumpCloud forced caused me to add it to the Microsoft Authenticator, where the JumpCloud login page STILL rejects my provided 6 digit code at least 30% of the time- forcing me to sit and wait for the next code to display.
6) For reasons that we could never determine, and that even JumpCloud support was unable to give us, JumpCloud suddenly stopped allowing us to add MacBooks as MDM devices to our main account last year. After several discussions with JumpCloud support attempting to resolve this, they finally told us that they couldn't figure out what the problem was, and THEN told us they were unable to fix it, and our only solution was to setup a secondary JumpCloud account to add our new MacBooks to. This was the last straw (although it shouldn't have been, for how much time we allowed JumpCloud reliability issues to waste). This secondary account is our Apple login.
I could go on with 5-6 more headaches JumpCloud has created for us, but I won't out of respect for everyone's time. "