Can't enroll devices via Intelligent Hub

[twmulroy]

Recently, started receiving "Something went wrong with discovery" whenever we try to enroll a device via Intelligent Hub. This occurs when trying to enroll via email or by typing the server address. Device server is up and available. Our enrollment page is available to devices via the browser. But, when punching the same address into Intelligent Hub, the "Something went wrong with discovery" error is returned within a second. Anybody else dealt with this issue before? Looking for help. We're stuck dead in the water.

[chengtmskcc]

Does this help?

VMware Knowledge Base

[Resolved] ESC-19126: Android devices using Intelligent Hub 19.06 cannot enroll if 'Allowed IPs' is enabled in the Workspace ONE UEM Console (2961048)

---

Last Updated: 6/2/2020Categories: Known Issue 1 subscribe

Symptoms

During Android enrollment, after entering an email address or Server URL, the following error is displayed in the Intelligent Hub application:
"Something went wrong with discovery"

Version Identified

Workspace ONE Intelligent Hub 19.06 and later for Android

CauseThis error will be displayed when the Intelligent Hub fails to connect to a Device Services monitoring endpoint to check for the Workspace ONE UEM Console version. If you have set up IP whitelisting under Groups & Settings > All Settings > Admin > Monitoring, this connection may fail.

Please note:

• This setting is only accessible in On-Premise environments.
• The error "Something went wrong with discovery." may occur if Hub is not able to connect to Device Services for other reasons.

Impact / Risks

Android devices will not be able to enroll if there are IP addresses listed on this page when using the Intelligent Hub 19.06 or later.

Resolution

In the Workspace ONE UEM Console, navigate to Groups & Settings > All Settings > Admin > Monitoring. Remove any entries from the Allowed IPs field, then flush the cache and perform an IIS reset on the Device Services server(s).

[twmulroy]

Thanks. We looked into this as a potential solution, but our Allowed IP list is currently empty. It seems like the Hub app is suddenly not able to connect to airwatch.ourcompany.com. However, we can navigate to airwatch.ourcompany.com via the browser and reach the enrollment page without any problems. Naturally, port 443 is open and site is available. But, when I type "airwatch.ourcompany.com" into the Hub app, I immediately receive the "something went wrong with discovery error". The environment was working fine in the past. Only changes that have been made recently was an update to our console and device server certificates in IIS. They're properly binded.

[HimanshuMishra]

Is it happening on both Android and iOS ?

[twmulroy]

That is something I may need to check for iOS. Currently, we only use Airwatch for managing Android devices.

[HimanshuMishra]

Please check that all the system certificates are enabled.

For example, on a samsung device - Go to Settings >  Biometrics and Security  > Other Security Settings > View Security settings  > Scroll down  and make sure all the system certs are enabled.

[twmulroy]

Thanks. Currently, this issue is affecting any Android device we are trying to enroll, or re-enroll. It is not relegated to a specific Android device.

[DimitrijPrudkij]

Hello,

please check with IISCrypto ( Nartac Software - IIS Crypto  ) your cipher suites and tell which Android version cant enroll.I have the same with Android 4.4.2 but with Android 9.0 works fine

[mustafaghazi]

Its not even working with an IOS device. Tried enrolling via QR code, server address but get the same error popping up. What can be done to resolve it?