Windows Virtual Desktop shutdown for inactivity

%3CLINGO-SUB%20id%3D%22lingo-sub-1314441%22%20slang%3D%22en-US%22%3EWindows%20Virtual%20Desktop%20shutdown%20for%20inactivity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1314441%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20WVD%20with%20single%20provisioned%20host%20pools%20and%20single%20user%20images.%20This%20was%20by%20design.%20We%20can%20set%20auto%20shutdown%20for%20each%20desktop%20but%20we%20would%20really%20like%20to%20have%20the%20WVD%20autoshutdown%20after%20a%20period%20of%20inactivity%20and%20then%20be%20deallocated.%20Is%20there%20a%20solution%20that%20can%20do%20this%3F%20or%20is%20Microsoft%20working%20on%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1314441%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInactivity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Virtual%20Desktop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWVD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1332849%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20shutdown%20for%20inactivity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1332849%22%20slang%3D%22en-US%22%3E%2B%20same%20question%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1332984%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20shutdown%20for%20inactivity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1332984%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F625457%22%20target%3D%22_blank%22%3E%40rachterberg%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20a%20Microsoft%20guy%2C%20just%20a%20WVD%20user.%26nbsp%3B%20But%20I%20think%20this%20is%20functionality%20that's%20far%20down%20the%20road%20at%20the%20moment%20if%20it's%20even%20on%20the%20roadmap%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20set%20up%20some%20Azure%20automation%20to%20deallocate%20based%20on%20CPU%20usage.%26nbsp%3B%20Check%20this%20out%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fautomation%2Fautomation-solution-vm-management-config%23cpuutil%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fautomation%2Fautomation-solution-vm-management-config%23cpuutil%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20maybe%20configure%20that%20for%20your%20session%20hosts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1636760%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Virtual%20Desktop%20shutdown%20for%20inactivity%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1636760%22%20slang%3D%22en-US%22%3E%2B%20same%20question%3CBR%20%2F%3E%3CBR%20%2F%3EReally%20need%20a%20way%20to%20autostop%20personal%20desktops%20so%20we%20can%20experience%20cost%20savings%20without%20full%20deallocation.%20We%20have%20a%20lot%20of%20devs%20and%20people%20who%20need%20personal%20desktops%20where%20a%20pool%20will%20not%20work.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20transitioned%20to%20WVD%20and%20previously%20used%20Amazon%20Workspaces%20and%20it%20has%20the%20ability%20to%20autostop%20'personal'%20VMs%20when%20a%20user%20is%20not%20active%20after%20'x'%20number%20of%20hours.%20This%20puts%20the%20Workspace%20into%20more%20of%20a%20'sleep'%20mode%2C%20not%20necessarily%20stopped%20'deallocated'%20which%20ensures%20no%20lost%20work.%20Also%20when%20the%20Workspace%20is%20autostopped%2C%20the%20login%20to%20the%20Workspaces%20client%20will%20auto%20launch%20the%20Workspace.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20found%20the%20tool%20called%20Azure%20Starter%20(%3CA%20href%3D%22https%3A%2F%2Fblog.itprocloud.de%2FWindows-Virtual-Desktop-Azure-Starter-for-WVD%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.itprocloud.de%2FWindows-Virtual-Desktop-Azure-Starter-for-WVD%2F%3C%2FA%3E)%20but%20this%20requires%20the%20end%20user%20to%20power%20it%20down%20themselves%2C%20there%20is%20no%20automation%20without%20the%20risk%20of%20lost%20work.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

We are using WVD with single provisioned host pools and single user images. This was by design. We can set auto shutdown for each desktop but we would really like to have the WVD autoshutdown after a period of inactivity and then be deallocated. Is there a solution that can do this? or is Microsoft working on this?

3 Replies
Highlighted
+ same question
Highlighted

@rachterberg 

I am not a Microsoft guy, just a WVD user.  But I think this is functionality that's far down the road at the moment if it's even on the roadmap at all.

 

You can set up some Azure automation to deallocate based on CPU usage.  Check this out:

 

https://docs.microsoft.com/en-us/azure/automation/automation-solution-vm-management-config#cpuutil

 

So maybe configure that for your session hosts.

Highlighted
+ same question

Really need a way to autostop personal desktops so we can experience cost savings without full deallocation. We have a lot of devs and people who need personal desktops where a pool will not work.

We have transitioned to WVD and previously used Amazon Workspaces and it has the ability to autostop 'personal' VMs when a user is not active after 'x' number of hours. This puts the Workspace into more of a 'sleep' mode, not necessarily stopped 'deallocated' which ensures no lost work. Also when the Workspace is autostopped, the login to the Workspaces client will auto launch the Workspace.

We found the tool called Azure Starter (https://blog.itprocloud.de/Windows-Virtual-Desktop-Azure-Starter-for-WVD/) but this requires the end user to power it down themselves, there is no automation without the risk of lost work.