Time Stamps :D Intro: 0:00 Creating Your Azure Subscription: 2:20 Creating VNets for Horizon Service on Azure Deployment: 4:20 Creating Hub Transit VNet: 7:22 Virtual Network Gateway For Azure-to-Site VPN: 8:38 Local Network Gateway Configuration for Azure-to-Site- VPN: 9:50 VNet Peering: 10:58 VPN Connection Definition: 12:03 VNet DNS Server Configuration: 14:10 Creating the Service Principal for use with the Horizon Cloud Control Plane: 15:06 Increasing Azure Subscription Quotas: 17:52 How to Format Certificates for use with Horizon Cloud Service on Azure: 23:44 Deploy First Pod to Azure Subscription: 29:54 Active Directory Service Accounts Domain Bind and Domain Join: 34:45 Uploading Pod Certificates for Smart Node Use: 37:44 The Final Touches: 38:43 Importing a Virtual Machine from Azure Marketplace: 41:26 Imported Virtual Machine Customization and Application Installation: 42:48 Creating Your First Desktop Assignment: 46:31 Testing Your Desktop Assignment: 49:59 Dashboard: 53:14 Useful Links/Closing Notes: 53:28
Great walkthrough. It would be nice if you could do one with no on-prem servers. Also almost every single Azure and VMware page has been changed since you made this. So there are several steps where it is no longer obvious how to follow along.
Hi shane, Thanks for this amazing video. while folowing the same ,i am getting an error. Unable to register active directory. Can you please help me in troubleshooting this error
when you copied the certificate data into the PEM file, did you copy the "Bag Attributes" of the cert? The cert is the only one with "bag attributes" and from your video I could not tell you did a select all and copy and only copied from "---BEGIN---" to "---END---"
Im getting an error stating "Failed to deploy the pod to Microsoft Azure. Unknown Server error" Any ideas? I am a VMW employee and trying to set this up using my own Azure account and was granted access to the Horizon Cloud Control Panel internally. Just cant get them to talk for some reason. EDIT: it was DNS...its always DNS...
hey shade, Im deploying and i got this msg "Pod cannot connect to Horizon Cloud control plane. Please check your Azure Networking/DNS/VNet/Proxy Settings" any idea?
While deploying POD deployer or temp jump box which sits on Mgmt network will talk to internet or set of DNS which uses to download binaries and other components which requires for POD deployment so make sure your mgmt subnet has the ability to talk to required DNS / URLs(plz refer HzC on Azure deployment guide) . If you use external DNS then make sure to configure under Vnet DNS settings.
I Agree with @AnandaKrishnan's comments. This is typically either a DNS, Routing, or firewall issue. I'd check that your DNS servers are correctly configured in your VNet and that VMs in your VNet are able to query DNS (ie deploy a VM into the subnet manually and check). I've seen issues where if your advertising a default route into your azure tenancy via an express route or VPN this can cause issues as well. (You either need to configure your on-prem infrastructure to allow internet access from VMs in your Azure tenancy, filter the advertised route or edit the route table for the management subnet). On the firewall side you need to make sure that traffic can flow from the management, DMZ, and tenant subnet to the internet. (This can be tested using the manual VM deployment I mentioned earlier)
@@shanefowler9370 hey , i the DNS team double check it and we found a problem with the comunication between the dns and Azure, fix that and worked like a charm
Time Stamps :D
Intro: 0:00
Creating Your Azure Subscription: 2:20
Creating VNets for Horizon Service on Azure Deployment: 4:20
Creating Hub Transit VNet: 7:22
Virtual Network Gateway For Azure-to-Site VPN: 8:38
Local Network Gateway Configuration for Azure-to-Site- VPN: 9:50
VNet Peering: 10:58
VPN Connection Definition: 12:03
VNet DNS Server Configuration: 14:10
Creating the Service Principal for use with the Horizon Cloud Control Plane: 15:06
Increasing Azure Subscription Quotas: 17:52
How to Format Certificates for use with Horizon Cloud Service on Azure: 23:44
Deploy First Pod to Azure Subscription: 29:54
Active Directory Service Accounts Domain Bind and Domain Join: 34:45
Uploading Pod Certificates for Smart Node Use: 37:44
The Final Touches: 38:43
Importing a Virtual Machine from Azure Marketplace: 41:26
Imported Virtual Machine Customization and Application Installation: 42:48
Creating Your First Desktop Assignment: 46:31
Testing Your Desktop Assignment: 49:59
Dashboard: 53:14
Useful Links/Closing Notes: 53:28
I really enjoyed how you teach the step by step process and your visual aids!
Excellent step by step on how to configure this network. I was looking for something similar, thank you very much, crack!!!!
Can you do a video with no on-premise servers, everything in the cloud?
Outstanding! Nicely done. Straight to the point.
Thank you Shane for this fabulous video! You saved me hours of reading :)
Hello. Grate staff :) Do You have in Plans to do next video with integration with Workspace one and with App volume maybe?
Great walkthrough. It would be nice if you could do one with no on-prem servers. Also almost every single Azure and VMware page has been changed since you made this. So there are several steps where it is no longer obvious how to follow along.
Well done Shane!! Thank you for doing this!
Well done Shane! This is just awesome!
Excellent. Thanks for your input.
Thanks Shane, pls clear why need 4 UAG Server 2 for internal and 2 for external, All users connect from public n/w.
Nice explanation Shane !!!
Great video. Thanks for sharing.
Can we change fqdn after pod deployment?
Hi shane,
Thanks for this amazing video.
while folowing the same ,i am getting an error.
Unable to register active directory.
Can you please help me in troubleshooting this error
when you copied the certificate data into the PEM file, did you copy the "Bag Attributes" of the cert? The cert is the only one with "bag attributes" and from your video I could not tell you did a select all and copy and only copied from "---BEGIN---" to "---END---"
It is awesome, thanks shane!
Great!
Re-synchronizing failed for pod XXXXXX: Failed to re-synchronize pod when creating my 2nd pod
Im getting an error stating "Failed to deploy the pod to Microsoft Azure. Unknown Server error" Any ideas? I am a VMW employee and trying to set this up using my own Azure account and was granted access to the Horizon Cloud Control Panel internally. Just cant get them to talk for some reason. EDIT: it was DNS...its always DNS...
hey shade, Im deploying and i got this msg "Pod cannot connect to Horizon Cloud control plane. Please check your Azure Networking/DNS/VNet/Proxy Settings" any idea?
While deploying POD deployer or temp jump box which sits on Mgmt network will talk to internet or set of DNS which uses to download binaries and other components which requires for POD deployment so make sure your mgmt subnet has the ability to talk to required DNS / URLs(plz refer HzC on Azure deployment guide) . If you use external DNS then make sure to configure under Vnet DNS settings.
I Agree with @AnandaKrishnan's comments. This is typically either a DNS, Routing, or firewall issue. I'd check that your DNS servers are correctly configured in your VNet and that VMs in your VNet are able to query DNS (ie deploy a VM into the subnet manually and check). I've seen issues where if your advertising a default route into your azure tenancy via an express route or VPN this can cause issues as well. (You either need to configure your on-prem infrastructure to allow internet access from VMs in your Azure tenancy, filter the advertised route or edit the route table for the management subnet). On the firewall side you need to make sure that traffic can flow from the management, DMZ, and tenant subnet to the internet. (This can be tested using the manual VM deployment I mentioned earlier)
@@shanefowler9370 hey , i the DNS team double check it and we found a problem with the comunication between the dns and Azure, fix that and worked like a charm
@@anandakrishnansivasankaran4450 we found a problem with the comunication between the dns and Azure, fix that and worked like a charm
Victor Jaraba thanks for letting us know about the fix. Glad to help.
.. love it ..