Microsoft Exchange Server - Change History

TKU October 2008

Introduced Registry Versioning for Microsoft Exchange Server. When successful, this method enables the pattern to retrieve any product version of the product, ranging from 4.0 up to 2007 SP1.

TKU November 2008

The following improvements were made:

• Added checks to make sure that one of the trigger processes does not cross-match with VERITAS DirectAssist.
• To assist reporting, if a version is unknown, then the 'full_version' string is set to an empty string, not 'Unknown'.

TKU July 2010

The following improvements were made:

• Re-worked the pattern to improve support for Exchange 2007 / 2010.
• Instances that do not include the Mailbox Server role are now recognized and modeled.
• Versioning for Exchange 2003 and earlier and 2007 and later is now performed in separate code sections.
• Added a server_roles attribute for Exchange 2007 and later server SIs to list all server_roles that the Exchange Server is running.

TKU October 2010

The following improvements were made:

• Improved detection of Exchange Server 2007 and later versions.
• Resolved an issue with a missing default value of the version mapping table.

TKU December 2010

Updated the code and table mappings to enable the edition detection of Exchange Server 2000 and 2003 based on information provided by the customer.

TKU March 2011

Improved detection of Client Access Server Role that is present on Exchange Server 2007 and later versions.

TKU February 2012

Added checks to make sure that one of the trigger processes does not cross-match with Hewlett Packard Motive Chorus.

TKU March 2012

Improved registry versioning for versions 2010 and 2010 SP1.

TKU May 2012

Updated the pattern to attempt to obtain edition information for modern versions of the product.

TKU August 2012

Improved the way in which the pattern obtains edition information for modern versions of the product.

TKU December 2012

Updated the pattern to make sure that mapping of multiple attributes to Atrium CMDB BMC_Product CI matches Atrium Product Catalog Data (as published by BMC Software).

TKU February 2013

The following improvements were made:

• Bug fixes regarding the way in which PowerShell commands are called.
• Updated the trigger processes and registry versioning to correctly model Exchange Server 2013.
• Added path versioning and package versioning.

TKU May 2013

Added version 14.3 to the version mapping table.

TKU January 2014

The following improvements were made:

• Updated the way in which database availability groups are identified in modern versions of Exchange (version 2010 and later).
• Updated the trigger of the main ExchangeServer pattern.

TKU March 2014

The following improvements were made:

• Added details of cluster resources.
• Updated the PowerShell commands used to find editions for versions 2010 and later.

TKU July 2014

Resolved an issue with the discovery of the Microsoft Exchange Server running on a cluster with special characters (brackets) in a cluster name. 

TKU December 2014

Updated the pattern to work if the PowerShell command returns details of multiple DAGs.

TKU April 2019

The following improvements were made:

• Updated the pattern to use runCommand functions.
• Updated the trigger (DRDC1-12893).

TKU December 2019

The following improvements were made:

• Updated the DAG node type to SoftwareCluster.
• Updated linking between DAG and Exchange Server SIs.

TKU April 2020

Improved product versioning for modern versions.

TKU December 2020

The following improvements were made:

• Improved the PowerShell commands used to find details of the Database Availability Group. 
• Resolved an issue with a product version for Database Availability Group.

TKU March 2021

Added new server roles.

TKU September 2021

Updated the pattern to prevent a possible ECA error.