Has anyone tested PVS catalogs with WebStudio? It seems as the complete documentation on how to implement this was just copied from citrix cloud docs. For a vmware on-prem pvs catalog it states: -HostingUnitName "AzueRes" -IdentityPoolName $catName

-InitialBatchSizeHint 1 -LoggingId "854xxxxx-2xxx-42e0-axxx-8c6xxx406xxx"

-MachineProfile "XDHyp:\HostingUnits\AzueRes\machineprofile.folder\abcdpvs.resourcegroup\abvda.vm"

-NetworkMapping @{"0"="XDHyp:\HostingUnits\AzueRes\\virtualprivatecloud.folder\East US.region\virtualprivatecloud.folder\abcdpvs.resourcegroup\fbgv-vnet.virtualprivatecloud\default.network"}

-ProvisioningSchemeName $catName

-ServiceOffering "XDHyp:\HostingUnits\AzueRes\serviceoffering.folder\Standard_D2s_v3.serviceoffering"

-UseWriteBackCache -WriteBackCacheDiskSize 40 ` -PVSSite 6556cxxx-fc88-45f6-8xxx-ea4b665e9xxx -PVSvDisk cf056xxx-f69b-xxxx-9a60-c41072b8xxxx .......... very bad documentaiton.

@Jitao Hou 👆

I am working with document team now to include an example on VMware.. Will be published soon.

Thanks Jitao, I was in contact with Ron 😉

I got a PoSH script now from our testing team, would ask team to verify and test in our lab environment. Hopefully we can publish it early next week.

Nice, beside the script some more information would be nice. Like: For Catalog Creation you must specify vdisk uuid. What happens when you delete the vdisk? Is it possible to change vdisk uuid in catalog or has the catalog to be recreated?

We have this in our backlog to change vDisk assignment for existing catalog on Studio…

Hi @Jitao Hou, saw your posh example. Its based on Citrix Cloud => VMware, I was looking vor CVAD onprem => VMware, so I modified it a little bit. It seems that many properties provided are just "compability things", which let the catalog looks good in WebStudio. For Example WriteBackCacheDiskSize and WriteBackCacheMemorySize Can you confirm this? Or are these parameters affecting anything? (Cache an RamCache are specified on the pvs vdisk and wont be changed by a delivery controller...)

Yes, you are correct. Please skip that parameter WriteBackCahceMemorySize.