New-AzVmss: Can't find the image 'Win2019DataCenterGenSecond'

Question

New-AzVmss: Can't find the image 'Win2019DataCenterGenSecond'

James Hao 5

I'm testing out creating vmss with image which supports TrustedLaunch, in this case, the 2019-datacenter-gensecond.

New-AzVmss -Credential $vmCred -ResourceGroupName $rgName -Name $vmssName -ImageName 'Win2019DataCenterGenSecond' -SecurityType TrustedLaunch

New-AzVmss: Can't find the image 'Win2019DataCenterGenSecond'.

I tried with -ImageName '2019-datacenter-gensecond', it also says can't find the image.

Is this because 'Win2019DataCenterGenSecond' is not the right image name or the subscription doesn't have the access to this image?

How do I get all the UrnAlias names, especially for 2019-datacenter-gensecond? I can only see the UrnAlias for all the offline images through 'az vm image list --publisher MicrosoftWindowsServer --offer WindowsServer -o table' but the outputs doesn't have the entry for 2019-datacenter-gensecond. If I add --all to this command to list all the images including 2019-datacenter-gensecond, the outputs doesn't have the column of 'UrnAlias'.

kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-11-03T06:13:07.6466667+00:00

Hello, @James Hao !

I was able to both reproduce the error you encountered and was able to deploy successfully using the full URN which I've updated below in the answer. If you get a moment, please consider accepting answers.

Thank you for helping to improve Microsoft Q&A!

Original error:

Successful deployment with full URN:
James Hao 5 Reputation points

2023-11-08T15:52:00.8666667+00:00

Thanks for the finding.

I managed to make it work through Set-AzVmssStorageProfile -ImageReferenceSku '2019-datacenter-gensecond' Then set SecurityType and create the vmss >

$vmssConfig = Set-AzVmssSecurityProfile -VirtualMachineScaleSet $vmssConfig -SecurityType TrustedLaunch

New-AzVmss -VirtualMachineScaleSet $vmssConfig

I found "New-AzVmss -SecurityType TrustedLaunch" very buggy maybe due to my subscription or az module versions. I'm happy to create TrustedLaunch vmss this way going forward in my deployment script.

Thanks again for all the help.
kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-11-13T21:38:32.4133333+00:00

Happy to help, @James Hao !

I've found updating az module (or just using Azure Cloud Shell) to be very useful when running into issues with commands. Hopefully that's all you need. If there is a persisting issue, please start a new thread so we can track and resolve that.

I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-11-03T06:13:07.6466667+00:00

Hello, @James Hao !

I was able to both reproduce the error you encountered and was able to deploy successfully using the full URN which I've updated below in the answer. If you get a moment, please consider accepting answers.

Thank you for helping to improve Microsoft Q&A!

Original error:

Successful deployment with full URN:
James Hao 5 Reputation points

2023-11-08T15:52:00.8666667+00:00

Thanks for the finding.

I managed to make it work through Set-AzVmssStorageProfile -ImageReferenceSku '2019-datacenter-gensecond' Then set SecurityType and create the vmss >

$vmssConfig = Set-AzVmssSecurityProfile -VirtualMachineScaleSet $vmssConfig -SecurityType TrustedLaunch

New-AzVmss -VirtualMachineScaleSet $vmssConfig

I found "New-AzVmss -SecurityType TrustedLaunch" very buggy maybe due to my subscription or az module versions. I'm happy to create TrustedLaunch vmss this way going forward in my deployment script.

Thanks again for all the help.
kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-11-13T21:38:32.4133333+00:00

Happy to help, @James Hao !

I've found updating az module (or just using Azure Cloud Shell) to be very useful when running into issues with commands. Hopefully that's all you need. If there is a persisting issue, please start a new thread so we can track and resolve that.

I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 1

kobulloc-MSFT 19,376 Microsoft Employee

Hello, @James Hao !

How do I find a VM alias I can use with the command, New-AzVmss?

Edit: The solution here is to use the full URN (as 2019-datacenter-gensecond won't work by itself):

MicrosoftWindowsServer:WindowsServer:2019-datacenter-gensecond:latest

Changing image alias is a breaking change which is scheduled with the November 2023 release of PS/CLI. Please refer to https://aka.ms/TLaD for more information.

Old:

The only available aliases for New-AzVmss are:

Win2022AzureEditionCore
Win2019Datacenter
Win2016Datacenter
Win2012R2Datacenter
Win2012Datacenter
UbuntuLTS
Ubuntu2204
CentOS
CentOS85Gen2
Debian
Debian11
OpenSuseLeap154Gen2
RHEL, RHELRaw8LVMGen2
SuseSles15SP3
FlatcarLinuxFreeGen2

Given that list, you are probably looking for Win2019Datacenter.

As a quick aside, az vm image list --all is a great way to find VM SKUs and URNs. A great tool is https://az-vm-image.info/ which makes navigating this information a bit easier:

User's image

I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

User's image

James Hao 5 Reputation points

2023-10-29T11:09:58.7933333+00:00

Thanks @kobulloc-MSFT for clearing it up and providing the azure image online tool.

I might get the wrong impression from https://learn.microsoft.com/en-us/powershell/module/az.compute/new-azvmss?view=azps-10.4.1 where in Example 5 it's using "Win2016DataCenterGenSecond" as imageName, so I thought Win2019 should use the same naming.

As I need an image supporting TrustedLaunch, so choose the 2019-datacenter-gensecond, Win2019Datacenter doesn't support TrustedLaunch according to az vm image show --urn "MicrosoftWindowsServer:WindowsServer:2019-Datacenter:latest"

I will use the imageSku '2019-datacenter-gensecond' in Set-AzVmssStorageProfile -ImageReferenceSku then enable TrustedLaunch either through Set-AzVmssSecurityProfile -SecurityType "TrustedLaunch" or New-AzVmss -SecurityType "TrustedLaunch". Hope that will work.

Other than checking each individual image by az vm image show to find if it's supporting TrustedLaunch, how do I find out all the skus which are supporting TrustedLaunch? any such online tool?
kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-10-29T18:43:11.7466667+00:00

That's a very good point, @James Hao. The example and the description of -ImageName appear to be contradicting each other.

As far as Trusted Launch is concerned, this is a full list of supported operating systems:

https://learn.microsoft.com/en-us/azure/virtual-machines/trusted-launch#operating-systems-supported

According to that, variations of Windows Server should be supported however I'm seeing the same thing.

az vm image show --urn "MicrosoftWindowsServer:WindowsServer:2019-Datacenter:latest"

Should return the following under features:

"value": "TrustedLaunchAndConfidentialVmSupported"

But that's not what I'm seeing:
kobulloc-MSFT 19,376 Reputation points Microsoft Employee

2023-11-01T19:27:08.76+00:00

Hello, @James Hao! I reached out to the document author for New-AzVmss and there do appear to be some errors in the documentation. I've created the following GitHub issue for tracking as requested by the content author:

https://github.com/Azure/azure-powershell/issues/23124

I've also reached out to the VMSS team and will update you if I learn more.

New-AzVmss: Can't find the image 'Win2019DataCenterGenSecond'

1 answer

Activity