Figure this is worth asking again. For anyone usin...
# citrix-vadn
Nick Panaccio
03/27/2025, 2:19 PMFigure this is worth asking again. For anyone using Azure for persistent VDAs on v6 SKUs, can you confirm that you're seeing this in Device Manager on those VDAs? Trying to get Citrix to confirm whether or not this is normal/expected, but haven't had luck. I see this in any MCS persistent image I build on a v6 SKU.
j
James Kindon
03/27/2025, 9:22 PM@Yuhua Lu maybe one for your team
y
Yuhua Lu
03/28/2025, 2:02 PMAh, thanks James. I just got asked yesterday on same issue from different customer. I am not sure what it is but engineering is looking into it. So far no impact to any operation, restart VM agent service works as well just odd entry showing up... Do you observe the same or you have additional info? @Nick Panaccio
n
Nick Panaccio
03/28/2025, 2:18 PMI actually had issues restarting that service - it fails entirely. However, if you stop the service, then start it, that works.
Nick Panaccio
03/28/2025, 2:19 PMWe have a request into Citrix engineering and the PM on the issue, just waiting on their findings. This is a red flag to me given that we want to switch over to v6 immediately, meaning we'll have 1000s on it in short order. Big risk until Citrix can confirm that we can safely ignore this for now. And if this winds up being addressed in a future CU... I guess that's okay, but I would prefer a hotfix so we didn't have to wait (this is 2402 CU2, but I swear I saw this on older VDAs, too).
y
Yuhua Lu
03/28/2025, 3:12 PMIf the image is converted from SCSI based, then yeah, we have customer reporting that behavior. If you build NVMe based image ground up, then no issue observed
n
Nick Panaccio
03/28/2025, 3:12 PMThese are net-new builds straight from Azure image gallery. New VM, run SCCM task sequence to install our apps, etc.
y
Yuhua Lu
03/28/2025, 3:18 PMWe have a request into Citrix engineering and the PM on the issue, just waiting on their findingsDo you have name of engineering and PM? because it should be me and/or Jeff
Yuhua Lu
03/28/2025, 3:18 PMlet me loop in our engineer who started looking into this @Paul Browne he is architect of MCS
n
Nick Panaccio
03/28/2025, 3:20 PMTrying to get the names. We have somebody from Citrix directly tied to our account, so I go through him for everything.
Nick Panaccio
03/28/2025, 3:24 PMlol... you're the PM and Paul is the engineer, so I'm the guy you're looking into this stuff for.
😃 1
😅 2
Nick Panaccio
04/22/2025, 10:52 AMI've got a ticket open with MS on this, and it's definitely related to the NVMe controller. I just confirmed that adding a data disk to a v5 SKU with an NMVe controller shows the same in Device Manager. Still hopeful that MS says we can safely ignore it.
y
Yuhua Lu
04/22/2025, 6:55 PMThanks Nick. Paul was on PTO last couple of weeks. We had another engineer looked into and determined it is generic issue with Windows whenever there is data disk attached to VM
n
Nick Panaccio
04/22/2025, 7:10 PMYep, I replicated what you saw with a vanilla disk attached to the OS, so I'll see what MS says and will update this thread in case anyone else runs across it. Once we have this info, it might be worth having Citrix make a note of this in the documentation.
Nick Panaccio
05/08/2025, 10:43 AMUpdate: Microsoft directed us to make the following registry change to address this issue where Azure v6 SKU VMs - or v5 SKU"s that use NVMe controllers, which is the real culpret - show attached disks as portable devices:
Path: HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters
Name: BusType
Value: 8
Type: REG_DWORD
This worked for us in our testing, so we're moving forward. You will also be shocked to learn that this is not documented.
🙌 1
👍 1