Autostart after 60 days (token refresh AVD)

Avatar
Stefan Beckmann

After you register a VM to a host pool within the Azure Virtual Desktop service, the agent regularly refreshes the VM's token whenever the VM is active. The certificate for the registration token is valid for 90 days. Because of this 90-day limit, Microsoft recommends VMs to be online for 20 minutes every 90 days so that the machine can refresh its tokens and update the agent and side-by-side stack components.

Can you add a feature that ensures that a VM is started for at least 20 minutes after, say, 60 days at the latest? Unfortunately, I already have this problem in labs and test environments, and it would certainly help to prevent a VM from having to reinstall the agent first. If Autoscale starts additional VMs and starts the VMs that have not been in use for the longest time first, this would optimize things even further and hardly any VMs would need to be started because they have not been used within the last 60 days. However, test host pools could still be affected.

https://docs.azure.cn/en-us/virtual-desktop/faq#how-often-should-i-turn-my-vms-on-to-prevent-registration-issues-

1

Comments (3 comments)

Sort by
0
Avatar
Carl Long
We appreciate your feature request—community input is essential to our ongoing development.

Next steps:
     • We will review your suggestion and update its status during the evaluation process.
     • If further clarification is needed, we'll contact you via comments.

We also encourage others to contribute through feedback and voting.
1
Avatar
Keegan Shearer

Could this not be done by using the Maintenance Window feature located in the Settings of the Hostpool to enable all hosts to power on once a week to get AVD Agent updates?

0
Avatar
Stefan Beckmann

That's right, that should work. Now that you mention it, I had already thought of that myself, but then forgot about it. 

Nevertheless, it would make sense for Nerdio to ensure that all instances are started after, say, 60 days if no maintenance window is configured with the option to start all vms prior. I have host pools (Lab) where I have not configured a maintenance window, and these are only started when needed.

Please sign in to leave a comment.