We’ve been saving costs using the Stopped OS Disk Type setting in Nerdio Auto Scale, with Running Disk Type set to Premium SSD and Stopped Disk Type set to Standard HDD.
Until recently, all our pooled host pools had Minimum Active Host Capacity = 1. As part of a cost-saving initiative, we lowered this to 0 across ~60 host pools.
After this change, we noticed that the first VM started in each pool is left running on Standard HDD. Fabian confirmed this happens because Start VM on Connect (which we use to start the first VM each day) is an Azure-native feature that doesn’t align with Nerdio Auto Scale disk type settings.
Unfortunately, we can’t use the pre-stage option since our users log in at varying times. This means we’re forced to choose between:
- Active Host Capacity = 0 (greater savings)
- Stopped Disk Type optimization (Premium → Standard while stopped)
We’ve prioritized the Active Host Capacity = 0 option for maximum savings, but ideally we would like to use both features together.
Request: Could compatibility be added between Start VM on Connect and Nerdio Auto Scale Stopped OS Disk Type settings, so that VMs started this way automatically switch to the configured Running Disk Type?
Comments (1 comment)