Anyone running MCS VDAs in Azure on v6 VMs? I just...
# citrix-vad
n
Anyone running MCS VDAs in Azure on v6 VMs? I just built a new master image/catalog and provisioned some W11 VDAs, and see this in Computer Management:
o
Hey Nick, we are in pretty sure but havent looked for this specifically. Not sure on this here. Maybe that new persistent location for WEM cache they have for non persistent now? I have to go check notes on what folder that was
n
I was told it was a mapped folder, but that was pretty much it. No WEM involved in this catalog, either. Worth mentioning that in the net-new v6 VMs I can restart the Citrix Pvs for VMs agent service, but if I convert a v5 VM to v6 using this procedure, this service basically fails: https://techcommunity.microsoft.com/blog/sapapplications/converting-azure-virtual-machines-running-windows-from-scsi-to-nvme/4192583
o
@Nick Panaccio Just checked my notes from prior convo with PM and engineers for WEM and this location is definitely the WEM persistent location now - not sure why you have it but this it. Here is what SR engineering resource confirmed in prior convo @Ray Davis and I had with them on something else for WEM with this new capability. Good summary! The file in the C:\Program Files\Citrix\PvsVm\Service\PersistedData\ is the compressed data and the agent generates the database using that cache file if it exists.
r
Yes, that is correct for WEM. Also last week myself and @richminichiello seen this when installing/looking at a topaz driver. It showed that the part of the config went here too, which I was a bit puzzled on the why. But the screenshot you show, we had the same thing in some USB stuff.
But you reminded me to follow up on the WHY here outside of WEM.
o
so might be location they are using as multi-purpose persistent data location for pooled is my guess
r
yea, that was what we thought too. Like a fail safe for something that needs to stick.
n
My guess was that it's the identity disk, which would make sense for the WEM bit, but I know that more info is stored here
You can see it in the registry
r
That is the junction point to the disk, yep
n
What I don't get is why this volume shows up as a portable device in Computer Management
This whole exercise for us started by wanting to try out the v6 SKU in Azure, which uses NVMe disk controllers.
r
You can look in that location via psexec. I had to do it to fix an issues on some honey pot files that AV dropped there before.
No recommended to tinker with it, but you can look if needed.
n
Oh, I don't even care what it stores, etc. More concerned with the comp mgmt thing
We don't see this with out v5 SKU stuff. I've got a note in to Citrix devs, so hopefully they can shed some light.
I don't even know if they support MCS in v6, or on these VDA versions.
r
I started seeing this on W11 24H2. I don't recall seeing it on previous builds myself.
o
Im opposite here. I don't really care what it shows up as - i only care it works as expected and for what it can be used for.
n
Well, the fact that it shows up as a yellow bang concerns me, lol
r
yea, same here. LOL
o
lol OCD aspect
r
haha.
n
The service that storage is tied to also handles computer object password resets, etc. Kinda important
o
k, yeah, I have to many other things to worry about with functionality and making sure working as expected. That again is functionality. not cosmetic item that I care about so goes back to what we have to worry about with any of that
so far, working as expected for WEM cache, we had some convos on A/V files going there, etc.
n
I have three more days of being in a change freeze, so I'm avoiding more serious stuff
Yeah, I tested the WEM cache stuff for S16 not too long ago, and it worked nicely
o
where its a portable device in device manager or not is cosmetic for me in how windows detects it - at least for now - until i find something that this affects how something is working
so that's what I have on that.
n
My concern is that I won't know until the AD object password reset fails and we have bigger issues, so digging in on this now. I can't find any relevant logs for this, unfortunately.
o
will let you know if we get word on how that shows up there in device manager from further convo
👍 1