Installing iLMT after migrating main BigFix server

1

I need to migrate our w2k12 Bigfix server to a new w2k19 server and want to try the procedure mentioned above (using the same masthead file).

The procedure https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Config/t_mgrt_rootapp_server.html looks simple and straightforward, but I miss the procedure of how to continue to get iLMT working again on the new server after the migration.

I want to verify we have to perform a new installation of iLMT, so treat it if it’s a new iLMT with new database etc.

Thanks!

2

Your question is not clear.
Are you planning to discard existing ILMT and install an entirely new ILMT application after BigFix migration?
Is any information from current ILMT need to be migrated?

If it will be a completely new ILMT installation, then use the following end-to-end checklist and the links:
https://www.ibm.com/docs/en/license-metric-tool?topic=installing-license-metric-tool-bigfix-end-end-checklist

There are other links on the same portal for migration of existing ILMT to a new server.

3

There is some documentation available from IBM:
https://www.ibm.com/docs/ru/license-metric-tool?topic=SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/probdet/t_migrating_lmt_bigfix_between_machines.htm

4

Thank you very much, your link and these 2 helped me to get the job done:

https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Config/t_mgrt_rootapp_server.html
https://www.ibm.com/docs/en/license-metric-tool?topic=upgrade-reinstalling-license-metric-tool-existing-database

5

@ssakunala - Tagging onto this thread. We were forced to uninstall/reinstall BigFix for a small ILMT implementation, as the version they were running was out of support, and would not upgrade with the 9.5 installer. We successfully installed BigFix 9.5 using the existing masthead.

Now the Data Source definition for BigFix will not connect based on a database validation error:

database is from a different deployment (expected epoch 2020-03-23 17:59:39 UTC, got 2023-04-07 17:22:50 UTC)

Can this be corrected by setting the resynchronize_datasources_once parameter to true?

6

Hi @itsmpro92, Please check the following link to use the “Migrating between Data Sources” option.

https://www.ibm.com/docs/en/license-metric-tool?topic=computers-migrating-between-data-sources

Was the existing BigFix database reused or was a new database created? If a new database was created then the computer IDs will change and the above procedure should help.

7

Since we re-used the masthead, the Computer IDs didn’t change.

Edit: unfortunately, the Computer IDs did change, probably due to the DB upgrade…

8

The masthead have nothing to do with the computerID assigned to an agent.

The computerID is a unique number assigned randomnly from the server to an agent at registration time.

To ensure the computerID does not change it is required not only the machine an agent is installed on remains the same, but in addition ensure a set of further restrictions agent side … ( it is clear the database on the server need to be the same )

Otherwise there are a lot of reasons the server decide to reset the computerID:
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0022713

After a server migration, for the agent installed on the server it is simply impossible the computerID remains the same. For other agents in the deployment, having followed the steps indicated in the documentation, no new computerID should have been generated.