Follow these steps to restore FlexNet Manager Suite databases on a new SQL Server instance and configure the FlexNet Manager Suite to use the new SQL Server instance. Some steps may need to be adjusted to fit your specific scenario or environment. 

TIP: Test and verify this procedure in a non-production environment before applying it in production to minimize downtime. 

NOTE: This article includes links to documentation from the FlexNet Manager Suite 2024 R2 release. If you are using a different release, refer to the corresponding sections in the documentation for that specific release, as there may be some differences. 

Step 1: Install and configure the new SQL Server instance 

1. Install and configure the new SQL Server instance according to your environment's requirements. 

2. Ensure the SQL Server instance meets all prerequisites for hosting FlexNet Manager Suite databases. Refer to: 

• • System Requirements and Compatibility > Prerequisite Software

  • Installing FlexNet Manager Suite On Premises > Create Databases (skip steps for creating the databases) 

Key points: 

• Use a version of SQL Server that is supported by the version of FlexNet Manager Suite you have.
• Enable Common Language Runtime (CLR) and install the Flexera signed security certificate from the same version of FlexNet Manager Suite as the databases. Using a certificate from a different version of FlexNet Manager Suite will likely result in errors later. 

Step 2: Restore databases  

Restore the following databases on the new SQL Server instance: 

• Database for FlexNet native inventory collection (the "inventory" database) 

• Operations database for compliance data (the "compliance" database) 

• Data warehouse database 

• Snapshot database 

Step 3: Update database connection string details in the registry 

1. On your FlexNet Manager Suite application server(s), locate the connection string details in the registry under: 

HKLM\SOFTWARE\WOW6432Node\ManageSoftCorp\ManageSoft\Reporter\CurrentVersion 

2. Update the following entries by changing the "Server=" values to reflect the new SQL Server instance details: 

• • DatabaseConnectionString

  • FNMPDWDatabaseConnectionString

  • InventoryDatabaseConnectionString

  • SnapshotDatabaseConnectionString 

Example: 

• Old value: Driver={SQL Server};Server=oldserver;Database=FNMSCompliance;Trusted_Connection=yes;
• New value: Driver={SQL Server};Server=newserver;Database=FNMSCompliance;Trusted_Connection=yes; 

Step 4: Run the Config.ps1 script 

1. Run the Config.ps1 script with the forceUpdateConfig argument on your FlexNet Manager Suite application server(s) to update configuration details. Refer to: Installing FlexNet Manager Suite On Premises > Configure the System. 

Example PowerShell commands to execute as the FlexNet Manager Suite administrator account to complete this process are:   

cd "C:\FNMSInstallers\FlexNet Manager Suite\Support"

.\Config.ps1 "Config\FNMS Windows Authentication Config.xml" forceUpdateConfig 

2. When prompted, review and update SQL Server instance details if necessary to reflect the new instance. 

3. Repeat this on all application servers if you have multiple. 

Step 5: Update connection details in the dbo.ComplianceConnection view 

The dbo.ComplianceConnection view in the compliance database contains records detailing connections to configured inventory sources. These records may include references to the old SQL Server instance in the Server column that need to be updated. 

1. Review current connection details: 

SELECT * FROM dbo.ComplianceConnection 

2. Update any Server values to the new SQL Server instance: 

UPDATE dbo.ComplianceConnection 

SET Server = 'newserver' 

WHERE ConnectionName = 'Your connection name' 

Step 6: Update connection details in any other local configuration 

Update any local configurations that reference the SQL Server instance, such as: 

• Business adapters that contain an explicit reference to the SQL Server instance details. 

• Custom scripts or processes that are configured to connect to one of the FlexNet Manager Suite databases. 

Step 7: Verification 

Changes made by the above steps will generally take effect immediately. To ensure the system is operating correctly after the changes, verify the following areas: 

1. Verify users can access the FlexNet Manager Suite web UI. 

2. Check logs in C:\ProgramData\Flexera Software\Compliance\Logging for errors related to SQL Server connection: 

• • BatchProcessScheduler

  • BatchProcessTask

  • Content

  • InventoryBeacons

  • WebResolvers 

3. Verify the System Tasks page for errors after daily and weekly tasks run.