Find out what version of Exchange is on a server

Here's some tips for finding out more about your Exchange server:

  • Neil Hobson has a great tip on the MSExchange blog today about finding out the Exchange version of a server by checking a file.
  • Neil also posted this tip last month about using Exchange System Manager to see more details about the servers in your organization - version, type (front-end, cluster, basic) and edition (standard, enterprise, eval).
  • Another related resource is a KB article I updated a while back that has all of the major releases of Exchange, their version numbers and release dates (note to self: add Exchange 2003).
  • You can also telnet to the protocol ports (such as 110 for POP3, 143 for IMAP4) to see the version of that service. Note that telnetting to SMTP (25) will tell you the version of Windows, not Exchange - but it's a quick way to tell if a server is running Win2k or Win2k3

Comments (8)

  1. Madura says:

    Hi KC,

    Telnetting the Exchange 2000 Server on Port 110 actually gives the Exchange version number (not the Windows version) here’s what I get when I telnet my Exchange server.

    +OK Microsoft Exchange 2000 POP3 server version 6.0.6487.0

    Hey btw, I have a quick question on Journaling…..

    I need to journal all the emails on an Exchange 2000 server to an external smtp address and it should be 100% reliable. I have enabled journaling and it works.. But


    If the remote server fails (external journaled smtp address is unreachable) I dont receive any NDR for the journaled emails. How can we avoid this situation. I need to know if an email is not journaled and I need to journal it back somehow when the remote server is up again. How can we achieve this?

  2. KC Lemson says:

    Right – 110/143 will tell you the version of the POP/IMAP service for Exchange. It’s port 25 for SMTP that tells you the version of Windows.

    As for the journaling question, I don’t know much about that feature. Let me ask around and see if I can find out (but given that most folks are on vacation, I probably won’t get back to you for a while). I’ll add another comment to this entry when I have a response.

  3. KC Lemson says:


    I heard back… Unfortunately there’s no way to find out if journaling is failing other than verifying it periodically. My only suggestion is to look into the functionality of the archivesink (;en-us;307798)
    and see if it works for you – it logs the messages locally to a file, so it’s not dependent on an external server. The archive sink has also been updated for exchange 2003 – There are also some third parties that have add-in
    products that provide more comprehensive solutions, the partner section from should provide some links.

  4. Madura says:

    Hi KC,

    Thanks a lot for your reply. I really appreciate it. I will check the partners link for more solutions.



  5. Madura says:


    Our Exchange 2000 Server (Win2k SP3 and Ex2k SP3) has slowed down dramatically after we enabled the Archive Sink on it. It has a 1 Ghz Xeon Processor and 1.2GB of RAM. We have around 75 users on it. How can we speed up the server? What is the impact on performance after we enable the archive sink? How can we monitor the performance?. Is archive sink not recommended on production environments?



  6. PatRick says:

    According to Microsoft: "Only use Archive Sink for troubleshooting purposes because archiving may affect server performance and possibly fill up disk space. You must manually delete archived messages"

  7. Todd Derksen says:

    we have exchange version 6.0.6487.0

    is there a way to tell how up to date that is?

Skip to main content