Brad D. Posted Wednesday at 04:57 PM Share Posted Wednesday at 04:57 PM 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. Quote Link to comment Share on other sites More sharing options...
Brad D. Posted Wednesday at 05:08 PM Author Share Posted Wednesday at 05:08 PM Forgot to mention this is the Cloud environment. Quote Link to comment Share on other sites More sharing options...
futureaw Posted Wednesday at 05:18 PM Share Posted Wednesday at 05:18 PM 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). Quote Link to comment Share on other sites More sharing options...
Brad D. Posted Wednesday at 11:07 PM Author Share Posted Wednesday at 11:07 PM 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? Quote Link to comment Share on other sites More sharing options...
futureaw Posted Thursday at 11:13 AM Share Posted Thursday at 11:13 AM Hi Brad, I haven’t received any responses. We’re not able to onboard any new customers or employees at this time. Quote Link to comment Share on other sites More sharing options...
Daniel.S Posted Thursday at 12:55 PM Share Posted Thursday at 12:55 PM (edited) 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 Thursday at 12:55 PM by Daniel.S Quote Link to comment Share on other sites More sharing options...
Brad D. Posted Thursday at 01:40 PM Author Share Posted Thursday at 01:40 PM Yes I am on 2406, thank you for the comment I will look at the topic. Quote Link to comment Share on other sites More sharing options...
Brad D. Posted Thursday at 02:04 PM Author Share Posted Thursday at 02:04 PM 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. Quote Link to comment Share on other sites More sharing options...
Employee Sascha Warno Posted Friday at 07:14 AM Employee Share Posted Friday at 07:14 AM 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. Quote Link to comment Share on other sites More sharing options...
futureaw Posted Friday at 01:56 PM Share Posted Friday at 01:56 PM 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? Quote Link to comment Share on other sites More sharing options...
Brad D. Posted 9 hours ago Author Share Posted 9 hours ago 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? Quote Link to comment Share on other sites More sharing options...
.jpg.e22c28efd054e3ac2a82765cf23cfba0.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.