I often found myself trying to adapt Jamf’s guides to work with Mosyle. Mosyle has a comparatively small amount of documentation and it’s not publicly available so you won’t be able to find it from a Google search. Jamf has a huge amount of documentation freely available online and if that doesn’t solve your problem you can pick up the phone and give them a call. Jamf’s support is lightyears ahead of where Mosyle’s was. With Mosyle I was often waiting around a minute for profiles to arrive which makes testing new profiles more of a pain than it already is. With Jamf the profile reaches the devices essentially instantly. Mosyle’s slowness extends to deploying profiles. With Jamf I can simply bookmark the URL and get where I want in a single click. To add to the pain, Mosyle also uses a single page layout, so making changes to a profile takes 4 page loads from opening the site. Tested using Chrome’s DevTools on a gigabit fiber connection Jamf takes around 400 milliseconds to load the dashboard, whereas Mosyle takes over 9 seconds - more than 20 times slower. Jamf’s user interface is also significantly more responsive than Mosyle’s. This design also makes it impossible to combine multiple payloads into a single profile. Instead of putting everything in a nice list like Jamf, they've decided to group everything by type without any sort of iconography to easily find what you’re looking for. It’s a compliment to Jamf’s flexibility that it’s even possible, but I have no idea why it isn’t easier.Īs much as I like Mosyle’s “everything's a profile” approach, the interface they’ve given it is downright painful to use. I’ve tried to recreate this in Jamf and I needed extension attributes populated by a script feeding into a smart group which is then used to scope the package installation. The package will be automatically installed or updated if needed. All you have to do is host the package somewhere, give Mosyle the URL then provide the bundle ID and version. Variable substitution is supported and you don’t have to mess around with certificates or signing.Īnother place Mosyle shines is the simplicity of their package installation. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |