![]() ![]() 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: Massive thanks to gabe2385 and junjishimazaki for their assistance.Jamf released version 9.98 of its Casper Suite/JSS Jamf Pro management suite last Thursday. If your company does not use logins verify that any login keys are removed). Verify Keychain Access keys are correct (publickey, privatekey, and login if used. Verify that the jss_url is correct in /Library/Preferences/ so it gave an unable to connect to MDM server error as a result. Further attempts to open Self Service were relying on those credentials and those were being denied by the server. Removing the login password from Keychain Access resolved the issue.įrom what I can tell, it seems someone tried to log into Self Service, and saved credentials which don't actually work there. We don't use the user logins on Self Service (it has been enabled for techs, but not for standard users and isn't built out enough for regular use). It is Keychain Access, but it's not the private or public key the user had a password enrolled for automatic login to Self Service. This information allowed us to further troubleshoot and we were able to find the issue! If anyone has any idea what this could be I'm open to further troubleshooting. Self Service appears to be the only thing affected. The Mac still has access to jamf controls via terminal, still receiving profiles and policies, still reporting in all information to the server. Issue is present both on and off VPN (so that is irrelevant).Ĭurrently this is only affecting the one machine but as I don't have a fix there's trouble if it spreads. I did find the list of ports, but we aren't seeing any blocked ports (on machine, router, or via ISP). also tested:Ĭomputer restart, trying from an IT account (removes any variables from the users startup items), refreshing the MDM, clean uninstall and reinstall of the JAMF Framework. There's a similar error "connecting to jamf server" which can be resolved by simply uninstalling and allowing JAMF to reinstall Self Service. We've been using JAMF for a few years mostly without issue - this is the first time we're seeing this error. The last post I can find relating to this is from 2017 There isn't a solution there and I've tried almost everything previously listed. ![]()
0 Comments
Leave a Reply. |