1811 Upgrade Issues

[CameronRhoten]

We recently upgraded from 9.1 to 1811 on-prem and it's caused some issues with Organization Groups and Admin accounts. I can't see the device details for any of our phones using an account that has access to our main organizational group. Also, some of the devices are missing. I can see all devices with the main global admin account. It seems like everything has been moved into the Global organizational group, and any new enrollments are going there as well. Support had me upgrade to 1811.0.13, but that hasn't fixed it. Has anyone else come across this?

[tonymckee]

thanks for the post -  we are exploring that same upgrade.  please keep this updated.

[CameronRhoten]

I guess this is a known bug in the 1811 release. They've only seen it a few times though. There isn't a workaround for it. We rolled back to the 9.3 install and everything *seems* to be working.

[MikeSimms]

Hi All
Looks like 18.11 is a bit flakey
I recently upgraded our on prem to 18.11.  had it bomb out first time because it could not stop all the services it needed to, but does not tell you which, If you click continue at that point it bombs out later on and then you find it has wiped all your config.
It will give you a prompt box 'The following applications are using files that need to be updated by this setup'
DHCP Client
IP Helper
Message Queuing
Network Location Awareness
SMS Agent Host
User Access Logging Service
WinHTTP Web Proxy Auto-Discovery Service.

If you click Automatically close and attempt to restart, and then get the error message The setup was unable to automatically close all requested Applications.  STOP and stop the services  before clicking ok.
Didn't get the message on our test instance but did on our production and DR instance.
Cheers
Mike

[RichB2u2]

We are considering upgrading from 9.7 on-premise. It sounds like 1811 should be avoided but there is no full installer for 1902 for on-premise yet.

[MikeSimms]

Just a thought, did you upgrade the DB in increments from 9.1 to 18.11 or jump to 18.11.
I have always incremented the DB version (recommended by AW) till I get to the final then jump the CS/DS installers straight to the final version.
For my upgrade from 9.7.0.8, I run the 18.10 installer then the 18.11.0.3 installer then the 18.11.0.11 patch.
For 9.1 system that would mean running the 9.2, 9.3, 9.4 etc DB installers before the 18.11 installer.
Cheers
Mike

[LukeDC]

I’m also waiting until 1902 is ready for onprem.

[DmitriAltum]

We updated our on-prem from 9.6 to 1811 on Tuesday in our Lab environment and haven't seen these issues. All our devices are still visible and within their normal OG's and enrollment has been going into the proper OG's. We went straight from 9.6.0.8 DB to 1811.0.03 DB & same with application

[ChrisMeador]

my upgrade from 9.7.x to 18.11 broke a few things for us.  the end resolution was that some fields were not set silly things like our address and older versions were fine with this but not 18.11.  by creating a new enrollment org and doing a side by side comparison i found what was missing and updating my original i resolved my issues.  would have been nice if the updater did a little sanity checking.