Computers are showing as updated in Snow License Manager (SLM), but the user details and application update, e.g. last run, are not updating.

Inventory shows an up to date scan and recent usage by a different users, but they are not appearing in Snow License Manager (SLM).
 

Snow License Manager 9.xx

The issue has nothing to do with the quarantine management.

Testing snowpacks in our test environment shows correct results and bring all the associated users of the machine in Snow License Manager.

The users comes into DataUserAccount, DataLoginUser and Datametering. It is also attached to the computer in DataClient.

But when running the Data Update Job (DUJ) the user then moves to SnowInventory.slm.inv_tbluser and to SnowLicenseManager.inv.tbluser.

It never gets put into the mapping table, SnowLicenseManager.inv.tblUserInvSlmMap and therefore never moves on to tblUser for customer environment but works in test environment.

It turns out that the User_exclusion rule setup in SMACC has an underscore added in the rule _. And any user that has underscore was being excluded from coming into SLM database.

The issue described here was due to a wrong configuration (the pattern for excluded users was missing square parenthesis around the underscore - it was “_“ instead of the correct “[_]”).

Users were not being sent to Snow License Manager (SLM) due to a mistake in the setup of the exclusion rules, the square brackets (parenthesis) around the underscore were missing causing the exclusion to treat it like a wildcard and filtering out more users than intended.

The solution is to change the user exclusion rule and include the underscore within square parenthesis.

Wrong configuration of user exclusion rules.