At the moment we have the problem that an AVD agent upgrade has to be carried out after the VMs have been created. And this is only because the old agent is still installed with the installed Nerdio version. At the moment this leads to a problem where the session host no longer accepts sessions, which causes problems with depth-first.
I think it makes sense to keep the AVD agent version independent of the Nerdio installation.
It would be ideal if you could configure in Nerdio on the host pool for VM creation which version of the AVD agent should be used:
- Latest (independent of Nerdio, simply always the latest version)
- Nerdio (The version that is stored in the Nerdio instance)
I'm not sure if you should be able to select versions, but Microsoft's update management will probably override that again.
At best, Autoscale could be improved so that VMs that are being upgraded are not switched off until the upgrade is complete.
Comments (5 comments)