Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Steps for Testing Jamf
serverServer after
upgrade.Upgrade
Jamf provides us
with awith a sandbox server to test all updates and any new policies, profiles, and workflows
asto
not affect the end users if there is an issue. We work closelyavoid affecting end users in case of issues. We closely collaborate with the ITSOs to
testconduct testing in this environment.
When jamfWhenever Jamf rolls out a new version of the server, we
immediately havepromptly install it
installedon our Sandbox for two weeks of extensive testing.
If any issues
are foundarise, we can
haverequest the
vendervendor to roll back the update and
delaypostpone the deployment to the production server until the issue
can beis 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
- assigned to the server to verify
- its check-in status.
- Push a policy to the test system to
- ensure the package downloads and installs correctly.
- Push a profile to
- ensure proper installation of the configuration
- .
- Test an app using the Jamf app installer to
- verify that the workflow is
- functioning correctly.
- Test an app using Apple Apps and Books
- to confirm the connection to Apple School Manager works.
- Reboot the test system and run a recon again to
- 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.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|