If you have seen my inquiry on another board, please forgive this cross-posting. I am seeking as broad an audience within the Exchange 2007 SP1 community as possible in seeking an answer to my inquiry.
Our organization currently has a single-forest, single-domain Active Directory infrastructure that is entirely located within a single AD site. We use Exchange 2003 in a front-end/back-end configuration and use an Ironmail appliance as an external SMTP gateway.
We are in the process of introducing Exchange 2007 SP1 to our infrastructure and have successfully ran all of the PrepareAD processes successfully. We have built our 64-bit Windows Server 2008 servers and have them ready for Exchange 2007 SP1.
Our desired high-availability configuration is to use four servers for our Exchange 2007 infrastructure. Two of these servers will connect to shared storage and serve as a two-node single-copy (SCC) mailbox cluster.
The other two servers will each have both the Hub Transport (HT) and Client-Access (CAS) roles installed on them. Our existing Ironmail appliance will continue to serve as our external SMTP gateway, in lieu of an Edge Transport server.
I understand that by design, having multiple HT servers provides redundancy and using load-balancing is not required (nor supported for internal connectors). However, we want to load-balance the CAS role only on the two servers, using Windows Load Balance Service (WLBS).
Have any of you successfully load-balanced CAS using WLBS on servers that also have the HT role installed on them. If so, how did you configure WLBS, in terms of port rules? Is there any specific guidance that you would offer or lessons learned in how you were able to get it to work?
Also, are there any specific additional connectors (either send, receive or both) that need to be set up to allow HT to work normally and skirt the CAS load balancer?
Thanks in advance for any guidance any of you are able to provide. I hope soon to be in the position of offering similar guidance to the next person to come along with a similar issue.