Documentation

Other

Jamf Nation, hosted by Jamf, is a dynamic and knowledgeable community of
Apple-focused IT admins and Jamf Pro users. Join us in person, in October, for the annual Jamf
Nation User Conference (JNUC) to discover new and better ways to manage Apple devices.

On-Prem Jamf Customers Upgrading to v9.98

Overview

If you have run v8.0 or v8.1 of Jamf Pro, follow the instructions in this article before upgrading to v9.98. This will help determine whether your environment is affected by an issue that has no impact to functionality but causes increased error logging in your JSS when inventory records are updated.

Procedure

First, run the following command and query to see if the unique key constraint exists in the serial_number field of the certificate_authority_issued table:

use YourDatabaseNameHere;

SHOW KEYS FROM certificate_authority_issued WHERE Non_unique=0 AND column_name='serial_number';

If "1 row in set" is returned, the constraint exists. If "empty set" is returned, the constraint does not exist, so do not proceed.

If the unique key constraint exists, do the following:1. Back up your database.2. Remove the constraint and the index to which it's attached by running the following command:

ALTER TABLE certificate_authority_issued DROP INDEX serial_number;

3. Put the index back into the database by running the following command:

So in clarification, if it returns "empty set", I should be okay to proceed with an upgrade? Not planning on it for a week or two, but figured I'd get prep steps ready.

This database started out years ago at Casper 8.6, but has been patched, upgraded, re-hosted on a different platform and migrated 2-3 times since then. I ran the command on it and received the following:

This sounds like I should not get snagged on this, but figured I'd seek clarification.

@blackholemac - That is correct. This issue would only impact people who at one point were on 8.0 - 8.1, and running that command and getting an "empty set" ensures that you're not in a state where these errors would appear in your log. So it looks like you're good to go!