Posted September 25, 2024Sep 25 Hello, Devices that are on the system before yesterday at 10:30am can still access the app catalog in the HUB app, however all devices setup new and/or logged into workspace one since then have no access to the HUB.
September 25, 2024Sep 25 I'm seeing this as well across my entire fleet. I also opened another thread in this forum that Hub will not install on a Supervised device after enrollment via Apple Configurator (meaning I have no way of onboarding new devices as of the same time @Brad D. reported).
September 25, 2024Sep 25 Author Hello, I have a ticket open as well I have not heard any response from Omnissa Technical Support on this issue is it on any ones radar at omnissa? This is affecting our deployment of 1800 devices. Thank you futureaw for your response. Have you heard from anyone on a fix or possible eta?
September 26, 2024Sep 26 Hi Brad, I haven’t received any responses. We’re not able to onboard any new customers or employees at this time.
September 26, 2024Sep 26 CRSVC-52748: iOS Intelligent Hub gets stuck in authentication loop (6000201) (omnissa.com) Are you on 2406? We havent been able to enroll new devices for a week now since the tennant got updated. Edited September 26, 2024Sep 26 by Daniel.S
September 26, 2024Sep 26 Author Yes I am on 2406, thank you for the comment I will look at the topic.
September 26, 2024Sep 26 Author So I have found that if I continually keep wiping the device with configurator and trying to deploy, sometimes very infrequent the device will pass the "configuring device screen" and continue to the home screen. (You have to do it like 5-10 times) If I use the old legacy app store and remove authentication from the legacy store, the app catalog is accessible but very clunky, none of the app icons are displayed there all black boxes. But if you click install then close the app store completely, then open it back up and click install for the same app it will install. If I add authentication it fails. The HUB is still inaccessible opening it will just provide the local user account info no App catalog. None of the HUB access features. However existing devices that have not been reset have less issues.
September 27, 2024Sep 27 Community Expert Employee There is an issue with Hub on 24.06. Do you see Auth-1005 errors in the troubleshooting logs of the affected devices? Engineering is working on a fix. This affects iOS usually only if you do enrollments other then through Hub directly, so DEP, user enrollment and it seems to configurator as well.
September 27, 2024Sep 27 Correct, enrollments with an iOS staging user via Apple Configurator does not install the Hub app so we cannot onboard devices. The device also fails to stay connected to the console after initial management profile install. Do you have an ETA on the fix?
September 30, 2024Sep 30 Author This is actually affecting us solely with HUB direct enrollments as that is how we manage our fleets onboarding. We had two devices friday out of 15 that actually connected the way they were supposed to and the HUB would open with the app catalog ability. Is there an ETA on this fix?
October 1, 2024Oct 1 Solution Our SE just informed us that there is a patch available now for the Hub app - 24.08.1. For my affected devices I have just reinstalled the Hub app from the admin console and appears to be working normally now. “Workaround is delivered with iOS Hub 24.08.1. Customer has to update Hub to the specific version to fix the issue. The version is GA now and available through App Store. Note: Customer may be prompted to authenticate with the latest Hub version once if their previous token was invalidated. However, the prompt will go away after token is fetched successfully through one-time authentication.”
October 2, 2024Oct 2 The new hub version fixed the authentication problem but we also have a problem where the hub or apps isnt installing after enrollment, it takes very long, yesterday it took like 6 hours before hub got installed. Anybody have similar problem?
October 2, 2024Oct 2 Author To Daniel S. Yes very intermittent have a support ticket in but still waiting for a call back. since last week.
October 2, 2024Oct 2 Author So actually tested it on about 5 devices this morning and as long as we wait about 20-25 minutes after inputting the username and password in the remote management the token seems to install in the HUB. Its very slow but seems to be more consistent this morning.
Create an account or sign in to comment