Forum Discussion
Hostpool is spining up new vm rather than connecting user to multi session windows 10 desktop
richiewrt: Looks like you might have multiple admins on your side eventually managing those VMs? The Windows Virtual Desktop Service doesn't manage VMs. Please review admin access.
- AquibQureshiOct 09, 2019Brass Contributor
If new VMs were spun up and i suspect it would be scaleup script which you configured for auto shutdown and auto start of the session servers? as scaler VM where you configure task scheduler. is that configured in your environment? If you are not using scaling script then new VMs cannot be deployed automatically by WVD and manual intervention is needed for such type of deployment. richiewrt
- Christian_MontoyaOct 07, 2019
Microsoft
richiewrt : Just to follow-up on Eva's comment, there is nothing that we do within our system that manages Azure resources. If you recall, we do ask for the Azure Subscription ID as part of creating the tenant, but that is just for notification of service outages.
If you look at the Azure resource group with the new VMs, you should be able to track Deployments and you may even be able to see which user account triggered that Deployment in the Activity Log of the resource group.