We've recently become much more proactive in pushing updates to our users' machines. One thing we've set up is a handful of extension attributes that report back the installed version of the various programs. Most machines are reporting back flawlessly. Here's what one of those machines looks like:
Since this data had been populating for a couple of weeks, I decided to start targeting smart groups to it. Adobe Flash, for example, is targeted to machines where "Adobe Flash Player " is not <current version>. I then targeted an ongoing policy to push the newest Adobe Flash to machines in that group on Startup, Login, Logout, Network State Change, Enrollment Complete, and Recurring Check in. The policy is set to update inventory, so machines that are in the group should be removed from it after the policy runs. So for every new version, the machine should run the policy once and then stop being targeted by it.
When I came in this morning, I found that one machine had run the policy 40 times over night. It wasn't the only one to run it multiple times. I went into the extension attributes on it and found something very odd.
This machine had been checking in just fine, but it wasn't actually updating the extension attributes. Others are updating some, but not all of them. I did a search for "Adobe Flash Player is "(blank value) and found that roughly 18% of our machines were not updating that field. I haven't checked the rest yet, but I'm guessing it's about the same.
I can't figure out why most machines are filling stuff in just fine but these ones are not. OS version isn't a factor(happening to machines on 10.6-10.10). Affected machines are a mix of form factors. We're using JAMF 9.72.
Does anyone have any idea why some machines would update the Extension Attributes while others would not?
Just to confirm, do you mean the EAs aren't up to date but an inventory has successfully completed like in this screenshot.
As a test, I would un-enroll and re-enroll one of them and see if it updates.
