With the release of Horizon 2212, VMware provides a way to integrate and manage the assignment of app packages directly from the Horizon console. While exploring the same, I encountered
DEM in HCS-V2DEM in HCS-V2
Horizon Cloud Service version 2 aka HCS-v2 gives you a direct option to integrate Dynamic Environment Manager directly via HCS-v2 Console. But once I started with that I was not
Dynamic Environment Manager integration with LinuxDynamic Environment Manager integration with Linux
VMware Dynamic Environment Manager (DEM) can do wonders for Windows OS as well as for User Profile and there is huge content available on VMware Docs as well as Internet
WorkSpace One Access with UAG as Reverse ProxyWorkSpace One Access with UAG as Reverse Proxy
I have been working with multiple customers and there has been a concern to block admin access to local admin user as well as domain users for administration console from
On-boarding Horizon 7 On-Premises to Horizon Cloud TenantOn-boarding Horizon 7 On-Premises to Horizon Cloud Tenant
In this article, I will talk about on-boarding Horizon 7 pod to Horizon Cloud tenant environment. This is basically done to achieve two primary use cases: Apply subscription based license
Horizon Cloud On Azure : 1. Preparing Azure SubscriptionHorizon Cloud On Azure : 1. Preparing Azure Subscription
In this blog, I am going to walk you through the deployment of Horizon Pod on Azure Cloud from scratch. For this setup, I am deploying Active Directory in the
VMware UAG integration with PING SAMLVMware UAG integration with PING SAML
Further in this series after Azure & OKTA SAML integration, I will be discussing about SAML integration of UAG with Ping IdP. This can be achieved by following the below
VMware UAG integration with OKTA SAMLVMware UAG integration with OKTA SAML
Further in the category after Azure SAML integration, I will be discussing about SAML integration of UAG with OKTA IdP. This can be achieved by following the below three steps