If you’ve upgraded to Workspace ONE UEM 18.10 and you have anybody enrolled with the AirWatch Agent, you wont fail to see the new Intelligent Hub app and Hub Services configuration.
Intelligent Hub is an overhaul of the AirWatch Agent to deliver a full Unified App Catalog features, allowing the Hub to be the one stop shop for users to access any app on any device. The app also allows Administrators to deliver notifications to end users.
If you are an end to end Workspace ONE user, integrating UEM (Unified Endpoint Management, powered by AirWatch) with VMware Identity Manager, you’ll probably want to deliver your SaaS Apps as well as Native applications.
I was lucky enough to find a good deal on eBay for a good NUC to help build out my Home Lab. As an EUC/VMware Mobility Specialist I’m not looking to run any massive vSphere/vSAN deployments, just a nice box to run the usual suspects (AD, ADCS, Unified Access Gateway) to give me everything I need.
Unfortunately, I started running my setup during what should be known as the end of times in the UK (June/July 2018) where temperatures hardly dropped below 27 during the day. This meant keeping my kit cool was difficult so I put it down a a bit more ambient heat than usual. When I started getting some major fan noise due to an issue with Azure AD Connect services taking more CPU, I decided to try and change some settings to resolve it.
I set up VCSA (vCenter Server Appliance) running on a vSAN datastore, then wanted to move things around. I disconnected my ESXI hosts and deleted the VCSA appliance. Proper SDDC experts are probably crying at that statement not, but you learn by doing! I then had the issue where I was unable to delete the vSAN datastore.
To resolve this, I had to run thr following:
First enable SSH on your ESXI host. SSH into it and run:
esxcli vsan cluster leave
Once this was done, I was still unable to re-claim the disks back into regular datastores. I couldn’t remove the partitions via ESXi Web Client either, so resorted back to Google.
So… I’m running an AD on an Intel NUC, and after a recent set of updates the NUC started to sound like a hairdryer!
The ESXi Host was reporting some pretty fantastic CPU numbers (considering there’s not a lot of workloads on this yet, 3 VMs doing not a lot).
When having a look at the VM, I see most of the CPU being taken up by ‘Microsoft.Online.Reporting.Monitoring.Agent.Startup’. This is a component of Azure AD Connect, which I’m using to sync user accounts into Office 365 for my Lab.
Providing access to applications as easy as possible is one of the primary goals of Workspace ONE. While Workspace ONE can enable Single Sign On to Office 365, I see most setups just deploying the main portal to Office 365. One massive improvement we can make is to provide users with links directly to O365 services, such as OneDrive, Outlook and Excel Online by enabling one click links into these services.
Below is a step by step guide to get each service within Office 365 presented to end users via the Workspace ONE Catalog.