exchange

You cannot set the "Country/region" attribute of a user mailbox to "Curaçao," "Bonaire, Sint Eustatius and Saba," or "Sint Maarten (Dutch part)" by using the Exchange Management Console on an Exchange Server 2007 server

On a Microsoft Exchange Server 2007 server that is running Windows Server 2008 or Windows Server 2008 R2 and has hotfix 2604521 installed, one of the following scenarios occurs.
Scenario 1

You try to use Exchange Management Console to set the Country/region attribute of a user mailbox to one of the following three countries or regions:

  • Curaçao
  • Bonaire, Sint Eustatius and Saba
  • Sint Maarten (Dutch part)

In this situation, the country options are not displayed.

Scenario 2

 Consider the following scenario:

  • You have hotfix 2607863 installed on the Exchange Server 2007 server.
  • You use the Active Directory Users and Computers MMC snap-in to set the Country/region attribute of a user account to one of the following three countries or regions:
    • Curaçao
    • Bonaire, Sint Eustatius and Saba
    • Sint Maarten (Dutch part)
  • You try to use Exchange Management Console to view the Country/region attribute of the user mailbox.

In this scenario, you receive the following error message:

The properties on %useraccount% have invalid data. If you click ‘OK’, default values will be used instead and will be saved if you do not change them before hitting ‘Apply’ or ‘OK’ on the property page. If you click ‘Cancel’ the object will be displayed read-only and corrupted values will be retained. The following values have invalid data: CountryOrRegion

This issue occurs because Exchange Server 2007 does not handle the new countries or regions correctly.
To resolve this issue, install the following update rollup:

2608656 

(http://support.microsoft.com/kb/2608656/
)
Description of Update Rollup 6 for Exchange Server 2007 Service Pack 3

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:  
2604521 

(http://support.microsoft.com/kb/2604521/
)
You cannot set the “Country/region” attribute of a user account to “Curaçao,” “Bonaire, Sint Eustatius and Saba,” or “Sint Maarten (Dutch part)” in Windows Vista or in Windows Server 2008
2607863 

(http://support.microsoft.com/kb/2607863/
)
You cannot set the “Country/region” attribute of a user account to “Curaçao,” “Bonaire, Sint Eustatius and Saba,” or “Sint Maarten (Dutch part)” in Windows Vista or in Windows Server 2008

Read the article:
You cannot set the "Country/region" attribute of a user mailbox to "Curaçao," "Bonaire, Sint Eustatius and Saba," or "Sint Maarten (Dutch part)" by using the Exchange Management Console on an Exchange Server 2007 server

SDP 3bf94612c-8d65-4848-8f2c-4527635a03f9 Office 365 Connectivity Analyzer

This Support Diagnostics Platform (SDP) diagnostic is designed to verify connectivity between an Office 365 Exchange customer and their hosted mailbox.  

The diagnostic described in this article can be used on the following versions of Microsoft Windows.
When you run the Office 365 Connectivity Analyzer diagnostic, you are prompted to select one of the following diagnostic tests:
  • Microsoft Exchange ActiveSync Connectivity Tests
  • Microsoft Office Outlook Connectivity Tests

Collapse this imageExpand this image

In Step 1, type the email address of the mailbox that you want to test.

Collapse this imageExpand this image

In Step 2, type the Microsoft Online Services ID and then click Next.

Collapse this imageExpand this image

Type the password for the Microsoft Online Services ID and then click OK.

Collapse this imageExpand this image

After the tests are completed, the results are displayed on the screen.

Collapse this imageExpand this image

Information Collected

Collapse this tableExpand this table

Description File Name
Diagnostic Test log %userprofile%O365TestResults.Log

Additional Information

The diagnostic tests included in the Office 365 Connectivity Analyzer are derived from tests in the Exchange Remote Connectivity Analyzer (see http://www.testexchangeconnectivity.com
(http://www.testexchangeconnectivity.com)
). Documentation for errors found during these tests are located at http://technet.microsoft.com/en-us/library/dd439364(EXCHG.80).aspx
(http://technet.microsoft.com/en-us/library/dd439364(EXCHG.80).aspx)
.

References

KB 973559 – Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) for Windows 7
http://support.microsoft.com/kb/973559
(http://support.microsoft.com/kb/973559)

Read the original:
SDP 3bf94612c-8d65-4848-8f2c-4527635a03f9 Office 365 Connectivity Analyzer

An Exchange Server 2007 Transport Rule does not work as expected

A Microsoft Exchange Server 2007 Transport Rule does not work as expected. For example, an email message that an administrator expects to be rejected may instead be delivered.
This issue can occur if the Transport Rule is based on a regular expression. For example, this issue can occur if you use the “$” character to create a pattern-matching regular expression.

Note Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 do not implement the full Microsoft .NET Framework regular expression classes. Additionally, the intermediate language that is generated may be incorrect.

To work around this issue, use one of the following methods.

Method 1

Create a Transport Agent and then implement your own .NET Framework regular expressions to route email messages.

Method 2

Use a filter to automatically process email messages. For example, use Microsoft ForeFront Security for Exchange Server to filter email messages based on the email originator and email recipient.

Regular expressions are a powerful, flexible way to evaluate a character sequence for matching against a given series of characters. Typically, a regular expression is written in a programming language such as C++ or C#. The regular expression can then be interpreted by a regular expression processor. The processor examines the character sequence and identifies parts that match the provided characters.

You can create a Transport Rule based on regular expressions in the Exchange Management Shell (EMS) by using the New-TransportRule cmdlet. When you use the Conditions parameter, the Exchange regular expression implementation is used. You can use regular expressions in any predicate that accepts the “Patterns” predicate property.

Transport Rule conditions and exceptions consist of one or more predicates. Predicates instruct the Transport Rules agent on a Hub Transport server (or the Edge Rules agent on an Edge Transport server) to examine a specific part of an email message. Those specific parts include sender, recipients, subject, other message headers, and message body. Then, the Transport Rule determines whether the rule should be applied to that message. Therefore, predicates act as building blocks for conditions and exceptions.

In the Exchange Management Console, you can use regular expressions with any condition or exception that contains the words “text patterns.” For example, you can use regular expressions with the following condition:

“when the From address contains text patterns”

Note The “Patterns” predicate accepts a regular expression that can be used to match text that follows an identifiable pattern. You must enclose the expression in quotation marks (“).

For more information about Transport Agents in Exchange Server 2010, visit the following TechNet website:
For information about how to use the NewTransportRule cmdlet, visit the following TechNet website:
For information about regular expressions and how to use regular expressions in Exchange Server 2007 Transport Rules, visit the following TechNet website:
For information about how to use predicates to create conditions and exceptions in an Exchange Server 2010 Transport Rule, visit the following TechNet website:

Continue Reading:
An Exchange Server 2007 Transport Rule does not work as expected

How to troubleshoot Exchange Server 2007 and Exchange Server 2010

The “Exchange Server 2007 SP3 and Exchange Server 2010 Troubleshooter for Windows 2008 R2″ tool collects a comprehensive set of information for troubleshooting Exchange Server 2007 SP3 and Exchange Server 2010 issues in Windows Server 2008 R2. This troubleshooter is integrated with the Microsoft Fix it Center Pro service. This service can perform automated diagnostic analysis to identify solutions.

To run this troubleshooter, follow these steps:

  1. Visit the Microsoft Fix it Center Pro
    (https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase/Create?showReturn=True)
    portal.
  2. If you are prompted, sign in by using your Windows Live ID.
  3. In the Analysis packages list, click Exchange Server 2007 SP3 and Exchange Server 2010 Troubleshooter for Windows 2008 R2.
  4. In the Create Analysis Session window, type a descriptive name for the session, and then click Save.

    Note You will use the name that you enter to view the analysis results later.

  5. Follow the instructions to download and run the analysis package.
  6. To view the analysis results, open the Fix it Center Pro – Analysis
    (https://wc.ficp.support.microsoft.com/Dashboards/Main/SelfHelpCase?shcID=SHC5007487727638252&maximizeDetails=False)
    webpage.
  7. Click the Analysis Session name that you created in step 4 to view possible solutions.
For more information about Fix it Center Pro, please see:For more information about this troubleshooter and what it scans, please see the following Microsoft Knowledge Base article:

See the article here:
How to troubleshoot Exchange Server 2007 and Exchange Server 2010

A client does not display email message content in an Exchange Server 2007 SP3 RU1 environment

Consider the following scenario:
  • You apply Update Rollup 1 (RU1) for Microsoft Exchange Server 2007 Service Pack 3 (SP3).
  • By default, the Best body format option is set for POP3 and IMAP4 message retrieval on a Client Access server.
  • The POP3 or IMAP4 client cannot display the HTML message format, and retrieves email messages from Exchange Server 2007 server.

In this scenario, the POP3 or IMAP4 client does not display the message content.

This issue occurs because the POP3 or IMAP4 clients that use the Best body format option only retrieve the native content that is stored on the Exchange Mailbox server. This behavior causes the POP3 or IMAP4 clients to no longer receive an additional text-only copy of the message. Therefore, if a client is unable to display the HTML message format, the content of the email message cannot be displayed.
To work around this issue, configure the message retrieval settings for HTML and alternative text. This configuration is set for the POP3 and IMAP4 services on each Client Access server that provides service to users. Additionally, the setting change takes effect after the affected services are restarted.
For more information about how to manage POP3 and IMAP4 message retrieval format options, visit the following Microsoft website:For more information about how to manage POP3 and IMAP4, visit the following Microsoft website:For more information about the Set-POPSettings cmdlet, visit the following Microsoft website:For more information about a content retrieval change in Exchange Server 2007 SP3 Update Rollup 1, visit the following Microsoft website:

Read More:
A client does not display email message content in an Exchange Server 2007 SP3 RU1 environment

Description of Update Rollup 6 for Hosted Messaging and Collaboration 4.5

Article ID: 979704 – Last Review: October 4, 2011 – Revision: 4.0

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

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 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:

977174  

(http://support.microsoft.com/kb/977174/
)
Description of Update Rollup 5 for Hosted Messaging and Collaboration 4.5

976864 

(http://support.microsoft.com/kb/976864/
)
Mails may be sent to unintended mail recipients in Hosted Messaging and Collaboration 4.5

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.

Collapse this tableExpand this table

File name File version File size Date Time Platform
Rpchttpconfigtool.msi Not Applicable 412,672 02-Dec-2009 17:21 Not Applicable
Adcollector.msi Not Applicable 419,328 02-Dec-2009 17:21 Not Applicable
Pwdb40ssis.msi Not Applicable 273,408 02-Dec-2009 17:21 Not Applicable
Categorizeroverrideagent-x64.msi Not Applicable 373,760 02-Dec-2009 17:21 Not Applicable
Categorizeroverrideagent.msi Not Applicable 373,760 02-Dec-2009 17:21 Not Applicable
Checkfoldergroupsandrmbyplan.msi Not Applicable 384,512 02-Dec-2009 17:21 Not Applicable
Kb959196.msi Not Applicable 756,224 02-Dec-2009 17:21 Not Applicable
Smtpdomaincachetask-x64.msi Not Applicable 369,664 02-Dec-2009 17:21 Not Applicable
Exchange2007oabresourcemanagerns.msi Not Applicable 253,952 02-Dec-2009 17:21 Not Applicable
Exchange2007resourcemanagerns.msi Not Applicable 308,736 02-Dec-2009 17:21 Not Applicable
Hostedactivedirectoryns.msi Not Applicable 264,192 02-Dec-2009 17:21 Not Applicable
Hostedemail2007ns.msi Not Applicable 349,184 02-Dec-2009 17:21 Not Applicable
Hostedsharepoint2007ns.msi Not Applicable 260,608 02-Dec-2009 17:21 Not Applicable
Managedadns.msi Not Applicable 285,696 02-Dec-2009 17:21 Not Applicable
Managedemail2007ns.msi Not Applicable 315,904 02-Dec-2009 17:21 Not Applicable
Managedunifiedmessaging2007ns.msi Not Applicable 247,808 02-Dec-2009 17:21 Not Applicable
Activedirectoryprovider.msi Not Applicable 364,032 02-Dec-2009 17:21 Not Applicable
Blockrmoprovider.msi Not Applicable 270,848 02-Dec-2009 17:21 Not Applicable
Corermoprovider.msi Not Applicable 360,448 02-Dec-2009 17:21 Not Applicable
Exchange2007mobilityprovider.msi Not Applicable 364,032 02-Dec-2009 17:21 Not Applicable
Exchange2007provider.msi Not Applicable 537,600 02-Dec-2009 17:21 Not Applicable
Filesystemprovider.msi Not Applicable 395,264 02-Dec-2009 17:21 Not Applicable
Unifiedmessaging2007provider.msi Not Applicable 251,392 02-Dec-2009 17:21 Not Applicable
Dnsclient.msi Not Applicable 682,496 02-Dec-2009 17:21 Not Applicable
Dnsprovider.msi Not Applicable 357,376 02-Dec-2009 17:21 Not Applicable
Resourcemanagedatabase.msi Not Applicable 790,528 02-Dec-2009 17:21 Not Applicable
Exchange2007oabresourcemanagerws.msi Not Applicable 445,440 02-Dec-2009 17:21 Not Applicable
Exchange2007resourcemanagerws.msi Not Applicable 467,968 02-Dec-2009 17:21 Not Applicable
Hostedactivedirectoryws.msi Not Applicable 475,648 02-Dec-2009 17:21 Not Applicable
Hostedemail2007ws.msi Not Applicable 530,432 02-Dec-2009 17:21 Not Applicable
Hostedsharepoint2007ws.msi Not Applicable 476,672 02-Dec-2009 17:21 Not Applicable
Managedactivedirectoryws.msi Not Applicable 472,064 02-Dec-2009 17:21 Not Applicable
Managedemail2007ws.msi Not Applicable 524,800 02-Dec-2009 17:21 Not Applicable

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:tempQFERollupPackage
  5. After backing up the existing files, copy the following MSI files from the C:tempQFERollupPackage 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 HostingProvisioningRPCHTTPConfig
    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:

  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:
  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:
  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:
    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 FilesMicrosoftExchange ServerTransportRolesAgentsCategorizerOverrideAgent
    2. Run the following command to uninstall the performance counters and event sender:
      %WINDIR%Microsoft.NETFrameworkv2.0.50727InstallUtil.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:
      HKLMSYSTEMCurrentControlSetServices

    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 hostingProvisioningSmtpDomainCacheTask
    2. Remove SmtpDomainCacheTask by using Add or Remove Programs.
  15. On the OMSQL server, reinstall the following components: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 HostingProvisioningCheckFolderGroupsAndRMByPlan
      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.


APPLIES TO
  • Microsoft Solution for Hosted Messaging and Collaboration 4.5
  • Microsoft Exchange Server 2007 Service Pack 2
kbautohotfix kbhotfixserver kbhotfixrollup kbexpertiseadvanced kbsurveynew kbqfe KB979704

Other Resources

Other Support Sites

Community

Get Help Now

Article Translations

Read More:
Description of Update Rollup 6 for Hosted Messaging and Collaboration 4.5

Public folder read/unread status is lost after a public folder on a second Exchange Server 2007 server is added as a replica folder

Consider the following scenario:
  • You have two servers that are running Microsoft Exchange Server 2007 in the same Exchange organization. 
  • A Microsoft Outlook 2010 user accesses their mailbox on Exchange server ServerA.
  • The ServerA mailbox user’s mailbox store has the default public folder store configured on the same server, ServerA.
  • You create a public folder on a second Exchange server, ServerB.
  • The user who has the mailbox on ServerA reads some posted items in the public folder. (The public folder currently exists only on ServerB.
  • The read/unread status of posted items is retained as expected for that user.

In this scenrio, after you add a replica of the public folder to the public folder store of ServerA, all the items for the user are set incorrectly as unread.

This issue occurs because Outlook 2010 uses the read/unread status only from the public folder replica that is now available in the user’s default public folder store.
 Microsoft is researching this problem and will post more information in this article when that information becomes available. 

More here:
Public folder read/unread status is lost after a public folder on a second Exchange Server 2007 server is added as a replica folder

Recent Comments

    Archives

    Categories