Forum Discussion

jaycrumpgp's avatar
jaycrumpgp
Brass Contributor
Jun 04, 2019

Pool provisioning DSC Extension error ... again

Hi -   Is anyone seeing the dreaded DSC Extension error upon provisioning new pools today?  I have one pool working fine - and have run into this three times in a row with a brand new pool deployme...
Christian_Montoya's avatar
Christian_Montoya
Icon for Microsoft rankMicrosoft
Jun 10, 2019
jaycrumpgp : Are you using a custom image or just a default image from the Azure Gallery? We've had customers report intermittent failures, but not something as consistent as what you're shared.
jaycrumpgp's avatar
jaycrumpgp
Brass Contributor
Jun 14, 2019

Christian_Montoya 

Hey Christian - sorry, I've been on different project work all week.

 

I finally figured this one out.....it was the vnet and subnet I was trying to bind to the East US WVD pool.  I had no default route set, so..no internet...so...the session host couldn't ever download that zip file from the azureedge.net URL that it kept failing on.

 

Live and learn - thanks for following up!

  • rgaron's avatar
    rgaron
    Copper Contributor
    May 02, 2021
    This worked for me. Just needed to have internet access on VNET. Added 8.8.8.8 to the list of DNS servers and worked great. Thanks!
    • nguyenphupn's avatar
      nguyenphupn
      Copper Contributor
      Jun 07, 2022

      Thanks Rob ,In my case, I have deploy hostpool in a VNET managed by firewall, then Firewall block all traffic to internet, I have allowed internet then it worked

       

  • wilsonosorio's avatar
    wilsonosorio
    Copper Contributor
    Apr 16, 2020

    jaycrumpgp Good evening Christian, I appreciate your collaboration, but do I have to do something on the virtual network to have internet access?

    • jaycrumpgp's avatar
      jaycrumpgp
      Brass Contributor
      Apr 16, 2020

      Hi wilsonosorio -

       

      I can't remember my exact scenario now, but this is what it boiled down to for me.

       

      As I was deploying the HostPool, it needs to access the 'azurexxx.net' FQDN that shows up during that DSC extension step.  If there's no name resolution in the subscription, that step will fail.

       

      If you have anything other than an empty subscription (as in, you've been messing with networking settings), then you could have problems as well.  I'm almost positive this is what happened in my original post.  I had a subscription with multiple systems in it:

       

      - couple of networks

      - application network gateway

      - static IPs on other VMs already in the subscription

      - tunneling between this sub and another (before I learned about vnet peering)

       

      I just didn't have a default route defined for the subnet I was using for WVD hostpools.

       

      I've set up multiple hostpools since this time, and it's always worked just fine (with no extra configuration in the subscription for routing/etc).

      • Alex_Prise's avatar
        Alex_Prise
        Copper Contributor
        Nov 17, 2022
        I had pretty similar errors during deployment- VMExtensionProvisioningError
        The DSC Extension failed to execute: Error downloading https://wvdportalstorageblob.blob.core.windows.net......... after 17 attempts: Unable to connect .... I fixed the Network rules of our FW policy by opening outgoing ports for the entire subnet, not just a few specific ones.
        Thanks a lot for the idea!