We haven't done an on-premise installation because we just acquired the representative license. In the coming month, we're going to deploy the on-premise installation in another country with a SOTI engineer from Morocco.

The maintenance is done through a SOTI partner. If we have any doubts, we can request assistance from SOTI.

Setting up MobiControl wasn't complex. I had someone help me. I asked him to go back and show me so that I could collect screenshots of the work he was doing, but it was fairly straightforward.

The setup is not at all hard. It's like any other program. You just install it. It's the configuration that is difficult. There are so many things on your network that need to be open. You need to take care of ports, URLs, access to certificates, etc. There is just a laundry list of things. It is not that they're hard to do, but in most enterprise companies, you not only need to know what you're asking the security or networking teams; you also need to be able to tell them. When they tell you no, you need to be able to say why they have to and explain it. You need to be able to explain that if they don't do this, this major thing in our company won't work. 

SOTI should not only tell me what needs to be done. It should also give me good reasons for it. If we need to open a certain port, it should explain why we need to do it, and if we don't do it, this won't work. With such information, I could tell the networking people that this is what I need. It's not going to be a security issue because we're only talking to our own servers. Instead of telling them only what I want to be done, I should be able to tell them why it's okay to do and why it's not going to hurt anything. Currently, because such information is not there, there is a lot of back and forth communication.

The initial setup is easy. I rate the process a ten out of ten. The deployment and application upgrade takes one or two hours to complete.

It takes 25% of a person's time to deploy and maintain the solution.

The SOTI team was hands-on and very supportive. They supported us enough to tackle any issues. 

13 people and all system admins were involved in the deployment.

The initial setup is neither easy nor too complicated. The solution is deployed on the cloud.

Actually, we have a team for maintenance, and we also help each other. So around 10-15 people are required for maintenance.

The initial setup is straightforward, but that's probably because I know the software well. The complete configuration took around two hours. We have some on-premises deployments, but most use cases are on the cloud.

The initial setup was easy for me.

Setup is easy for the on-prem. For transitions to the cloud, it can take two days to get everything converted up and uploaded into the cloud. We just did one recently and there weren't any problems. It switched over from on-prem to cloud pretty seamlessly.

The initial setup was pretty straightforward. We had to work with our server team so that it was set up the way QC likes to have things set up. To set up the server, it took about a week or two, and that was more just a matter of coordinating. It was very reasonable. It took longer, on our side, to do the legal part.

Our strategy has been to use SOTI to move away from MSP and to get legacy equipment operational, before trying to get anything new going.

In terms of deployment, we've mostly had one person from each of our sites focused on this particular implementation. At some sites, the configuration changes more rapidly than at others.

I wasn't here when our account was set up with SOTI, but what I can speak about is setting up SOTI within the device, when we have to deploy a new one.

The process, at least for me, having been trained by our engineer, has been super-straightforward. Knowing how I can troubleshoot it myself, knowing what needs to happen in terms of right-clicking it so it pings to the device, all of that has been very straightforward. I'm not sure if I would describe myself as a super-tech-savvy person, but the technical understanding is straightforward: You have a device that's paired with SOTI, now you have to turn on the iPad to make sure it works. That has been very straightforward for me. SOTI has been super-easy on that side.

When we're pairing a device to SOTI, it takes no more than five minutes, as long as it is on WiFi. As soon as it's on WiFi, it takes no time. 

The deployment process is simple because the legacy interface is easy to understand and easier to use than Workspace ONE. The SOTI Next-Generation UI is just like Workspace ONE, so sometimes it's difficult to use.

SOTI is changing from the classic user interface to a more modern type of user interface, which is more difficult to use.

The part I can speak to is the version updates. The initial installation went quite well. We had five users five years ago. Now we've got 50 users. How we used devices five years ago is way different. We did not have a call center at the time, and now we have a call center. The version update is what I can talk to you about because I pushed for it, to get the latest and greatest version, and they were incredibly helpful.

We had older servers it was running on, so we had to update the servers. The quality of the technical people at SOTI was phenomenal, it didn't take much to figure it out. We were able to import our stuff from an older server to a newer server and connect to the database with minimal impact.

Once that happened, all consecutive version updates are basically pushing a button and letting it chug and it's done, it's up. We have a really solid platform for what we're doing right now.

We were on version 9 or 10. Once the servers were updated to the most current servers that support version 14.3, after that, it was straightforward. It took 15 minutes to do the last two updates that came in. MobiControl was already up, and all we had to do was update the agents. I had no issues with the devices in the field connecting. So as far as I'm concerned, it was a 20-minute window.

In terms of updates, we haven't had any bugs. As soon as the device comes online, I can do a global Agent Upgrade within 24 to 36 hours, and the handhelds all update. I haven't had an issue with an agent. It just works.

The initial setup is very simple. 

The solution's initial setup is a little complex, but not too much.

The initial setup of the SOTI environment is easy. They do most of it for you.

We went from an on-premise to a hosted solution, and I think the setup for the hosted took about a week. It didn't take very long for them to set it up at all. It was very simple to do.

They're actually in the process of upgrading one of our environments right now, and then we are going to migrate into the upgraded environment. All of that, again, has been done very well. Their change-review process is very effective and careful. Once you get with the technical teams, it's always pretty simple.

The way that we were able to implement MobiControl was with equipment refreshes: "Here's your new device, it's got SOTI on it, you can't take it off."

SOTI MobiControl's initial setup is a little bit complex, and we have a lot of missing options in them.

The initial setup is not complex. It's really straightforward.

The initial setup of MobiControl was straightforward. After receiving our initial information, we coordinated with the support team, who promptly set up the cloud-based server. They provided us with login credentials, allowing us to access the console and perform the initial configuration effortlessly.

The deployment typically takes around five to six hours to complete. However, the duration may vary depending on the customer's specific requirements. Our usual deployment process involves collaboration between our sales team and the customer. After receiving the license, we will communicate with the customer to schedule a configuration session. During this session, we work closely with the customer to complete the necessary setup and customization.

I rate the process a ten out of ten.

The installation of SOTI MobiControl is straightforward. However, it can take approximately one hour because you have to create multiple rules and other policies more many devices.

The setup was straightforward. We have the Enterprise Support package, so they walked us through how to set it up.

In terms of our implementation strategy, right now we're upgrading from version 12.4 to 14.2. It's taken a couple months, but I just set up an on-premise test environment to start moving some pilot devices over. Once that's complete, I'll upgrade the test environment to 14.2, and we'll test it for two or three weeks and then schedule a time to upgrade the production environment.

I am doing the deployment myself, but the admins at each site are helping with the testing process. Once I've completed the test environment, the site admins will test their devices, and I'll do the upgrade after they're done testing.

The initial setup was pretty straightforward. Our deployment strategy is to do pilots, expanded pilots, and full roll-outs. The amount of time it takes depends on what we're doing and how big the application is.

The initial setup of the cloud version of SOTI MobiControl is easy and quick. However, the on-premise version can have some challenges.

The cloud version of the solution took us five days to configure the platform and deploy it. The on-premise version can take more time, approximately three to four weeks. However, the time depends on what setup the customer has, such as a proxy and firewall.

I was not a part of the initial setup of SOTI. I was brought in a few months after. There were definitely some growing pains with the setup, it was brand new. We didn't have any sort of MDM or anything like this. We actually didn't deploy mobile hardware until we had SOTI.

I came in about three months after they initially started to use the MDM and, honestly, the changes we made to it were minor. It was more looking at the way device groups were structured and how they grouped everything together: profiles, settings, and that sort of thing. We figured out best practices pretty quickly.

Because I wasn't there for the initial setup and start-up of SOTI, I don't know what information was presented at the time. Since then, and since moving into Enterprise Support, we do have a SOTI rep who explains things. He's open to any questions and shows us things. He's done a great job of that so far. That availability is definitely there. It's the day-to-day right now, in my staff, where we don't have time to really move ahead on other features yet. We're trying to be proactive but a lot of time we end up being reactive, just based on workload.

The setup of the solution was straightforward. Everything was okay with no problems related to the application. For the initial deployment, it took us about a week to enroll the devices.

Before MobiControl we had another solution from Zebra. We used that application to deploy the environment to all the devices that we had on that system. That was how we enrolled all our devices to the new solution.

Setup was very straightforward. The installer scales quite easily to allowing you to install everything on a single box, or splitting the roles among various servers for high-availability. The most complex part of setup was configuring all the firewall rules for Device Agent communication and web portal access.

It was pretty straightforward. Our administrator set up the local server that would run SOTI, and getting all the devices configured was super-easy. The setup went really well.

To get all the devices set up didn't take very long at all. In total we have 60 devices. It took an hour-and-a-half to do all of them.

Our implementation strategy was like an assembly line. I wrote down the last four digits in the serial number, and then as I edited each device, I input the type of device with the serial number, and then just dragged the file onto it.

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.

The initial setup is easy for us because we have a specialist engineer. Otherwise, it is not so user friendly. You need an experienced engineer and some knowledge to deploy this solution, especially if it is a complex configuration.

The initial setup is straightforward. It took three or four months to deploy.

The installation is very straight forward if it's on-premises. Many customers are doing the installation by themselves due to the fact that it is so easy. The complex part is more about networking and how they can configure Mobicontrol in their network with the security requirements and everything. However, if you are talking about the installation itself, it's straightforward.

If we have all the different teams available, for example, for security and infrastructure, we can deploy this solution in one day. It really depends, as in some structures we need a security team just to open a network. It can take days, or hours to confirm and validate this point. It really depends on the customer and its structure. However, if we have everything available, all ports open, we have the infrastructure available for it, we can do this in one day at most.

Usually, there is one person from the SOTI side that can assist.

The setup was fine. The only time we actually need any assistance is when we're doing an upgrade.

The initial setup is fairly simple. It took us about two weeks to develop a package and roll it out to a set number of devices.

It was pretty simple.

Initial setup was complex for us as we wanted to upgrade from an older version V4.1 to Version 9 or 10 or later. We have 1600+ devices that were to be upgraded to new server and device agent. But even after multiple rounds of calls with SOTI Support they were still unable to upgrade correctly. They suggested to install a new version instead of upgrade and then move the devices. This is not an easy task and we are still on old version 4.1 of SOTI Mobicontrol.

The initial setup was definitely a little more complex. We're using the on-premise version, and to get it to work behind our firewalls was a little bit tricky. I am still basically in the process of deploying. I have about 20 devices on it and, as I said, at this point, my server is broken and I've been waiting for a technician to help. He's scheduled to help shortly.

It's been an ongoing process for at least three weeks and every day I'm running into different issues and it's frustrating.

The initial setup process is simple. It involves generating a QR code as an admin and having users scan it to enroll their devices. We can manage devices through hardware control settings.

The initial setup was very easy.

It is a matter of hours. It is done within a day, and then it is handled mostly by SOTI or the manufacturer, whatever you want to call them.

The setup was straightforward because the systems architecht is simple compared to other solutions like VMware Airwatch.