If you Download Windows 8 consumer preview (Free) and install VMware workstation rel 8.02 (or later) this can operate your Virtual Machines as Servers where NOBODY needs to be logged on to the host or even have an account on it.
In other words for example users can logon (locally on the same Lan or remote if your router / firewall allows it) to the VM without having to have an account on the Host machine itself.
Of course the Virtual machine will have the same restrictions as to number of concurrent users as a Native machine would -- I use a Windows 2003 Server - but unless you can get some arrangement from work / college (if you are a student you can often get a server OS from Ms via your college) you'll probably have a single user machine such as Windows 7 as the remote Virtual Machine.
VMware's vmserver is now discontinued -- functionality has been incorporated into VMware workstation rel 8.
I haven't tried the facility in Windows 7 but it definitely works in W8 consumer preview -- as far as users of the remote machine are concerned -- no difference as the are only seeing the standard W2003 server login screen.
You wouldn't have ANY problems running 2 or 3 Windows 7 instances as virtual machines on the host and as I said users don't have to have an account on the HOST.
Note that to use say RDP (Remote Desktop) to each virtual machine you will have to arrange for the RDP ports via your router to be mapped differently for each machine as RDP has a standard port setting.
It's fairly simple to set up and if the Windows 7 machines are reasonably identical (should be with Virtual Hardware etc) you can test say one machine and then clone the rest.
Note here to avoid confusion
What I mean here that NORMALLY when you run VMware on a Host YOU (or a USER) have to be logged on to start the VMware program and need to be logged on throughout the life of the application.
What operating it as a "Server" does means that this process can run in the background WITHOUT anybody being logged on to the Host -- so the host gets booted up and starts the VM's and you are in business.
It's probably a bit heavy to start with but if you can perservere and peruse this article it should point you in the right direction --actually although it sounds complex once you've got the basic process going you'll be amazed at how easy it is. http://kb.vmware.com/selfservice/mic...rnalId=2005585