Good day folks, I am aware that this topic has been discussed many times in the pass on how to resolve duplicate computer generated by “Citrix Provisioning Services”. Then there is a new setting called “clientIdentityMatch” available in latest version of BigFix. However, there are customers reported back that this setting does not work on Citrix environment.
Is the a real youtube video demonstrated or going through the whole procedure to prove this setting will work on Citrix environment?
Is it just setting up “clientIdentityMatch=100” on BigFix console (1 single step) and it will fix the issue?
Then you have steps described in this doc link below are so confused as it seems that there are too many steps involved just to enable this setting. Can someone re-define the steps more clearly to address this duplicate computer issue in Citrix environment? Thanks and appreciate it.
This advanced option can help you to avoid having duplicate computer entries when the endpoints are detected as possible clones by the BigFix Server. Starting from BigFix Version 9.5.7, the BigFix Server can use the existing computer information to try to match the identity of a Client and reassign the same ComputerID to computers that might have been rolled back or restored. To guarantee the correct applicability of this option, it is necessary that the following components are at least at 9.5.7 level:
The BigFix Server.
All Clients that will apply the option.
All Relays that are in the configuration tree between the Clients and the Server.
If clientIdentityMatch=0, the BigFix Server performs strict clone detection. This means that, if the BigFix Server receives a registration request from a Client that was rolled back or restored, the Server invalidates the old ComputerID, resets the old Client definition, and assigns a new ComputerID to the registering Client. This is the default behavior and is the same way the BigFix Servers earlier than V9.5.7 operate.
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.