Microsoft has released an update that is dated December 2009. This update fixes issues in the following components in Microsoft Solution for Hosted Messaging and Collaboration 4.5.

• Exchange 2007 Resource Manager Namespace
• Exchange 2007 Resource Manager Web Services
• Hosted Email 2007 Namespace
• Hosted Email 2007 Web Services
• Managed Email 2007 Namespace
• Managed Email 2007 Web Services
• Exchange 2007 Mobility Provider
• Exchange 2007 Provider
• Unified Messaging 2007 Provider

Additionally, this update also includes native 64-bit versions of the following components:

• Categorizer Override Agent
• SMTP Domain Cache Task

• The issues that the update rollup fixes.
• The prerequisites for installing the update rollup.
• Whether you must restart the computer after you install the update rollup.
• Whether the update rollup is replaced by any other update rollup.
• Whether you must make any registry changes.
• The files that the update rollup contains.

Issues that the update rollup fixes

This update rollup fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• When a folder is created, the value of folder allocation is not consistent with StorageQuota calculation result.
• When a public folder is created by using the “-StorageQuota” and “-postStorageQuota”, the operation fail.This is because the two parameters was replaced by the parameters “–IssueWarningQuota” and “–ProhibitPostQuota” in the Exchange SP2.
• An overflow exception occurs when allocating 2Terra bytes or above mailbox space to an organization. This is because the maximum mailbox space that can be allocated to an organization lower than 2Terra bytes.
• If an organization allocated a "not shared" mailstore, it cannot reallocate on the same mailstore.

This update rollup includes the following fixes that were released:

Update rollup information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

• Hosted Messaging and Collaboration version 4.5 must be installed before you apply this update.
• The logon user should be a member of the Domain Admins Group.
• The HMC Deployment Tool must be installed on the first Microsoft Provisioning Server (MPS) Engine server.
• Microsoft Exchange Server 2007 Service Pack 2 must be installed before you apply this update.

Restart requirement

You do not have to restart the computer after you apply this update rollup. But you have to restart the Provisioning Engine on each MPS server, restart Internet Information Services (IIS) on each Web Services server, and restart the Exchange Transport service on all Exchange Hub Transport servers.

Hotfix replacement information

This rollup replaces the previously released RU1, RU2, RU3, RU4 and RU5.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Installation information

To deploy the hotfix follw these Deployment steps:

1. Disable and shut down the provisioning engine on all MPS engine servers (MPS0n).
2. Log on to the first MPS server (MPS01) as a member of the Domain Admins Group.
3. Start the MPS Deployment Tool, and then uninstall the following components.
   • Exchange 2007 Resource Manager
   • Exchange 2007 Resource Manager Web Service
   • Exchange 2007 Hosted Email
   • Hosted Email 2007 Web Service
   • Exchange 2007 Managed Email
   • Managed Email 2007 Web Service
   • Exchange 2007 Mobility Provider
   • Exchange 2007 Provider
   • Exchange 2007 Unified Messaging Provider
   If you have not previously installed Update Rollup 5, you must also uninstall the following components:
   • Active Directory Provider
   • BlockRMO Provider
   • CoreRMO Provider
   • File System Provider
   • DNS Provider
   • Exchange 2007 OAB Resource Manager Namespace
   • Exchange 2007 OAB Resource Manager Web Service
   • Hosted Active Directory Namespace
   • Hosted Active Directory Web Service
   • Managed Unified Messaging 2007 Namespace
   • Managed AD Namespace
   • Managed Active Directory Web Service
   • Hosted SharePoint 2007 Web Service
   • Hosted SharePoint 2007 Namespace
   • Exchange 2007 Mobility Provider
4. Extract the QFE Rollup pack on the MPS server to a temporary location. For example, extract it to the following location:
   C:\temp\QFERollupPackage
5. After backing up the existing files, copy the following MSI files from the C:\temp\QFERollupPackage folder to the C:\MSIShare\ folder:
   • Exchange2007ResourceManagerNS.msi
   • Exchange2007ResourceManagerWS.msi
   • HostedEmail2007NS.msi
   • HostedEmail2007WS.msi
   • ManagedEmail2007NS.msi
   • ManagedEmail2007WS.msi
   • Exchange2007MobilityProvider.msi
   • Exchange2007Provider.msi
   • UnifiedMessaging2007Provider.msi
   If you have not previously installed Update Rollup 5, you must also backup and replace the following files:
   • ActiveDirectoryProvider.msi
   • BlockRMOProvider.msi
   • CoreRMOProvider.msi
   • FileSystemProvider.msi
   • DNSProvider.msi
   • Exchange2007OabResourceManagerNS.msi
   • Exchange2007OabResourceManagerWS.msi
   • HostedActiveDirectoryNS.msi
   • HostedActiveDirectoryWS.msi
   • ManagedUnifiedMessaging2007NS.msi
   • UnifiedMessaging2007Provider.msi
   • ManagedADNS.msi
   • ManagedActiveDirectoryWS.msi
   • HostedSharePoint2007WS.msi
   • HostedSharePoint2007NS.msi
   • Exchange2007MobilityProvider.msi
6. Use the Deployment Tool to reinstall these components on the MPS Engine Server.
7. Restart the Provisioning Engine on each MPS server. To do this, follow these steps:
   1. On the MPS Engine servers, start Component Services.
   2. Expand Component Services, expand Computers, and then expand My Computer.
   3. Click COM+ Applications.
   4. Right-click Provisioning Engine, click Enable, and then click Start.
8. In the Deployment Tool, expand Hosted Exchange, expand Exchange Provisioning Configuration, right-click the following nodes, and then execute the Initialize commands:
   • Hosted Active Directory
   • Managed Email 2007
   • Exchange 2007 OAB Resource Manager
   • Hosted Email 2007
   • Exchange 2007 Resource Manager
   • Hosted SharePoint
9. Click Start Deployment.
10. On each Web Services server, restart Internet Information Services (IIS).
    Important If you have previously installed Update Rollup 5, your installation of Upgrade Rollup 6 is now finished. If you have not previously installed Update Rollup 5, you must also complete steps 11 through 17.
11. Log on to PROV01 as the Domain Administrator, and then follow these steps:
    1. Back up any files that you have customized in the following folder:
       %Program Files%\Microsoft Hosting\Provisioning\RPCHTTPConfig
    2. Use Add or Remove Programs to remove the RPCHttpConfigTool, and then install the version from the update.
    3. Reapply your customizations.
    4. Follow the instructions in the "Deploy the RPC over HTTP Client Configuration Web Site" section in the RTM HMC 4.5 Deployment guide to install the RPCHttpConfigTool.msi component.
    For more information about how to deploy the RPC over the HTTP Client Configuration Web site, visit the following Microsoft Web site:
    
    How to deploy the RPC over the HTTP Client Configuration Web site (http://technet.microsoft.com/en-us/library/cc501357.aspx)
12. On OMSQL01, copy the Pwdb40ssis.msi file from the update, and then run it two times to remove the earlier version and to install the new one.
    Follow the instructions in the "Create the Performance Warehouse Database" section of the RTM HMC 4.5 Deployment guide to install the pwdb40ssis.msi component. For more information about how to create the Performance Warehouse Database, visit the following Microsoft Web site:
    
    How to create the Performance Warehouse Database (http://technet.microsoft.com/en-us/library/cc501397.aspx)
13. Run the DNSClient.msi from the update two times to remove the earlier version and to install the new one. Follow the instructions in the "Deploy the MPS DNS Client" section in the RTM HMC 4.5 Deployment guide to install the DNSClient.msi component. For more information about how to deploy the MPS DNS Client, visit the following Microsoft Web site:
    
    How to deploy the MPS DNS Client, (http://technet.microsoft.com/en-us/library/cc501405.aspx)
14. Install and then configure the Out of Office (OOF) agent that includes the following two utilities:
    • Categorizer Override Agent: This is a transport agent that overrides the categorizer behavior on the Hub Transport servers.
    • SMTP Domain Cache Task: This is a scheduled task that generates cache files so that the categorizer override agent can filter the OOF messages.
    Note To support multi-tenant capable Out of Office functionality for tenants among different organizations within the same domain, you must install the OOF agent on all Exchange Hub Transport servers. The Exchange Transport service must be restarted for the installation of Categorizer Override Agent.
    For more information about how to install and configure the OOF agent, visit the following Microsoft Web site:
    
    How to install and configure the OOF agent (http://technet.microsoft.com/en-us/library/cc545931.aspx)
    
    To remove the existing CategorizerOverrideAgent, follow these steps:
    1. On EXHUB01, open the CategorizerOverrideAgent.dll.config file from the CategorizerOverrideAgent directory, and note the Cache Refresh Time.
       Note By default, the CategorizerOverrideAgent.dll.config file is located in the following folder:
       C:\Program Files\Microsoft\Exchange Server\TransportRoles\Agents\CategorizerOverrideAgent
    2. Run the following command to uninstall the performance counters and event sender:
       %WINDIR%\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe CategorizerOverrideAgent.dll
    3. Open the Exchange Management Shell, and then disable and uninstall the TransportAgent.
    4. In Add or Remove Programs, remove the CategorizerOverrideAgent.
    5. Open regedit, and then remove the "Categorizer Override Agent" subkey under the following:
       HKLM\SYSTEM\CurrentControlSet\Services
    
    To remove the existing version of the SMTPDomainCacheTask, follow these steps:
    1. Make a backup copy of SMTPDomainCacheTask.exe.config file from the following folder:
       %PROGRAM FILES%\Microsoft hosting\Provisioning\SmtpDomainCacheTask
    2. Remove SmtpDomainCacheTask by using Add or Remove Programs.
15. On the OMSQL server, reinstall the following components:
    • ADCollecter.msi
    On the MPSSQL server, reinstall the following components:
    • ResourceManageDatabase.msi
16. If current system is upgraded from Hosted Messaging and Collaboration 4.0, follow these steps to install and run CheckFolderGroupsAndRMByPlan.msi.
    1. Copy the CheckFolderGroupsAndRMByPlan.msi to a location on the MPS engine server (MPS01).
    2. Run the CheckFolderGroupsAndRMByPlan.msi file.
    3. Locate the CheckFolderGroupsAndRMByPlan.exe.config file in the following folder:
       %program files%\Microsoft Hosting\Provisioning\CheckFolderGroupsAndRMByPlan
       Remove the file's read-only property, and then edit the file to point to the SQL server location of the ResourceManager and PlanManager databases (MPSSQL01).
    4. Open a command prompt, and run the CheckFolderGroupsAndRMByPlan.exe file.
17. Log on to the MPSSQL server as the Domain Administrator, run the KB959196.msi file to install the MPS Resource manager Database Function Update tool.