I am provisioning pvs servers through studio in azure. its working pretty decent but i am running into one irritating thing so far. in the process you must define the write cache disk size. what happens is we use a d16ds_v5 which contains a temporary 600gb disk for a few different reasons. Bis-f does its thing and moves the w/c to the d drive (600gb temp) as it should. However, there is still a 32gb disk (e:\) from provisioning process. Question is, how can I get around that additional drive creation?

Is it actually using that writecache disk? My environment is still flipping back to Server side caching, instead of cache to ram, fallback to disk.

isn't there a file you can put on the drive that tells PVS not to use that particular drive?

What does your prov-scheme look for your catalog?

@Jeff Riechers , yes its using the disk and not falling back to the server

If you modify your provscheme you can change the usetempdiskforwbc value and it will use the Azure temp disk. You may also have to set the use writebackcache to false if you enable the temp disk.

ahh cool - why does it seem like you and I am pioneering this 😉

A trick i used to use on PVS servers was setting a reg key to use the template WC disk rather than letting Xendesktop setup wizard automatically create the write cache disk. https://support.citrix.com/s/article/CTX237313-pvs-xdsw-retain-template-disks?language=en_US

@Jeff Riechers I am struggling with the machine templates in azure. do you have anything thats working you could share so I can hack around?

Not as of yet. Still working with support to track down getting Web studio to generate machines correctly. What versions are you using? And is it on-prem or citrix cloud?

citrix cloud, using 2411 of pvs. bicep is just new to me so Im sure its something simple. I can get the template loaded but cant select them when doing a deployment. Feels like I am missing something

@Shane Swacus Looks like this is bug in the new workflow (backend and Studio). This new workflow only allows persistent WBC disk. It should only allows cache file to live on the WBC disk not temp disk. There are two features in backlog. One is to use temp disk if exist and large enough. Another one is allow WBC to be deleted at shutdown if admin does not need WBC to be persistent

I am still even trying to get the Web studio created machines to properly use the writecache drive, every time I build machines they go to Server side caching, even though the drive is there and formatted. I was able to set the downgrade to standard from premium. I have a ticket open but waiting to hear back on any of the data I have sent and escalated.

Oh, I see, the cache file is not on temp disk?

83090517 might be 2402 cu1 related, as Shane is using CR and it seems to be working for him.

Thanks Jeff, sorry I thought Shane is having problem. We have two problems in thread? 😅

Yeah, we both kind of starting talking about our writecaching issues.

sorry for the confusion. Yuhua, I do not have a support ticket open but I can if youo prefer. My issues, is that the cache file is not on the temp disk, by default. Bis-f does move it there but the original disk still is attached. I'd prefer native to just use the temp disk if that is possible

As Yuhua said, there is a prov scheme flag to specify that the temp disk should be used for cache -- it's entirely possible this is not currently effective for PVS catalogs created with studio. If that is specified then there should be no additional cache disk created at all.

thanks Simon, so you'd have to create the catalog with powershell then instead of studio to do what you are saying? I went back to change the prov scheme previously to use the tempdisk and it doesnt let you do that, it comes back with a message that it shouldnt be used for pvs.

@Shane Swacus what you observed is expected behavior for PVS target created by Studio, that temp disk will not be used for cache file on WBC disk. https://worldofeuc.slack.com/archives/CKL5UCNCX/p1739000183490869?thread_ts=1738853562.444579&cid=CKL5UCNCX To allow PVS target use temp disk is still pending feature in our backlog. I thought you are seeing cache file getting created in temp disk, sorry for misunderstanding