9.81 Installation Reports - Gotchas ?

Just did the upgrade on my dev and prod from 9.73 to 9.81 on Windows 2k12 without issue, very smooth. No issues to report on the client side either.

Smooth upgrade on Windows Server 2012. Self Services also works.

No issues on a Linux install on a cloud-based VM.
Not a lot of testing yet though...

No issues so far. Upgrade was fine on Win 2008r2. Self service is fixed here as well. Device based app assignment seems to work fine so far.

Our JSS upgrade (9.73 on Server 2k8r2 - clustered) encountered issues and the installer proceeded to "back out the changes" which broke Tomcat and Java.

Initial error message received:

Product: JSS -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. Custom action initTomcatAsUpgrade.vbs script error -2147024894, WshShell.Exec: The system cannot find the file specified. Line 273, Column 2,

Subsequent attempts fail as Java is no longer seen by the installer package:

Product: JSS -- The JSS requires Java 1.6 or later to be installed to function properly. Please verify that you have Java 1.6 or later installed and try running the JSS installer again.

I'll be rolling back to our snapshot for now... :/

RHEL upgrade from 9.72 to 9.81.

Pretty smooth upgrading the JSS and one clustered JSS. Upgrading the JDS was a little weird. The jds.conf file was overwritten and apache would not start. I had to do a little editing to get apache back up, but nothing major.

Overall happy at the moment...clients are checking in, Self Service is working. My site admins will be checking this out over the next week so we'll see.

Just upgraded to 9.81 from 9.73 on Server 2012 R2, no errors. We will see what happens tomorrow. Looks good so far!

9.8 to 9.81 went pretty smooth, broke the clustering, but found a JN post on now to fix it, so minimal impact there.

Since then I've noticed a problem with Config Profiles deploying to all machines when scoped to just one. Though, that could be my own fault - waiting on my jamf support case.

Also, I noticed composer wasn't displaying the popup for flat vs non-flat pkg file creation.

I've updated from 9.72 in our test environment to 9.81. One thing I've noticed is that I don't have the ability to add ("+" button) configuration profiles for OS X devices. I can edit existing profiles but no provision to add. I have that ability for the iOS side. Anyone else see this or is it just my environment?

So far, I can't seem to add or remove Dock Items using Casper Remote. Anyone else?

@Brad_G - It's OK here on a Linux VM...

We just upgraded from 9.73 to 9.81 to get support for iOS9. Installation went smoothly, but somewhere along the line our websites were turned off. Not sure where/how this happened and have not found a solution yet.

@Brad_G While I know it should not have been affected or changed, have you gone in to look at the privileges enabled for the account you log into your JSS with? Its possible the option to create Config profiles moved or changed in some way and just needs a check next to it to show up. Missing features after upgrades are kind of common because new or modified privileges don't get enabled automatically for accounts.

@Brad_G I know the Config Profiles New button disappears if you have Enable Push Notifications unchecked in the Security Pane of Computer Management.

Just a heads up to anyone who is upgrading to 9.81 and running Mac Server 5.0.4. You will need to go in and disable the 8443 on your mac web server to allow the JSS to maintain its web presence.

Same here. Only issue was the port 8443 problem on OS X Server 5 that @mschuring mentioned. Beyond that it was quick and painless and everything is working fine today.

JDS also will not install with Server 5.

Apple changed config file names with 5 which JDS expects to be there with hard coded values.

JAMF is working to resolve.

My Sandbox JDS on RHEL7 is non-functional after upgrading from 9.72 to 9.81. It syncs, files are present, but can't mount it. I'm still troubleshooting, but thank the tech gods for test environments.

@mtruskowski and @mschuring, how did you disable port 8443 on OS X Server 5, to preserve your JSS web presence?

@brandon.white What worked for me (based on this blog post, which has some really good info about gotchas in server 5) was going in to /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf and commenting out anything related to port 8443. After a reboot I was back up and running. This will break the calendar service, but we are not using it so no problem for us there.

Thanks @mtruskowski, that worked perfectly for me as well.

Update on my previous post of install fail - Ended up just migrating the servers and db I adopted here to new Win2012 VMs - no issues and things are faster... so definitely a win there. Figured the other server was gonna go at some point (no clue who set it up, but it was a mess), so I'm actually glad the install failed and pushed me to move it all over.

We had the same issue as @jreinstedler on one of a clustered servers, ended up cleaning the registry of all the TomCat key's which then after backing up the database & server files etc allowed us to do a clean install without issue and all is well.

Be aware that if you have a configuration profile that has Login Window preferences, if Auto Logout was not enabled before the 9.81 upgrade, it WILL be enabled after the upgrade (with a default of logging out users after 30 minutes of inactivity). I've verified this across 5 different production JSSes and make this change immediately post-upgrade (even before fixing any scripts or policies with the old jamf binary path)...

After seeing mostly good responses here I decided to upgrade. Went from 9.73 to 9.81yesterday. No issues on the upgrade part at all. It was a very quick install. Ran a few tests afterwards and all seemed fine. All seems good so far today.