Just an interesting observation... I went out to Citrix documentation and noticed they no longer maintain the below document where you get the scripts for SQL AlwaysOn (you know multisubnetfailover=true) and the new documentation no longer has them available. If you go to the old link to grab them, they are dated 2014. I thought surely there are newer ones and that's when I noticed they were no longer in the documentation.. PVS is still maintained/updated but not CVAD... weird. Anyone know what's up with that? Old link that has scripts (It has an "Important" note stating it was written and tested on XD 7.6 and they no longer maintain or test with later versions): https://docs.citrix.com/en-us/advanced-concepts/implementation-guides/database-connection-strings#update-strings-manually New Link that doesn't have scripts: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/technical-overview/dat

the product can figure it out on its own now, I set it up with multi subnet Basic Availability Groups without needed to run any scripts

Got any proof of that?

Run the powershell after adding a multi subnet listener and it’ll show it is multi subnet

ah, good point

You might still have to set it if you manually change the database later, but if you have it set it up automatically then it can figure it out itself using the database account.

That is why you are a ctp and we are not 🙂

lol, I think I lucked out there :P

I almost asked Mike if he would post a screenshot of the powershell showing the output... I think it's something like "Get-DBConnection"... I guess I wasn't the only one thinking about proof... LOL Good one Mr. Miller!

I don’t have direct access tot he client environment where I set this up, but it’s this: Site database = Get-BrokerDBConnection Monitoring database = Get-MonitorDBConnection –DataStore Monitor Configuration logging database = Get–LogDBConnection –DataStore Logging

Any update from the CTP chat?

nothing yet

Thank you sir! Always good to know those little details 🙂

it’s funny how things change as .net changes, Guy Leech ran into this with a storefront upgrade that did funny things with TLS because it originally used an older .net

And after all that... they ended up not having a muti-subnet failover... so I won't be able to share what it would look like in Powershell. Maybe the next deployment... womp... womp.