GreenPages Blog

As an IT professional, you need to stay current on all things tech; with articles from industry experts and GreenPages' staff, you get the info you need to help your organization compete and succeed!

Breaking Down a BYOD Initiative

Read More
All Posts

Breaking Down a BYOD Initiative

An Interview with Matt Mock, IT Director at GreenPages Technology Solutions

Ben: What encouraged GreenPages to adopt a BYOD policy?

Matt: The biggest reason we implemented a BYOD policy was that it offered the ability to give users the flexibility to use the technology that they are most comfortable with. Our IT department was getting frequent requests for non-standard equipment. This forced us to do one-offs all the time and made support very difficult.

Ben: How was the policy made? Who was involved in creating it?

Matt: The policy was created after many months of research. We looked into what other companies were doing, researched the costs for hardware and internal support, and interviewed different departments to see what was needed. We involved people from the top down, getting buy in from senior management to start. In addition, we also worked closely with the accounting department to make sure BYOD wouldn’t cost more than traditional hardware refreshes would. Our department did a proof of concept, then a pilot group, and then a gradual rollout. This allowed us to tweak the policy as needed.

Ben: Who has access to the BYOD program?

Matt: Not all departments. The program is for those where it makes the most sense from both a financial and support perspective. We didn’t want to grant BYOD to someone who couldn’t handle the issues on their own that would in turn create more technical support. We rolled it out to groups with specific requirements that weren’t going to cause us to spend more time on internal support.

Ben: Can you describe some of the highlights of the policy?

Matt: Within the policy we specify eligibility for the program, provide exact cost and reimbursement methods, and outline user responsibilities and requirements such as how to get hardware support. We also provide more specifics around what is and isn’t covered in the policy.

Ben: How do employees go about getting hardware support?

Matt: The user assumes responsibility of hardware support and is required to get a warranty. IT will help facilitate support but will not be responsible for the device. This goes back to making sure IT doesn’t spend more time supporting BYOD than they would have previously.

Ben: Makes sense.

Matt: I should also mention that GreenPages’ VDI environment allows us to offer the flexibility of BYOD with multiple devices because everyone can get the same experience regardless of the device used. Utilizing VDI also alleviates concerns around corporate data loss. If a device is lost or stolen, a person doesn’t have access to corporate resources just because they have the corporate device.

Ben: What have some of the main benefits been of the program?

Matt: The main benefits have been employee satisfaction and a decrease in hardware support for internal IT.

Ben: Some people think there are immediate cost savings from BYOD, but Chris Reily (GreenPages’ Director of Solutions Architecture) recently wrote a blog post cautioning people not to expect ROI in the first couple of years. Is this true?

Matt: Correct. You end up spending the same amount on hardware but support costs go down and employee satisfaction goes up. Direct ROI is difficult to measure when offering reimbursements. A company can avoid offering reimbursements but then you are greatly effecting employee satisfaction. If you give reimbursements, you probably end up spending the same over all amount.

Ben: What is your overall opinion of BYOD?

Matt: BYOD is not for every company nor is it necessarily for every employee within a company. A key thing to remember is that your infrastructure has to be ready for BYOD. If it is, then it’s a great perk and a great way to reduce time spent on internal support. It’s also a great way to allow new technologies into the organization and not have to give strict guidelines on what is and is not allowed.  Our BYOD initiative has also helped save my team time so that we can focus on more strategic projects that will help the business.

If you have questions for Matt around his experience implementing a BYOD policy, leave a comment or email us at socialmedia@greenpages.com

 

Comments

Related Posts

Tech News Recap for the Week of 07/15/19

If you had a busy week in the office and need to catch up, here’s our recap of tech articles you may have missed the week of 07/15/19!

Tech News Recap for the Week of 07/08/19

If you had a busy week in the office and need to catch up, here’s our recap of tech articles you may have missed the week of 07/08/19!

What Was Great in 08' Now Needs an EOS Update

Back in 2008 I still had a faceplate for my car radio, Bleeding Love by Leona Lewis was crushing the pop charts, and organic bean sprouted bread was something you’d find in the pet food aisle. It’s also the year Microsoft released Windows 2008 and SQL 2008, leaving a lasting impression like a tune you can’t get out of your head. For Windows Server 2008, it was the first Windows edition that allowed you to license for virtualization. If you recall, there used to be an Enterprise Edition of Windows 2008 that allowed for 4 VMs and if you needed 12 VMs you had to purchase 3 licenses. Datacenter provided unlimited VMs, and Standard edition both covered standalone and virtual machines.  At the time Microsoft was really making us work to understand the minutia of their licensing rules. Thank goodness Microsoft’s licensing has gotten a lot easier to understand (insert sarcasm.) Windows 2008 and 2008 R2 and SQL 2008 and 2008 R2 had a good run, and like all good things, including Leona Lewis’s career, it will be coming to an end. SQL 2008 and 2008 R2 End of Support (EOS) is July 9, 2019. Windows 2008 and 2008 R2 EOS is January 14, 2020.  Once Microsoft products go EOS, Microsoft offers ZERO support for the product, meaning they’ll no longer provide updates and patching. With no support, it would leave the product vulnerable to security threats because no fixes will be available to prevent infiltration. Security updates are mission critical. In 2016, 4.2 Billion records were stolen by hackers. Twenty percent of organizations lose customers during an attack and 30% of organizations lose revenue during an attach. Not fun!  It would be like if John Rambo retired and stopped drawing blood, which is a bad analogy because Rambo: Last Blood is being released in September. This begs that question, is this really the Last Blood? Probably not, however you can be certain the Microsoft’s “Last Blood” is actually happening. So what to do when your support goes away? Well you’ll need to think about modernizing and in this case adopting cloud. It’s a good time to seize EOS as an opportunity to transform with Microsoft’s latest technologies. A jump to Azure will allow you to migrate your Windows 2008 and 2008 R2 workloads to Azure VM or Azure SQL Database. Customers who move 2008 and 2008 R2 workloads to Azure Virtual Machines (IaaS) “as-is” will have access to Extended Security Updates for both SQL Server and Windows Server 2008 and 2008 R2 for three years after the End of Support dates for free. Those that decide to move to Azure SQL Database Managed Instance (PaaS) will have access to continuous security updates, as this is a fully managed solution. Or you could stay with on-premises licensing and upgrade to Windows 2019 or SQL Server 2017 by leveraging your Software Assurance benefits to modernize on-premises or on Azure (i.e. Azure Hybrid Benefit), to help reduce security risks and continue to get regular security updates. Regardless of what investment you decide to make, GreenPages can help right-size you for the future and ensure your data continues to be protected. To have further conversations about Windows 2008 and 2008 R2 and SQL 2008 and 2008 R2, please connect with your Account Executive or reach out to us!