Exchange 2000 Conferencing Server Release Notes

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Updated : June 14, 2001

Includes Web Addendum

About this Document

This document lists critical issues that can potentially impede you from successfully installing or deploying Exchange 2000 Conferencing Server in your environment. The issues listed in this document do not include Exchange 2000 release notes.

For a list of issues that are important to deploying Exchange 2000 and Exchange 2000 Conferencing Server and that require more detailed explanation, see Exchange 2000 Deployment Resources at the following URL: https://www.microsoft.com/exchange/techinfo/deployment/2000/default.asp
For issues that relate to special cases or require very detailed explanations, see the Knowledge Base articles at the following URL: https://support.microsoft.com/

Exchange Conferencing Server

Installing Exchange Conferencing Server Using Terminal Server

If you use Terminal Server to install Exchange Conferencing Server, do not use a mapped network drive. If you use Terminal Server with a mapped network drive, the installation will fail. Instead, use a universal naming convention (UNC) path to access the installation program. For example: \\Servername\ConferencingInstallShare\USA\Conferencing\Setup\i386\Setup.exe.

Enabling Secure Conferencing for Non-Windows 2000 Clients

The following applies to Windows 95, Windows 98, Windows NT 4.0 and earlier clients.

Client Requirements

To participate in secure data conferences, each client must have the following:

NetMeeting version 3.01 or later. Users can download the newest version of NetMeeting from the Windows NetMeeting Home Page.
An exportable user certificate. Users can download exportable user certificates from a certificate server on the network.

Server Configuration

To prepare the server to support secure data conferences for non-Windows 2000 clients, you must do the following:

On the server with the conference access pages installed, disable Integrated Windows authentication in the ConferencingPrivate virtual directory.
When basic authentication is used, make the Conferencing and ConferencingPrivate virtual directories accessible only over Secure Sockets Layer (SSL).

To disable Integrated Windows authentication:

Start Internet Services Manager: Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
Navigate to the ConferencingPrivate virtual directory: In Internet Information Services, click the server name, and then click Default Web Site. Right-click ConferencingPrivate.
Click Properties, and then on the Directory Security tab, under Anonymous access and authentication control, click Edit.
On Authentication Methods, under Authentication access, clear Integrated Windows authentication. This forces the ConferencingPrivate virtual directory to use basic authentication.

To make the conferencing virtual directories accessible only over SSL:

If you have already installed a server certificate for the server with the conference access pages installed, skip to step 4.
Start Internet Services Manager, and then navigate to Default Web Site. (See above procedure.) Right-click Default Web Site, and then click Properties.
On the Directory Security tab, under Secure communications, click Server Certificate. Follow the instructions to install a server certificate.
In the virtual directory tree, right-click Conferencing, and then click Properties.
On the Directory Security tab, under Secure communications, click Edit.
Click Require secure channel (SSL).
Repeat the previous three steps for the ConferencingPrivate virtual directory.
Start Conferencing Manager: Click Start, point to Programs, point to Microsoft Exchange, and then click Conferencing Manager.
Under Exchange Conferencing, right-click the site name, and then click Properties.
On the Conference Settings tab, under Access URL for user connections, change the protocol identifier in the URL from https:// to HTTPS://.
Restart Conference Management Service using the Services snap-in.

Upgrading Exchange 2000 Conferencing Server from Release Candidate 2 to Final Version

The following applies to all servers that have Release Candidate 2 (RC2) versions or evaluation versions of Conferencing Manager and/or a Multipoint Control Unit installed. Upgrading from a compact disc (CD) will fail if the names of the CD volumes are different. Instead, you can map the CD to a network share and perform your upgrade from there.

To upgrade to the final version of Exchange 2000 Conferencing Server

Insert the Exchange Conferencing Server CD into your CD drive.
Share the CD drive: From a command prompt, type net share conf=< cd drive letter >:\ and then press the ENTER key.
Connect to the shared drive: From the command prompt, type net use x: \\< servername >\conf and then press the ENTER key.
From the command prompt, navigate to the following directory: x:\Conferencing\Setup\I386
From the command prompt, type msiexec.exe /fvemus "Microsoft Exchange 2000 Conferencing Server.Msi" and then press the ENTER key.
You might be asked to restart the server when setup is complete. This is not necessary.

Addendum

Microsoft Exchange 2000 Server, Microsoft Exchange 2000 Enterprise Server Release Notes

This document is a supplement to the Release Notes provided with Exchange 2000 Server and lists critical issues that can potentially impede you from successfully installing or deploying Exchange 2000 in your environment.

Forcing an Installation of Exchange Conferencing Server

Before Exchange Conferencing Server is installed, Setup runs prerequisite checks to locate a valid server to install Exchange Conferencing Server onto. If the Fully Qualified Domain Name (FQDN) and the domain name do not match, Setup will not be able to recognize a valid installation server, and you will not be allowed to install Conferencing Server. If this problem occurs, you must set up a register key override before you are allowed to install Conferencing Server.

To bypass the prerequisite check, set the appropriate registry key:

On the Start menu, click Run.
In Open, type regedit.
Navigate to the following key: HKEY Local Machine\SOFTWARE\Microsoft\Exchange Conferencing\Parameters.
Right-click Parameters, point to New, and then click DWORD.
Type a name of Setup Prerequisites, and then press ENTER.
Right-click Setup Prerequisites, and then click Modify.
In Value name, make sure it says Setup Prerequisites.

In Base, select Hexadecimal, and in Value data, enter one of the following values depending on your situation:
- To force a valid FIRST installation of Conferencing with IIS installed, type in 1A7.
- To force a valid SECOND+ installation of Conferencing with IIS installed, type in 1BF.
- To force a valid FIRST installation of Conferencing without IIS installed, type in 27.
- To force a valid SECOND installation of Conferencing without IIS installed, type in 3F.

Key Management Server and Global Catalogs

If you are using Exchange 2000 Key Management Server and you are enrolling users that are located in a separate domain, then you should apply Windows 2000 hotfix 272378 on the server running the Key Management Server. Without this hotfix you may experience problems enrolling new users.

Deleting a Public Folder Database Can Impact E-Mail Flow

Problems with e-mail flow can arise when a deleted database is still referenced as the default public folder store for an Exchange 2000 Private Store database. To ensure that mail flow is not impacted, before deleting the database, ensure that no Exchange 2000 databases use the database to be deleted. If not caught before the database is deleted, this issue can result in messages being removed from the queues without notification or logging. The missing messages can be replayed once the situation is resolved.