IBM MaaS360 Reviews

We have lots of applications deployed on our employees' smartphones. To ensure secure access of these applications from these smartphones, we have deployed an MDM solution from IBM, and we have done containerization on these smartphones. A container has been created, and all applications that are being used for the official purpose are put into that container. All security policies, as per our company guidelines, are forced on that container. All personal applications that our employees have on their smartphones are outside this container, and they remain untouched. We have basically created a kind of partition between professional life applications and personal life applications on the smartphones of our employees.

It is about bringing more agility to our workforce and providing them the flexibility to use their smartphones in accessing office applications. Email is one of the applications. There are other CRM tools that are provided by the company to the employees. To sum it up, it is about providing a secure environment to our employees for working in a more seamless, agile, and productive manner.

All features that we have deployed are useful. We do access office emails on our smartphones, and we have complete sync with Active Directory. Our calendar also gets synced in the MaaS360 application. 

We also ensure that the data from these official applications is not being misused by any of the employees. We have disabled cut, copy, paste, and all such features. It ensures that all the official data that our employees have on their smartphones is secure. Security is the paramount feature that we value in this product.

When we have MaaS360 installed on smartphones, it consumes the battery of the device at a much faster pace. This is one of the areas of improvement that I would like to highlight. We have also observed that in the contact list, a lot of duplication is happening. A single contact is duplicated three or four times, which also consumes more memory resources. If they can work on improving it for these aspects, it will have a more positive impact not only on the way the application is being consumed by the user but also on user satisfaction.

A lot of new features are being deployed or rolled out by companies that are competitors of IBM MaaS360. IBM will have to ensure that all those features are on board so that we have a complete suite of features in the platform, rather than deploying multiple diverse solutions to cater to the requirements of our customers.

I have been using this solution for more than 18 months.

All applications that IBM rolls out are pretty stable and robust. I am sure they do all the testing before launching a new product. MaaS360 is a pretty robust product that is available for use in the enterprise world. From the stability point of view, we have not faced any challenges. We have not yet done any updates.

Its deployment is happening on the cloud, so scalability comes with the solution by default.

We have an in-house team that handles both L2 and L3 support. Until now, we have not faced any issue with respect to the support.

We had another solution that we were using, and we migrated from that solution to MaaS360.

It is very easy. There is an in-house team from IBM that helps not only us but also our customers with lifecycle management and onboarding. It has been pretty easy until now. The application is available on all platforms such as Google Play and iOS App Store. We can download the application from there, and start configuring it with the help of our dedicated team.

Price is something for which we are always under pressure. If we have to look at the MaaS deployment, the price definitely has to come down. This is clearly one of the areas that we will have to work on, not only as a provider to our customers but also as a consumer of this service.

As far as devices are concerned, this is the world of Bring Your Own Device, and such decisions are left to the end-users. As long as a solution is device agnostic, they can choose the device that they want to use.

Keeping the competition in mind, I would rate IBM MaaS360 a nine out of ten.

The most valuable feature of the solution is policy implementation.

Sometimes IBM MaaS360 seems buggy. The buggy nature of the solution is the first impression it gives out due to some mismatches in the solution, though in the background, it really works. At first, the tool may not look so efficient, but it is quite efficient in reality. The aforementioned area of concern can be considered for improvement.

In the future, I would like to see better integration capabilities in IBM MaaS360 that allow it to integrate with productivity software from Microsoft.

I have been using IBM MaaS360 for more than three years. My company has a partnership with IBM.

The solution's technical support functions quite well and can be described as average. The solution's technical support team is sometimes slow to respond and not competent enough. I rate the technical support a six out of ten.

Neutral

The implementation phase of IBM MaaS360 was pretty easy. One must clearly understand how MDM solutions work and whether it is valid for all the platforms in the environment.

I rate the overall product a seven out of ten.

The most valuable features are mobile device management and security (which allows you to quarantine infected devices). 

An area for improvement would be handshaking with Microsoft in terms of trying to get a DLP on Microsoft OS. It would also be useful to be able to do containerization with Microsoft. There are also issues with email security when the functionality is defined from your AD or Exchange.

I've been working with this solution for around three years.

MaaS360 can be easily and effectively expanded.

IBM's technical support is fair to good. We had some challenges initially because we weren't well-connected to the support structure, but if you understand the IBM server structure, you can get a lot of help from IBM. They're also very responsive and will always provide solutions, shortcuts, and other alternatives when there are challenges.

The initial setup is straightforward - because it's cloud-based, it's just a matter of doing some settings here and there.

We have a yearly subscription. The licensing structure is broken down into levels, each with different functionalities available. Depending on your license, there may be additional fees for extra features.

My advice for anyone thinking of implementing MaaS360 is to work with a partner who understands the product and IBM's support structure. Some decisions need to be taken during setup that will be easier with the presence of somebody who understands the implications of the various options. I would give MaaS360 a rating of nine out of ten.

I primarily use this solution to manage desktops and mobile devices.

The most valuable feature is that it's comprehensive - it covers mobile devices and laptops in one package. 

The reporting and alerting could be improved.

I have been using this solution for two years.

We haven't run into any usability issues with this product.

MaaS360 is very scalable, we haven't pushed up against any limitations so far.

Initial setup is easy as the product is cloud-based.

We implemented this solution ourselves.

We're an IBM business partner, so we get fairly good pricing.

If you're looking for a cloud-based input management solution, I would recommend MaaS360. I would rate it as eight out of ten.

In this scenario, we only used MaaS for telephones, not computers. We used the MaaS360 IBM mobile management tool to protect email accounts on phones, ensuring they were compliant. 

MaaS can force people to lock their phones. Not everyone likes having a PIN and other security features on their phones, but this sets a requirement that you can't get your emails unless you have a PIN on your phone. That was a good feature, and we were able to easily increase the PIN from four digits to six digits. Overall, it was pretty user-friendly.

We had a problem with Microsoft computers. If you downloaded emails on a Microsoft Windows Surface PC, that would also require a license. The Outlook application didn't look great for us on a PC. 

My company deployed MaaS360 six years ago, and I last used it about nine months back. 

MaaS360 has gone down a few times over the years, and people couldn't get their emails on their phones, so it was problematic, but that didn't happen often. It was a lot less stable than Intune.

MaaS360 is scalable for a price. At that point, we had a subsidiary company that had many more employees abroad, and they weren't in Intune. We don't have that company now, so that's why we don't use it anymore. But we were able to run it out for all different countries, so it was scalable.

We had our agents who ran through the support by IBM, but I think they also had priority in the queue, so there was no lead time. They had no longer lead time between raising an issue and getting an answer.

IBM MaaS360 was deployed maybe six years ago, and an external IT consultant handled that. It was complex to set up, and they needed to connect their server. 

MaaS360 was nearly double the price of Intune. Except for the server costs, which were built into our IT budget, there were no additional costs.

I rate IBM MaaS360 eight out of 10. I prefer MaaS360 over Intune because I'm a much heavier IBM user. If someone is considering MaaS360, I recommend having an Apple account for business so that it integrates smoothly. You also need to have an overview of your devices, what the applications are, and what the impact will be. 

A general use case would be providing a secure environment for accessing an organization's email. The compartmentalization that MaaS360 provides allows the organization to make sure that the information remains secure.

One valuable feature is the ability to provide a secure environment. Another is the kiosk mode where MaaS360 can be used over a tablet or mobile device to ensure that a single application is used. We make sure at the organization level that a device is not misused.

It is stable, scalable, and easy to install.

From an improvement perspective, I would say that it could be more granular. MaaS360 could take features from both AirWatch and Jamf and integrate them into their solution.

Zero day support is something they can work on. They can make it a little bit more user-friendly as compared to Jamf or AirWatch.

I have been working with it for the past four years.

It is a cloud based solution.

It is stable and reliable. I have clients who use it on a daily and hourly basis. So, their whole deployment is actually dependent on the stability of this product.

It is fairly easy to scale. You can easily scale from a hundred to a thousand in a couple of hours. It doesn't take much time.

Technical support is good. There have been a couple of cases where the timeline was a little bit elongated as compared to what was expected by the customer, but these cases have been very minimal.

The initial setup is a fairly simple process. For 5-10 devices, the deployment may take not more than an hour or one and a half hours.

From a maintenance perspective, there is nothing much locally that can be done. As it is cloud based, the maintenance is predominantly taken care of by IBM.

MaaS360 is priced at a balance. It is not as expensive as AirWatch or Jamf and is not a cheap solution like a few of the local products. For any organization that is looking for a balanced product, MaaS360 is a good solution.

We work with Jamf and AirWatch. Jamf is predominantly targeted only towards Apple customers. It works only on Apple devices; that is their main USP.

AirWatch is more detailed as compared to MaaS360. It gives you more control over your devices as compared to what MaaS360 gives.

Apart from these, there are a couple of local players, like 42Gears, that we work with, but these are more like MBM solutions. They only provide wipe out solutions if the device is compromised and not much more than that.

It is predominantly for mid to large enterprise customers with a couple of hundred deployments.

It's a fairly balanced solution. If you leave the backing to an organization like IBM, you can rest assured that it's a good solution. It actually takes care of your defense endpoint to get rid of pollution. Your laptops, Android devices, and Apple devices could all be secure with this solution. It provides a fairly good level of control and monitoring to suit your needs.

On a scale from one to ten, I would rate IBM MaaS360 at six.

We have a few use cases. Firstly, we are using the solution for incorporating the licenses. We also use it for smaller devices or to allow an inventory of devices to have access.

We also use the solution for our stores in our business. We need to protect our information while being able to deploy apps and business applications, specifically for our departments.

The most important aspect of the solution is the fact that the platform is unified, and that it covers all the mobility services - that includes not only the MDM components or services. The solution includes mobile application management in order to have an application catalog, which is very helpful. In this catalog, we can synchronize and install applications with ease. Within the MDM component, there's mobile set management, in order to incorporate security. 

The deployment itself was quite easy.

The stability has been very reliable.

We've found the scalability to be very good.

The price of the solution is quite good.

We've found the interface to be pretty good overall. The dashboards are quite good.

You can customize the solution easily.

The main issue we have with the solution is synchronization between the information and between the devices and the portal. The information that we see in the portal sometimes does not reflect, or not show, the real-time situation.

The user experience really isn't so good. It's important that they work to improve this aspect.

I've been using the solution for three years, more or less. It's been a while.

The stability of the solution is excellent. There are no bugs or glitches. It doesn't crash or freeze. The performance is very good.

The scalability is good. If a company needs to expand it, it can do so. It's not a problem.

Currently, in our organization, we have 4,000 people, more or less, that use the product. 

We have two models for support. Normally, it falls to the internal department, which manages the support with the IBM products.

However, it's difficult to add new features or to improve anything as there are so many departments around the world. Occasionally, IBM will ask for logs that they want to or need to review, and that can be difficult.

The initial setup was not complex. It was pretty straightforward. A company shouldn't have any issue with the process.

The licensing is paid yearly. We find the pricing to be reasonable. It's not too expensive.

We are an IBM partner.

We are using the latest version of the solution at this time. I'm unsure of the exact version number.

We have the service model, which is very useful to us.

I'd recommend the solution to other companies. There are similar solutions, however. One might be better at this while another is better at that. 

In general, I would rate the solution eight out of ten.

We primarily use the solution for our organization's phones and iPads.

We use the solution for locking down the phone. If it gets lost or stolen, we deploy apps. We have an internal app that will be deployed. It's connected to Apple DEP VPP, and we do document deployments through it as well.

Maas360 uses distribution groups to deploy apps, which makes it a bit easier than, for example, Intune.

Overall, I haven't been happy with it.

Their licensing platform is absolutely awful. We've got locked out of our own account several times and that just has put a bad taste in my mouth. 

The initial setup is not exactly straightforward.

There have been some changes in its software. The portal, for example, has changed. One nuisance feature is that, when you login, you have to always press enter, which is annoying. With most sites, you just click on the login and you go. With this portal, you have to specifically hit enter.

The solution needs to offer live technical support. Right now, it's just a chat window and it's rather unhelpful.

I've been using this solution for about six years. It's been a while. We have some good experience with it.

The solution is scalable. A company shouldn't have any issues in that regard.

We use the solution on about 600 different devices across the organization. Everyone from sales and distribution to the president of the company uses it.

The only way you can get technical support is through a chat window. They weren't exactly friendly. I wouldn't say that we have been happy with technical support.

I wasn't aware of anything being used previously to this solution.

Anything you set up is going to be a bit challenging. However, this was not straightforward per se. It's not cut and dry. You have the rules and regulations on everything that you have to contend with.

I didn't handle the initial implementation. I took it over after the fact.

The initial setup was handled in-house. The company did not require the assistance of consultants or integrators.

We are charged on a monthly basis. It's my understanding that the pricing is the same as or similar to Intune. If we do switch over, the pricing will be pretty much the same.

With IBM, you had to have a certain type of license inside of Microsoft for it to work, however, I don't have too much detail on that.

We are also looking into Intune. The one thing I did notice with Maas360 versus Intune was that Maas360 uses distribution groups to deploy apps. Intune does not have that. With Intune, you have to use security groups. That's causing us a little headache that we've got to get around.

I'm getting my feet wet on it right now. I'm beginning to learn how to use it. We're in the POC stage.

We are a customer and end-user.

The solution is deployed onto the actual device itself.

I wouldn't recommend the solution. We're pretty much working to move off of it. We haven't been too happy with the solution in general. How it was described to us ultimately wasn't how it worked.

Overall, I would rate it at a six out of ten.