XCLN: Improving Windows Client Startup Times

Last reviewed: June 11, 1997
Article ID: Q136516
The information in this article applies to:
  • Microsoft Exchange Windows client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0

SYMPTOMS

When you start a Microsoft Exchange Windows client, the main application window may take a relatively long time to load after the startup screen appears.

RESOLUTION

You can significantly improve startup time by properly configuring the RPC binding order on the machine running the Microsoft Exchange client:

  1. Use the Microsoft Exchange Setup Editor to adjust the RPC binding order. The Setup Editor is installed on the server, with the Microsoft Exchange Administrator program.

  2. In the Setup Editor, choose the Modify Setup Program Options command on the File menu. This brings up the Setup Program Options property sheet.

  3. Select the Binding Order property page. Modify the RPC protocols according to your network configuration and delete those protocols not being used.

For example, if the client is communicating with the Microsoft Exchange Server using the TCP/IP protocol, use the Setup Editor to remove all the protocols defined except the TCP/IP protocol.

The Setup Editor must be run against a client installation share point. After you use the Setup Editor to make changes, users must run SETUP.EXE from the client installation share point and install or reinstall the client as necessary.

MORE INFORMATION

When the Microsoft Exchange client starts up, it uses the first protocol in the RPC binding order to attempt to communicate with the Microsoft Exchange Server. If this attempt fails, the Microsoft Exchange client then uses the next protocol in the binding order, and so on, until it has established communication with the server or it has run out of protocols. In the latter case, an error message is displayed and the user is asked if he or she would like to work offline.

Hence, if the protocol installed on the client machine is at the top of the binding order, the client will establish communication with the server in the first attempt and will not have to time out and go down the binding order. This can significantly reduce the startup time.

NOTE: The information in this article only applies to setting the RPC binding order for the 16-bit Windows, Windows NT, and Windows 95 clients. It does not apply to the MS-DOS client as a different setup method is employed.


Additional query words: faq
Keywords : kbenv XCLN
Version : 4.0 5.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.