Description of Update Rollup 3 for Hosted Messaging and Collaboration 4.0: December 2009

Article translations Article translations
Article ID: 979702
Expand all | Collapse all

On This Page

SUMMARY

Microsoft released an update rollup that is dated December 2009. This update fixes issues that may occur in the following components of Microsoft Solution for Hosted Messaging and Collaboration 4.0:
  • 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
  • Hosted SharePoint 2007 Namespace
  • Managed SharePoint 2007 Namespace
  • Hosted SharePoint Web Service
  • Managed SharePoint Web Service
  • DNS Provider
This article describes the following items about the update rollup:
  • 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 replaces any other update rollup.
  • Whether you must make any registry changes.
  • The files that the update rollup contains.

Introduction

Issues that the update rollup fixes

This update rollup fixes the following issue that was previously documented in a Microsoft Knowledge Base article:
977990 You cannot create a new Offline Address Book in a Hosted Message and Collaboration environment
This update rollup fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
  • When you create a public folder by using either the -StorageQuota parameter or by using the -PostStorageQuota parameter, the operation fails. In Microsoft Exchange Server 2007 Service Pack 2 (SP2), these two parameters are replaced by the –IssueWarningQuota parameter and the –ProhibitPostQuota parameter.
  • When you create a folder, the value of the folder allocation is not consistent with the result of the -StorageQuota parameter.
  • You cannot change a shared mail store to a not shared mail store by using the ModifyExchangeResources procedure.
  • Mails are sent to unintended mail recipients.
  • The DeleteResourceRecord procedure in DNS Provider runs for a longer time than expected. Or, the procedure times out if there are too many records in the DNS zone.
  • Exchange Resource Manager cannot allocate mailboxes from the mail store that has the most available space by using the "level" algorithm. This issue occurs when you add the first mail user of a company to a mail store.
  • In Exchange 2007 Resource Manager, the ReallocateOrganizationMailNoMove procedure cannot reallocate an organization correctly when you use the "level" algorithm for "not shared" mail stores.
  • When you create a public folder, the useDatabaseQuotaDefaults parameter is automatically set to true.
  • The SetUMServer procedure in Unified Messaging 2007 Provider fails if you specify more than one value in the dialPlans property. This procedure only fails if at least one of the dialPlans property values contains a space character.

MORE INFORMATION

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:
http://support.microsoft.com/contactus/?ws=support
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

  • Microsoft Solution for Hosted Messaging and Collaboration 4.0 must be installed before you apply this update.
  • Microsoft Exchange Server 2007 Service Pack 2 (SP2) must be installed on all Exchange servers.
  • You must install the previously released HMC 4.0 Update Rollup fixes that are described in the following Microsoft Knowledge Base (KB) articles:
    952077 Description of Update Rollup 4 for the Hosted Exchange services in Microsoft Solution for Hosted Messaging and Collaboration 4.0
    952075 Description of Update Rollup 1 for the Hosted SharePoint services in Hosted Messaging and Collaboration 4.0
    957005 Description of Provisioning Update Rollup 1 for in Microsoft Solution for Hosted Messaging and Collaboration 4.0
  • The logon user must be a member of the Domain Admins Group.
  • The HMC Deployment Tool must be installed on the first Microsoft Provisioning Server (MPS) Engine server.

Restart requirement


You do not have to restart the computer after you apply this hotfix. However, you must restart the Provisioning Engine on each MPS server. Additionally, you may have to restart Internet Information Services (IIS) on each Web services server, on PROV01 and on each Front-end Windows SharePoint Services server (COLLAB01).

Hotfix replacement information


This update rollup does not replace any previously released update rollups.

File information

The English version of this hotfix has the file attributes (or later versions of the 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.

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Servicebase.msiNot applicable378,36813-Dec-200912:15Not applicable
Sharedoabutility.msiNot applicable391,68013-Dec-200912:15Not applicable
Managedhelpers.msiNot applicable317,95213-Dec-200912:15Not applicable
Exchange2007resourcemanagerns.msiNot applicable289,79213-Dec-200912:15Not applicable
Hostedemail2007ns.msiNot applicable314,36813-Dec-200912:15Not applicable
Hostedsharepoint2007ns.msiNot applicable254,46413-Dec-200912:15Not applicable
Managedemail2007ns.msiNot applicable279,55213-Dec-200912:15Not applicable
Managedsharepoint2007ns.msiNot applicable271,87213-Dec-200912:15Not applicable
Exchange2007mobilityprovider.msiNot applicable367,10413-Dec-200912:15Not applicable
Exchange2007provider.msiNot applicable510,46413-Dec-200912:15Not applicable
Unifiedmessaging2007provider.msiNot applicable406,01613-Dec-200912:15Not applicable
Windowssharepointserviceswebservice.msiNot applicable645,63213-Dec-200912:15Not applicable
Dnsclient.msiNot applicable679,93613-Dec-200912:15Not applicable
Dnsprovider.msiNot applicable358,91213-Dec-200912:15Not applicable
Resourcemanagedatabase.msiNot applicable791,04013-Dec-200912:15Not applicable
Exchange2007resourcemanagerws.msiNot applicable469,50413-Dec-200912:15Not applicable
Hostedemail2007ws.msiNot applicable528,38413-Dec-200912:15Not applicable
Hostedsharepoint2007ws.msiNot applicable475,64813-Dec-200912:15Not applicable
Managedemail2007ws.msiNot applicable515,07213-Dec-200912:15Not applicable
Managedsharepoint2007ws.msiNot applicable469,50413-Dec-200912:15Not applicable

Installation information


To install this update rollup, follow these steps:
  1. Log on to the MPS server as a member of the Domain Admins Group.
  2. Start the Deployment Tool to uninstall the following old components:
    • Exchange 2007 Resource Manager Namespace
    • Exchange 2007 RM Web Service
    • Hosted Email 2007 Namespace
    • Hosted Email 2007 Web Service
    • Managed Email 2007 Namespace
    • Managed Email 2007 Web Service
    • Exchange 2007 Mobility Provider
    • Exchange 2007 Provider
    • Unified Messaging 2007 Provider
    • Hosted SharePoint 2007 Namespace
    • Managed SharePoint 2007 Namespace
    • Hosted SharePoint Web Service
    • Managed SharePoint Web Service
    • DNS Provider
    • Managed Helpers
  3. Extract the rollup package to a temporary location on the MPS server. For example, extract it to the following location:
    C:\temp\QFERollupPackage
  4. Copy the following 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
    • ManagedSharePoint2007NS.msi
    • HostedSharePoint2007WS.msi
    • ManagedSharePoint2007WS.msi
    • DNSClient.msi
    • DNSProvider.msi
    • WindowsSharePointServicesWebService.msi
    • ResourceManageDatabase.msi
    • ManagedHelpers.msi
    • SharedOABUtility.msi
  5. Use the Deployment Tool to reinstall these components on the MPS Engine Server. Deploy the updated Web services to each Web Service server.
  6. In the Deployment Tool, expand Hosted Exchange, and then expand Exchange Provisioning Configuration.
  7. Right-click the nodes that open in Exchange Provisioning Configuration, and then execute the following commands:
    • Initialize Exchange 2007 Resource Manager
    • Initialize Hosted Email 2007
    • Initialize Managed Email 2007
  8. Expand SharePoint Services Hosting, right-click the nodes that open, and then execute the following commands:
    • Initialize Hosted SharePoint
    • SharePoint Initialize Namespace Security
  9. In the Deployment Tool, expand Hosting Platform, and then expand Initialize Default Services.
  10. Right-click the nodes that open in Initialize Default Services, and then execute the following initialize commands:
    • Initialize Active Directory for Hosting
    • Initialize Namespace Security
  11. Click Start Deployment.
  12. Log on to PROV01 as the Domain Administrator.
  13. Run the DNSClient.msi file two times. This action removes the previously installed version of the DNS Client and installs a new version. To install the DNSClient.msi component, follow the instructions in the "Deploy the MPS DNS Client" section in the HMC 4.5 deployment guide. For more information about how to deploy the MPS DNS Client, visit the following Microsoft Web site:
    How to deploy the MPS DNS Client
  14. Configure the DNS Web Client. To do this, follow these steps:
    1. In IIS Manager, right-click DNSProvider, select Properties, and then select Directory Security.
    2. Under Authentication and Access Control, click Edit.
    3. Set the default domain value for the basic authentication setting to '\' (backslash). Click OK.
    4. Select Require security channel (SSL).
    5. Save the configuration changes and close IIS Manager.
    6. Restart IIS.
  15. On the MPSSQL server in which the resource manager database resides, install the ResourceManageDatabase.msi component. When you run the ResourceManageDatabase.msi component, the following actions are performed:
    • Add an index to the table [rmcore_Candidates]:
      • rmcore_candidates_ix_target_set_object_category_object_id_trans_id
    • Add the following stored procedures that perform read-only operations to the ResourceManager database:
      • SeleteAndAssembleAllocateOrgMailStores
      • SeleteAndAssembleReallocateOrgMailStores
    • Add the following user-defined functions that perform read-only operations to the resource manager database:
      • fn_min (scalar valued)
      • fn_ResourceCapacityOnAllocatedMailStores (table-valued)
      • fn_ResourceCapacityOnUnallocatedMailStores (table-valued)
  16. On all front-end SharePoint servers (COLLAB0n), uninstall the old version of the WindowsSharePointServicesWebService.msi file. To do this, follow these steps:
    • Copy the new version of the WindowsSharePointServicesWebService.msi file from MPS01 to COLLAB0n.
    • Execute the new version of the WindowsSharePointServicesWebService.msi file.
    • Restart IIS on all SharePoint servers.
  17. If you have to create a shared OAB when you approach the limit of 32,000 OABs, execute the SharedOABUtlity.msi file on MPS01, and then accept the default settings.
  18. 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, and then click Shut Down.
    5. Right-click Provisioning Engine, and then click Start.
  19. Restart IIS on each Web services server.

Properties

Article ID: 979702 - Last Review: February 21, 2010 - Revision: 1.2
Keywords: 
kbexpertiseadvanced kbautohotfix kbsurveynew kbqfe kbhotfixrollup kbhotfixserver KB979702

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com