This message was deleted.

Yes we are using this key on our VDAs as such it does not matter if workloads in azure or on prem. That enables communication over EDT protocol for the VDA

This is only required if you have specific challenges with MTU - Azure had it back in the early days of NetScaler deployments, but I hadn't touched that in the last 4 or 5 i did prior to leaving consulting - so no in short, it's there on a per-use-case basis. MTU discovery should be your friend now though?

MTU Discovery should handle that just fine now. Previously there was only hard coding the MTU as no client supported it, then Windows did and others but not - Linux for example we had to wait for and still hardcode as the IGEL/Linux situation didn't support the auto discovery in tandem. But yea, if you had any CWAs that didn't support the auto negotiate you still have to hard code it in. Azure you still have to usually make sure it stays under some value for NetScaler but autodiscovery on supported VDA and CWA together should handle figuring it out now.

I may be spinning my wheels on this but have to satisfy those asking to do some testing. Biggest complaint is Teams (if you can believe that) and with HDX redirection, any MTU changes aren't going to affect that traffic because it's outside the ica tunnel.