Hello everybody! I’m glad you’re here again! At this point, you might be aware about your Microsoft Azure access, privileges and you have access to the console within properly roles assigned for you. So let’s check Quota and why is this an important step towards establish your Horizon Cloud on Azure environment. Understanding Quota Quota
Category: Horizon Cloud
If you’re new on Microsoft Azure, you’ll need to have a valid subscription and specific administrative privileges in order to start setting properly your environment to receive Horizon Cloud on Azure. So let’s check what you need to cover: Subscription Everything starts with your Azure Subscription. This is the place where you can put all
Every time I have a conversation with a customer and some times this ends up in a PoC for testing VMware Horizon running on Microsoft Azure, the following documentation is provided with an extended requirements in which customer needs to prepare its environment prior start testing it. Requirements list is well documented on this link.
If you follow the steps from Part I, your RADIUS server is properly configured and you have Google Authenticator working as well. Now it’s time to finish our integration from Workspace ONE Access side. Configuring Radius Authentication – Workspace ONE Access Whether you’re using On-Premises or SaaS, all configuration steps will be basically the same,
I was having a conversation with a customer during a PoC and one requirement was keeping using Google Authenticator as a MFA when shifting Workspace ONE Access over the current solution. I told my customer we can configure Google Authenticator with RADIUS but when I checked VMware documentation, there’s not a step by step on
I’m a big fan of Workspace One Access, which is part of Workspace One UEM and VMware Horizon licenses. This solution makes our life even better if you or your company is using SaaS based applications, virtual desktop, application virtualization or even internal sites (intranet, SharePoint, etc). I personally like the quotes coming from VMware
If you’re here it means that you’re accomplished with the following configuration steps from my previous blog post, deploying Horizon Connector into your On-Premises infrastructure. Moving on our configuration, your appliance should be at the following state, according picture below. Before configure our appliance we need to make two simple (but important) actions: 1- Set
I have customers which moved into Horizon Universal License, according my previous blog post, and in some cases those customers still need to keep using Horizon On-Premises and come across with the following question: How to configure Horizon Service Plane using my On-Premises Horizon infrastructure? To make it easier crystal clear, these are the steps
You might be asking right now: I did move to Horizon Subscription license and I’m missing my licenses when I access MyVMware portal. So, where’s my license key? Different from previous licenses you’ve acquired from VMware in the past, within this service you don’t receive a license to be used like a perpetual configuration way.