microsoft/get-exchangebuildnumber

You can search build numbers of Exchange Server.

ExchangeBuildNumber PowerShell Module

You can search build numbers of Exchange Server. Not only that, but you can also get the relevant KB numbers and blog posts.

PS C:\> Get-ExchangeBuildNumber "2019 CU9"


Product Name : Exchange 2019 CU9
Build Number : 15.2.858.5
Date         : 2021/03/16
KB           : KB4602570
Blog         : https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2021-quarterly-exchange-updates/ba-p/2205283

Installing ExchangeBuildNumber PowerShell Module

The module is published on the PowerShell Gallery.

Install-Module ExchangeBuildNumber

Updating ExchangeBuildNumber PowerShell Module

Update-Module ExchangeBuildNumber

Example

If you want to know the build number of Exchange 2013 CU11, run the following command.

Get-ExchangeBuildNumber -ProductName "Exchange 2013 CU11"

If you want to know the product name of 15.0.1156.6, run the following command.

Get-ExchangeProductName 15.0.1156.6

If you want to update the definition file manually, run the following command.

Update-ExchangeBuildNumberDefinition

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

get-exchangebuildnumber's Issues

Build date parsing is faulty when locale is not set to US dates

Get-ExchangeBuildNumber/src/ExchangeBuildNumber/ExchangeBuildNumber.psm1

Line 203 in 20dd79b

return Import-Csv $FileName | Select-Object "Product Name", @{n = "Build Number"; e = { [System.Version]$_."Build Number" } }, @{n = "BuildNumberInt"; e = { $Version = [System.Version]$_."Build Number"; $Version.Revision + $Version.Build * 1000 + $Version.Minor * 10000000 + $Version.Major * 1000000000 } }, "KB", @{n = "Date"; e = { Get-Date $_."Date" } }, "Blog"

Since the dates in the CSV are formatted according to US standards (mm/dd/yyyy), Get-Date $_.Date only works when the locale is set to US. If the current locale has a different date format, this results in errors and null values.

Should use [DateTime]::Parse($_.Date,[CultureInfo]::CreateSpecificCulture('en-US')) instead.

For instance, if the default locale is set to nl-BE, this happens:

PS> [DateTime]::Parse('12/10/2022')
woensdag 12 oktober 2022 0:00:00

PS> [DateTime]::Parse('12/10/2022',[cultureinfo]::CreateSpecificCulture('en-US'))
zaterdag 10 december 2022 0:00:00

PS> [DateTime]::Parse('12/19/2022')
Exception calling "Parse" with "1" argument(s): "String was not recognized as a valid DateTime."
At line:1 char:1
+ [DateTime]::Parse('12/19/2022')
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : FormatException
 
PS> [DateTime]::Parse('12/19/2022',[cultureinfo]::CreateSpecificCulture('en-US'))
maandag 19 december 2022 0:00:00

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Exchange build numbers not updates since 01/2023

Can the buildnumbers file please be updated, it is now almost 1 year behind on current releases.

See #7

Include SU's in the list

I was looking for an Excel or CSV with all Exchange version numbers, and found this module, but it only lists the current CU level.
With more and more critical updates surfacing in between CU's lately, it would be very useful to also list/determine at what SU an Exchange server is.
Currently using IWR to parse the official build number list, but it would be very useful if it were added to this module.