TheGeezer2010
asked on
Forefront TMG 2010 DR between two physical sites and two DMZs
Hi All
Looking at implemneting DR for Forefront TMG 2010 Enterprise. This needs to be between two physical sites (same domain) both of which the TMG will be located inside a separate DMZ - theat is 2 x sites, 1 x domain, 2 x DMZ.
I believe using EMS (1 at each site for DR purposes), can set up an Enterprise EMS with two separate arrays ? But how is the synchronization managed between the TMGs in different DMZs ?
Other option is use DNS round-robin. If so, would it be best to use two separate stand-alone TMGs and sync manually the policies/rules, or again, set up an EMS or stand-alone array ?
Confused and any help welcomed - especially if any articles on best practice in this scenario.
Looking at implemneting DR for Forefront TMG 2010 Enterprise. This needs to be between two physical sites (same domain) both of which the TMG will be located inside a separate DMZ - theat is 2 x sites, 1 x domain, 2 x DMZ.
I believe using EMS (1 at each site for DR purposes), can set up an Enterprise EMS with two separate arrays ? But how is the synchronization managed between the TMGs in different DMZs ?
Other option is use DNS round-robin. If so, would it be best to use two separate stand-alone TMGs and sync manually the policies/rules, or again, set up an EMS or stand-alone array ?
Confused and any help welcomed - especially if any articles on best practice in this scenario.
pwindell
If done with an Array that would require 5 nics in each TMG. That can become a lot of complexity to try to deal with,...and Arryas can be a "handful" already to begin with. I'm not saying it can't be done,...I'm saying that you need to consider the complexity of what monster you may create.
ASKER
Turns out cannot do an array as only have Standard version of TMG. I have manually exported/imported the rules, listeners and farms - these will not change at all due to the nature of the solution so manual process is acceptable. Will now test Round Robin DNS to see the effect on the iPhones. Will advise outcome.
ASKER
Testing round-robin tomorrow.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Final issue was that users with iPhones IOS between 4.21 and 4.24 were getting prompted for cert when connecting to other TMG. This is because Apple changed to using per host authentication instead of per cert. Resolved this by upgrading to latest version of IOS which uses per cert.
Ok.
Very good.
Very good.
ASKER
Self-resolved