We are using PVS 7.6. is that ok to merge to maintenance/Test while I have a number of targets running the image?
Please see my screenshots from our PVS console, can you see any problem merging this?
You can merge, it should just create a new version'd disk. When I have done it, the old versions that you will have to cleanup out of the store will have a red X when you view the versions in PVS console.
But, what drive are you expanding?
Is it the actual PVS disk that is booted to? (The C: drive)
Or is it a log drive?
Never let the pagefile write to the C: drive, you also want your vdiskdif.vhdx pointed away from C: as well. For a production PVS guest booting from the PVS image, the more changes made to the C: drive will cause the vdiskdif.vhdx to grow rapidly. Hence scheduled reboots.)
If it is not the PVS C: drive that you are extending, the below will help.
Since we know nobody want to deal with KMS any more than needed.... avoid private mode.
I am in the process of doing this now and it is working like a champ.
I have a 20GB D drive on the guests for logs and EdgeSight, which was not enough once we added PrinterLogic to the PVS image.
I extended it on the my PVS image Maintenance server by 5GB and Generalized the image and promoted it.
Booted the Maintenance guest up and it has the new space.
Booted one of the other guest servers and it sees the extra 5GB but has not been extended, so it is not usable.
For giggles, I extended it on the PVS guest (not in maintenance mode) and rebooted. But to my surprise that it actually retained it......
I think it has more to do with the actual disk itself for that PVS guest. Each PVS guest is unique and such each disk is also.
Citrix PVS is not provisioning that "Log" disk, so it cannot manipulate it as each PVS guest boots.
But once it is extended on the PVS image and set in Production, you still have to manually extend it in each existing PVS guest.
The only way around that would be to modify your VMware (hyper-V) template to include the extended space, delete the guests and run the Streamed Vm Setup and deploy from the new template.
It just depends which one you think will cause more work. I guess that would depend on how many PVS guests you have.