AKA Another great reason to consider using Virtual Server 2005 for test/dev scenarios....
I was asked a question a couple of days ago, and I hadn't thought of using the VMRC client in this particular circumstance. I haven't tested it, but there's no reason I can think of which should cause it to fail. Once I return from the USA, I'll try it out.....
- User is at home, connected to work network over VPN
- At work, there is an XP machine running Virtual PC
- From home machine, user uses RDP (remote desktop) to connect to the XP host
- Once logged onto the XP host, user starts Virtual Machine
- User at home optionally disconnects RDP session to host machine at work
- From home machine, user uses RDP to connect to the guest virtual machine
- Upgrade to Virtual Server 2005 on the XP host which is physically at work. (Note this is test/dev only)
- User is at home again, connected to work network over VPN
- Install VMRC on users home machine
- Run up VMRC and get full BIOS space operations on the guest VM running on work machine.
Previously, to get BIOS space operations from the users home to a virtual machine, it was necessary to operate the virtual machine through the remote desktop connection to the host machine at work. If you've ever tried this, it's very confusing. Trust me. Through VMRC, you wouldn't actually need to get to the host machine atall, you can go straight to the virtual machine and its pre/post BIOS. Kind of neat.
Hope this is useful!