Skip to content
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

SKU and VM size in Azure wrong and gives error during deployment #4

Open
LockTar opened this issue May 10, 2022 · 0 comments
Open

SKU and VM size in Azure wrong and gives error during deployment #4

LockTar opened this issue May 10, 2022 · 0 comments

Comments

@LockTar
Copy link

LockTar commented May 10, 2022

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Use the deploy to azure button on the samples page

Any log messages given by the failure

"The following list of images referenced from the deployment template are not found: Publisher: MicrosoftWindowsDesktop, Offer: Windows-10, Sku: rs5-pro, Version: latest. Please refer to https://docs.microsoft.com/en-us/azure/virtual-machines/windows/cli-ps-findimage for instructions on finding available images."

Expected/desired behavior

The whole template is deployed

OS and Version?

Windows 11

Versions

Latest

Mention any other details that might be useful

It seems that sku rs5-pro is replaced by sku rs5-pro-g2. When I changed that in the portal and redeployed the SKU error was solved.

Another error was the VM Size. When I clicked the "deploy to azure button" from this page the VM size was a "VM Generation Support Gen 1" Standard_D2_v3. It must be a Gen 2. In the code I saw the the size Standard_DS3_v2 and that worked. Is the last version of this code already deployed to Azure???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant