up vote -1 down vote favorite
share [g+] share [fb]

I think I labeled everything in the title. My setup is as follows. I have a Windows 2008 R2 server that only has 12GB of RAM available, I am unable to upgrade the RAM on this server. I need to be able to run at least the following.

Team Foundation Server - Source Control Exchange - Email

I understand that Exchange requires AD, so that is another requirement.

I currently have the following environment, but after some reading (and struggling to get my VMs onto the domain), I'm curious if I should be doing things differently.

Primary Partition contains Hyper-V DNS DHCP DC AD

VMs for each of TFS Exchange

Should I have setup the server differently? If not, any idea how to make the VMs join my domain? They can get an IP address statically and I can access the internet, but when I set them to DHCP they aren't given an IP address.

Edit - The machine is a dual xeon 2.66ghz Mac Pro running Boot Camp and Windows Server 2008 R2 as my base. I have the OS HD at 250GB, the HD to host the VMs (500GB) and then a data HD with 1.5 TB. Re: home server, this is actually a test bed for a business deployment, but I am trying to get the steps right here first. Hence the TFS, Exchange, AD requirements. My small business (software consulting) currently can't afford more hardware, so I need to test the install at home. Sorry for the mix up.

Edit Connectivity Issues - So I have been fiddling around enough to finally get the VMs to join the domain. However, I still can't access the VMs from non virtual, domain PCs. I have the following setup.

Developers (3) on the domain with laptops set to receive IP from DHCP. This is working great and I can ping the host server (but I can't ping any VMs) They all receive IP addresses in the DHCP range (.105 - .199)

The Host server has 2 NIC, .201 and .202 I am virtualizing .201 with the VMs and the VMs are now a part of the network. The VMs can ping the (.1**) machines, but the reverse is not true. The VMs (.210/.211/.212) can all ping the host (.202) and each other.

link|improve this question
Can you provide som additional details on the host? Processors, HD and RAID config – Dave M Oct 26 '11 at 19:48
1  
"home server" - Questions about home equipment are explicitly not allowed on SF. See the FAQ. You either have a problem with your Hyper-V Network configuration, or a hardware issue (especially common with cheap NIC chips, like Realtek). – Chris S♦ Oct 26 '11 at 19:58
@DaveM Really not sure how that info makes any difference for "VMs aren't getting an IP" – Chris S♦ Oct 26 '11 at 20:00
feedback

closed as off topic by Shane Madden, Chris S♦, mfinni, DJ Pon3, mailq Oct 26 '11 at 21:49

Questions on Server Fault are expected to generally relate to servers, networking, or desktop infrastructure, within the scope defined in the faq.

1 Answer

up vote 0 down vote

i suggest the following Main Host install HyperV - nothing else

VM1 ActiveDirectory VM with 2 Gig of ram -add DHCP to the server (not recommanded though)

VM2 TFS VM with 4 Gig of ram

VM3 Exchange (if you must ?!) vm with 4 gig of ram

since your tight on resources you can use a free mail solution that is very low on resource usage i have setup a small production (25 users) environment for TFS2010 using MailEnable for email services and the clients don't even notice the difference.

mailenable can run on almost nothing (256MB would be enough for it) that way you can save those 4 gigs of ram and the CPU power you would waste on exchange.

if you got issues with network connectivity please explain in depth.

hope this helps

link|improve this answer
This is great advice, thanks! As far as DHCP, if I need DHCP is that the only place it makes sense to put that feature? How about the domain controller? I will add more info regarding my connectivity issues above. – firetoast Oct 26 '11 at 21:12
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.