This page tracks all updates to all supported versions of:

• Microsoft Forefront Protection 2010 for Exchange Server
• Forefront Protection 2010 for SharePoint
• Microsoft Forefront Client Security
• Microsoft Forefront Security for Exchange Server
• Forefront Security for SharePoint
• Forefront Server Security Management Console
• Forefront Security for Office Communications Server
• Antigen 9.0 for Exchange
• Antigen 8.0 for Microsoft SharePoint Portal Server
• Forefront Threat Management Gateway 2010
• ISA Server 2006
• Forefront Unified Access Gateway 2010
• Intelligent Application Gateway 2007

http://technet.microsoft.com/en-us/forefront/ff899332.aspx

This error appears if you have extended the schema for Exchange 2007 SP3, because the schema version for SP3 is higher than the one for Exchange 2010 RTM.

Luckily Exchange 2010 SP1 has been released. SP1 introduces a higher schema version that 2007 SP3 and thus solves the problem.

Below an overview of the Exchange versions and which schema version they use:

Release notes

Download here

In Exchange 2010 SP1, ISInteg is no longer a standalone program.

The functionality provided by the ISInteg tool has been rolled into two new Exchange Management Shell cmdlets:

• New-MailboxRepairRequest
• New-PublicFolderDatabaseRepairRequest

Note: Like other Shell cmdlets, these are subject to Role-Based Access Control (RBAC) scoping restrictions. For details, see Understanding Management Role Scopes.

Cool Features

These new ISInteg cmdlets come with some cool new functionality!

• The cmdlets work with the database mounted. It’s no longer required to unmount the database to perform an integrity check or fix database errors.
• You can repair logical corruption at the mailbox level.
• You can fix corrupt search folders.
• You can fix the Provisional Fid.
• You can fix Aggregate Counts.

ISInteg can now work at the database or mailbox level

How does it do that? Well, the new schema in Exchange 2010 effectively partitions the database by mailbox. So the top problems fixed by ISInteg are now mostly limited to the affected mailboxes only. Previous versions of ISInteg required the database to be offline while validation and fixing are in progress. In Exchange 2010 SP1, the ability to do these checks at the mailbox level removes the need to dismount the database. It is actually required to have ISInteg operate against an online database!

New-MailboxRepairRequest

The New-MailboxRepairRequest cmdlet detects and fixes the following types of mailbox corruptions:

• Search folder corruptions (SearchFolder): Repair tasks now look for all folders named in ptagSearchBacklinks, ptagSearchFIDs, and ptagRecursiveSearchFIDs and verifies that each folder exists. If the folder no longer exists, then it will remove that folder from the list.
• Aggregate counts on folders that aren’t reflecting correct values (AggregateCounts): Repair tasks tally all messages in a folder and keep a running total of various counts and sizes. Once the iteration is complete, it will verify the computed counts against the persisted counts on the Folders table record for the folder. If there is a discrepancy, it will update the persisted counts to reflect the computed counts.
• Views on folders that aren’t returning correct contents (FolderView): Repair tasks will iterate over all views for a folder and for each one, bring the view fully up to date and then reconstruct a temp copy. If there is a discrepancy between the existing view and the contents of the temp table, it will delete the view so it can be rebuilt from scratch the next time it is requested.
• Provisioned folders that are incorrectly pointing into unprovisioned parent folders (ProvisionedFolder): Repair tasks can fix Provisioned folders incorrectly pointing into unprovisioned parents or vice versa.

Syntax

New-MailboxRepairRequest -Mailbox <MailboxIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Archive <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

New-MailboxRepairRequest -Database <DatabaseIdParameter> -CorruptionType <MailboxStoreCorruptionType[]> [-Confirm [<SwitchParameter>]] [-DetectOnly <SwitchParameter>] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]]

Parameters

• Only 1 active repair task is permitted to be running per server if the active task is a database level repair.
• Only 100 mailbox level active repair tasks are permitted to be running at once per server.
• There is no -Server parameter to do all databases or mailboxes on a server.
• The repair task dies on database dismount or store stop/crash.
• The only way to stop a repair is to stop the store or dismount the database.
• Mailbox access will be disrupted for the mailbox that is being repaired.
• Repair for a mailbox will skip a mailbox if it has been quarantined.
• Repair will cause a move-mailbox operation to be delayed until the repair is finished

Source: http://msexchangeteam.com/archive/2010/08/23/455899.aspx

Enterprise IT organizations, including the Microsoft Information Technology (Microsoft IT) group, deal with service level agreements (SLAs) and power users accustomed to high levels of performance, availability, and responsiveness. The 180,000-plus users at Microsoft send over 15 million internal e-mail messages a day from more than 150 offices worldwide, as well as from home and while on the road. At Microsoft, many business-critical communication processes depend on the availability of messaging services provided through Microsoft® Exchange Server 2010.

Managing the complex Microsoft IT infrastructure is a team effort that involves many different groups, such as the Datacenter team, the Network Infrastructure team, the Active Directory® team, and the Exchange Messaging team. Overall, Microsoft IT manages two distinct environments: a pre-release production environment to test new product versions and upgrades prior to their release to manufacturing (RTM) and a corporate production environment to provide IT services to Microsoft users. Within these environments, the Microsoft IT Exchange Messaging team handles all Exchange-related operation, management, administration, and process optimization. In that role, the Exchange Messaging team works with many other peer teams at Microsoft IT, sharing its operations and process optimization expertise to help those teams implement efficient and reliable operations processes.

The Messaging Operations group within the Exchange Management team must meet several reliability, availability, and performance targets (such as 99.99 percent availability of Exchange services). To meet these targets, the Messaging Operations group makes use of industry-standard methodologies such as Microsoft Operations Framework (MOF), Microsoft Solutions Framework (MSF), and Information Technology Infrastructure Library (ITIL). For example, the operations model that the Messaging Operations group implemented based on the ITIL framework relies on structured incident management, problem handling, configuration management, and change control processes. These processes enable the Messaging Operations group to capitalize on Exchange Server 2010 administrative features, such as the Exchange Management Console (EMC), to reduce operations costs and ensure efficiencies.

The key to success in daily operations is the right combination of technology, people, and processes. For example, the Messaging Operations group uses technical tools, such as the built-in product features of Exchange Server 2010 and Microsoft System Center Operations Manager, combined with a clear team structure and work processes that facilitate collaboration. Built-in product features of Exchange Server 2010, such as Database Availability Groups (DAGs), help the Messaging Operations group meet 99.99 percent availability and performance targets. New tools and software features, and optimization opportunities gained through customer feedback, enable the Messaging Operations group to analyze and implement changes when necessary to keep pace with the innovative and agile business landscape at Microsoft.

This white paper is for business decision makers, technical decision makers, and operations managers. It assumes that the reader has a working knowledge of Microsoft Windows Server® 2008, Active Directory, Exchange Server 2010, and Microsoft System Center Operations Manager. Because many of the principles and procedures discussed in this paper are based on standard operations methodologies, a high-level understanding of the MOF, MSF, and ITIL models is also helpful.

http://technet.microsoft.com/en-us/library/ff934521.aspx

Supported Products

• Forefront Protection 2010 for Exchange Server
• Forefront Protection 2010 for SharePoint

Configuration Management and Reporting

• Capture server configuration snapshots and push snapshots to any number of servers
• Compare configuration of any number of servers or baselines
• Obtain statistics from one or many servers, including information about infected files, detected malware, server health, and more
• See summary and/or server detail views

Ease of Use

• Discover Forefront Protection Servers and export information to a .CSV file
• Use customizable Windows PowerShell™ scripts to enhance your existing automation

Full documentation here

Download here

** July 26, 2010 Update **:  There have been several reports of problems (failure of the Front End Service to start) after applying the CU6 updates on the server. Consider holding off applying this update until more information is known.  It is important to install the CU 6 update to the back end database role first (see Description of the cumulative update package for Office Communications Server 2007 R2 database: July, 2010).  So far, the problems appear to be related to this, but more information to come.

Client Updates

Communicator 2007 R2:

• The July, 2010 update for Communicator 2007 R2 can be found here:  Description of the cumulative update package for Communicator 2007 R2: July 2010. This update brings the Communicator version up to 3.5.6907.206 from the last update in April 2010 (3.5.6907.196).
• Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.
• The update can be downloaded here.

Communicator 2007 R2 Phone Edition:

• The July, 2010 update for Communicator 2007 R2 can be found here: http://support.microsoft.com/kb/2267962/.
• The update can be downloaded here.

Communicator 2007 R2 Mobile:

• This was update was released about 2 weeks ago, but the knowledge base article has been updated. The description can be found here: http://support.microsoft.com/kb/969816.
• You can download the Smartphone update here.
• You can download the Pocket PC packager here.

OCS 2007 R2 Group Chat Client:

• The July 2010 update can be found here: Description of the update for Office Communications Server 2007 R2 Group Chat Client: July 2010.
• The update can be downloaded here.

Server Updates

OCS 2007 R2 Server:

• Note: the update for the SE/EE Back End Database is here: Description of the cumulative update package for Office Communications Server 2007 R2 database: July, 2010.  This update (OCS2009-DBUpgrade.msi) SHOULD BE RUN FIRST.
• All of the Cumulative 6 server updates can be found here: Updates for Communications Server 2007 R2.
• The updates can be downloaded here.
• It looks like the update includes new hotfixes for the following server roles: Audio/Video Conferencing, Web Conferencing Server, Core Components, Communicator Web Access, Conferencing Attendant, Standard/Enterprise edition Server Back End, and the UCMA Managed API 2.0 Core Redist 64-bit.
• Note: the links to the knowledge base article for the individual fixes do not work right now, or not ready yet, on the Microsoft support site.

OCS 2007 R2 Group Chat Server:

• The Cumulative 6 updates for the Group Chat Server can be found here: Update package for Office Communications Server 2007 R2 Group Chat Server: July 2010.
• The Group Chat Server update can be downloaded here.

OCS 2007 R2 Group Chat Admin Tool:

• The update can be found here: Description of the update for the Office Communications Server 2007 R2 Group Chat Administration Tool: July 2010.
• The update can be downloaded here.

This white paper provides information about publishing Microsoft Exchange Server 2010 using Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010, including how to choose between them for different scenarios, and provides specific steps you can take to configure Forefront TMG and Forefront UAG to publish Exchange 2010.

Download the whitepaper here