2008

TKU Oct 2008

In TKU October we introduced Registry Versioning for Microsoft Exchange Server. When successful, this method allows the pattern to retrieve any version of the Product, ranging from 4.0 up to 2007 SP1.

For more information, please refer to the relevant section.

TKU Nov 2008

In TKU November the pattern has had checks added to ensure that one of the trigger processes does not cross-match with VERITAS DirectAssist.

In addition to this, to assist reporting, if version is unknown, then the 'full_version' string is set to an empty string, not 'Unknown'

2010

TKU July 2010

In TKU July 2010 the pattern was significantly revised to improve support for Exchange 2007 / 2010. Instances that do not include the Mailbox Server role are now recognized and modelled. Versioning for Exchange 2003 and earlier and 2007 and later is now performed in separate code sections. Exchange 2007 and later server SIs now also have 'server_roles' attribute added to the SI to list all server_roles the Exchange Server is running.

TKU Oct 2010

In TKU Oct 2010 the pattern was updated to further improve detection of Exchange Server 2007 and later versions. Furthermore, an issue related to the version mapping table not having a default value was resolved.

TKU Dec 2010

In TKU Dec 2010 the pattern was updated with code and table mappings to enable determination of edition of Exchange Server 2000 and 2003 based on information provided by the customer

2011

TKU Mar 2011

In TKU March 2011 the pattern was updated to further improve detection of Client Access Server Role that is present on Exchange Server 2007 and later versions.

2012

TKU Feb 2012

In TKU February 2012 the pattern has had checks added to ensure that one of the trigger processes does not cross-match with Hewlett Packard Motive Chorus.

TKU Mar 2012

In TKU March 2012 the pattern now has improved registry versioning for versions 2010 and 2010 SP1.

TKU May 2012

From TKU April 2012 the pattern attempts to obtain edition information for modern versions of the product

TKU August 2012

In TKU August 2012 improvements were made to way the pattern obtains edition information for modern versions of the product

TKU December 2012

In TKU December 2012 the pattern has had a minor update to ensure mapping of certain attributes to Atrium CMDB BMC_Product CI matches Atrium Product Catalog Data (as published by BMC)

2013

TKU February 2013

In TKU February 2013 the following changes were made:

• Bugs were fixed regarding the way powershell commands are called
• Updates were made to the trigger processes and registry versioning to correctly model Exchange Server 2013
• Path versioning and package versioning were added

TKU May 2013

In TKU May 2013 version 14.3 was added to the version mapping table.

2014

TKU January 2014

In TKU January 2014 there was a significant update to the way database availability groups are identified in modern versions of Exchange (version 2010 and later). There was also an update to the trigger of the main ExchangeServer pattern to improve coverage

TKU March 2014

In TKU March 2014 we made two changes:

• We added details of cluster resources
• We updated the powershell commands used to find edition for versions 2010 and later

TKU July 2014

In TKU July 2014 there was a bug fix for the discovery of the Microsoft Exchange Server running on a cluster with a special characters (brackets) in a cluster name (QM001850601). 

TKU December 2014

In TKU Dec 2014, the pattern was updated to support situation where powershell command returns details of multiple DAGs (QM001866145).

2019 to present

TKU April 2019

In TKU April 2019 the following changes were made:

• Pattern runCommands updated.
• Updated trigger (DRDC1-12893)

TKU December 2019

In TKU Dec 2019 DAG node type was updated to SoftwareCluster, updated linking between DAG and Exchange Server SIs

TKU April 2020

In TKU April 2020 we improved how we find product version for modern versions

TKU December 2020

In TKU December 2020 we improved the powershell commands used to find details of the Database Availability Group.  We also fixed a bug with now we find the product version for Database Availability Group

TKU March 2021

In TKU March 2021 we added extra server roles