Upgrading SQL Server to 2016+ while connected to an existing SEPM

Products

• Endpoint Security Complete

Issue/Introduction

Upgrading SQL Server to 2016+ while connected to an existing Symantec Endpoint Protection Manager (SEPM)

Environment

Single site
Multiple-SEPM site with SEPM replication

Resolution

To upgrade the Full SQL version while connected to an existing SEPM manager use the steps below: (NOT applicable to SQL Express)

It is STRONGLY RECOMMENDED this process is tested in a testing environment first, before being done in Production to ensure 100% success.

Single site: 

1. If your SQL server uses TLS 1.2, ensure that new version of SQL Server supports TLS 1.2 as well. 
2. Take a SEPM DB / SQL database backup (from each site before continuing)
3. Stop the SEPM services for "ALL" SEPMs sharing the same SQL Database "yet" to be upgraded.
4. Perform your in-place SQL upgrade per Microsoft Best practices and reboot the SQL server.
5. Next, on "ALL" your SEPM managers connected to the "upgraded" SQL server - update their SQL Client components (ODBC driver, command line utilities) mentioned in kb: (NOTE: This must be done before continuing with Step 6.)
   https://knowledge.broadcom.com/external/article/178648/install-sql-client-components-for-endpoi.html  (specific to your SQL version)
6. Only once you've updated the SQL Client components, will you need to reconnect the existing SEPM manager(s) to the SQL database after the SQL upgrade.  To do that, run Management Server Configuration Wizard on ALL SEPMs connected to your now "upgraded" SQL server 2022, AND Deselect the "use a recovery file option" to reconnect your SEPM manager to your database.
7. Provide any new paths for bcp.exe and then put in your same password (as before) and click Next.
8. Click Next until Management Server Configuration Wizard (MSCW) is done.
9. Test and make sure SEPM(s) are working as expected

Multiple-SEPM site with active SEPM replication

1. If your SQL server uses TLS 1.2, ensure that new version of SQL Server supports TLS 1.2 as well. 
2. Take a SEPM DB / SQL database backup (from each site before continuing)
3. Make sure SEPM Replication isn't running before you begin. (NOTE: If it will take a day or more to do this then consider suspending SEPM Replication for a week, or if it will be longer than a week, then consider deleting the SEPM replication partner from each site (NOTE: Don't delete the Remote Site). 
4. Stop the SEPM services for "ALL" SEPMs sharing the same SQL Database "yet" to be upgraded.
5. Perform your in-place SQL upgrade per Microsoft Best practices and reboot your SQL server.
6. Next, on "ALL" your SEPM managers connected to the "upgraded" SQL server - update their SQL Client components (ODBC driver, command line utilities) mentioned in kb: (NOTE: This must be done before continuing with Step 7.)
   https://knowledge.broadcom.com/external/article/178648/install-sql-client-components-for-endpoi.html  (specific to your SQL version)
7. Only once you've updated the SQL Client components, will you run Management Server Configuration Wizard on ALL SEPMs connected to your now "upgraded" SQL server version, AND Deselect the "use a recovery file option" to reconnect your SEPM manager to your SQL database.
8. Provide any new paths for bcp.exe and then put in your same password (as before) and click Next.
9. Click Next until Management Server Configuration Wizard (MSCW) is done.
10. Test and make sure SEPMs are working as expected
11. Repeat the above steps on your Second site #2. 
12. Once this is completed in both sites then un-suspend SEPM replication or re-add any deleted replication partners and then run SEPM replication after the above changes.
13. Next, monitor for any issues.

NOTE: For supported versions of SQL see this link: 
https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/release-notes/system-requirements-for-v53308029-d69e1453.html