We had this same issue in our environment. It started sometime after upgrading from 9.4 to 9.52, and persisted after upgrading to 9.6. It also persisted after removing all extension attributes.
A thorough audit revealed a few poorly configured smart groups, but correcting or removing these didn't fix anything either. It was only after going through and deleting almost every inactive policy that smart groups started updating normally after an inventory check. Unfortunately this wasn't done in a way to pinpoint the exact policy, but it's another thing to try for people experiencing this issue.
FIXED
First of all thanks to the people in this post!
It would have been nice to have been pointed here before the upgrade when i asked our jamf support manager if there was anything else i need worry about before upgrading.. but hey i should have done more research.
I had the same issue after upgrading the day before yesterday from versions 8.72 to 9.6. I managed to fix the updating of the groups thanks to this post. All is now flowing smoothly and i am happy about this.
Smart groups would not update what so ever. Even the smart groups i had made "JSS binaries updated" and "JSS binaries not yet updated" based on binary criteria would not update. Started to get very annoyed about this after maybe 3 minutes.
I had originally planned on doing a migration to a newly built server by deploying the quickadd.pkg from the new server which i had previously provisioned and set up all smart groups, extension attributes and policies for our environment. Unfortunately we have a BYOD system and rely on location information for smartgroups so this was not possible.
Anyway when i compared the EA's on the upgraded JSS to the preivously built test JSS i had there was an issue where a couple of values were set as integer instead of string. I corrected this but it did not initially fix the issue.
Since i had pretty much all of the EA's i needed working correctly in the test JSS that i could not migrate to i decided to delete all of the EA's on the broken JSS. I then downloaded the EA.xml files from the test JSS and uploaded them to the broken JSS, so replacing each one.
I deleted any smart groups that were based on extension attributes criteria. I deleted a load of smart groups based on versions of software i didn't need also. I probably deleted more smart groups than i needed to since i knew i could just recreate them anyway.
Once i was satisfied I ran an inventory update on the scope "All Computers" and switched off the screen and moved back to my Windows side of things and focused on SCCM 2012 for a while, which was strange since it's normally is a lot more stressful than Casper.
So after the inventory update completed on all machines i recreated a load of smart groups. Re-advertised a load of policies which now had no scope defined and created some test policies and based some test groups on package receipt criteria. All seems good. I have also enrolled a few more macbooks and all smart groups are updating accordingly.
Thanks to everyone who posted their issues and how/if they went about fixing it.
Ben
I've been on 9.52 for a while now, but am just now seeing that a handful of smart groups in our environment are not updating. Which makes me a sad panda. I'm hesitant to jump to 9.61 just yet, but I clearly need to test some things out to see why the smart groups are having issues.
We have also started to see this and it is now stopping us rolling out Yosemite due to the config profiles not being push out unless we use 9.5 or higher
my findings so far
9.24 SG Working
9.24 > 9.25 SG Working
9.25 > 9.3 SG Working
9.3 > 9.31 SG Working
9.31 > 9.32 SG Working
9.3 > 9.4 SG Working
9.4 > 9.5 SG NOT Working
We have a ticket open with support to try and find the rouge smart group.
Sorry for the duplicate post, but I also just found this thread.
I posted the following in https://jamfnation.jamfsoftware.com/discussion.html?id=12446
I'm working with JAMF as in 9.61, apparently there's a "Defect" (I call them bugs), where the smart group doesn't properly update. You simply edit the smart group, make no changes and just save, then click Done.
Voila! The smart group updates. Unfortunately, every time your policy relies on a smart group, you have to go onto the smart group scoped to that policy and edit/save it. Pretty annoying and I hope they fix it soon!
@chuck3000
Managed to fix issues after reading through this thread and searching our JSS and deleting dodgy extension attrributes, and smart groups based on those. Seems like one rogue group/ EA can cause issues with the rest.
@chuck3000
I second @BenDenham. To play it safe, I ended up deleting, analyzing, and recreating all of my EA's prior to upgrading to 9.61. So far my Smart Groups are still smart.
If you want to verify operation, try making some dummy receipts/smartgroups like I outlined 3 weeks ago in this same thread.
Just found the 5 rough EA an corrected them, re started TomCat and the smart groups are now working on 9.61.
All this time wasted looking for rough smart groups :-( thanks @BenDenham for the tip on EA i would never of found this looking in our smart groups.
Clarification question: are all SGs broken in these situations, or just SGs that are dependent on the 'bad' groups?
If the former - why?
All SG fail you have to manually and update, this is a bug that seems to be in 9.5 and above
(D-007887) with description 'Bad Criteria in One Smart Group Causes ALL Smart Groups to Not Automatically Update’
We're on 9.61 and for us the problem was indeed one bad SG (invalid criteria). Once I removed that SG all of my SG's started updating.
Me too, after I deleted all my old EA's and SG's the smart groups started working again : )
C
We just ran into this issue after we upgraded from 9.32 to 9.61. We were able to determine that it was one smart group which had "bad criteria" and was causing the rest of our smart groups to not update. Here are the details in hopes that this can help some of you solve this.
Smart Group - Sophos Not 9.1.7
Criteria - (Application Title has Sophos and Sophos Version is not 9.1.7)
Sophos Version is an Extension Attribute fed by this script:
#!/bin/sh
SophosVers=$( defaults read /Library/Sophos Anti-Virus/product-info ProductVersion )
echo '<result>'$SophosVers'</result>'
What it looks like is that when you bracket in the Application Title with an Extension Attribute it causes it to fail. When I generate a saved search with the same it produced a "page could not be found" error, that same as viewing the broken Smart Group's membership. When I run the same search with each criteria bracketed on its own, or without brackets, it works fine.
Ok, so if one bad smart groups can cause the problem, is an easy way to figure out which smart group of EA is causing the problem.
I can manually go through the smart groups, but how would I know that one had "bad criteria"? Since I think they all used to have "good criteria".
Tim
Well, I think I found my "bad criteria" by trial and error. Just wishing there was a better way to figure out which group was bad.
I just came across this thread as I was running into a similar issue on my server. I have yet to find the "bad" smart group and fix it, but I noticed this on my Licensed Software entries (which are essentially smart groups). We are on 9.65 and still having this issue so just wanted to let everyone know to also look at any Licensed software if you have that set up.
