The information in this article applies to:
SUMMARYThe following article lists all versions of Microsoft Exchange Server, Exchange Client, and Outlook software that have been released to date and how to determine which version or versions are currently running. MORE INFORMATIONDetermining Exchange Server Versions
NOTE: Selecting help/about from within the Administrator program gives the version of Admin.exe and may be misleading if you are running the Administrator program against a different Exchange Server computer or from a Windows NT Workstation. Determining Exchange Client VersionsSelect help/about from within the Microsoft Exchange Client.NOTE: From Windows 95 or Windows NT, you may be able to determine which version is installed by selecting properties for a particular file from Windows (NT) Explorer and selecting Version. Microsoft Exchange Server service packs are posted at the following address: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/Here is a list of Exchange versions numbers and their associated Build numbers:
The Windows Messaging Client that ships with Windows NT version 4.0 also has a
build number of 837, the same as Exchange 4.0. The splash screen, however, is
entitled Windows Messaging, not Microsoft Exchange. The Windows Messaging
client that ships with Windows 95 is build 950. Neither of these clients
provide connectivity to an Exchange Server and must be upgraded to one of the
versions listed in the table above to work with Exchange Server.
Determining Microsoft Outlook Versions
The version and build number are in brackets at the top of the dialog
box.
Additional Information About Service PacksMicrosoft releases service packs for Microsoft Exchange on a regular basis. Microsoft recommends running the latest service packs on all servers and clients whenever possible, but it is not required that all Exchange Servers or Clients be simultaneously upgraded to the same service packs (although this may be ideal).In general, Microsoft Exchange service packs are cumulative, that is, each service pack contains all fixes up to that point. This means that in order to bring an Exchange Server or Client up to a SP level, the earlier SP doesn't need to first be installed. The exceptions to this rule are Exchange 4.0 service packs later than SP2. Due to the size of Exchange 4.0 SP2, subsequent SPs were created as deltas only. To bring an Exchange Server or Client up to a later 4.0 SP, SP2 needs to be first applied. As with any major software rollout, Microsoft recommends that you install service packs on a non-production (test) computer first and test similar functions to those that your production server/client encounters. Always read the release notes (usually Readme.wri) prior to installing the service pack into production. Additional query words:
Keywords : XGEN XADM exc4 exc5 exc55 |
Last Reviewed: August 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |