Windows Virtual PC with XPMode or another Windows 7 or Vista virtual machine running with full integration features can be highly insecure since it exposes all the host's drives to the VM by default via RDP and TS as available shares, unless the drives shared resources are specifically disabled.
In order to do the changes to the VM settings it is usually necessary to have the Virtual Machine fully powered down, not running or hibernated etc.
The trick is not
to run the VM with full integration features enabled. On one hand this means you can't run applications in the VM seamlessly on the host machine, but you will have the advantage of running the VM at the best screen resolution (32-bit) rather than the default 16-bit or forced 24 bit resolution (the video driver from integration feature pack can still run, as well as USB and devices connected to the host).
First you need to enable the integration features and shut down the VM, and restart the VM after changing the Integration features settings:
In the VM settings you are best to set integration features to manual
and uncheck the enable at startup
checkbox. This also removes the credentials logon, and the black screen, whenever screen size is changed or switching from VM to host and back.
Your VPC VM does
have an IP address - you can determine this by running
at the command prompt in your Virtual machine. However it is likely to be on a different network segment (by design - via NAT on a virtual ethernet adapter in VPC) from your host machine.
You can make your VM use the physical ethernet adapter on the host in the virtual machine settings by selecting Networking, Network Adapter 1 to be the same Ethernet adapter device as shown in the Control Panel\Network and Internet\Network Connections, Local Area Connection, Device Name. Your VM should now connect on the same network segment as the host machine - your Intranet - obtaining a separate IP address from your Intranet's DHCP server. Otherwise you will need to supply a Static IP address in line with your work network admin policy.
Once you know this local IP address, and you have enabled sharing of resources on the VM by adding and enabling "File and Printer Sharing for Microsoft Networks" in the Properties of the network connection on the VM, and enabled the sharing a folder and naming the share, with any necessary credentials and passwords, you should be able to map the share from anywhere on the intranet. If you have a Workgroup, or a Domain, the VM's computer name should enable ad-hoc network access via the Windows Explorer Network side panel.
Some screenshots can be found here:http://www.fxxxingcomputers.co.uk/home/virtual-pc