I recently deployed some AVD session hosts using a custom image that I created from a virtual machine which had accelerated networking enabled. However, after deploying the session hosts, I noticed that none of them have accelerated networking turned on, and I have to enable it manually for each one. The image definition clearly has the setting for accelerated networking set to true. Has anyone else encountered this issue or have suggestions on how to fix it? It's really inconvenient to make these changes after deployment. Any help would be appreciated!
4 Answers
We're experiencing intermittent latency issues with our users, which is why we manually enabled accelerated networking, and we noticed a significant drop in call rates. I'm really looking to find a way to automate it during the image deployment process for better efficiency since we're planning on moving to ephemeral disks with dynamic scaling.
It might depend on the SKU of the VM you used for the deployment. Make sure you’re using the same SKU that had the accelerated networking feature enabled during the image capture.
Just a heads up: the accelerated networking setting is usually tied to the NIC configuration rather than the OS image itself. So if the NIC isn't set up correctly on the new session hosts, that could be the reason why it's not enabled automatically.
On a related note, why are you enabling accelerated networking? Have you noticed any significant improvements? We turned it on for one of our pools, but neither our users nor we saw any notable changes.
We tested it using a tool called Latte and found that it can provide considerable performance gains, especially depending on your workload. You might want to check it out: https://github.com/microsoft/latte.
I checked, and I used the same SKU: d4as v5.