I have a beefy server (dual Xenon & 16GB RAM with RAID5) I use as the domain controller and file server for an office network on a dedicated internet connection.
I also have a guest network with wifi access and a few public workstations for guests to use with its own dedicated internet connection.
The guest computers are not centrally managed, but I would like to change that and set up the guest network with its own domain, but still keep it completely segregated from the office network.
I plan on using the guest network's server for locking down the workstations with GPO, deploying new images to workstations, and managing deep freeze on the guest workstations.
There were two options I was considering:
1) Set up Server 2008 on a desktop workstation (Dell Optiplex 330) with a RAID mirror and put it on the guest network. While this is simple and straight-forward and ensures that the two networks are kept seperate, I'm a little hesitant to do this since it is not a very robust solution because of the possibility of a hardware failure (but if there is a failure, I have a spare Optiplex 330 I could use for spare parts or to restore a backup to).
2) Install a new physical intel 10/100/1000 NIC in the office server and set up a seperate VLAN on the office network switches that connects the NIC to the guest network. Then, set up a Hyper-V virtual machine with Server 2008 to manage the guest network. While this solution would be robust, I'm hesitant to this since this solution uses the office network's switch's resources and because of security concerns in how to make the office resources on the server inaccessible from the guest network.
Which approach might you consider, or do you have additional suggestions for either (or additional) solutions?