Skip to main content

We recently upgraded from 8.73 > 9.31 and one of the things we noticed is our once-per-computer policies were running again on the computers as they cut over to the new JSS. We suspected our policy logs were being dumped on re-enroll.



Thanks to our JAMF sleuths (Tim H and Dan K), we ran some tests and it looks like we may have found a bug.



If we pull a JSS Summary we see:



Flush history on re-enroll fase


However, MySQL shows the opposite:



$ /usr/local/mysql/bin/mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 1264
Server version: 5.5.36-log MySQL Community Server (GPL)

Copyright (c) 2000, 2014, Oracle and/or its affiliates. All rights
reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or 'h' for help. Type 'c' to clear the current input
statement.

mysql> use jamfsoftware;
Database changed
mysql> select flush_management_history_on_remanage from
mac_os_x_enrollment;
+--------------------------------------+
| flush_management_history_on_remanage |
+--------------------------------------+
| 1 |
+--------------------------------------+
1 row in set (0.01 sec)

mysql>


So if you're going to migrate, make sure you check MySQL to make sure you won't lose your logs.



HTH,
Don

On my 9.4 test-JSS the summary doesn't seem to reflect my changes to the DB



external image link



external image link


@Chris][/url][/url,



I know it's a bit of a silly question but, after you made those changes in MySQL, did you restart Tomcat before running the Summary?



Amanda Wulff
JAMF Software Support


@amanda.wulff Yup, restarted Tomcat, and then the whole server, just for good measure


@Chris



Noted! I just wanted to make certain that was done before I dropped one of my test machines back to 9.32 to test whether or not the display discrepancy requires toggling the option off and on again (or on and off again) to get them to match up. In your case, if you flip flush_location_information_on_remanage back to 1, restart Tomcat, then flip flush_location_information_on_remanage back to 0 and restart Tomcat, does it reflect accurately in the Summary?



If it does seem to require manual toggling in MySQL to get the Summary to accurately reflect the setting, I'll create a new defect for that.



We did have a defect in 9.3x and, as part of it, we saw the Summary not accurately reflect the setting in the database (typically, it reported false when management history flushing was set to true), but that is listed as fixed in 9.4.



Thanks!
Amanda Wulff
JAMF Software Support


I noticed there is also a 'flush_management_history_on_remanage' setting in the 'client_check_in' table now. Is this where we should be changing this setting in 9.4+?



It seems like this should be an enrollment setting to me, but it is listed under Check-In in the JSS Summary.


@amanda.wulff][/url i just tried switching both flush_management_history_on_remanage and flush_location_information_on_remanage to 1 and then back to 0, restarting Tomcat after every change.
My summary did not pick up any of the changes, however the changes definitely take effect as expected.


Ok, now i think i know where i'm wrong:



The table "enrollment_settings" i was modifying applies to User-Initiated Enrollment, which apparently includes QuickAdd packages created by Recon.
Including "User-Initiated Enrollment" in the summary displays the correct values from the "enrollment_settings" table



The table "client_check_in" applies to the Check-In section of the JSS summary.
These settings seem to be used when enrolling a client during Imaging.



@amanda.wulff can you confirm that? Sorry for the confusion.


@Chris



No worries there, it stumped us for awhile as well, but that does look like that's the difference between the two tables and what they do/where they show up on the summary.



One set shows up under the User Initiated Enrollment section of the summary, the other, as you saw, under Check-In.
A couple of us had a, "Wait, why would it do that at check in?" moment when looking into it because of that.



I think it was the wording in terms of where they show up and the table names that gave a little head-scratching pause.



Amanda Wulff
JAMF Software Support