Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As a follow up question to How Do i host multiple servers on HyperV with only a few public IP Addresses I am now trying to figure out where to put the ISA/TMG Server? Should it be virtualized, listening on an External IP and sending data between an internal network, or should it be hosted on the host partition? The last time i played with ISA/TMG, it was a physical box, and there where other machines in behind, so it makes me think the virtual option. Give it 2 public IPs, and let it sort out the rest... give 1 IP to the box itself for managment... Which way should it work?

share|improve this question
up vote 1 down vote accepted

TMG as a VM works well, and there us a technet video that describes various scenarios using TMG, just google "Virtualize your ISA or Forefront TMG servers". As always in these things, there is best practice, good practice, and stupid .

Best practice as espoused by the vid is to have your virtualised TMGs on hardware that's specifically used for perimeter duties. Obviously this won't work if you've only got one server. However, segmenting your network as recommended by the vid is easily doable in a single server scenario, so long as you have at least 3 physical network connections.

  1. One will become a virtual/physical network (i.e. virtual with external access) connecting the VM TMG to the internet (or your gateway router) - this must not be used for hardware management. In hyper V settings I name this network 'black' because it is unsafe and leads to the big outside.

  2. One will be a virtual network (i.e. no external access) connecting the VM TMG to your target VMs - again, not used for hardware management. I name this network 'blue' because it is notionally safe and it links all the VMs together.

  3. One is a physical network (not used at all by Hyper V) purely used for the hardware management lan. I name this 'management' and best practice is to keep it and the host off the internet, or only go onto the internet from the host for updates.

Logically it looks like this:

TMG as hyper V

So, when you assign virtual network interfaces to your VMs, the TMG VM gets given two (black and blue) and all the other VMs get given just blue.

It's pretty straightforward, the main complexity is what you will encounter anyway when trying to understand how Hyper V allows you to co-opt network connections as 'virtual switches'. I've setup the same above with a 'black' network and 'blue' network spanning a multi-server cluster and found it works brilliantly. The basic leap of faith is that you have to trust that a nasty on the black network can't leap over via the host to the blue network. Hyper V has been EAL4+ rated for security anyway, so it's fair to say that it's improbable, unless your host is drastically compromised.

share|improve this answer
Ok, so if i read that correctly (i will need to watch the video when i get home from work) one of my IPs will be assigned to the HyperV host as my "managment" IP (remote desktop, SSH only probably) and the 2 others will be given to the TMG box. they will be bridged connections. then the TMG VM will have at least 3 NICs (2 public, at least one internal). Am i right? – TiernanO Nov 7 '11 at 11:56
You're right about the management IP (remote desktop etc.) – Mark Lawrence Nov 7 '11 at 12:07
Cool. will try that out so! thanks! – TiernanO Nov 7 '11 at 12:17
You're right about the hyper V host having one NIC assigned as a management IP (remote desktop, ssh is best). In HV manager make a NIC a virtual switch (i.e. blue network) and add your webhost VMs (IPs in a private range say 192.168.1.x) to this virtual network. Take another NIC and give it an physical address in the range of your gateway/public IP address. In HV Manager turn this into a virtual switch, click the 'has external access' option and give that the name 'black network'. Configure your TMG VM with 2 adapters, one that links to black and one that links to blue. – Mark Lawrence Nov 7 '11 at 12:20

I would probably make it a VM so that if you get another host you have HA for the service.

share|improve this answer
how do you mean? Do you mean i would have a Virtual TMG on both servers, and load use NLB to "share" a single front facing IP address? This would then mean both servers would need to "share" the VMs since if one Dedicated box goes down, i would need to move VMs over... also, it meas i would need a lot more hardware... Think this is out of scope for what i want currently, but still a valid answer! thanks. – TiernanO Nov 7 '11 at 10:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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