This post will be a bit different because I will show you the end result first. 🙂

What we want to achieve in the out of box enrollment experience. In real world this means you can ship the laptop directly to the employee or your employee can buy any device in the local store and after unpacking it will be automatically configured and he is able to work.

I’ve recently upgraded my home lab from UAG 3.6 to 3.7.1 and I’ve noticed, that basically everything stopped working. That’s weird, so I started my investigation and by the investigation, I mean reading carefully release notes for UAG 3.7.

The last bullet point caught my attention because my lab domain is minarik.local.

So I started this mini-series about setting up all the integration points, when starting (or doing a free trial testing) with Workspace ONE. The first post was about Workspace ONE Access (vIDM) Connector, which is only one part of the integration needed for the full functionality of Workspace ONE UEM.

The second part is Workspace ONE UEM Connector (sometimes referred to as Airwatch Cloud Connector or just Cloud Connector). This component is used for integration with your on-prem:

• Email Relay (SMTP)
• Directory Services (LDAP/AD)
• Email Management Exchange 2010 and later (PowerShell method)
• Lotus Domino Web Service (HTTPS)
• Syslog (Event log data)
• Microsoft Certificate Services (PKI)
• Simple Certificate Enrollment Protocol (SCEP PKI)
• Third-party Certificate Services (on-premises only)

So let’s set up one. It’s straight forward.

Recently I am doing a lot of proof of concepts for VMware Workspace ONE running as SaaS in our cloud and it always starts with a question – “What do I need to prepare on my side?”. To simplify my life, I decided to write this post, which should summarize all the requirements to get everything up and running.

My idea is to slowly over time expand this post and provide also nice installation instructions, so it will be extremely easy for anyone to test our Workspace ONE trial environment.

It happens to everybody, you install your Workspace ONE UEM console on-prem and use the default administrator account for everything. But then one day you decide to go for a vacation and after that you cannot remember what was the damn password.

Don’t worry I have a solution for you.

Well this will be a short post, but from my experience not everybody knows about this.

So the situation is, that you’ve installed your Workspace ONE Intelligent Hub, started the enrollment process and for some reason it’s failing even before the device reaches the Workspace ONE UEM console and you have absolutely no idea why is that.

Workspace ONE UEM makes the enrollment process simple, using an auto discovery system to enroll devices to environments and organization groups (OG) using user email addresses. Auto discovery can also be used to allow end users to authenticate into the Self-Service Portal (SSP) using their email address.

It’s a nice feature, but recently some customers reached out to me, saying that it’s not working for them especially when deploying Workspace ONE UEM on premises.

The cloud service is pretty straight forward, API call to VMware’s Workspace ONE servers will return a JSON with your device services server and organization group (Group ID), which is then pre-filled for you to the Workspace ONE Intelligent Hub app. So, what can go wrong?