Microsoft KB Archive/136516

= XCLN: Improving Windows Client Startup Times =

Article ID: 136516

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Client 5.5
 * Microsoft Exchange Client 5.0
 * Microsoft Exchange Client 4.0
 * Microsoft Exchange Client 5.0

-



This article was previously published under Q136516



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 correctly configuring the remote procedure call (RPC) binding order on the computer running the Exchange client. For additional informationabout the steps necessary to modify the RPC binding order, click the article number below to view the article in the Microsoft Knowledge Base:

163576 XGEN: Changing the RPC Binding Order



MORE INFORMATION
When the Exchange client starts up, it uses the first protocol in the RPC binding order to attempt to communicate with the Microsoft Exchange Server computer. If this attempt is unsuccessful, the 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 establishes communication with the server in the first attempt and does 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, because a different setup method is employed.

Additional query words: faq exfaqclnt exclnfaqold outlook

Keywords: kbenv kbprb KB136516

-

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

© Microsoft Corporation. All rights reserved.