Forum Discussion
Solved
Recurring session host deployment problems
Summary: I'm having errors during the session host deployment process caused by a failure of the new VM to connect to the Internet and download a .zip file. A Microsoft support engineer is advising m...
- This is now resolved, with the help of MS support. I'll just copy and paste the case summary here, since it captures the issue pretty well.
Symptom: Need help in fixing session host deployment failure when adding a new session host in host pool.
Resolution: We helped you in fixing the session host deployment failure by asking you to use a NAT Gateway to provide a fixed public IP address for your session hosts rather than a load balancer.
This allows you to replace your Load Balancer and on a per subnet level, allows all outbound connections to use specified static public IP address(es).
Reference Articles :
Virtual Network NAT: https://docs.microsoft.com/en-us/azure/virtual-network/nat-overview
NAT Resource: https://docs.microsoft.com/en-us/azure/virtual-network/nat-gateway-resource#resource
Implementation: Tutorial: https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-create-nat-gateway-portal
Update for anyone following along ...
In my environment, I have an Azure load balancer configured with a backend pool. (I configured this so that all my session hosts have the same outbound public IP address.) I have noticed that the VMs getting deployed through the session host deployment wizard have no Internet connectivity whatsoever, unless/until I add them to the backend pool. My ticket at Microsoft is being routed to the Azure networking team so they can help figure out what it is about my network configuration that's blocking Internet access for VMs that are outside the load balancer. (There's no way to add a session host to a load balancer as part of the deployment wizard.)
Stay tuned ....
In my environment, I have an Azure load balancer configured with a backend pool. (I configured this so that all my session hosts have the same outbound public IP address.) I have noticed that the VMs getting deployed through the session host deployment wizard have no Internet connectivity whatsoever, unless/until I add them to the backend pool. My ticket at Microsoft is being routed to the Azure networking team so they can help figure out what it is about my network configuration that's blocking Internet access for VMs that are outside the load balancer. (There's no way to add a session host to a load balancer as part of the deployment wizard.)
Stay tuned ....
