All versions for ISA Server 200x and Forefront TMG 2010 contain the following changes: Introduced support for applying multiple quota rules to the same connection. This enables more complex and flexible configurations. For example, it allows to simultaneously apply daily, weekly, montly quotas to the same client. Another example is simultaneously applying per-user and group quotas. In future, when we add more options to quota rule settings (such as schedule, destinations, protocols), it will allow even more flexible configurations. In order to enable support for this feature, just 2 options were added in quota rule settings. By default they are unchecked, which means that after you upgrade to this version, the behaviour of your existing rules remains the same as before, until you change those new options. Note that this new functionality means that single client may now have multiple quota counters, one for each applied quota rule. Bandwidth Monitor client utility shows only the counter of the first applied quota rule. But clients can see all of their quota counters via web statistics interface. In this version only the first applied quota rule is collected for bandwidth usage reports. We plan to correct it in the next version. A numerous other minor fixes, improvements, and optimizations.
All versions for ISA Server 200x and Forefront TMG 2010 contain the following changes: Improved performance that should result in reduced processor usage. Improved connection handling to prevent possible bottlenecks under heavy load. Updated bandwidth usage reports service and web application. Now they use .NET Framework 2.0 and support installation on 64-bit Windows systems. If maximum database size is reached when adding banwdidth usage stats or creating reports, oldest stats are deleted to allow insertion of new data. (SQL Server Express limit is 4 GB per database, MSDE limit is 2 GB per database.) Bandwidth Splitter Monitoring could show incorrect client computer names if clients use DHCP and their IP addresses change frequently. It happenned because of using cached DNS results. Fixed.
Changes specific to Bandwidth Splitter for Forefront TMG 2010: TMG Management console could crash at startup on Windows Server 2008 R2 and Windows 7 if Bandwidth Splitter controls were selected last time you closed the console. Fixed. Adding Windows Firewall rule on Windows Server 2008 R2 to allow connections to Bandwidth Splitter service from remote computers to enable intra-array synchronization of Bandwidth Splitter activity, and also to enable monitoring using remote TMG Management console. Corrected documentation on configuring bandwidth usage reports (clarified configuration with SQL Server Express). 1e1e36bf2d