Blog Post

Exchange Team Blog
1 MIN READ

Dude, where's my rollup?

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Mar 09, 2010

So I just installed RU1 on my brand new Exchange 2010 server and then I issue a Get-Exchangeserver -Identity MyExchangeServer and get the following output for AdminsDisplayVersion and ExchangeVersion:

Ok that looks a little familiar for some reason. I go to my Exchange 2010 RTM server and issue the same cmdlet and get:

...The same result! But one server has RU 1 installed and the other is RTM. Shouldn't I get a different version number back?

Well... no. Exchange 2007 and forward do not reflect the version number either in the value for AdminDisplayVersion, ExchangeVersion, or at this registry key HKLM\SOFTWARE\Microsoft\v8.0\<Role>\ConfiguredVersion as influenced by roll ups. This is a common misconception.

The most conclusive way to get the version of your exchange server, rollup and all, is to check the file version of ExSetup.exe in the BIN folder.

Here is Exchange 2010 RU1 version:

And here is Exchange 2010 RTM:

Another way of getting this information is to run the following PowerShell one-liner:

GCM exsetup |%{$_.Fileversioninfo}

The below output is from an exchange 2010 server running RU1:

Here is an exchange 2010 RTM server:

You can then correlate the version number you find with those listed in Exchange Server 2007: Platforms, Editions, and Versions, Build numbers and release dates for Exchange Server or on the actual rollup update download pages.

Hope this post reduces some confusion out there!

Tom Kern

Published Mar 09, 2010
Version 1.0

18 Comments

  • @KB and @Klaus historically Exchange has never updated the version number in AD based on RU or hot fix.
    Recall in Exchange 2000/2003 the serialNumber attribute did not increment after installing a hot fix and thus ESM did not reflect a different build number as well.
    You still had to check the version of store.exe or excdo.dll etc to find what build you were really on.
    With Exchange 2007 and PS this information is decidedly easier to obtain.
    Thanks
  • I'm keeping a list of versions, dates and builds here
    http://eightwone.wordpress.com/versions-builds-dates/
  • Well, not supplying it anywhere in AD leaves some room for improvements in the future. Think positive, folks.
    OK - for orgs with 3+ servers all over the world you have to make sure all lines are up prior to running the "home-made-script".
    Which indeed happens almost once a year...
  • You can also check the version from the Exchange Management Console by going to Help --> About Exchange Server 2010...  as shown here:
    http://blog.elieb.info/2010/03/06/exchange-2010-with-ur2-installation-in-unattended-mode.aspx

  • Here is a list of Product Version Numbers (actually Update Rollup version) on TechNet Wiki
    Exchange Server and Update Rollups Builds Numbers
    http://social.technet.microsoft.com/wiki/contents/articles/exchange-server-and-update-rollups-builds-numbers.aspx

    (Updates regular)

    Also exist lot of "homemade" powershell scripts to get UR for 3+ servers

    But questions is why there no built-int script to get UR (version number) across whole exchange organization.

    Arman.


    Arman.
  • Also - RU2 was just released..   the Product Version and File Version for that are 14.00.0689.000.
  • I wish I could pipe get-exchangeserver to GCM exsetup - Any easy powershell for 3+ servers to make sure you patched them all?
  • I understand that this is the way things are, but is there any advantage to the way this was done?  Seems like it blocks a lot of the advantages to do something like get-exchangeserver and see across the organization what rollups have been applied.