Re: Responsability
Corp IT only provides a vendor-neutral, standards compliant back-end for all clients to be able to connect (IMAP, POP3, and the like).
Incidentally, companies have had this for years before BYOD even came up. It's not external connections in that are a problem, you can filter them to hell, restrict what they can access on the server etc.
It's when users want to plug their malware infested devices into the LAN or connect to the WLAN that's the issue with BYOD from a basic security PoV. Unless, of course, you think running a VLAN for each client is fun.
Reading your post has me thinking of the Corp. IT issued laptops that run outdated software (XP with IE6 anyone? Outdated Flash or Java...)
That does suck, no disagreement there. On the other hand, it is a work computer and if the business has decided IE6 is all you need then that's what you get. You should of course raise hell about it where IE6 is involved.
The web is filtered to protect staff from the likes of WebEx. IT Support are either a help desk of a dozen low qualified interns, or asleep when you call at 3 in the morning.
Budgets are often cut, perhaps if the helpdesk had a few less qualifications between them IT could afford to buy you the Alien laptop you'd prefer. Of course, the support would be worse, but you'd have better kit. Addressing a balance can be difficult, and very few businesses get it quite right.
The technology is ready - what needs work are the internal application policies that are compatible with law and the users' expectations.
Sorry but user expectations don't factor in, business needs do (and that includes the law and regulatory compliance). Users' expectations don't take into account things like law, budgets, scope for expansion, ongoing support costs, licensing costs etc. Nor should they have to, it's not their job.