[MUSIC] I might interject. Like he said I have no idea. >> No, it's good. [CROSSTALK] >> It's going to be live. [NOISE] So, with more and more companies buying into BYOD, there is this blurring of the lines between IT and user needs. Now, in your Opinion and experience, how can that issue be addressed? Is it even an issue? >> I'd say that companies, if you're integrating your mobile device with the corporate workflow, you're getting emails and apps and what have you, then companies are going to want to control that to an extent. And so, you have your IT guys that are going to want to send you things, like as a group policy that all users will get. And then, depending on what your role is, then you'll have different policies and things from each other. Users, however, might not necessarily like that. This is their phone, they don't want to have a corporate entity controlling what they do. But, now there are things called containers. So, Google has Android for Work and then Samsung has Samsung Knocks. And, they're containers within your personal device where your mobile device management solution can control only that container. So, you don't have to worry, you can have a set hard line of what's work and what's not. And, it's almost like two devices in one. So, I would say that's kind of how it interacts at the end of the day. Yeah, and I guess just to add to that. Some of the solutions that we see kind of out in the marketplace, some of the things that IT administrators want to be able to do, is, say for instance, they want to be able to wipe the corporate data on a device if it's lost. So, they have that functionality to do that but the user, on the other hand, is going to say, I don't want my device to be wiped because they could lose personal data. So, it's really this kind of tug of war between the personal data and the corporate data. The OS is really what allows the corporations to kind of manage the two. I think when we started out it was kind of all grouped on a device as one but now we're getting, like she said, this container kind of model where the administrators could send down a command to say, hey wipe out the data on this device but it would only apply to that data in the container. So, the corporate data. >> So, what kind of checks and balances do you think need to be there? For example, if one guy is in charge of that, like hey you know what click, let's just wipe this, what if they wipe the wrong thing? Or, let's say they wipe everyone's data across all platforms. >> So, it's a concern. The administrators of the Mobile Device Management Solutions have to go through a large amount of training so that they don't end up with a big mess up like that on their hands. It definitely it possible. It's within the click of a button except for a little warning pop-up that you'll get, you're about to wipe a device. >> Right. >> So, it's possible and that's. >> And that's concerning among users. And, in fact In terms of end users, we work with IT admins all the time and in terms of the companies that we serve but end users are coming to their IT admins. I don't want a possibility of you actually wiping my device. So, its usually not forced, like absolutely you have to put this mobile device management solution on your device. But, if you don't then you're not going to have the convenience of emailing, you're not going to have the advantages of corporate apps. So, at the end of the day, I'm sure some companies do make it mandatory. But, a lot of them It's up to the end user, ultimately, if they're going to accept the terms of having it on their device. >> Yeah, and that's one of the push backs that IT administrators are getting from users is that the user says, hey I want to connect to the corporate network on my device. And, the IT administrator says, okay well then we want to be able to do this. And, users they don't feel comfortable with that, because if it's their own device, they don't want their data to potentially be wiped. But, the container model really kind of helps curb that kind of issue for the user. >> So, not having, let's say a chain of command where okay, just one person is not responsible for wiping that, maybe two people. Maybe there needs to be that second guy who just signs off on it. Do you think that would help, or is just, would with the advent of MDM's it's not necessary? >> Yeah, I think with the advent of MDM's it's not so much. Because what corporations we see will normally do is have a policy in place. If it's a corporate owned device and it doesn't connect in within X amount of days or months, then we're going to wipe it. It's no longer being used and it if they'll get reports of people are no longer with the company. So, they'll get a report within their MDM solution that says that this device no longer needs to be controlled, so they'll wipe the policies that they've sent. Now, if it was a BYOD, then they're not going to actually wipe the device because a lot of the data on there actually belongs to the user, in a personal sense. But, they can wipe everything they they sent to it from a corporate standpoint. So, that there's no type of data breach or anything in that regard. >> What it really boils down to is it's really up to the company to define what policies they're going to put into place when it comes to administering devices. And, I think that's really one of the challenges because this kind of environment with mobile devices out in the field and managing them it's really different than kind of what we've seen in the past. And so, companies are having to figure out these types of issues and figure out how are we going to go about managing this. And so, a lot of new policies are having to be put into play. So, there's a lot of work that's having to occur in that area. >> Perfect. Thank you. [SOUND] [MUSIC]
