User Device Affinity Client Config not being updated

Maybe I am misinformed about the client settings, but we mad ea change to the User Device Affinity over two weeks ago and the client logs are still reporting the old settings. Below are all the pertinent details:

- We have a separate client policy that is deployed to all system with a higher priority over the default.
- The Client policy polling interval is set to 60 minutes (Is this what determines how often the client checks in for policy?)
- The longest time cycle we have configured for anything including hardware and software inventory is 1 day
- The original Affinity setting we had configured was 4 days 60 minutes
- The new setting is 30 days 60 minutes
- The change was made on roughly 1/23/2015

Here is a sample of a UserAffinity.log file:

>>>>>>Starting processing user affinity usage task<<<<<< UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Auto affinity threshold settings Days = '4', User minutes threshold = '60', Auto approve affinity = '1'. UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Clean up agents user logon events... UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Retrieving user minutes map... UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Loading approved and pending user affinities... UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Checking if any pending affinity is approved... UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Checking usage minutes per user against current minutes threshold... UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
User 'production\usera' has 1172 usage minutes UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Setting auto affinity for user 'production\usera'. UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
Found same state message existing. (was sent before) Skip sending same state message for user 'production\usera'.. UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)
>>>>>>Finished processing user affinity usage task<<<<<< UserAffinity 2/3/2015 7:11:09 PM 7472 (0x1D30)

As you can see the old affinity policy is still in affect... Do we need to delete the deployment and redeploy this to all systems? I really would rather not do this as I am unsure of the consequences of the Default policy taking affect even if for a short while...

Thanks

Tony

February 3rd, 2015 5:32pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics