This message was deleted.
# citrix-vads
Slackbot
12/08/2023, 1:28 PMThis message was deleted.
r
Ray Davis
12/08/2023, 1:29 PMRay Davis
12/08/2023, 1:30 PMeither BIS-F or CVAD 2305 and later.
https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/machine-catalogs-create.html#assign-a-specific-d[…]rite-back-cache-disk
m
Marco Hofmann
12/08/2023, 1:33 PMThank you for the hint, so it was in the Release notes of 2305+
We are on 2203.3000 for this project. So I can't set it via Studio/PowerShell.
But I didn't understand the answer from @Matthias Schlimm
Can I set it through BIS-F with a VDA older than 2305, or will this break the process?
m
Matthias Schlimm
12/10/2023, 6:53 AM@Marco Hofmann before VDA 2305 that’s hard coded by Citrix to drive D for MCS. If you configure it with BIS-F to a different driveletter other D, ended up in a reboot loop.
First with 2305 or later, you are able to configure a different driveletter with Powershell
m
Marco Hofmann
12/11/2023, 9:51 AMHi @Matthias Schlimm! I do understand that to a 90% degree. But BIS-F 7.1912.7 is much older than VDA 2305, and the option to select a MCS drive letter is there non the less. That's the point that confuses me. Why was that option part of BIS-F, long before VDA 2305?
Besides that I think the conclusion is still, that it's impossible with VDA LTSR 2203.3000 and I would have to use VDA CR 2308 instead.
Would it be enough to switch just the VDA, or would I have upgrade the Delivery Controllers to gain access to the PowerShell Commands?
Or can BIS-F solve that with Controllers 2203.3000 and VDA 2308?
m
Matthias Schlimm
12/12/2023, 12:08 AMI think this is a delivery controller feature, but I has not testet it. BIS-F old or not, expect that the VDA unterstand a different driveletter than D.
Sorry, not the best answer I know 🙈