Article ID: 277778 - View products that this article applies to.
This article was previously published under Q277778
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you manage the Site Conferencing object in the Conferencing Manager, you are prompted to define the Site Conference Calendar mailbox. This prompt is displayed whenever conferencing management is performed.
After you define the Site Conference Calendar mailbox and conferencing resources, they are not displayed in the user interface.
A Lightweight Directory Access Protocol (LDAP) query is performed on the rootNamingContext attribute for the calendar mailbox and conference resource objects but does not resolve because the Microsoft Windows 2000 domain was not created with an ending attribute, for example ".com".
To resolve this problem, remove and reinstall the servers in the domain, being certain to include an appending domain attribute, for example ".com".
To work around this problem, use one of the following methods.
Method 1Install the Exchange Conferencing Service in the root domain, along with all associated conferencing objects, such as the Site Conference Calendar and resource mailboxes.
Method 2NOTE: Method 2 requires the installation of Exchange 2000 Conferencing Server Service Pack 1. The registry entry in the following procedure sets the Conference Management Service to query the defaultNamingContext attribute instead of the rootNamingContext attribute.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.