Welcome back everyone to the next chapter of the Mastering Horizon Cloud on Azure article series.
In the past articles, I have shown you how to setup the Azure subscription, Resource Groups, networks and accounts as well as the creation of the first POD infrastructure on Azure.
In this article, we’re going to complete the setup by enabling the infrastructure to authenticate to the domain controller, that you should have in place on Azure or on-premises. In addition to that we will configure the Broker and will enable monitoring.
Facebook Twitter LinkedInOn the 11th February 2022 I had the pleasure to attend the GeekSprech Podcast. Eric Berg, fellow MVP and Blogger / Podcaster is running this awesome format and invited me to be a guest in his show! It was a real fun session where we have spoken about all things Azure Virtual Desktop and Horizon Cloud on Azure. We explained the differences and
Facebook Twitter LinkedInAfter a few years working on old hardware (self made PCs) running VMware ESXi it was getting time to upgrade the lab environment to be able to write blogs about VMware Horizon and Cloud Pod Architecture, as well as doing more advanced blogs on Azure migration scenarios in the future. I researched a lot, which device could be a good fit to save
Facebook Twitter LinkedInWelcome back everyone to the next chapter of the Mastering Horizon Cloud on Azure article series. In the past articles, I have shown you how to setup the Azure subscription, Resource Groups, networks and accounts as well as the creation of the first POD infrastructure on Azure. In this article, we’re going to complete the setup by enabling the infrastructure to authenticate to the
Facebook Twitter LinkedInWelcome back to my article series on VMware Horizon Cloud on Microsoft Azure. In the previous articles, we have learned what is needed to prepare the infrastructure to be able to enroll new virtual desktop via the VMware Universal Console. We went through the initial Azure configuration and had a look on how to prepare the certificate for the UAG setup, which we
Facebook Twitter LinkedInWelcome back to part 2 of my article series on how to master VMware Horizon Cloud on Azure. In the first part I gave a general overview on what the service actually represents and how it can be seen especially in the Azure Virtual Desktop ecosystem. Now we’re proceeding to a more technical blog, describing how to prepare our environment before we can
Facebook Twitter LinkedInIt’s been quiet for a while on this blog, which was primarily related due to a very successful AVD Tech Fest, which we have performed in November. With a new year, there are new blogs and content to share and I’m happy to present you another blog series, this time about VMware’s Horizon Cloud on Azure service. I’ve seen some blogs around Citrix
Table of Contents
Configure Active Directory
To allow our users with a familar experience, we need to ensure that we bind our Active Directory domain to the Horizon POD. This allows us to entitle users to consume the desktop services that we will provision at a later time.
After signing in to the Horizon Universal Console using: https://cloud-de.horizon.vmware.com/
We will be back in the Getting Started guide, where we left of in the previous chapter.
In this chapter we will primarely focus on working on the second tab, which we will need to expand to complete the general setup. To configure the Active Directory connection, we need to click on “Configure” on the right hand site of Active Directory.
In order to bind the Horizon POD to the domain the following information must be filled out prior clicking on “Domain Bind”.
NetBIOS Name: NetBIOS name of your domain. E.g. avdlogix
DNS Doman Name: Full DNS name of your domain. E.g. avdlogix.com
Protocol: LDAP (by default)
Bind username: A service account that you should create upfront in your AD. E.g. horizonadmin
Bind password: The corresponding password to the horizonadmin account.
Auxiliary Account Bind username: An alternative service account for Horizon. E.g. svc_horizon
Bind password: The corresponding password
Port: 389 (LDAP) or 636 (LDAPS) are supported
Domain Controller IP: In case that the name cannot be resolved the DC can be contacted by IP
Context: Search context within the domain
Once all the settings have been made, click on “Domain Bind” to perform the operation.
On the following page, you have to provide the information about the DNS server and the default OU you want VMs to join in. Provide the information that are right for your environment and finalize the setup by clicking on “Save”.
Finally, provide information about the Horizon Admins that you want to enable in your environment. The picture below shows Domain Admins, I highly recommend to choose another group over domain admins, but just wanted to point this out.
Click on “Save” to finalize the setup. Afterwards you get signed out by the Horizon Universal Console and log back in using first the VMware Account followed by an Admin Account from the group that we have just defined.