TMG 2010 and UAG 2010 SP1 Fully Supported on Windows 2008 R2 SP1

Microsoft Windows 2008 Server R2 SP1 contains changes that are focused on supporting new types of hardware, adding support for several emerging standards, and addressing specific reliability, performance, and compatibility issues.TMG 2010 SP1 and UAG 2010 SP1 are fully compliant with the new Windows SP. "We've successfully tested both TMG and UAG scenarios after the […]

Microsoft Windows 2008 Server R2 SP1 contains changes that are focused on supporting new types of hardware, adding support for several emerging standards, and addressing specific reliability, performance, and compatibility issues.

TMG 2010 SP1 and UAG 2010 SP1 are fully compliant with the new Windows SP. "We've successfully tested both TMG and UAG scenarios after the upgrade to new Windows SP. Moreover, installing TMG/UAG on WS2008 R2 SP1 machine is also supported,' stated Microsoft TMG team blog.

When upgrading gateway machine to Windows 2008 R2 SP1, restart will be required. After installation, the TMG/UAG services restart automatically. Microsoft suggest upgrading TMG SP1 in the following order:

  1. Enterprise Management Servers (master and replicas -- only for TMG deployments).
  2. Array managers.
  3. Array members.

"For deployments with NLB enabled, we encountered one issue:

After upgrading to Windows 2008 R2 SP1, creating new NLB cluster using the administration console may fail.
Machine network interface of the newly load balanced network will become disabled.

As a workaround, it's suggested to reboot the TMG/UAG machines after SP1 installation once again. This will ensure that setting up new NLB cluster after Windows upgrade will succeed," explains Microsoft.

SP1 changed areas relevant to TMG/UAG products are below:

ws 2008 r2 sp1 and tmg/uag changes

[Source]