I would strongly recommend you create a list of the work you will need to do, and in what order. There are potentially a great many tasks and steps you would need to follow in order to minimise any issues with the upgrade path it can be easy to forget something, or perform a step in the wrong order. If you go ahead with this, we would suggest cutting all internet access to the test/development server to ensure the restored backup instance cannot send any MDM or other commands out to devices or Apple. It will also give you the opportunity to ascertain whether your backups are good and usable. ![]() This should give you an idea of the time the process may take and any issues you might come across. It is possible to take your last database backup (you are backing it up, right?), restore this to a second test or development Jamf Pro server and run through the upgrade process in isolation. How long should you plan for? Test the upgrades in another environment Plan for this as part of your downtime and in your playbook for the upgrade work. Depending on the changes and size of your database, these can take a long time – occasionally more than an hour or two. Some Jamf Pro upgrades make large changes to the database when the Tomcat service is started up. The release notes for each version can be found here: Jamf Pro release notes.Ī good example is the few tweaks Jamf has made for the APNs changes over recent releases (more information on that from our blog here: Upcoming changes to Apple Push Notification Service (APNs) protocol). Review the release notes pages for each version of Jamf Pro you will be upgrading to for any known issues or changes that may affect you. Review each version’s release notes for changes
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |