cancel
Showing results for 
Search instead for 
Did you mean: 

BYOD vs. CYOD: The lesser of two evils?

Level 17

We know mobile devices are must-have tools for your end users and they’re growing more accustomed to having options when it comes to picking their corporate-connected mobile devices. Two end user mobile enablement strategies seem to be leading the pack: BYOD (bring your own device) and CYOD (choose your own device). BYOD, of course, involves end users providing their own device(s) from a virtually unlimited set of possibilities and connecting it to the corporate network and resources. CYOD, on the other hand, involves end users selecting their soon-to-be corporate-connected mobile devices from a defined list of devices that IT supports and can have more control over. The idea being that the burden on you is lessened because you don’t have to be prepared to manage every mobile device under the sun.

So we’re curious, has your organization settled on one of these strategies over the other? If so, we’d love to hear about your first-hand experience implementing either of these policies—or a hybrid approach—into your organization, and how your company arrived at the decision to go the route they did. If you have implemented a CYOD policy, what benefits have you seen? Was it successful or did your employees revolt and turn to smuggling in their own devices anyway? I'm looking forward to hearing your feedback.

And if you haven’t already taken our BYOD vs. CYOD poll, you can find it here.

5 Comments
Level 12

We have a hybrid approach of sorts, CYOD for our C-level execs and BYOD for everyone else. For BYOD, the device must be supported by our MDM solution and the only support we provide is the installation of the MDM client. Since most devices are supported we have to know the basics of many devices, but since we use an MDM, we only need to know that app well to get it installed and running. Our corporate apps reside in the MDM so it is easy to push an app out as well as remove them when needed. Without the MDM, we would not allow BYOD at all.

Level 9

I run both BYOD and CYOD with no MDM. Instead we have a Cisco Secure-X architecture. With their Web Security Appliance, ASAs, and ISE. Cisco ISE takes care of a little MDM without the burden of managing a whole group of more apps.

Level 7

We aren't quite at the point of BYOD, but we're working towards it. CYOD is just not an option outside the tech department, excluding the choice of a laptop or desktop.

For our BYOD, we're looking to VMware Horizon View 5.3 to solve many of our problems. With 5.3, we can offer a full Win7/Win8 desktop in an HTML5 compatible browser, so even Chromebooks become fully functioning enterprise computers. For those on any software platform that supports the actual client software, users are invited through the web page to download it. Since the only thing we want our users to access from their personal devices is the View environment, we use ACLs on a BYOD WiFi network to only allow them access to it.

Level 15

We have a variety of BYOD and CYOD.  No MDM but there is some policies and procedures if any company data is on the device. 

MVP
MVP

We are on the potential cusp of such a venture. For most of the company it is pretty much a standard desktop set.  Those in IT get a little more latitude but not quite a COYD.  There have been rumors of BYOD...

About the Author
I'm a Head Geek and technical product marketing manager at SolarWinds. I wrote my first computer program in RPG-II in 1974 to calculate quadratic equations and tested it on some spare weekend cycles on an IBM System/3 that I ‘borrowed’ from my father’s employer. After that I dabbled, studied, and actually programmed in just about every language known for the past 40 years; worked on a half-dozen different variants of Unix on 3B2s, RS6000s, HP9000s, Sparc workstations, and Intel systems; connected to CompuServe on a 300 baud modem; ran a FidoNet BBS on OS/2 on a 9600 bps modem; and started working with Windows when Windows NT4 was still the latest operating system. Along the way, I did a few years in database programming and database administration. I installed some of the first ADSL and SDSL Internet circuits in Texas, and then migrated into full-time Windows systems management, which had a lot to do with my interest in SUS and WSUS 10 years ago. This ultimately led me to EminentWare in 2009, and SolarWinds three years later.