Never looked back.
"...some feel that providing contractors and other outside parties access to select corporate systems would be another hot area for VDI deployment. In the US a number of organisations have begun to experiment with variations on this theme: instead of supplying users with corporate PCs they provide them with an allowance with which they can purchase a machine of their choice. This machine then has a desktop virtualization system laid upon it and corporate access is delivered in an isolated virtual machine on the desktop thus in theory completely separating corporate and personal use."
My current client is rolling out VDI. I am one of the lucky few who stepped up and wanted 'in' as soon as it was available. I've not looked back. As a contractor, the ability to do the job using my own equipment is a really nice bonus. No longer do I have to carry around a laptop owned by the client, pre loaded with M$ shiteware and a whole load of stupid instrumentation / monitoring software / USB lockdown etc etc. Now I take my Ltd Co owned laptop, with it's proper kubuntu OS, home converted to dvorak keyboard etc etc with me. At work I sit it on the desk and slap in my 3g Dongle. I avoid the corporate LAN and therefore having to sit behind the stupidly prohibitive proxy. I can pull up a terminal and ssh to my boxes at home, I can spend 10 mins on facebook, I can read my webmail or pop connect to pull it into kmail. At the same time I can do my work, efficiently and professionally all in a window on that machine. The point is, from a digital perspective I'm both at home and at work all the time. No need to dial in over some modified VPN client, just point firefox at the client's gateway, key in the # on the RSA fob and I'm at work - At home I do this over wireless, at work, over 3g.
Of course, I can use any machine I want, too. Recently I was in a datacenter owned by the client. I had taken my laptop in to plug into a serial port on a piece of kit to give it it's first ever IP address. Normal task for someone like me. I realised I needed some stuff from my VDI session. Previously this would mean leaving the Data Center, taking the old company lappy with me, plugging it into the network somewhere where there's a desk (ops bridge etc) - so long as there was a spare eth port / power etc, then logging in blah blah. This time I left the lappy where it was, wandered along a couple of racks, popped out the keyb/screen from a SAN management server owned by our team, logged into that and then mstsc'd to my session. And there it all was, email open right where I left it, IM chat with colleagues still up. I probably only reboot the actual VM once a month, no daily routine of log on, open apps, do work, close apps, log off, just connect from wherever, whenever, and do some work, then drop off again. In a traffic jam I've done 'in car VDI' with 3g dongle and Asus eee. I didn't have much screen, but I was productive (read 'billing') and not sat in a jam losing money. Good for the client, good for me. If you work 1 hour's drive away from home and you're on call, you can pull in anywhere and connect so long as there's a PC. Internet cafe I've not yet done, and I realise I'm bigging up 3g as well as VDI. But the combination is awesome. I can take the kids to the zoo AND do that 10 minute failover test that no one not on VDI would volunteer for on a Saturday afternoon.
Ok, so this reads a bit one-sided, time to balance it.. It is rubbish for that 20Mb VISIO diagram with 80 switches, 400 servers and all the cables shown on it. Running anything graphics intensive (and I even mean looking at google maps etc in the VM's browser) is horrible. But then for a lot of stuff you could do that in your native OS, if you're not on a thin client. Also, for obvious reasons, you generally can't get stuff to move between your VM and your native OS, even copy paste of text is locked out. This clearly makes complete sense, but is a touch annoying at times. It really depends on your role/contract/needs. I'm not a web designer, I'm a SAN/NAS/Backup architect / consultant. 90% of what I do is unix or CLI based, if there's a GUI and a CLI, I'm using the CLI, but that's because it's more efficient and I'd do that anyway, without the slow refresh of VDI. In short, this works for me and I'll never look back. But if 90% of my job was in spent in photoshop then it wouldn't make the job harder, it would make it impossible.