Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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 as to not affect the end users if there is an issue.  We work closely with the ITSOs to test in this environment.  When jamf rolls out a new version of the server we immediately have it installed on our Sandbox for two weeks of extensive testing.  If any issues are found, we can have the vender roll back the update and delay the deployment to the production server until the issue can be 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 that is assigned to the server to verify that it checks in.
  3. Push a policy to the test system to make sure the package downloads and installs.
  4. Push a profile to make sure the configuration installs.
  5. Test an app using Jamf app installer to make sure that workflow is working.
  6. Test an app using Apple Apps and Books make sure the connection to Apple School Manager works.

  7. Reboot the test system and run a recon again to make sure the above changes are reflected in the system’s record in Jamf.


Search UT EPM Documentation
Get Help

EPM is available to IT Support Organizations (ITSOs) with any endpoint management questions. If you have a question about a specific endpoint client, please reach out to your local endpoint client support organization.

SERVICE STATUS

Planned Maintenance

  • ConfigMgr: Every Tuesday, from 6 a.m. – 10 a.m.
  • Jamf: Every Tuesday, from 8 a.m. – 12 p.m.








  • No labels