Sunday, December 2, 2012


A bring your own device (BYOD) is nothing but allowing employees to bring their own device to access enterprise network.A bring your own device (BYOD) strategy for enterprises can be a winner for both users and administrators. But switching to BYOD requires more than throwing open the barn doors and letting employees buy whatever device they want. IT still needs to manage and secure the data on mobile devices, whether they are owned by an enterprise or user.

In more traditional mobility deployments, the enterprise itself was responsible for all facets of the mobile device, including purchasing, its associated voice and data plans, as well as managing the device assets. The IT department would track what device was assigned to each user and would be the clearinghouse for any device replacement or upgrades. Essentially, IT treated mobile devices in the same way that it did other IT assets like laptops or printers.Consumers, however, are embracing smartphones and tablet devices as ways to stay personally connected. This has led to a two-device dilemma, with many enterprise users carrying both a personal and work device with them. The bring your own device movement is partially a solution for this dilemma, enabling users to carry a single device for both business and personal use.

Bring your own device (BYOD) programs, especially when they include desktop virtualization, have gained steam in organizations looking to centralize desktop management and make hardware management easier. Allowing end users to employ their own personal devices can also make them more productive, saving companies time and money. But if an organization implements BYOD poorly, it can lose control over its infrastructure and, even more importantly, its data.

It’s important to take some time and plan out a BYOD initiative by following these guidelines:

Determine the need for a BYOD program
Some organizations jump on the BYOD bandwagon too quickly, not realizing how it can affect their existing IT infrastructure. Examine how users work on their corporate PCs to gauge whether they will be able to continue this type of productivity on their personal devices. In some cases, users will be a lot more productive given the chance to use their own equipment. Other times, a BYOD initiative just won’t make sense, either because of employees’ work styles, the corporate culture or other reasons.

Consider desktop virtualization
Desktop virtualization can deliver corporate desktop images to personal endpoints, ensuring that there won’t be a drastic change for users when a BYOD program takes effect. At the same time, users can still have very powerful, personalized computing experiences because they are in charge of managing their devices. The added benefit is that IT administrators can manage desktop images directly from one interface and worry less about endpoint hardware.

Don’t forget application delivery
Even though they’ll be using their own devices, employees will still need access to corporate applications. Application delivery is an important subset of desktop management, especially when it comes to BYOD. It means not only controlling how applications get to end users, but also how to monitor and manage application settings all from a centralized location. Virtualization is one way to handle application delivery in your BYOD program.

Plan for BYOD security
Even with a BYOD program in place, IT admins still have to control and manage access to the corporate infrastructure and data. Another benefit of using desktop or application virtualization is that data and applications live in the data center. This way, a lost device doesn’t spell disaster, because the device doesn’t actually contain any sensitive corporate information. As they do with standard, corporate-owned devices, administrators will still need to create comprehensive security groups and strict policies, plus perform general security monitoring.

Get end users’ support
Keep in mind that some of your users might not be up for BYOD. Some people may take issue with the blurring of the line between their personal and work lives, for example. Educating end users and assuring them that their IT department can help them have a better work experience with their personal devices should be on the BYOD checklist. By gradually testing the program, organizations can gain employees’ support and make them much more enthusiastic about using their own devices for work.

Develop BYOD policies
Implementing a BYOD program doesn’t mean users will be able to use any device they want. For BYOD to be successful, admins must decide in advance which devices they will support for various workloads. For example, you can deliver a full desktop to an Android phone, but it probably isn’t practical because of the small screen (and other factors). But delivering that same desktop to an iPad might work for some users. Figure out what the needs of your users are, then pick a device (or devices) to fit those needs. IT also needs to develop, implement and enforce a BYOD policy that governs user access to corporate infrastructure and data on their device.

BYOD still requires mobile device management
Shifting users to a BYOD strategy does not absolve IT from responsibility for mobile device management. It doesn’t matter who is paying for the mobile device, IT will still have to manage that device as a corporate asset. Companies will need tools to support mobile devices, including tools for mobile device management (MDM), mobile security and mobile application management.

No comments:

Post a Comment