- Jamf Nation Community
- Products
- Jamf Pro
- post 9.97.1488392992 upgrade issues?
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
post 9.97.1488392992 upgrade issues?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-14-2017 07:05 AM
Is anyone else seeing issues with the JSS after upgrading to 9.97.1488392992?
I've been having problems with users of the JSS getting kicked out to the login screen unexpectedly and with cached packages not appearing in inventory properly. I'm trying to figure out if it's just my local instance or a problem with this version of JSS.
Labels:
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-14-2017 08:35 AM
Yes we've seen that here as well. Working with JAMF (or was, haven't heard back for a couple days now) to isolate what it might be. Appears to be LDAP related from other posts here.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-14-2017 09:22 AM
I've just updated yesterday and had cached package issues yesterday as well. However, we haven't had any issues with users getting kicked out. Hopefully we'll hear something back on how to fix this.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-14-2017 01:15 PM
This has been an issue on AD bound sites since the previous release 9.97.1482356336.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-15-2017 09:26 AM
forcing a inventory from all clients fixed the cached packages not appearing issue.
Halting all scripted use of the JSS API seems to have lessened the unexpected logout issue. but it is still happening in all my environments. :( We also found database corruption on closer inspection.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-16-2017 02:31 PM
What fixed the logout issue for us was changing the "User ID" to sAMAccountName in the User Mappings for our LDAP connections. Ours had been set to uSNCreated and that was causing the issue in this new release.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-17-2017 06:34 AM
Are you guys using the Mac, Windows, or Linux installer? Any word if they Windows installer is working ok now? I'm planning on upgrading our system this Saturday and trying to figure out what could go wrong.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-17-2017 07:13 AM
@roiegat We do only manual installs but they did release an updated Windows installer so you should be okay.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-17-2017 10:54 PM
@roiegat We upgraded two systems (dev and then prod) with the Windows installer without any issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-20-2017 02:40 AM
Updated using windows installer about 2 days after release and was not able to login. Was getting logged out straight away even on a local account. Had to restore to old version.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-20-2017 05:52 AM
Thanks for the information guys. Will try it shortly.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-20-2017 07:22 AM
I was also having an issue on not being able to login to JSS after updating. Our Windows VM had an incorrect time. I fixed the time and was able to login.
