XGEN: Microsoft Exchange Version Numbers

 Last reviewed: February 18, 1998
Article ID: Q166349
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client version 4.0 and 5.0
  • Microsoft Exchange Windows 95 client version 4.0 and 5.0
  • Microsoft Exchange Windows NT client version 4.0 and 5.0
  • Microsoft Exchange Server, versions 4.0 and 5.0

SUMMARY

The following article lists all versions of Microsoft Exchange Server and Client software that have been released to date and how to determine which version(s) are currently running.

MORE INFORMATION

Determining Exchange Server Versions

  1. Start the Microsoft Exchange Administrator program.
2. Select the Exchange Server in the left-hand pane. 3. Click Properties on the File menu.

The version, build number, and any service packs that are installed should be displayed.

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 or from a Windows NT Workstation.

Determining Exchange Client Versions

Select 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 Service packs are posted at the following address: 

   ftp://ftp.microsoft.com/bussys/exchange/exchange-public/
Here is a list of past and current Microsoft Exchange versions numbers and their associated releases:

Here is a list of Exchange versions numbers and their associated Build numbers: 

   Version                 Build Number
   ------------------------------------
   4.0 RTM                      837
   4.0 SP1                      838
   4.0 SP2 (Exchange 4.0a)      993
   4.0 SP3                      994
   4.0 SP4                      995
   5.0 RTM                     1457
   5.0 SP1                     1458
   5.5 RTM                   8.03.4629 (due to the switch to the Outlook Client)
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.

Additional Information about Service Packs

Microsoft 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 a Server (or Client) up to a SP level, the earlier SP doesn't have to first be installed. The exceptions to this rule are Exchange 4.0 Service Packs greater than SP2. Due to the size of Exchange SP2, subsequent SPs were created as deltas only. To bring a Client or Exchange Server up to a later 4.0 SP, SP2 needs to be first applied.

As with any major Software rollout, Microsoft recommends installing service packs on a non-production (test) computer first and testing similar functions to those that your production Server/client encounter. Always read the release notes (usually 

Readme.wri) prior to installing the Service Pack into production.

Additional query words:
Keywords : XADM XGen kbinfo
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbinfo
Solution Type : Info_Provided

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: February 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.