Service pack 3 for Forefront Unified Access Gateway 2010 (UAG) is out and is available for download.
You can even find installation guidelines here (NLB in my case).
However what is not mentioned in the installation procedure are several kludges you're going to face during the process.
The very first one is you have to run downloaded UAG-KB2744025-v4.0.3123.10000-ENU.msp as an Administrator. Windows Explorer does not offer this option for you by default, because the file is msp, not some kind of exe. Even worse setup starts without "run administrator"and fails with the error 1603:
![]()
Luckily this is the same error you saw during SP2 installation (for the same very reason).
The workaround was to run msp installation from elevated (Run as Administrator) CMD window.
The same trick works here also.
After you install SP3 and activate configuration as instructed you'd better check Forefront services.
In my case DNS64 service (on both array servers) was in Manual startup mode and Stopped state. And if you have some resources within your corpnet with IPv4 addresses, where DNS64/NAT64 is required you need this to be running. I have also experienced the same problem with SP2 and it was explained here.
You can even find installation guidelines here (NLB in my case).
However what is not mentioned in the installation procedure are several kludges you're going to face during the process.
The very first one is you have to run downloaded UAG-KB2744025-v4.0.3123.10000-ENU.msp as an Administrator. Windows Explorer does not offer this option for you by default, because the file is msp, not some kind of exe. Even worse setup starts without "run administrator"and fails with the error 1603:
Luckily this is the same error you saw during SP2 installation (for the same very reason).
The workaround was to run msp installation from elevated (Run as Administrator) CMD window.
The same trick works here also.
After you install SP3 and activate configuration as instructed you'd better check Forefront services.
In my case DNS64 service (on both array servers) was in Manual startup mode and Stopped state. And if you have some resources within your corpnet with IPv4 addresses, where DNS64/NAT64 is required you need this to be running. I have also experienced the same problem with SP2 and it was explained here.