Updating uag array member
You can load balance traffic across multiple Forefront Unified Access Gateway (UAG) array servers using a hardware load balancer or by using the Windows network load balancing (NLB) feature that is integrated into Forefront UAG.This topic describes the following steps that are required for configuring integrated NLB: If you do not enable the setting, no warning is issued, but the behavior of the server after configuring NLB may be unpredictable.Open UAG and select the Network Settings Then we have to define the Topology: Select the node as Array Member and specify credentials Before you join the 2nd node as the array member, open the TMG console and add the 2nd server to the “Managed Server Computers” group. Open the UAG console on the 2nd server and join him to the array TIP: If the UAG services on the 2nd node don’t start, copy the content of folder C:\Program Files\Microsoft Forefront Unified Access Gateway\von\Conf from the manager to the member server. Now we have to configure the NLB from the UAG console.Open Network Load Balancing from the Admin menu and add the first VIP IP: Next you have to save and activate the configuration.
If multiple DIPs were previously configured, only one will remain after you configure NLB; the rest will be deleted.
One of the major new features in this UAG release is ‘array’.
An UAG array is a set of machines that share the same configuration (trunks, applications, etc.) and is managed as a unit.
Connecting to different network switches for network redundancy is supported, providing that both are defined as part of the internal or external network.
Using Forefront TMG running on the Forefront UAG server to provide multiple network routing is not supported.