Our devs want to use virtual computers for dev, but the sysadmins can't have server os's on the network. Is there a resource that talks about locking down the Virtual Computers so that they can
- Authenticate against AD
- Not have internet access
- Have settings and configuration be controlled by the sys admins, not the user
- Have intranet access to hit Visual Source Safe
Question #1: Are the requirements possible with a single configuration?
Question #2: What are some search terms to use to find out more?
Question #3: Is there a definitive resource / authority?
Scenario 1: SharePoint development requires Visual Stuido to be installed on the server directly. From there packages are rolled up and sent to a staging, then production server. The dev needs to be an admin on Win2k3, but no Internet access, but intranet access for the source control / backup solution would be good.
Scenario 2: GIS devs want to replicate bug reports on various workstation OSs (win2k, XP, Vista) and fix those bugs. They require access to Visual Source Safe, but don't need server operating systems. Internet access isn't crucial
Scenario 3: Web devs just want a platform to test the staging and public internet sites with more browsers and OS than are allowed in our baseline. These machines would require Internet access, but not Intranet access.