In TKU November 2010 we added additional information on known versions to the lookup table. In addition, version information is now not taken from a package name matching 'Visual Studio'.
In TKU November 2011 code was added to ensure that version information is not taken from a package name matching 'Administration Toolkit'. (QM001726981)
In TKU March 2012 Pattern updated to model relationship with content DB. (QM001725982)
In TKU May 2012 pattern has been updated with an improved version mapping approach to help handle more recent versions of the product, as well as improving the active versioning methods and the code to create relationship to MS SQL Server SI
In TKU September 2012 additional version mapping entries to account for version 2013 (preview) were added to enable correct full version to product (marketing) version mapping
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)
In TKU June 2013 the pattern was updated to use common code which determines the relationship between the SI the pattern creates and the related database SI. This change resolves the issue in the original code which could lead to this relationship not being created even if all the data was obtained (QM001785434)
In TKU September 2013 format of related_rdbms_sis_search() function was updated
In TKU December 2013 additional version mapping entries to account for version 2010 SP2 and version 2013(including updates) were added to enable correct full version to product (marketing) version mapping
In TKU July 2014, a new client-server relationship is created between the Microsoft Windows SharePoint Services software instance and the Sharepoint Configuration Database software instance.
In TKU October 2015, Versions mapping table was updated.
In TKU May 2017, was added an extra check to prevent "could not resolve endpoint" messages in the logs.