TommyThomassen
Enthusiast
Enthusiast

Cannot fully enroll iOS devices with Intelligent Hub 21.01

Jump to solution

Hi.


We are having issues enrolling all iOS devices, manually through Hub or DEP iPad devices.

When enrolling through DEP, it looks "ok", then opening the Hub app which is latest 21.01 for iOS, it does not show "Account" name in the circle.

Also the branding is not applied, which leaves me to believe it is not finished enrolling completely.
It shows in Console, but Device compromised is unkown (typical if Hub is not finished or started by the user). But this status never changes, and the Hub is in limbo.
I have read there is SDK changes in 21.01, but it seems to break our enrollment. Any have seen the same experience?
This of course causes Boxer and Content to fail, since they cannot fetch information from Hub.

We did have Access before, but the server is powered off. So we are using plain Hub and Webclip for the Catalog function.

Thank you guys.

0 Kudos
1 Solution

Accepted Solutions
sturmanc
Enthusiast
Enthusiast

Are you on-prem?

We saw the same issue this past weekend.

Issue was resolved by removing the .NET 4.8 cumulative update (kb4601051) pushed to the Windows 2016 application servers during Microsoft February patching.

https://kb.vmware.com/s/article/82294?lang=en_US

View solution in original post

0 Kudos
3 Replies
sturmanc
Enthusiast
Enthusiast

Are you on-prem?

We saw the same issue this past weekend.

Issue was resolved by removing the .NET 4.8 cumulative update (kb4601051) pushed to the Windows 2016 application servers during Microsoft February patching.

https://kb.vmware.com/s/article/82294?lang=en_US

View solution in original post

0 Kudos
TommyThomassen
Enthusiast
Enthusiast

Thanks for the tip, will check this right away.😉
We are On prem yes, and this just occured since Friday.

Get-Hotfix did not show the patch installed, but this seems to be very similar to our issue. 

0 Kudos
TommyThomassen
Enthusiast
Enthusiast

So to confirm we had the same errors in the article, sent some Fiddler logs to VMware also.

We had to remove KB4601055 so this contains the .Net updates as well.

Hopefully they have a good communication line with MS and get this sorted.
Thanks again for the quick tip 🙂

0 Kudos