I think I asked this before or saw this somewhere, but how do you guys handle updates to platform layer so it does not mess up the PVS cache drives later? I followed the Citrix's doc about adding a disk, settings signature, and specifying the drive letter. Then removing during promotion. But recently when I did this my images booted up with cache drive moved to another drive letter. anyone seen this?

Unless they are using the old streaming wizard you dont have to do anything.

I am using the streaming wizard with templates and cache drive homed to E

ok then when you create the platform layer you need to copy your cache disk into the packaging machines folder and attach it, then add it in as the e drive so that windows saves the vol id wiht the vm. That way when uts deployed it will knwo to make that volume the e drive

I was adding a blank drive before to the platform layer, setting the same signature and drive letter. And it worked but for some reason it stopped working 🤷‍♂️ 🤔

i find it easier to just use a copy of the actual disk that way you are sure of the ids

Do you know if this process is documented somewhere?

its not

hmm

yea thats correct i wasnt aware of that artolce but it will work.

so if I was to attach existing disk, how would that be done in VMWare? sorry for dumb question.

its a whole lot easier to use the d drive and the virtual desktop setup wizard

"point to the oen" ? what is that?

sorry point to that one

trying now....

you wont need to detauch becasue that vm will get deleted

would the promote process not get messed up if there is extra disk attached?

no

ok looks like i did not even need to change drive letter - it set itself to E

we just copy the fisk and throw it all away

great. I will make the updates and promote. fingers crossed. (adding the project to switch to D and use modern provisioning wizard)

good luck let me know how it goes

working on it now. Thank you for all your help and advice @Rob Zylowski

Youre very welcome