'Synchronize assigned user with calculated user' is not working
'Synchronize assigned user with calculated user' is not working
Summary
In FNMS System Settings > Inventory, you have selected the 'Synchronize assigned user with calculated user' option, but the assigned user is not being populated with the calculated user automatically.
Symptoms
In FNMS System Settings > Inventory, you have selected the 'Synchronize assigned user with calculated user' option. With this option, when the calculated user is updated for a device, the assigned user is also updated and this is a one-way relationship: changes to the assigned user do not affect the calculated user. Despite the option being enabled, the assigned user is not being populated with the calculated user automatically.
Cause
When the system setting 'Synchronize assigned user with calculated user' is enabled, two settings are enabled, one of which is a hidden setting that informs the Compliance Importer to synchronize the assigned user with the calculated user for every computer, essentially performing a full update. This hidden setting fails to be enabled on versions of FNMS prior to 2020 R2, and thus previous devices are never synchronized. By manually enabling the hidden setting 'RecalculateAllCalculatedUsersNextImport' this forces the full update to take place.
After import has completed, the hidden setting is reverted to 0 so that the full update is not performed each time the import runs. This is beneficial for performance reasons, as there are database triggers in place that should ensure the synchronization continues on a computer-by-computer basis.
In FNMS 2020 R2, the issue relating to the hidden setting not being enabled, thus not resulting in a full synchronization has been resolved.
However, in some circumstances there may be cases whereby the database triggers designed to update each computer record may still not work as expected. In this case, please raise a support case with Flexera to investigate.
Steps To Reproduce
Enable the 'Synchronize assigned user with calculated user' and run a Compliance Import. You will notice the Assigned User value is not changing.
SELECT @AssignedUserSync = CASE ISNUMERIC(SettingValue) WHEN 1 THEN CONVERT(bit, SettingValue) ELSE 0 END FROM dbo.ComplianceTenantSetting WHERE SettingNameID = 67 -- 'RecalculateAllCalculatedUsersNextImport'
And:
UPDATE dbo.ComplianceTenantSetting SET SettingValue = '0' WHERE SettingNameID = 67 -- 'RecalculateAllCalculatedUsersNextImport'
In both lines, please change the 67 (highlighted in red) to 66 and save the file.
The next Compliance Import should now update the Assigned User to the same value as the Calculated User.
Additional Information
If you are using FlexNet Manager Suite Cloud, please log a support case and if applicable, we will make the above changes.
From reporting that I can see, this problem is not showing up as being fixed in either the 2019 R1 or R2 release.
Be aware that the resolution described in this article will only be possible to apply with FlexNet Manager Suite On-premises; the resolution described will not be possible with FlexNet Manager Suite Cloud.
@WStephans unfortunately I can't see any plan to fix this on FNMS Cloud (yet). You can log a ticket to Flexera Support to get the workaround applied for your organization.
@dennis_reinhardt - in @WStephans' case the fix was actually a configuration change made in the backend of FlexNet Manager Suite Cloud, which the Flexera Support team was able to arrange. For FlexNet Manager Suite On-premises, the workaround described in this article stil applies to the 2020 R1 release.
@vmarinaro - when it is working, the synchronization would normally occur daily. However obvious if the problem described in this article has not been fixed on your system then the synchronization would never occur.
