Well, let me describe what I am trying to do and tell me if workstation will do it.
I currently have about 6 windows server 2003 virtual machines. Each one runs a custom install of a software our company uses. Without touting all the bells and whistles, it basically it a specialized web server running on it's own install of tomcat and java. It uses only ports 80 and 443 for communication.
Each VM hosts a seperate install of this software. Each VM has a unique internal LAN IP, which is NAT'ed from a Public WAN IP for each server. All the VM's are exactly the same with the exception of the different install settings for our software. No other software is installed on the servers. Base 2k3 install with updates, etc.
Now then, how we set them up for rapid deployment is we have a base VM that already has the OS installed and updates and everything (pre software install). When we want to deploy a new VM we simply do a full clone of the base VM, rename the computer and give it a different IP. Then install the software.
The problem is we are running out of disk space on the server that hosts the VM's and I don't want to move the VM files to a networked drive. Each VM once we deploy it eats up about 5GB of space. And the SAS drives aren't very big to begin with and we only have about 10GB left on them.
I am wondering if we can setup a "linked clone" setup where each new VM is simply a linked clone from the base VM.
Would the linked clones allow us to have different IP's, computer names, software installs, etc? Or are we better off with the full clones?
A caveat is that each VM must "appear" from a remote user standpoint to be a fully dedicated machine as users log in to the VM's to do work. But they only work on their particular VM without seeing or otherwise knowing about all the other VM's.