wondering if anyone else can reproduce this issue - when editing an MCS catalog with machines in Azure, the "select machine size" dialog does not return any results (see attached images). Creating new catalogs provides the correct "select size" dialog as expected, but editing an existing catalog always fails to return results

Do you not have a Machine Profile selected (a few tabs up)? I've never run into this, but that would be the first thing I checked.

thanks for reply, checking the machine profile selection now...

Do you have this box checked at the bottom of the screen when you do the select size? I will ask what is meant by only machine sizes this catalog supports as im not sure what that chaecks

Apparently customer doesn't have that checkbox. They have tried updating via PowerShell and received a more detailed report: It looks like the problem is down to the catalog using ephemeral disk, Citrix Cloud doesn't think that the new E8ads_v6 series provides a temp disk (spoiler alert, it does!) https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/memory-optimized/eadsv6-series?tabs=sizestoragelocal#feature-support @Yuhua Lu are V6 series SKUs not fully supported with Citrix Cloud + MCS yet? Thanks

Generally speaking, v6 is absolutely supported, as we're using them for our W11 testing (about to move to Prod).

are you using ephemeral Nick? I saw your other thread about the unknown PVS device on V6, thanks for sharing that btw

We tested it, but only on v5 SKUs. Our v6 stuff is all Standard_D4as_v6 for W11 persistent.

appreciate the insight

We've got the exact same error from DaaS testing the V6 SKUs @Chris Rodgers

there is another thread around mcs and nvme ephemeral support which looks to be that issue. Fix coming end of July or so per Yuhua, Citrix PM around MCS. I’ll find it later and link, popped in for a few and saw this so just replying quickly. hope you all are good!

@Shane Kleinert just checking in to see if you managed to find the thread - I had a look through Citrix forums but couldn't find anything relevant

I ran into this ages ago so it seems to be a recurring issue

Folks, fix for ephemeral disk support is scheduled to roll out at 26th May - 13th June from DaaS, CVAD fix will be in 2511, sorry the troubles it caused.

Do you have an internal case ref @Yuhua Lu so I can get our ATS to track it?

It is on DaaS release 125, you can ask the ATS to track the release progress

Thank you @Yuhua Lu - is there an associated KB article yet?

Hi Neil, there is no KB planned for this one