50 posts tagged with "Change Request"

Change Request 1004432 Jamf Pro - Server Upgrade 11.31.1.

Description: Details of maintenance: We will be making the following changes the production server of our Jamf Instance:

Upgrading the Jamf instance from 11.30.2 to 11.31.1

Changing the log retention of policy logs/computer and mobile device management history logs from six months to three months

Benefit of Change:

The 11.30.2 update will have security and bug fixes: https://community.jamf.com/release-announcements-177/jamf-pro-11-31-1-now-available-58772

Changing the log retention will reduce a lot of the server degradation alerts we've been getting from Jamf

Will improve the performance of the server

Impact to customers: No impact to customers.

Change Request 994059 Jamf Pro - macOS 27 Deferral.

Description: Details of maintenance: We will deploying an OS block for macOS 27 ahead of the recently announced release date of 9/14/26. This will be a 30 day deferral. There will be a static group for people that decide to opt-out of the deferral.

Benefit of Change:

Will block the macOS 27 update for 30 days which will allow IT staff across the organization to conduct testing and make sure there are no major issues or broken compatibility.

Impact to customers: No impact to customers.

Change Request 957739 Jamf Pro - Server Upgrades.

Description: Details of maintenance: We will be making the following changes the production server of our Jamf Instance:

Upgrading the Jamf instance from 11.25.0 to 11.30.2

Changing the log retention of policy logs/computer and mobile device management history logs from one year to six months

Enabling Jamf Account (OIDC) authentication

Cancelling Failed Management Commands

Benefit of Change:

The 11.30.2 update will have security and bug fixes: https://community.jamf.com/release-announcements-177/jamf-pro-11-30-2-now-available-58681

Changing the log retention will reduce a lot of the server degradation alerts we've been getting from Jamf

Switching from SAML to OIDC authentication will allow us to enable blueprints which will be necessary for features such as OS blocks in the near future.

Will improve the performance of the server

Impact to customers: No impact to customers.

Change Request 937068 Jamf Pro - Test Server Upgrades.

Description: Details of maintenance: We will be making the following changes the test server of our Jamf Instance:

Upgrading the Jamf instance from 11.25.0 to 11.30.2

Changing the log retention of policy logs/computer and mobile device management history logs from one year to six months

Enabling Jamf Account (OIDC) authentication

Benefit of Change:

The 11.30.2 update will have security and bug fixes: https://community.jamf.com/release-announcements-177/jamf-pro-11-30-2-now-available-58681

Changing the log retention will reduce a lot of the server degradation alerts we've been getting from Jamf

Switching from SAML to OIDC authentication will allow us to enable blueprints which will be necessary for features such as OS blocks in the near future.

Impact to customers: No impact to customers.

Change Request 902930 Jamf Pro - Upgrading Jamf Connect to 3.11.0.

Description: Details of maintenance: The latest version of Jamf Connect is 3.11.0 and this update will upgrade eligible computers from 3.5.0 to 3.11.0

Benefit of Change: This will get devices on the latest version of Jamf Connect. From testing, it seems that devices that have 3.11.0 installed do not run in to the boot loop issue on 14.8.8. This change will allow us to remove certain people who agree to test from the OS block we are currently issuing, and find out if this solves the issue in our wider environment before the 30 day OS block expires.

Impact to customers: No impact to customers.

Change Request 885758 Jamf Pro - Deploying Proofpoint Version 4.4.3.

Description: Details of maintenance: The Proofpoint agent has been upgraded from 4.4.2.76 to 4.4.3. This change will be upgrading the version for targeted devices.

Benefit of Change: This will get devices on the latest version of proofpoint.

Impact to customers: No impact to customers.

Change Request 686152 SGPS - Migrating Elastic to TAMUS Cluster - JAMF Pro.

Description: We are ready to migrate the remaining SGPS devices to the TAMUS Elastic Cluster.

The following smart group will be added to the deployment scope. This will target all devices in the SGPS site that are currently enrolled in the Jamf server under Elastic Deployment V2 - SGPS (Full Site) https://tamu.jamfcloud.com/smartComputerGroups.html?id=-1&o=c

This scope will also include any new devices enrolled into the SGBS site via the existing prestage enrollments, ensuring they are automatically migrated to the TAMUS Elastic Cluster.

Change Request 681903 Jamf Pro - Update Privileges App.

Description: Details of maintenance: Update Privileges elevation tool to the latest version to enable updated security features and functionality.

Benefit of change: There are various benefits of the new version of Privileges. Here is the release page on changes made up to the latest version. https://github.com/SAP/macOS-enterprise-privileges/releases -Revoke admin rights at login

• Unified expiration interval for administrator privileges

• Renew expiring administrator privileges at any time

• Smart card and PIV token support

• Tamper protection (requires macOS 13 or newer)

• Run actions on privilege change

• Status item for the macOS menu bar

• Command line tool now supports Touch ID

• AppleScript support

• Webhooks

• Localized in 41 languages

• Elevate privileges by end user credentials for better security

• Send logs to Elastic when privileges change Impact to customers: The functionality of the customer device will be the same but the Privileges application UI has been slightly updated to a more sleek look.

Change Request 672431 CLLW - Migrating Elastic to TAMUS Cluster - JAMF Pro.

Description: We are ready to migrate the remaining CLLW devices to the TAMUS Elastic Cluster.

The following smart group will be added to the deployment scope. This will target all devices in the CLLW site that are currently enrolled in the Jamf server under Elastic Deployment V2 - CLLW (Full Site) https://tamu.jamfcloud.com/smartComputerGroups.html?id=1575&o=r

This scope will also include any new devices enrolled into the CLLW site via the existing prestage enrollments, ensuring they are automatically migrated to the TAMUS Elastic Cluster.

Change Request 672763 Jamf Pro - College of Architecture Device Site Change.

Description: We are moving the computers that belong to the College of Architecture to the Architecture site that was created for them.

We used Axonious to find the device ownership for all of our machines in the server and were able to get a list of 30 machines that have the following tag from Axonious: College: Architecture from this data source: Mssql: MSSQL_ Divcollegedesc.

The list has been giving to the IT Staff at the Architecture College which they have reviewed and approved the list.

Breaking computers out into their own site in Jamf is important because it allows for proper scoping, management, and security separation between departments. Sites ensure that devices receive only the policies, configuration profiles, applications, and restrictions intended for their specific college or unit.

By assigning computers to the correct site, administrators can prevent accidental deployments, reduce configuration conflicts, and maintain clearer ownership and accountability of devices. This also improves troubleshooting, reporting accuracy, and access control by limiting visibility and administrative actions to only the devices that team is responsible for.

Overall, proper site separation helps maintain a cleaner Jamf environment, reduces risk during deployments, and supports scalable device management across multiple colleges and departments