Pocketsidewalk

This is precisely my reason for wanting to use this method. I don't want my personal machine to be on the company VPN. I realize that VPN connections can be setup to use split tunneling so that corporate traffic is routed through the VPN and all other traffic is routed through the ISP's gateways, but from a security and privacy standpoint I'd rather have the machine sandboxed inside a VM that is only used for telework purposes. I'm currently using a Windows XP VM running on Virtualbox for all my remote connections. But since we have Windows 7 desktops available through VMware View (and will soon be rolling out thin clients across our offices), I thought it would be a good idea to start researching a way to access my virtual desktop from home. I hope that eventually my employer will implement a Security Server, but in the mean time this information has been very helpful.

The company I work for recently implemented VMware View. I work from home on a regular basis and would like to access my virtual desktop when working from home. My company currently has no plans to setup a View Security Server, so the only way to connect to the View Connection Server remotely is by first establishing a VPN connection to the company network. I would prefer not to run the VPN client directly on my home PC. Instead, I would like to create a thin client inside a Virtualbox VM and use that thin client to access the VPN and the View Connection Server. Before I dive in, I have a few questions: Is there an alternative setup that I might be overlooking? What is the best thin client OS to use for the Virtualbox VM? I'm using the Cisco VPN Client which claims to work on Linux.