Workspace ONE Access Horizon Args

I had an interesting customer use case last week that called for some ingenuity with how we establish Horizon app launch URIs in Workspace ONE Access. In short, a 3rd party agency required management access to retail location IoT devices on a closed network. These contractors were road warriors of sorts; sometimes onsite, but more often than not, out in the field servicing other customers of their own. We call this the “managed aisle” use case in my world, referencing a common retail arrangement where 3rd party vendors manage certain retail product aisles in a store (i.e. beverages). The customer was already using Workspace ONE as the unified app catalog for their enterprise and third party MSPs, publishing an assortment of management and enterprise tools that could only be accessed when on the intranet. They also had an existing Horizon RDS farm deployed with the same management suite for badged resources to perform similar functions on company-owned equipment. So the question became, how could we breadcrumb the user experience in such a way that a contractor could continue consuming applications […]

NSX-T LBaaS with Workspace ONE Access

Opening A few homelab versions back, I exclusively ran NSX-v LBaaS for all things “edge”. I’ve since had the opportunity to shift over to F5 BIG-IP, and now Avi Networks (welcome to the VMware family!), but still asked on numerous occasions to provide guidance on how to load balance Workspace ONE Access with NSX. Let me just say, the world is moving to NSX-T; it’s time you do the same. So without further ado, let’s dig into the recipe for how to load balance Workspace ONE Access with NSX-T. Pre-Requisites Only a handful of things to account for here: Functional NSX-T 2.4 Environment – For the below, I am using a highly available NSX-T 2.4.0 Manager cluster, with dual ‘large’ sized virtual Edge Nodes Functional Workspace ONE Access Node – I’m using an on-premises 1903 cluster below. Keep in mind, to implement a functional cluster, you will need to change the FQDN which won’t be possible without the below implemented. For now, start with one node, then follow the instructions for establishing a 3 node cluster. Here’s a great document […]

#VMworld 2019

EDIT [9/8/19]: Here is the recorded version of our session if you weren’t able to attend: Session Recording Slides Leader board (@lamw) EDIT [8/9/19]: See https://blogs.vmware.com/euc/2019/08/vmworld-workspace-one.html for ‘Can’t Miss’ sessions to register for! It’s that time of year again; #VMworld 2019 is less than 3 weeks away, but the content catalog is live for you to book your conference schedule. A few sessions you might be interested in checking out: Workspace ONE and Azure AD Integration: Deep Dive from the Trenches [DEE2023BU] – Ryan Costello and I will dive deep on how to deliver a rich end-user experience with your investments in Workspace ONE and Azure AD/Office 365. This is 300 level configuration with live demos, so bring your tablets and notebooks! If you’re a fan of my recent post on the WS1 UEM SCIM Adapter fling, come checkout Joe and I give a LIVE DEMO in the Solution Exchange on Wednesday from 10:00AM-12:30PM PST, booth #949. Look for the “Innovation Accelerating Transformation” headline above the kiosks. Sneak peek! Stay tuned here for information on an additional session not yet […]

WS1 UEM SCIM Adapter

Today is an exciting day. It’s my first experience developing a VMware Fling, and it’s is the GA release of what Joe Rainone and I put hours of laborious love into. Identity is not only our day job, but also an area that we are both very passionate about. Our belief is that this Fling, while unsupported, answers a question that many of our customers ask when designing production Workspace ONE deployments. Take a look, play around, and please provide feedback here! What is the Fling about? The SCIM protocol is quickly modeling after what SAML brought to identity management almost 15 years ago: a common way to establish resource identity in a service-to-service architecture. Gone are the days where LDAP and Active Directory are the primary systems of record. This concept is particularly enhanced as EUC platforms like Microsoft Azure, VMware Workspace ONE, and others provide native directory services while maintaining a common identity among themselves and their relying parties. Furthermore, the burden of maintaining ‘connector’-like infrastructure for the sole purpose of identity synchronization not only diminishes the value […]