Steps for Testing Jamf server Server after upgrade.Upgrade
Jamf provides us with a with a sandbox server to test all updates and any new policies, profiles, and workflows as to not affect the end users if there is an issue. We work closely with the ITSOs to test avoid affecting end users in case of issues. We closely collaborate with LAITS, TRECS, Engineering, and other ITSOs to conduct testing in this environment. When jamf Whenever Jamf rolls out a new version of the server, we immediately have promptly install it installed on our Sandbox for two weeks of extensive testing before deploying it on the production server. If any issues are foundarise, we can have request the vender vendor to roll back the update and delay postpone the deployment to the production server until the issue can be is resolved. Below are the testing procedures we follow after every new upgrade.:
- Log into the server with both local and SSO accounts.
- Run a recon on a system that is assigned to the server to verify that it checks inits check-in status.
- Push a policy to the test system to make sure ensure the package downloads and installs correctly.
- Push a profile to make sure ensure proper installation of the configuration installs.
- Test an app using the Jamf app installer to make sure verify that the workflow is workingfunctioning correctly.
- Test an app using Apple Apps and Books make sure to confirm the connection to Apple School Manager works.
- Reboot the test system and run a recon again to make sure 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.