Mosyle’s solution couldn’t be easier: Upload a profile, give it a name then assign it to devices. This prevents the use of any variable substitution. With Jamf, profiles need to be signed or Jamf will screw around with them. For this workflow Mosyle is unbelievably superior. Most of the profiles I use are hand-made with exactly the keys I need then uploaded to the MDM. In my experience they almost always create massively bloated profiles that have a heap of unintended side effects. In most cases I despise the built-in configuration profile creator from both Mosyle and Jamf. In general they also do a really good job of making things behave like configuration profiles would. In some cases they seem to combine functionality from multiple places within a single “profile” which makes life a lot easier. In Mosyle everything’s exactly where you’d expect it to be. This means you’ll often have to check two or three places to find what you’re looking for. In Jamf there’s a very clear separation between configuration profiles, MDM commands and commands for the Jamf binary. Mosyle’s main design philosophy appears to be “pretend everything’s a profile” which I absolutely love. Previously I was using Mosyle for education, which appears to be hosted in the central US, this could explain some of the network slowness I’ve experienced with their offering. I’m also comparing how Jamf is today to how Mosyle was around 6 months ago, so some things may have changed.įor a bit of background: I’m based in Australia and currently using Jamf Cloud where our instance is hosted in Sydney. Jamf is around 5-10x more expensive than Mosyle and has been around a lot longer, so it’s not exactly a fair comparison. I started with Mosyle then moved to Jamf around a year later after having a few issues, although I’ll try to stay as objective as possible. I’ve seen a few threads asking for a comparison between Jamf Pro and Mosyle Manager, so I thought I’d share my experience.
0 Comments
Leave a Reply. |