![]() Don't try to run it, as also on Windows this is a Command Line Tool. Or for Windows, just have a look at C:\Program Files\JSS\bin\jamf-pro.exe Note: Just check if the exe file is there. This should give you the path of the Jamf Pro Server Tools: /usr/local/bin/jamf-pro To do this, just run the following command (Linux or macOS): $ which jamf-pro The first thing to do before you can use the tool is: right – check if it’s installed. It’s compatible with all Jamf Pro version 10.0.0 or later and replaces the Jamf Pro Database Utility. This has been around since Jamf Pro 10.7 and is automatically installed in the bundled Jamf Pro installer ever since. I’m talking about the Jamf Pro server tools. ![]() But since Jamf Pro 10.7 there is a nice new tool available! No, I’m not talking about the Jamf Database Utility … For different reasons, and this is my personal opinion, I’ve never been a big fan of this tool. But why would you make your live more complicated than necessary if someone already did the heavy lifting for you? Yes, Jamf already provides you with a tool to do all of this without too much effort! So the only thing you really need, to avoid the ultimate disaster, is a backup of that precious mySQL database.įor sure you could use the native ‘ mysqldump‘ command to make the backups, and schedule them via a cron job. This means that all your Jamf Pro settings, profiles, policies, device inventory, etc are stored within that mySQL database. ![]() Except server level settings such as the server.xml, database.xml or any other Tomcat tweaks of course. The full server backups will of course depend from your (virtual) infrastructure, so let’s limit this quick discussion to database backups only.Īs we all know, the entire Jamf Pro server lives inside the mySQL database. When things go horribly wrong, you’ll be able to restore the server backup, and replace the database with most recent backup. My strategy would be something like a full server backup before every upgrade of Jamf Pro (or any server level change), combined with at least a weekly database backup. Those are going to be smaller than a full server backup, and they also give you more flexibility when things go wrong. I would however still make sure I have separate backups of Jamf Pro database as well. As well as the Jamf Pro Database of course. A backup of the entire server includes the full setup and installation of Java, mySQL… Any customisation you made on a Tomcat level (when running Jamf Pro on a custom port for instance). So, what’s the story with your Jamf Pro server? Are you confident all is sorted out? Are you sure everything is running smoothly? Maybe it’s a good moment to have a look and check again.įor sure, you could backup the entire machine, which is, especially for VM’s quite a straight forward thing to do. And if you fancy to keep your job in 2019, you might want to think about backing up this oh so important little server. If you are hosting your own server however, you have the important responsibility to do this yourself. Jamf has some powerful wizards on their payroll who are taking care of all this for you. If you’re using Jamf Cloud, you have nothing to worry about. I still have some pending tutorials in mind, but before diving into another long topic, what’s better to start a new year than to start with some good practices? You know, like those resolutions we tend to make following the festivities each year… One of those could be making backups all those things you highly value. We are 1 week into 2019, and I was thinking about a new topic to kick this new year into action.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |