The setting “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BigFix\Enterprise Server\UseRemoteDB” has a value set by default to “0”, if the BigFix database is local, or set to “1”, if the BigFix database is remote.
If i will export the old bigfix server registry key and then import it to new server (what kind of registry do I need to change aside from the registry keys mentioned above?
Are you migrating both the database server, as well as the BigFix Root Server? (It’s not clear to me why you’d export the old bigfix server’s registry keys and import them to a new server?..that would not be necessary if only migrating the BigFix database to a new remote SQL Server)
If you’re only migrating the database to a new remote SQL Server, the steps you’ve referenced provide good general guidance.
Note that it primarily comes down to 2 things:
pointing the ODBC DSNs to the migrated database on the new SQL Server
ensuring that the BigFix Services can properly authenticate with the new SQL Server and access the BigFix databases. For this portion, you can either leverage SQL accounts, or better yet a domain service account. If using a domain service account, ensure that it has local admin privileges on the BigFix Server, and sysadmin privileges on the remote SQL server, then run the BigFix Server services (ex: GatherDB, FillDB, Root Server, Web Reports, WebUI) as the domain service account.
With something like this, if you’re not comfortable with the steps, consider reaching out to Support and/or Services for more guidance and assistance.
Hello Aram. Thank you for your feedback and apologies for the confusion.
I am migrating as well the bigfix root server. is it still not necessary to export the old registry keys and import to a new server?
It looks like you’re referencing the migration procedure, but just in case, be sure to read through all the sections at https://help.hcltechsw.com/bigfix/11.0/platform/Platform/Config/r_mgrt_server.html especially the linked server backup and recovery procedures and using serverkeytool to decrypt, move, and re-encrypt the server signing keys.
Backing up & restoring the Registry keys is not necessary, but you should preserve a copy of them as a reference. You will need to recreate any client settings, as well as any server configurations such as Unmanaged Asset Importer, Server Plugin Service, or Download Plug-Ins on the new server. Some of the values are encrypted in such a way that they would not work if you copied them to the new server anyway.
As part of the server recovery, you would first restore the SQL database backups to the new server, then run the root server install on the new root. As part of the install when you specify the remote database, the UseRemoteDB registry value will be configured as needed, you shouldn’t need to change it.