A lot has been said about the strategic advantages (and problems) of BYOD, but much less about how to build a wireless infrastructure for it. Good job we're here to put that right. Join Trevor Kelly and Andy Cooper from HP, and Dale Vile from Freeform Dynamics, as they set out the essentials of what will make BYOD work: the …
Subtitle sums it up really
'Don’t think about it, build it'
The order given from on-high to IT departments regarding BYOD.
BYOD - the choice of the thought-challenged.
Re: Subtitle sums it up really
Of course. The only thing that they think matters is that they have more commas in their salaries than we do.
Re: Subtitle sums it up really
> The order given from on-high to IT departments regarding BYOD.
Closely followed by BMAiD
Just for clarity...
It would be nice to start with Bring Your Own Device before using the abbreviation, especially since this movement has several off springs like bringing your own phone, pc, laptop, etc. Not everyone keeps up, that's why we have you afterall...
Although I made quite a bit of fun about in the comment section of one of the earlier articles I do see the potential here, but in my opinion the thing shouldn't be focussed on bringing your own gear but to allow your personal broader and wider access to your data. That's the main key point, one which could have been made anyway. However, I'm a little sceptical about the massive touting people are doing because let's face it: giving access is one thing, using said access is something completely different. That takes someone who feels committed and involved with his job.
But yes, it can work. This reminds of a sysadmin job back in the 90'ish. It was an enterprise-like company, but not as big that we could afford 24hr monitoring of our services. We did have something as a hotline; one person who would "take watch" for the evening to make sure that if their were problems he could get into his car, go to the office and step in when required. Due to safety concerns there were no outside connections permitted, none what so ever. At once time the upper brass became a little more lenient and allowed a Unix machine to be accessible from the outside with limited connections to the internal network.
And so I designed a scheme to relay 3389/tcp data internally, and went through all the official channels to get permission for implementation, even more tiresome than developing the model itself. The result was that certain people, amongst myself, would now get strictly controlled access to the internal Windows server network from their home location (this was only allowed if you had a static IP address; both for easier administration as well as a form of signal to the upper brass that you were deeper involved with this technology).
The result should be obvious; many people, including myself, would easily logon during the evening in their own time to check if everything was still ok. This even prevented a disaster one day because one of my colleagues did the same, spotted something weird, immediately called the manager and prevented a major disaster due to a bug in one of the monitoring scripts. This guy was working from home, in his own time, because he felt that was important.
This BYOD thing is basically no different, apart from one thing... I fear that its main motivation isn't so much to involve more people into the way the company works, but to try and apply a cost reduction on hardware and making it more appealing for the crowd to use their own stuff. I can see how this will have a psychological effect too: "Ha, at least those asses from ICT will no longer be able to tell me how to use my computer!". Of course without an extra pay check for all the hours you put into getting the whole thing to work.
And there's the small issue, one which I made fun off in my previous post about this subject, that there's usually a good reason why ICT restricts several things on the network.
I think a lot of companies are going to find out that BYOD sounds awesome in theory, and that the first signs will also be very positive due to a large number of employers embracing the idea. But I think it will mostly be fuelled by the wrong motivations (cost reduction, less limitations) and that can come to haunt you....
The growth of BYOD has created major challenges for IT staff. How do they secure sensitive data? How do they manage all those different types of devices? How do they connect employees and their devices with corporate applications?
One strategy for meeting these challenges is to separate data and applications from the end user devices. This can also be achieved with a combination of virtualization and HTML5 technologies. For example, data and applications can be securely hosted on VDI virtual desktops or on Microsoft RDS (Terminal Server) while mobile employees access those applications and desktops using HTML5-compatible browsers.
That's the idea behind solutions like Ericom AccessNow, an HTML5 RDP client that enables access to Windows applications and desktops from a browser. Basing access on the browser allows employees to get to their applications and data from Android tablets and phones, iPads, iPhones and other devices.
This white paper - "BYOD is Here to Stay, But Organizations Must Adapt" - discusses additional approaches to managing BYOD:
Please note that I work for Ericom
- Crawling from the Wreckage Want a more fuel efficient car? Then redesign it – here's how
- Apple SILENCES Bose, YANKS headphones from stores
- Nobody wants to look at your boobs: Snapchat gets ads 'that interest you'
- TV Review Doctor Who's Flatline: Cool monsters, yes, but utterly limp subplots
- Vid NASA eyeballs SOLAR HEAT BOMBS, MINI-TORNADOES and NANOFLARES on Sun