Enrolling bulk devices through the Device Enrollment Program (DEP) is simple, straightforward, and quick. Multiple methods for device enrollment are available, including barcode scanning, email, and manual entry via the platform. App synchronization between Apple Business Manager (ABM) and the MaaS360 platform occurs swiftly. Additionally, app distribution and removal are efficiently managed on the platform.
Kandji is well-suited for the following: - Onboarding remote employees (we are a remote company). Kandji offers zero-touch deployment via Apple Business Manager, making it incredibly easy to configure our Macs. -Maintaining security and compliance for Apple devices -Managing a fleet of iOS devices in the field. Where it's less appropriate: -When there is a mixed OS environment -If you have a highly custom or script-heavy environment.
MaaS360 with Watson has a lot of features and capabilities, which can sometimes make it difficult for us to navigate. Improving the user interface and making it friendly could help make the platform easier to use.
Expanding integrations with other systems to provide better support for a wider range of systems and platforms.
Problem after problem after problem with employees getting locked out of their laptops, (which was the whole reason we switched to Kandji - to prevent that from happening), employees ultimately having to factory reset their laptops to get back in, pop-ups that never go away, and continuous password sync issues.
Rock solid solution with highly accessible support when needed. We do not want to interact with MaaS360 on a daily basis but when an issue occurs we are always able to find resolution due to the various support resources we have access to
Having years of experience with MDM and experiencing the evolution of the granularity of the functionality MDM's have had to evolve, no MDM is ever "easy" to use. MaaS360 rises to the top however, because zero day changes are always ahead of the competition. A huge benefit with MaaS360 and IBM's approach to supporting these changes is that they seldom change configuration work flows. Competing Vendors always arbitrarily change workflows which requires a significnat ongoing learning curve in order to maintain technical competence
I gave it an 8/10 because overall, it offers a spotless and intuitive interface that makes routine device management easy. Features such as onboarding, app deployment, and compliance enforcement are handy, thanks to the various blueprints we can set up. The only reason I didn't give it a 10 is that it lacks some advanced configurations, and the reporting aspect is not as customizable.
MaaS360's phone support has been decent the few times I have used it. In addition the person who on-boarded us has been available for additional questions after the process was over. However IBM could do a much better job in creating a user-friendly search engine and white-paper database to help people find topics. Right now finding info is more based on searching through white papers themselves.
To implement IBM Security MaaS360 with Watson, follow these steps: Set up the platform, enroll devices, configure policies and settings, monitor and manage devices. Implementing it can help organizations to securely manage and monitor the use of mobile devices and related resources in their networks, improving security and productivity for their users.
Intune claims to be free, but if you need certain features you actually have to pay for it. So the "free" claim does not fly. In addition, pushing policies can take hours with Intune. In comparison with IBM MaaS360, where policies are changed within minutes. The usability and versatility of IBM MaaS360 is no match for Intune
With Intune, they aren’t friendly with Macs. We had to add each app individually and constantly update the packages for updates. Even when we do everything right, it still doesn’t work all the time
We worked with an IBM SE who was incredibly competent and extremely professional in handling our questions in addition to ensuring the Knowledge Transfer was completed properly
They promised us we could add devices as needed. I even had that written in an email. However, they rescinded that promise and required us to add devices in buckets of 50. That means, since we had 55 users, we had to pay for 100 licenses.
Password issues were made much worse by using Kandji instead of our old MDM (Hexnode).
Overall, Kandji created major headaches with laptop instead of improving.
