How to Enable the New Intelligent Hub Catalog on Windows 10

After much waiting, the 20.03 console version of Workspace ONE finally brings us support for the new Intelligent Hub catalog for Windows 10! While there are still some missing features (we’ll get to that later) this finally aligns the Windows 10 catalog with the other platforms, namely Mac, iOS, and Android.

Hub Pre-Requisites

A few pre-reqs are required in order to enable this new catalog:

  1. Console must be upgraded to 20.03 (obviously)
  2. Intelligent Hub must be upgraded to 20.03 (obviously x2)
  3. Hub Services must be turned on (which also requires a Workspace ONE Access instance setup)
  4. Enable the “Intelligent Hub Catalog (Windows Desktop)” under Settings > Apps > Workspace ONE > Airwatch Catalog > General > Publishing Tab.
  5. “Source of Authentication for Intelligent Hub” must be set to “Workspace ONE UEM”

Let’s dive into the details on each of these.

Getting the correct console and client versions

First, ensure that your console is in fact on or later. Click “About” in bottom left of your UEM console.

Next, we need to make sure the the hub versions on Windows 10 are also updated. If you have “Intelligent Hub Automatic Updates” checked, this should go out automatically to clients. But we still want to verify. On a client, load up “Apps & features” from the settings menu and find Workspace One. You’ll noticed 2 entries:

Workspace ONE Intelligent Hub – This is the new Hub UI components that show the catalog and hub information page. This is UWP (Universal Windows Platform) based. Click on “Advanced Options” to see the version. It should be or later.

Workspace ONE Intelligent Hub Installer – This is the regular “agent” and handles the normal agent stuff like inventory, profiles, Bitlocker, etc. This should also be or later.

Enable Hub Services

Enabling Hub Services “unlocks” the actual feature. You may have this already turned on if you are using this for iOS/Android. To check go to Settings > Configurations > Intelligent Hub.

Search “Hub” and then click on “Intelligent Hub”

If you go here and see a “Get Started” button, then you know that hub services is not turned on at all. Clicking “Get Started” will bring up a page to enter your Workspace ONE Access (which used to be called vIDM) URL and username and password.

Enter Workspace ONE Access URL and credentials

If you are in a shared SaaS environment, you can even request a cloud-tenant of Workspace ONE Access right there and walk through a short wizard to get it enabled.

Once Workspace ONE Access is setup and linked, you should see a page like this:

Enable New Hub Catalog

Now we need to “enable” the new catalog. To do so, click on the “Configure” button under “Catalog Settings” in bottom right

Select “Enabled” under “Intelligent Hub Catalog (Windows Desktop)”

Don’t forget to hit Save at the bottom.

Set Authentication to UEM

Finally, we need to set the authentication to be UEM and not Workspace ONE Access. The ability to use Workspace ONE Access for auth should be coming in a future release. To configure this, go to Settings > Device & Users > General > Enrollment Tab. Ensure “Workspace ONE UEM” is selected under “Source of Authentication for Intelligent Hub”.

Load the Catalog and Install some apps!

After all of these settings are saved, the catalog should now be enabled. To launch it, simple double-click the icon in the system tray.

Find your favorite apps and install away!

Just a reminder that some features aren’t fully implemented yet:

  • SaaS Apps
  • Horizon Apps
  • Uninstall Apps
  • App Statuses – You may notice that some app statuses (installing, installed, etc) may not be instantly updated.
  • Notifications – Hub Notifications aren’t fully implemented yet either.

I’ll keep this updated as new features become available.


This Post Has 4 Comments

  1. Peter

    Thank you for another excellent write-up.
    Can you please clarify, if it’s enough to just do the WS1 Access config from within the UEM console to enable HUB services on any OS (without any config like AD integration, user and group import inside the WS1 Access UI), or do we need to have a “full” Access configuration, like we need for SaaS apps?

    1. Brooks Peppin

      I hope I understand your question, but setting auth to WS1 Access isn’t required, per se, but is is required to show SaaS/Horizon apps as those don’t live in UEM console. WS1 Access is what gives access to those things and so that is required in order to see them. If you only want to see native/internal UEM Apps, then Intelligent Hub Authentication can be set to UEM.

  2. George Petrides

    Hi Brooks,
    Could you please clarify a few points…

    There is a screen capture showing SaaS and Horizon apps, but just below that comment you mention

    Just a reminder that some features aren’t fully implemented yet:

    SaaS Apps
    Horizon Apps
    Uninstall Apps

    I’ve set this up, and when I launch hub from win10, I can only see the apps pushed from UEM. (When I access Access from a browser, I can see all apps).

    Also I enabled Workspace ONE UEM as the source of authentication, however it does appear in the settings (by settings, I mean the capture under the following)
    Enable New Hub Catalog
    Now we need to “enable” the new catalog. To do so, click on the “Configure” button under “Catalog Settings” in bottom right

    Thank you

    1. Brooks Peppin

      The screenshot I show are only win32 apps. Which ones are you that that are horizon or saas apps? The horizon client listed there is just the installer for the win32 horizon client.

Leave a Reply