Hello Everyone!

I wonder how do you deal with ILMT and live virtual environments being “in-motion”, where VMs are often cloned, moved to other Data Center etc. which causes Agent ID to change.

It results in mess in both BigFix and ILMT reporting, showing computers duplicated, old Agent IDs becoming disconnected and new portion of software discovery attends to be confirmed… again. I always do manual cleaning, however maybe there is a better option.

Thank you for answers.

If you have BigFix 9.5.7 or higher there is an advanced setting in besadmin to resist the clients from duplicating: clientIdentityMatch=100

https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Installation/t_preserving_bundling_when_clientreinstalled.html?hl=clientidentitymatch

In “Avoid having duplicated computers when the BigFix client is rolled back or restored from a snapshot” chapter. If clientIdentityMatch=100, the BigFix Server performs an additional check before assigning a new ComputerID to a registering Client to avoid creating cloned computer entries. This means that the BigFix Server tries to determine if the information about the rolled-back Client sufficiently matches the data held for that ComputerID. If the identity of the Client is matched, the Client keeps using the old ComputerID and its identity is not reset.

You can configure the setting clientIdentityMatch=100 via BigFix Administration Tool

https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_running_the_tivoli_endpoint_ma_onlinux.html

To remove the computers that are already in place. https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Installation/c_clean_up_computer.html

Regards,