IBM MaaS360 Reviews

I have 30 phones, and I don't like setting up a new phone every time. Turning a new phone on should bring up the organization that controls it, ask you to type your email address and password, and then load all the apps. Then I can monitor the phone remotely.

The most valuable features of IBM MaaS360 are remote control and setting up a phone.

It's difficult for someone like me to set up a phone that doesn't require a SIM card, like Apple's new phones. I prefer to open up a phone and ensure it's properly set up before the user starts using it. As soon as the phone is turned on, it automatically connects to the network and becomes the user's new phone. If the phone isn't set up properly before this happens, it could cause problems for the user. Additionally, without a SIM card, the speaker can't monitor or remotely wipe the phone if necessary.

I have been using IBM MaaS360 for three years.

I had to change one of the phones that didn't connect to the network. I could set the device name for the new phone I set up for a user. However, I could not set the device name for the other phone that I did not set up. This is annoying because I should be able to do that.

The scalability of IBM MaaS360 is good.

IBM MaaS360's customer service is awesome. I rate IBM MaaS360 a nine out of ten for customer service.

Initially, the setup was pretty good. Right now, I have 19 devices that are not upgraded to the new April 2023 release, and I can't force a phone to do it. It might have been because I'm not a power user or because of the fact that I didn't do it.

Make a lot of comparisons before opting for IBM MaaS360.

Overall, I rate IBM MaaS360 a nine 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.

We use IBM MaaS360 for the iPads of our field sales reps. We use it to ensure that they are only using authorized apps, and these apps are maintained and have the latest version.

The ability to send an iPad out to someone and have them auto-provision it when they are out in the field is fantastic. We don't have to have it all configured before we ship it. This is probably the biggest value add.

We opted to go with Microsoft Intune because it just seemed to be a more mature and comprehensive enterprise solution, whereas IBM MaaS360 didn't seem to have the necessary breadth to manage all of our equipment. Along with laptops, I've had some BYODs. IBM MaaS360 just didn't seem as mature in our assessment.

Our company was founded in May of last year, and we launched our sales force in September of last year. We have been using IBM MaaS360 since then, that is, for more than a year. We are using the latest version.

It is stable.

It is scalable for the field sales reps. It didn't seem to be as scalable for the enterprise across multiple platforms. We have around 70 users.

We have IBM MaaS360 for our iPads, but we are using Microsoft Intune for our laptops and our BYODs. When our licensing expires, we will migrate our iPads from IBM MaaS360 to Microsoft Intune. 

Considering that we are moving to Microsoft Intune, I should ideally not recommend this solution, but there's no reason to not recommend it for the iPads of your sales force. It is a very standard solution. There is lots of knowledge out there and lots of resources who are experts in the solution. It is not a bad solution to use. If I had just the sales force, using IBM MaaS360 is a great way to manage their iPads.

I would rate IBM MaaS360 an eight out of ten.

We use the solution for data protection, data leakage prevention, and email containerization.

The solution's most valuable features are site protection, pricing, and easy implementation.

The solution's integration with Microsoft Teams could be better.

We have been using the solution for seven years.

It is a stable solution. I rate its stability a nine out of ten.

It is a scalable solution. I rate its scalability an eight out of ten. It is suitable for enterprise businesses.

The solution's technical support team could respond faster. Also, there should be clarity regarding whom to escalate the call to within the team in case of queries.

Neutral

The solution's initial setup process is easy. The time taken for deployment depends on the number of mobile devices. If you have a few hundred machines, it will take an hour. It requires three to five engineers for deployment and two to three engineers for maintenance.

The solution generates a good return on investment.

The solution is cost-effective. I rate its pricing as a four out of ten. We purchase its yearly license. Also, there are no additional costs involved.

I advise others to stay updated with the latest version and use company-owned mobile devices for the solution. I rate it an eight out of ten.

We are customers and resellers of this solution and I'm the company's deputy manager.

The solution has made everything more convenient for us and it's now easier to identify whether something can be fixed remotely or whether it requires a physical examination on the device.

The most useful features are remote enablement and access to internal resources on the VPN.

The user interface could definitely use some improvement. It's very basic, but anyone not used to it might require some assistance. It's not really intuitive. I'd like to see more access at the account level. It's difficult to identify the number of licenses available in our account and to which interface they belong. We sometimes have to segregate; some users require the full enterprise features while others, who are partners or employees, are just given basic access. Being able to identify and assign the licenses would be very helpful. It's more of an administrative thing in terms of bookkeeping, but it would be great if that issue could be addressed.

I've been using this solution for two years. 

The solution is quite stable. 

My organization has more than 5,000 users now so I don't see a problem with scale.

I'm a reseller and I provide my own technical services along with the licenses. We charge for professional services. However, if technical support was purely through IBM, the service is definitely lacking. There is a significant turnaround time, and you do need to have someone with qualifications from your own team who understands what to do. Unless you already have somebody who's tech savvy and understands the language, you're going to have to pay for professional services. It's a complex thing to manage.

It's a simple initial setup but complex to use. I believe overall deployment took about a month as it was rolled out in phases. There was integration phasing out of all the software as well as integration with new upcoming cloud services.

I would rate this solution an eight out of 10. 

We are using IBM MaaS360 to manage applications and to control some functions in mobile phones. We do mobile device tests and control the applications on mobile devices.

My customers value the ability to control all their devices from a central point in IBM MaaS360.

IBM MaaS360 can improve the information provided for DLP control. Some of our customers would benefit from this.

In a future release, they should add more compatibility with different types of devices, Zebra. Our clients needed to control different types of devices using the same license to control mobile phones.

I have been using IBM MaaS360 for approximately three years. 

IBM MaaS360 is a stable solution.

The technical support from IBM is good.

The initial setup of IBM MaaS360 is easy.

We have a SOC, a security patient center where we have two engineers that provide the support for our customers for IBM MaaS360.

I would recommend this solution to others. There is a possibility to improve, but in general, it's a very good solution.

I rate IBM MaaS360 a nine out of ten.

We use it to configure policies on all of our mobile devices for our field staff.

It helps us with HIPAA compliance, and it meets the standards for that.

The most valuable feature is the fact that we can find a lost device or shut the device down and wipe it, which is good for HIPAA.

The look needs to be updated and it could be simpler to use.

The portal itself looks old and outdated.

I would like to see more automation and better reporting. Their reports are a bit archaic.

I have been working with this solution for a year and a half.

We are using the latest version.

It's a stable solution, we haven't experienced any issues.

We haven't had to scale it but it's pretty easy to add a license to it.

There are three in the IT department who are using this solution in our organization.

Technical support is pretty good and responsive. I would rate them an eight out of ten.

We had a couple of issues, where we had to go through two or three different people to get a resolution.

Previously, I did not use another solution. At this company, this was already in place when I came here. This is what they had.

The initial setup is pretty straightforward.

Fees are monthly and it's approximately $8 per user.

It's a solid product and it gets the job done. It just needs to be a little bit more updated in the look and feel of it.

I would rate this solution an eight out of ten. It's a good product and just needs to be easier to find things in the portal and move your way around. Having it a bit more explanatory would be helpful.

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.