Page Comparison

Steps for Testing Jamf

Server after

Upgrade

Jamf provides us

with a sandbox server to test all updates and any new policies, profiles, and workflows

to

avoid affecting end users in case of issues. We closely collaborate with the ITSOs to

conduct testing in this environment.

Whenever Jamf rolls out a new version of the server, we

promptly install it

on our Sandbox for two weeks of extensive testing.

If any issues

arise, we can

request the

vendor to roll back the update and

postpone the deployment to the production server until the issue

is resolved.

Below are the testing procedures we follow after every new upgrade

:

1. Log into the server with both local and SSO accounts.
2. Run a recon on a system

1. assigned to the server to verify

1. its check-in status.
2. Push a policy to the test system to

1. ensure the package downloads and installs correctly.
2. Push a profile to

1. ensure proper installation of the configuration

1. .
2. Test an app using the Jamf app installer to

1. verify that the workflow is

1. functioning correctly.
2. Test an app using Apple Apps and Books

1. to confirm the connection to Apple School Manager works.

2. Reboot the test system and run a recon again to

1. ensure the above changes are reflected in the system’s record in Jamf.

These steps ensure thorough testing of the Jamf server after an upgrade, allowing us to identify and address any issues before deploying the upgrade to the production server.