What is our primary use case?
The primary use is providing support to remote employees on mobile phones. We also use it to deploy software and updates to the phones.
How has it helped my organization?
The remote control technology and screen-sharing absolutely help us resolve issues faster. If there is a remote user who has difficulties or does not understand an error or a problem or a crash, the support team can remote control the phone and see right away what is on the screen and act on the problem. We could debug, we can help, we can reboot the phone. We have many options to help the remote user who is struggling with an application or with the phone. Before, they had to bring the phone to the office or to their manager so that we can debug it. Now it can be done remotely, most of the time, if the phone is not broken. These are very important features that we like. That's why we use SOTI.
The Lockdown Kiosk Mode is very useful. After the remote control, it's one of the main reasons we use the solution. When you have 9,000 people remotely using your applications, you want to make sure that they don't play with Facebook while they're supposed to be working. It's a very important feature to prevent installation of applications we don't want and to provide a uniform device interface for everybody, no matter what the phone brand. The uniform interface makes training easier. It also prevents installation of software that could be harmful or compromise the security of the phone. It's a very important feature.
Because we have a custom, business-to-business application, the solution's deployment features give us the ability to control the deployment of new versions. We can granularly decide which people or which phone receive updates. It's kind of like having your own "app store" and being able to control what you deploy on the phones, how you want to deploy it and when you want to deploy it. You can see how the deployment is happening; if it's going well or not. It's a convenience feature that provides us with great flexibility in the deployment of our software to our users.
By enabling a faster response time to support users who are having difficulties on their device, it helps us with downtime or with a device that was blocked or malfunctioned. The support team is able to respond faster to problems, providing a faster resolution time so that the end user is back working with the device.
It has improved the security of the phone, through lockdown. If the phone is lost we can remotely wipe it. It reinforces the overall security of the device.
There are many aspects in which we've improved the efficiency of our operation.
What is most valuable?
There are many features that we use.
- The main one is providing support through remote control of the phone.
- Another feature we use provides a lockdown screen, which prevents remote users from starting or installing applications that are not officially supported by the company.
- We also use it to deploy updates of our software remotely.
- There are some additional features, like antivirus, that are part of the solution and are nice to have.
In a nutshell, those are the four main features that we use. The software has many more options which we don't use that often.
What needs improvement?
You need to get used to the admin console. I think it could be improved. It's not the best I've seen. Certainly, the software has a lot of features so you necessarily have some complexity in the interface, but I've seen better. They could make it easier in certain aspects.
Once you know it and how to navigate through it, it's good. When you're not trained on it, that could lead to some difficult situations where you say, "Where is what I need? What do I do?" If you don't know how to navigate through it, you could get lost. It's a complex interface in that regard. You need to be trained.
Development of lockdown screens, and certain aspects of the application, are still cumbersome and difficult to work. A certain subset of the features of the application are sometimes difficult to work with due to the complexity or maturity of certain modules.
One of the main pain points I have had with Soti is support for the latest device. That could cause a problem. Let's say Samsung comes out with its latest device and Sprint and Verizon start to sell that device, and we have a few of those devices to support. Sometimes you need to have an agent on the device and there are times when the agent is not fully compatible with the new device. That can cause problems. Certain stuff crashes. They need to catch up with the latest devices. Generally, when we have difficulties, it's because the phone is brand new and SOTI doesn't have a connector or agent that is fully compatible with the device. Any MDM always has to make sure that its agents support the latest phones that come out. Sometimes it's difficult.
They have to really work on making sure they lock down a strong relationship with the device manufacturers so that they can work in advance on their agents before the phone is released to the wider market.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
The solution is very stable. In the four years we've been using it, there have been very few issues.
What do I think about the scalability of the solution?
As I mentioned, we have nearly 9,000 users on one machine. Over the four years, we have had to upgrade the type of machine we're running it on. It scales but the problem is that you need to upgrade the server on which you run. You need to add more CPU or more disk space to support the scalability.
The scalability is horizontal, not vertical. One machine has to have all the accounts. That's one of the issues that we have found with scalability: You always have to keep the same machine. If you want to add a second machine, you need to split the account and that removes flexibility of management.
The other weakness that they have currently is that they don't have systems that are built for redundancy. You have one database that manages everything and, if that database crashes, you have a problem. They could have done a better job with redundancy, and on scalability there is some weakness. It scales but you need to add more horsepower every time.
Because machines are very powerful, it's not so much of an issue. Now we're on the cloud. You can scale servers very easily. But I would like, eventually, for there to be better redundancy in the system for failovers. Failovers are a weakness of the solution. If my server goes down then my solution goes down. They don't have a failover strategy for their solution. That's a weakness in the scalability.
How is customer service and technical support?
We have Enterprise Support. We have additional support because we are one of their large customers. We have access to some of the senior developers. Generally, we have a direct line. If there is any glitch or any step that we don't understand or we need help, we have fairly quick access to support from SOTI.
Support is very good. They are very knowledgeable, very good at helping, at doing everything to help when we have issues. They follow through. If they don't have a solution, they bounce it to the dev. Generally, I have always been pleased by their response time, by the quality of the response, and by the knowledge of the people in support. I am very pleased with support.
How was the initial setup?
Generally, you have to install from the app store or they have an OEM website where you can download the agent. Once you know the process, it's fairly straightforward. We've done so many that we're used to it.
It's not complex. It's not simple. It's in between. You have to have a license key and a few other elements on hand. Then you install the agent on the phone, you register it and it appears on the interface. Any MDM will be like that. Deploying a device takes a few minutes, assuming you have everything already set up on your server.
In terms of our deployment strategy, first, we set up our own servers. We have remote users in both Canada and the US. We break it down by countries first. Then we have a breakdown by type of device: tablets or phones. In our implementation, we then segment the phones by provider: Verizon, AT&T, etc. Within those categories, we break it down by type of lockdown screen because we have different types of lockdown screens for a manager and for a regular employee. Based on their roles, they have more or fewer applications available.
What about the implementation team?
We did it internally. We have some people helping on the lockdown screen. For the rest, we manage the software ourselves. But because we are a large SOTI customer, we have Level 3 support. When we have issues or problems or questions, we have access to the top SOTI engineers.
What was our ROI?
For us, the solution is part of the overall business cost. It's required. It's not about saving money. It's about supporting the users' security.
What's my experience with pricing, setup cost, and licensing?
There are solutions that can be more aggressively priced, but they may not provide all that SOTI does. It's a matrix regarding what feature you use. You need to compare the features you use and what you are willing to pay for them. You may have MDMs that have half of what SOTI provides. They are cheaper but you have less.
SOTI's pricing is okay. It's in the middle. But pricing is a subtle issue. They can provide more aggressive pricing once you start to have a lot of licenses. They have volume discounts and can be very competitive.
What other advice do I have?
You can have the solution in-house or you can have the solution on the cloud, managed by SOTI. Evaluate your needs. There are advantages to having SOTI managing it for you. That's something to look at.
You definitely require some training and understanding of the management platform. That's part of the deployment, especially if you use certain features, like lockdown screens which require some configuration and setup. SOTI can provide support to evaluate this. They help you with certain deployment aspects and training on the solution.
We may look at the real-time location services from time to time, but part of our own software on the cellphone gives us tracking through GPS. So this feature from Soti is not something that is necessary. It's not critical to our use case of SOTI.
Another thing that is important is knowing very well the types of devices that you have and making sure that they are supported by SOTI. If you use older devices or devices that have been on the market a while, that should be okay. If you're planning to have a lot of new devices, and if you're changing devices very frequently, make sure they're supported by SOTI.
Also, if you use an unknown device brand, that could be problematic. We are in the security industry. While you probably you use an iPhone or a Samsung or some well-known brand, in certain industries, like ours, there are specialized phones. You may have phones that are made especially waterproof or that you can drop. They've been "ruggedized," made to work in difficult environments. Those phones may be from brands you've never heard of. If all your phones are from unknown brands, you have to make sure they are supported by SOTI. Generally they are, but you have to do your due diligence between your inventory and what SOTI supports.
For administration of the solution, we have a small team of five people. Because we are hosting the solution ourselves - we have and manage the servers - it's our responsibility. We have two sys admins who maintain and administer the solution.
We are growing every month. We are adding hundreds of licenses every month.
I would rate SOTI at seven out of ten. It's a good product, very stable. There's some stuff that they could improve and I think they are improving it.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.