Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Users who do not use Exchange Server experience delayed responses when they query free/busy data for users who were migrated to Exchange Server 2007
Article ID: 928874 - View products that this article applies to.
Users who do not use Microsoft Exchange Server query free/busy data for users who were migrated to Microsoft Exchange Server 2007. When they do this, they experience delayed responses.
For example, Lotus Notes users query the free/busy data of users who previously used Notes but who have been migrated to Exchange Server 2007. When this occurs, the Notes users experience delayed responses.
This problem occurs when the Exchange Migration Wizard does not remove the additional properties in the free/busy data of a migrated user at the time of the migration.
Note To prevent this problem on Notes accounts that you want to migrate, use the latest Web release version of the Microsoft Exchange Server 2003 Migration Wizard for Lotus Notes.
The following file is available for download from the Microsoft Download Center:
Download the NotesMig.exe package now.
Collapse this imageExpand this image
(http://www.microsoft.com/downloads/details.aspx?familyid=C105B3E4-3BEB-4F1E-8F52-E345AF6C3E50&displaylang=en)Release Date: June 6, 2007
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
(http://support.microsoft.com/kb/119591/ )How to obtain Microsoft support files from online services
To work around this problem for accounts that you have already migrated, you must manually delete the additional properties in the free/busy data of the migrated user by using the MFCMAPI tool. To do this, follow these steps.
Step 1: Locate the free/busy dataThe free/busy public folder for a particular site or for an administrative group is located in the following path:
Public Folders\NON_IPM_SUBTREE\Schedule+ Free Busy\EX:/O=Organization Name/OU=Administrative Group NameA message in the following format may indicate that free/busy data is available for that object:
User-/cn=Recipients/CN=aliasThe following additional properties may exist for an affected user:
Step 2: Use the MFCMAPI tool to remove the additional properties in the free/busy dataTo do this, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
About the function of the calendar connectorNote In this section, the term "third-party calendar connector" means a connector such as the Calendar Connector for Lotus Notes or the Calendar Connector for Novell GroupWise.
A third-party calendar connector performs several different operations.
Accepts notifications from the Store.exe processThe connector accepts notifications from a user who requests free/busy data for a third-party user.
After a notification is received, the third-party calendar connector retrieves free/busy data from the third-party system. Then, the connector puts the data in a free/busy message in the public folder store.
When this process is complete, or when the time-out period has expired, the free/busy data is returned to the requesting client.
Responds to requests from third-party usersThe connector responds to third-party systems that request free/busy data about Exchange Server users.
The third-party calendar connector resolves the third-party address of the requested user. Then, the connector performs a lookup operation against a public folder that contains the schedule information. This information is converted to the correct format for the third-party system. Then, the information is returned to the requesting client.
Synchronizes the list of third-party users from the Active Directory directory serviceThe calendar connector synchronizes the list of third-party contacts to the free/busy public folder that is named Calsync. This synchronization first occurs when the calendar connector first starts. Later, if the setting on the Schedule tab of the Properties page of the third-party calendar connector is configured to Always, the synchronization occurs every 15 minutes.
The third-party calendar connector searches for users who are synchronized by using the Directory Synchronization (DirSync) services of the connector. Then, the third-party calendar connector creates new free/busy messages for each user or contact.
How it is determined that the free/busy query is for a third-party userThe Store.exe process determines whether a free/busy message is for a third-party user by determining whether additional properties exist in the free/busy message. If additional properties exist, the query is directed to the calendar connector service to retrieve the third-party user's data.
Why users experience delayed responsesTypically, when a user who does not use Exchange Server is migrated to Exchange Server, the Migration Wizard tries to match the user's free/busy message. Additionally, the wizard tries to remove the additional properties.
However, in some cases, the migrated user may not be correctly matched to the Exchange Server contact. Therefore, the additional properties are not removed.
Matching may not occur in the following cases:
In turn, the Exchange Calendar Connector queries the calendar connector of the non-Exchange system. This procedure causes the delay in retrieving free/busy data.
For more information about the terminology that Microsoft uses for software that is corrected after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
817903The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
(http://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages