Run the MySQL Installer again – this time, you’ll see that MySQL Server has gone. Once the process is complete, if you’re prompted to reboot, do so. You did take a backup of the my.ini file in there, didn’t you? It’s up to you if you wish to do this – there’s no harm leaving it behind apart from it taking up disk space. It contains your databases and configuration. You’ll be asked if you want to remove the MySQL Data folder for MySQL Server 5.6. Tick the “MySQL Server 5.6.xx” entry and click Execute, then confirm that you really are sure. Depending on your setup, you may have other items listed – I tend to have Workbench as it’s really useful for monitoring database activity and troubleshooting. If you are running the most up-to-date version, you won’t see the yellow circle/arrow icon either. Click Cancel to get to the main installer window above. If you’re not running the most up-to-date version of 5.6, you’ll be thrown straight into an upgrade installer for it. Run the installer – you should see a dialog like this: We’ll use the installer to remove MySQL 5.6 and then install MySQL 5.7. That’s just the installer, not MySQL Server! Now, download the MySQL Server installer from – don’t worry about it being 32 bit. The default location for it is here: C:\ProgramData\MySQL\MySQL Server 5.6\my.ini Next, let’s take a copy of our current MySQL settings file, just in case we need to reference it later (folks often alter things here for their specific environment). This may take a little while depending on the size of your database In the Database Utility, click Save Backup Now and choose where you want to save it. Now you only need to right-click that file and select “Run as administrator”. Handy hint: to make things quicker for next time, stick that command in a text file and save it as “JSS Database Utility.bat” on your Desktop. Next, issue the following command (assuming that you installed the JSS to the default location): java -jar "C:\Program Files\JSS\bin\JSSDatabaseUtil.jar" I found the only way to do this was to open a Command Prompt as administrator – hit the Start menu and search for ‘cmd’, then right-click and select “Run as administrator”: You need to run it with local administrator privileges. Jamf provide a little Java utility for this (I think it uses mysqldump) – if you installed your JSS to the default location, it’s in: C:\Program Files\JSS\bin\JSSDatabaseUtil.jar You’ll probably find yourself coming back here quite often… Right-click the “Apache Tomcat 8.0 Tomcat8” service and choose Stop. This is where we can control all the services running on our server. Click Start, Administrative Tools, then launch the Services application. We don’t want the database being changed whilst we’re working. I’d love to hear from you if you’ve got any comments/suggestions – drop a comment at the bottom of the post! There may be other ways to do this – here’s what I did. You do have your MySQL database user (default name is jamfsoftware) password to hand, don’t you? You’ll need it later… Finally, I’m assuming that your MySQL Server data folder is in the default location (C:\ProgramData). That’s good but we want new shiny MySQL Server 5.7 goodness bestowed upon our green and pleasant land. We’ve just upgraded our JSS to version 9.98 and the humongous database migration/changes it made were successful and everything is working. I’m also assuming that we’re running MySQL Server 5.6 and the Java JDK 8. I’m assuming that we’ve got a single server environment (not clustered) and that we’re running Windows Server 2012R2. Surprisingly, Jamf don’t provide much in terms of documentation for this specific activity, but the move to MySQL 5.7 will be something admins will have to consider as Jamf Pro evolves on its way up to version 10. What follows is how I did it in a Windows Server setting. I’m deliberately avoiding the word ‘upgrade’ because it’s more like an uninstall and re-install, with a few steps in between. In the interests of future proofing as well as satisfying my little OCD monster, I decided to migrate to MySQL 5.7 as well. I’m running 5.6 and successfully upgraded my Jamf Pro Server to 9.98 in our development/test environment. You’ll likely have MySQL 5.5 or 5.6 installed. Prior to version 9.98, MySQL 5.7 was not recommended. The eagle-eyed amongst us may have noticed a change to the system requirements deep within the documentation: Jamf released version 9.98 of its Casper Suite/JSS Jamf Pro management suite last Thursday.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |