Posted on 02-03-2024 12:51 AM
I can provide more detail if needed, but I'm noticing a good amount of devices with last inventory updates of months ago or over 1 year ago. Is there a common theme to this sort of reporting issue or could this be due to a number of different things?
Before I dive in to this issue I wanted to ask the world instead of reinventing the wheel and wasting time. Troubleshooting has been minimal, I've just been correcting it with using scutil to set device names sudo profiles renew -type enrollment, sometimes I have to sudo jamf -removeFramework to re-enroll.
Thank you guys!
Posted on 02-05-2024 05:26 AM
Are the devices unenrolling or just no longer checking in? Unenrolling is something I have never heard of unless someone was actively doing something. No longer checking in is not entirely uncommon, if a device is not rebooted every week or so daemons like the Jamf will hang. Other things like certificates expiring can also cause this.
In most environments the -removeFramework argument is disabled as you normally set the flag to not allow the user to remove the Jamf binary. This in and of itself should not cause issues, but does raise questions.