Microsoft KB Archive/265169

= XCCC: How to Enable Secure Conferencing for Clients That Are Not Windows 2000 Clients =

Article ID: 265169

Article Last Modified on 2/26/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange 2000 Conferencing Server

-



This article was previously published under Q265169





SUMMARY
When you use Microsoft Exchange 2000 Server with clients that are not Windows 2000 clients (such as Windows 95, Windows 98, and Windows NT Workstation 3.5, 3.51, and 4.0), you may be unable to engage in secure conferencing. This article describes how to enable secure conferencing with clients that are not Windows 2000 clients.



MORE INFORMATION
The following procedure applies to clients that are not Windows 2000 clients (Windows 95, Windows 98, and Windows NT Workstation 3.5, 3.51, and 4.0).

Client Requirements

 * NetMeeting version 3.01 or later
 * &quot;Exportable&quot; user certificates to participate in secure data (T.120) conferences

NOTE: If the user certificate is from a third-party service (non Microsoft), the Conference Management Service (CMS) and associated T.120 MCU/H.323 Bridge must be trusted by the clients Certificate Authority (CA).

Server Configuration
Make the following configuration changes on the server:  Disable Integrated Windows authentication on the ConferencingPrivate virtual directory on which Conference Web Access is installed by using Internet Services Manager:  On the toolbar click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager. Open Properties for the ConferencingPrivate virtual directory, and then click the Directory Security Properties tab. Under Anonymous access and authentication control, click Edit, and then clear the Integrated Windows authentication option. After you change this setting, the ConferencingPrivate virtual directory uses basic authentication only.  Make the conferencing virtual directory (Conferencing, ConferencingPrivate) accessible only over Secure Sockets Layer (SSL) when basic authentication is used:  Install a server certificate for the Web server, if a server certificate is not already installed.

NOTE: The server certificate must be from a Microsoft Certificate Authority service for secure conferences to work successfully.  Locate the Web site on which the conferencing virtual directories are installed.</li> Open the properties, and then click the Directory Security Properties tab.</li> Click the Directory Security tab.</li> Under Secure Communications, click Server Certificate.</li> Follow the instructions in the wizard to complete installation of a server certificate.</li></ol> </li> Change the conferencing virtual directories to require SSL:  In the properties, click the Directory Security Properties tab.</li> Click the Directory Security tab.</li> Under Secure Communications, click Edit.</li> Click to select the Require Secure Channel check box, and then click OK.</li></ol> </li> Change the default access Uniform Resource Locator (URL) for user connections to use &quot;https://&quot; instead of &quot;http://&quot;:  <li>Open the properties for the Conference Management Service.</li> <li>Click the Conference Settings tab, and then change the default access URL for user connections to https:// under Access URL for user connections.</li> <li>Restart the Conference Management Service for the conferencing site.</li></ol> </li></ol> </li></ol>

Additional query words: x2krtcht

Keywords: kbinfo KB265169

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.