Hi, I want to setup an office network for a small software development company. The following is the list of servers/services that need to be set up: Domain Controller (using Windows Server 2008 R2) Team Foundation Server 2010 (which will also need SharePoint Services and SQL Server 2008 R2) Threat Management Gateway 2010 (TMG) Windows Server Update Service (WSUS) I have come to know that Team Foundation Server and Threat Management Gateway cannot be installed on a Domain Controller. So probably three separate servers will be required for Domain Controller, TFS/Share Point/SQL Server and TMG/WSUS. The following is the network diagram of this possible configuration. The total number of workstations will be less than 10 so the load on these servers will probably be quite low. I have following queries related to this configuration: Is this network configuration right? Will DHCP be provided by the router or should I set it up on Domain Controller? Where shall I set up the DNS service? Is it possible to virtualize one or more servers/services so that this all might be accommodated by just two servers, instead of three? For example, running Windows Server 2008 R2 with Hyper-V as Domain Controller and running TMG & WSUS in a virtual machine on it. Any help or suggestion is highly appreciated. Thank you.

1.) All but TMG looks right. You can ask them here if multi-homing TMG server is the correct method. http://social.technet.microsoft.com/Forums/en-us/Forefrontedgegeneral/threads 2.) I'd not use router. If on DC then see this article. http://technet.microsoft.com/en-us/library/dd145315(WS.10).aspx If you virtualize then better to do DHCP on a member server. 3.) You can setup DNS on the DC 4.) I don't see any reasons not to virtualize what you have here. Also ask them here. http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

Hi Jazzzz20, Thanks for posting here. Just to add Dave Patrick’s suggestions. About the Mulit-Homed TMG server, is supported, but we need careful about the DNS settings. The configuration depending on the situation you have, such as the server is a domain member server or not. For detailed information, please refer to the below Link: Planning for DNS name resolution for TMG http://technet.microsoft.com/en-us/library/cc995245.aspx In addition, I would never use a DC as a Hyper-v server in production environment. Always keep DC physical and separated from other tasks. However, it is recommended to install DNS on DC. You may consider installing Hyper-V role on other physical server, and place the DHCP role on the virtualized member server. I agree with Dave Patrick, for further virtualize questions, please post you question at Hyper-V forum. http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads Best Regards, Aiden