Mar 31 2021 10:04 AM
Mar 31 2021 10:04 AM
For all early birds who want to start testing, keep in mind that we have the following limitations:
Please review carefully the additional pre-requisites and set-up guidance here in our documentation.
We are working to make the setting available for you through the Azure portal. Later in preview you can expect support for pooled hostpools and support for remaining Remote Desktop clients. We will keep you updated in this forum. Please share your feedback by commenting to this post or create a new post.
Apr 01 2021 01:44 PM
@Eva Seydl I tested this feature it looks good!
I have a feedback because I tested with Windows WVD RD Client and WVD RD Webclient both.
Can we have the timer showing up the time when we are starting the VM using Windows WVD RD Client also.The timer shows up the time when we connect using WVD RD Webclient. Here is the screen shot for reference.
Apr 06 2021 01:47 AM
@Eva Seydl Worked flawlessly for us. We've sampled an average of ~3mins from clicking on the WVD resource until the user gets a login prompt to sign into their personal host.
Glad this feature is out! Looking forward to this coming out to GA!
Apr 06 2021 03:51 AM
@Eva Seydl My understanding of this new feature is that it still needs to rely on the Azure virtual machines auto-shutdown feature. If I configure a machine to auto-shutdown at 17:00 as an example and a user is logged off said machine at 13:00, does this mean that the machine will remain running for an additional 4 hours before it is shut down? If so, this should be an enhancement request. I appreciate that some cost will still be saved as the machine will still shut down at 17:00 in my example, but further cost savings can be realized if the machine shuts down a few minutes after logoff.
Apr 06 2021 07:49 AM
Apr 06 2021 01:47 PM
@Eva Seydl Spent some time today testing the Start VM On Connect feature with little success. It may be due to my customers unique configuration, but can't seem to get it to work.
WVD Spring Release (v2)
Personal Host Pool = check
Validation Host Pool = check
Custom Role = check
Azure Public = check
Updated Host Pool with StartVMOnConnect:$True = check
The session host was initially stopped (deallocated). Started the VM from PowerShell and logged in to the VM using RD Client (1.2.1844.0). Shutdown the VM from inside the Session and confirmed via PowerShell the VM was stopped (not deallocated). Tried to Connect to the VM and got the error below:
An internal error has occurred.
[^] Hide details [OK]
Error code: 0x0
Extended error code: 0x0
Timestamp (UTC): 2021-04-06T20:46:42.414Z
Activity ID: b574ca6f-a0cb-4717-a7d2-f2606dd50000
Press Ctrl+C to copy.
Apr 07 2021 01:38 PM
Apr 11 2021 10:58 AM
May 20 2021 09:52 PM
May 21 2021 09:55 AM
@MaartenvandenBerg : thank you for feedback :)! We are happy to hear that you are happy with the results. In terms of Linux clients I assume you are using a client one of our partners. I recommend to raise the ask with the partner.
NOTE: desktops should start even with the Linux clients but the new status messages will be missing.
May 25 2021 03:58 AM
@Eva SeydlWorks as advertised, thank you.
I'd like to continue using the scaling script to deallocate machines...is it known whether it plays nice with WVD scaling automation? https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-scaling-script
For example, could there potentially be a conflict with both the scaling script and start on connect starting machines at the same time?
Jul 13 2021 06:30 AM - edited Jul 13 2021 06:32 AM
@Eva Seydl Any way to limit certain users? Only want one WVD user to be able to start VM on connect. I know this sounds odd but that user has program that needs to be started before any other WVD users can log in.
Jul 13 2021 07:52 AM