Ok, back to trying and provision PVS images from C...
# citrix-provisioning
j
Ok, back to trying and provision PVS images from Citrix Web Studio. Got the PVS servers joined to Delivery Controllers, and attempting to build. But they are creating Identity Disks in Azure like MCS machines, instead of just the BDM and writecache disk. Anyone been able to build PVS images from Web studio in Azure?
n
Probably not the same way you are. We're taking our compiled PVS image (done via App Layering) and running it through Citrix IPS to convert it to an Azure image, then building the catalogs using that image.
Actually, ignore me because I'm an idiot. This is non-persistent MCS, not PVS.
r
That is the benefit of using studio provisioning. Identity disks work better than using the database to store the identity and trust information
j
Yeah, unfortunately it breaks PVS images. They don't join to the domain correctly, because there are effectively 2 layers setting those passwords and machine states
r
?? It shouldn’t be using the old way when you use studio provisioning
c
If you install the proper version of the VDA it will work. Also do not set the PVS vdisk to do AD, that will be handled by the MCS agent code installed by the VDA. the reason for the change to add the identity disk is to take advantage of features that rely on the identity disk,
j
There needs to be more documentation on this then. Because no matter what configuration changes I make on the prov-scheme I can't get it to work and line up correctly. I have a call setup with support to go over my configuration and see where the failures are happening.
s
When you create a target using studio provisioning, it appears in a separate area in the PVS console and AD management is disabled for targets in that area of the console tree. But as Carl said, you have to be running VDA >= 2311 to allow studio provisioning to work... so the vdisk needs that VDA installed.