There is a XMas package for you that use TMG 2010…hey and for you that use ISA Server 2006 too
Today we are making publicly available the Software Update 1 Rollup 2 for Forefront Threat Management Gateway (TMG) 2010 Service Pack 1 . This hotfix include resolution for the following issues:
article |
Title |
2452980 (https://support.microsoft.com/kb/2452980) |
Upload speed through Forefront TMG 2010 is very slow on a high speed Internet connection |
2478286 (https://support.microsoft.com/kb/2478286) |
Connection does not time out after inactivity time elapses in an OWA 2010 client connected to Exchange Server 2010 if published by using Forefront TMG 2010 |
2484988 (https://support.microsoft.com/kb/2484988) |
A DNS server publishing rule stops working for a DNS server that is published by using Forefront TMG 2010 |
2478297 (https://support.microsoft.com/kb/2478297) |
User Activity reports that are created by Forefront TMG 2010 show a wrong value in the reported data range |
Notice that the first issue on this KB is the same that we were discussing on this TechNet thread here. So if you are facing such issue, make sure to install this update and run the script from KB2452980 (https://support.microsoft.com/kb/2452980). The other issue that we address on this rollup was raised from one of my customers as a problem, working with him I was able to reproduce the issue and after a long investigation we were able to find the root cause of the problem (in a great partnership with Exchange Team and TMG Developers), read KB2478286 (https://support.microsoft.com/kb/2478286) for more details. The third issue that we address on this TMG rollup is a DNS publication that stops to work, see KB2484988 (https://support.microsoft.com/kb/2484988) for more details. Last but not least a problem on the user activity report, simple stuff but that bothers for sure; see KB2478297 (https://support.microsoft.com/kb/2478297) for more details.
For ISA Server we are releasing the ISA Server 2006 hotfix package: December 2010 , which includes the following updates:
KB article |
Title |
2478307 (https://support.microsoft.com/kb/2478307) |
MAPI client does not connect to an Exchange server on an internal network through an ISA Server 2006-based VPN connection on a computer that is running Windows 7 |
2481980 (https://support.microsoft.com/kb/2481980) |
Unexpected authentication prompts while you use an OWA website that is published by using ISA Server 2006 SP1 if RSA authentication and FBA are used |
Go get it and enjoy your holidays.
Merry XMas !!
Comments
Anonymous
January 01, 2003
Hello Petter, I understand the terminology is really broad and the best way to determine if you need this or not is really on monitoring standpoint. Read the thread social.technet.microsoft.com/.../3871606b-6547-48dd-a79d-053bba72067b and there you will see what this is refering to. HTH, Yuri DiogenesAnonymous
January 01, 2003
Hi buddy!, have a greate Xmas! Is it mandatory to have the rollup 1 before installing this one? Hugs!Anonymous
January 01, 2003
Hi Uilson, No, you don't need to have Rollup 1, here are the pre reqs: To install this update, you must be running Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1 (SP1). Additionally, you must have Software Update 1 for Forefront TMG 2010 SP1 installed. Merry Xmas :)Anonymous
January 01, 2003
Hello Chat, as we discussed by email looks like you were able to apply the fix.Anonymous
January 01, 2003
Hi Christopher, The name changed, Updated 2 is now called Rollup 1 and this is the Rollup 2. IOW, if you already installed former Update 2 (now Rollup 1) you just need to install Rollup 2 on top of that. Happy new year to you too.Anonymous
January 02, 2011
What if we have Update 2 already? I guess we should still install this update. Just wanted to clarify as it says Rollup2 for TMG 2010 SP1 Update 1. Happy New Year :)Anonymous
January 13, 2011
The comment has been removedAnonymous
January 17, 2011
I've deployed both Rollup 1 and 2 and only have the issue when I'm using WNLB, I've tried using the script included but get an error that it can't be compiled. Has anyone gotten the script to work when copied from the kb? Am I missing something?