Change running OS Disk with "Start VM on Connect"

Hi,

we have a few customers where we try to minimize costs as much as possible, especially during the POC phase or for host pools that are used only occasionally.

To achieve this, we set the minimum active hosts to 0 and enable “Start on connect”. And we configure the stopped OS disk type to Standard HDD.

However, I noticed that when a VM is started via the “Start on connect” the OS disk remains on Standard HDD. This makes sense, as the VM is started by AVD and not by Nerdio.

 

I’d love to hear your thoughts or recommended best practices in this scenario. Would you still suggest keeping the minimum active hosts at 0 but disabling OS disk optimization

Or would It make sense to raise a feature to get OS disk optimization working even with “Start on connect”?

Philipp

1

Comments (3 comments)

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.
0
Avatar
Dave Stephenson

We've had a few partners ask for this, but the Start VM on Connect functionality is native in Azure so we're kind of limited in what we can do (see Start on Connect button needs more information icon to let you know Nerdio startup scripts won't run – Nerdio Help Center for more info).

Nerdio did add the “Set all hosts to running OS disk type" function to the Pre-Stage Hosts section of the Auto-Scale Profiles that kind of works as a work-around for the “Start VM on Connect” feature.

Do you think that will work for what you're needing?

 

1
Avatar
Philipp Mair

Hi Dave, yes I thought that this would be something where Nerdio has no influence.
So we'll have a look at the “Set all hosts to running OS disk type” feature. 

Thank you!

Please sign in to leave a comment.