-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DSC configuration file #790
Comments
This! How can we find the latest version? I binged the https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts url and found a reference to https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts/Configuration_1.0.02774.414.zip Is this the current version? |
Same question! I am looking at a script that references Configuration_1.0.02774.414.zip but where can I check if there's a newer version? |
Enumeration is not allowed on the AVD product group's Azure Blobs container. Every so often, I run through the Portal deployment and review the JSON file instead of submitting the deployment. That's how I currently track the latest version of the configuration file. I would love to hear if someone has found a better method. It's not the end of the world if you use an old configuration file. When a session host is added to a pool, the agent is automatically upgraded. |
Great suggestion, @jamasten! I'll take a look at whatever version the portal is pulling in. Thanks! |
I'm using Terraform to deploy AVD session hosts. To figure out the "latest" VM DSC extension, I used the AVD wizard of the Azure Portal and I downloaded the ARM template. The ARM file contains the following location of the script:
https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts/Configuration_1.0.02655.277.zip
When trying to resolve what files are in the container I use the following command:
https://wvdportalstorageblob.blob.core.windows.net/galleryartifacts?restype=container&comp=list
I've got the following error:
I have two questions and hope someone can answer them:
Thanks.
The text was updated successfully, but these errors were encountered: