Forum Discussion
What is your experience with Start VM on connect. Share your voice!
Hi Community :)!
If you remember I announced a while ago public preview of start VM on connect. As you had some time to explore the feature, let me know what you think.
Please answer this...
Start on connect works great, if you are not using fslogix or mapped drives.
When using fslogix and\or mapped drives, I end up with local profiles being created and drive maps missing.
Presuming this is related to the session host advertising it self as ready prematurely, before all appropriate services are started.
Any advice appreciated.
When using fslogix and\or mapped drives, I end up with local profiles being created and drive maps missing.
Presuming this is related to the session host advertising it self as ready prematurely, before all appropriate services are started.
Any advice appreciated.
I appreciate this is an old thread but I am struggling.
Having literally created a brand new AVD deployment by just using the AVD management in the portal the steps to add the custom role cannot be completed sine there is no "Windows Virtual Desktop" service principal.
How do I remedy this? I ran the app registration URLs and ended up with and Windows Virtual Desktop AME and Client.
What is needed to get this going?
Thanks
barnesyboy Just in case it helps someone in the future. The docs are not entirely accurate now.
The principal is "Azure Virtual Desktop".
