Forum Discussion
poblem provisioning a host pool behind proxy
Hi,
I am trying to provision a host pool to a subnet which is firewalled. All virtual machines (including session hosts) are supposed to have internet access through a proxy server.
problem is that WVD host pool provisioning uses DSC VM extension and tries to download the configuration from a source that is not accessible by VMs.
Wondering if there is any workaround for this problem.
vadood2120 : At the moment, we do not support proxies for the deployment stage. For now, I would recommend two options:
1. If you're early in testing, I would start with manual provisioning (https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell).
2. If you're beginning to push towards pilot/POC/production pilot, I would recommend forking our GitHub repo indicated here in the ARM template steps: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-arm-template . You can then host local versions of the files, then edit the _artifactsLocation parameter to point to your local versions. Unfortunately, this means you won't get all of the changes immediately, but you can manually keep your repo in sync with ours.
- Christian_Montoya
Microsoft
vadood2120 : At the moment, we do not support proxies for the deployment stage. For now, I would recommend two options:
1. If you're early in testing, I would start with manual provisioning (https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-powershell).
2. If you're beginning to push towards pilot/POC/production pilot, I would recommend forking our GitHub repo indicated here in the ARM template steps: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-host-pools-arm-template . You can then host local versions of the files, then edit the _artifactsLocation parameter to point to your local versions. Unfortunately, this means you won't get all of the changes immediately, but you can manually keep your repo in sync with ours.
vadood2120
Now, I face the problem same you. my organization want to make WVD on Private Network, so i use AzureFW to fillter outbound.On Pic1 1st 6 rules is on WVD doccument recommend to open outbound. After that for Log-Analytic and Automation services.
Although, we open rule follow on Pic1 for connect to WVD services, we can reach and work (if we already deploy hostpool already.) but we will issue on deploy new hostpool, deployment will failed.
So, i try to query on AzureF Firewall service log and get some FQDN traffic when deploying. On Pic2 that is Additional FQDN that i found and add more to allow Firewall. so I can suscces deploy hostpool.
but, for safe you maybe open all 443 outbound. because the fqdn vary every month or week because i just add more fqdn on this week.
Pic:1
