After you verify the upgrade was successful, consider the following notices for performing any necessary post-upgrade procedures.
Upgrade considerations
Software catalog
The following notices relate to the replacement of the Flexera software catalog with the BMC software catalog:
Flexera software catalog applications cannot be mapped with BMC software catalog applications. After the master server is upgraded, all the software catalog inventories are purged. They will be populated again after the next device inventories upload.
If you are using the BMC Helix CMDB integration:
During the first import in the BMC Helix CMDB, after the master server is upgraded, all applications are regarded as new. Managed-Supported and Managed-Unsupported status will be reinitialized. You must set these statuses back for the licenses before exporting data for a CMDB import. In conclusion, if you use this method, capture the values set for Managed-Supported and Managed-Unsupported before you upgrade. This makes the process easier after the catalog is populated.
You must start the Delete Software job to delete the old entries, the Reconciliation & Merge job, and finally, the Purge job.
After an upgrade, you must manually update the Licensed Software linked to the Software Catalog. All the entries are removed but can be reconciliated using the dedicated wizard. A notification is available regarding this operation on the dashboard.
In case of existing queries based on Products, you need to deactivate them before upgrading, as the result of the query will be removed due to the new catalog, which could affect the groups where these queries are assigned.
If you are using compliance rules based on the software catalog, the catalog change could impact the results.