November 15, 2018
ANNOUNCEMENT FROM BLUEPRINT ENTERPRISE PRODUCT MANAGEMENT
Page 5 of the Blueprint 5.2 R2 Upgrade Guide contains two statements that are potentially disruptive for sites running Blueprint Enterprise 5.2 R1 at any service pack level:
Please be aware that we are not dead-ending Blueprint Enterprise 5.2 R1 implementations. Rather, Blueprint 5.2 R2 is functionally equivalent to Blueprint 5.2 R1 with Service Pack 3; the only significant difference is that the installer for Blueprint 5.2 R2 supports Microsoft Windows Server up to version 2016 and Microsoft SQL Server up to version 2017. The following scenarios are presented in an "existing Blueprint 5.2 R1" environment:
Let's walk through each one.A Collector is being added, but the host operating system is Microsoft Windows Server 2016In this scenario, the only activity required is to:
A "technology refresh" event is underway, and all servers will be migrated to machines running Microsoft Windows 2016
The ultimate challenge is ensuring that the Analyst and database are migrated; Collector installations are straightforward in this scenario. Please visit https://pharos.custhelp.com/app/answers/detail/a_id/2211 for this process.
The database server software is being upgraded to Microsoft SQL Server 2017
There's really not much to do here. The database "support" for Blueprint 5.2 R1 is based on a new installation. Once installed, there is no ongoing check to ensure that the backend database is supported or not.
Retrieving data ...