#Workspace one intelligent hub manuals
#Workspace one intelligent hub install
#Workspace one intelligent hub windows

VMware Global Support Services has created an internal ticket number for the Hub Services product management team. there is OTA OG, but this one is empty and just for demo the OG structure.

In my environment I configured the Directory Service integration one level below “Global”, because I don’t have a separate production, acceptance, and test environment, and as the common practice says don’t set all your configurations at “Global” level. If all above three rules does not apply in your environment a big chance that your devices are also not being listed in the web (browser) version of the Workspace ONE Intelligent Hub.

And here is my issue, your Directory Services integration (Microsoft Active Directory domain) must also be set at “Global” level in your Workspace ONE UEM tenant.

Workspace ONE UEM and Workspace ONE Access must be integrated at the “Global” level in your Workspace ONE UEM tenant.

Hub Services must be enabled on the “Global” level in your Workspace ONE UEM tenant.

In the Hub Services documentation, there is no hard requirement noted, that you must configure it like this: With all my best intentions to implement the common practice about earlier mentioned OG structure, it is now a kicking in my back and facing a limitation. After a couple of explanations, videos, and browser developer logs, they found the misconfiguration in my environment. Together with VMware Global Support Services I was trying to find the root cause of the issue I am facing. Trust me in my environment I have 5 registered devices in Workspace ONE UEM.

#Workspace one intelligent hub windows

Be aware that the Intelligent Hub app on iOS, Android, macOS and Windows doesn’t have this issue, so it is only in the web browser version. When using the web (browser) version of the Intelligent Hub (Workspace ONE Access Portal), you may not see your devices at all! You are facing the same bug as me and VMware said it will be fixed in one of the next releases, but still waiting for it after a couple of months. There is only one exception in this scenario.

#Workspace one intelligent hub install

By selecting one of your devices, you have the option to sync to Workspace ONE UEM and install device profiles which are associated to them. Besides adding a new device, it also lists all your devices which are registered in Workspace ONE UEM. Some device profiles are set to optional (on-demand) by your organization.Īt the user’s perspective you can add (register) devices via the Support tab (if not being renamed, in my case it is Self-service) in Workspace ONE Intelligent Hub (Web or App). Here you can decide if a user is allowed to register a device in Workspace ONE UEM by themselves (useful when your company enrollment policy is set closed) and decide if a user is allowed to install device profiles or not. I think the most interesting part of this section will be Device Self-service.

#Workspace one intelligent hub manuals

Where in Helpful Links you can add several internet/intranet links to for example a FAQ, Self-service IT ticketing system, Manuals etc. In this section of the Hub Services, you can configure “Helpful Links” and “Device Self-service”. In the September 2019 release of Workspace ONE UEM (20.09), VMware introduces the “End user self-service” in the Hub Services section.

In this design you have freedom to associate your production Microsoft Active Directory domain at the Production OG within Workspace ONE UEM and your test Microsoft Active Directory domain at the Test OG. A common practice is that you create an OG under “Global” and name it as your “Organization” and below that level you make an “Production”, “Acceptance” and “Test” OG and so on and so on. Especially in the SaaS version of Workspace ONE UEM it was a NO-GO to configure settings on the “Global” level unless you need to. One of the things in the course was designing your OG (Organization Groups) structure. Workspace ONE UEM – OG StructureĪ couple of years I ago I followed the official AirWatch bootcamp course (4 days). This time I found a bug in VMware Workspace ONE – Hub Services, but there is no fix for it yet. These kinds of situations don’t exist every day, so I saw another VMware vExpert releasing the blog after another blog about things he is facing during projects and just write about it and use these blogs under the name “notes from the field”. In the end you hope other people facing this issue as well and use your solution in their own environment. For me a (technical) blog consists of a problem description, things you tried and a solution to make it work. A new section in my blog series… Lately I didn’t find much useful to blog about.