Forum Discussion
Device Strategy for WVD (Windows 10) Deployment
KitSMFX Found my answer.
Thin clients running Windows 10 IoT Enterprise x64 is supported using the new WVD client (available at aka.ms/wvd/clients/windows). A x32 WVD client does not exist but is expected by November at the latest.
Windows 10 IoT Core does not have any support today but the team is looking into it.
Linux does not have native support but a SDK exists but will rely on partners to create them. Alternatively, the HTML 5 is a workaround.
KitSMFX Found my answer.
Thin clients running Windows 10 IoT Enterprise x64 is supported using the new WVD client (available at aka.ms/wvd/clients/windows). A x32 WVD client does not exist but is expected by November at the latest.
Windows 10 IoT Core does not have any support today but the team is looking into it.
Linux does not have native support but a SDK exists but will rely on partners to create them. Alternatively, the HTML 5 is a workaround.
I am coming this topic currently and finding it very difficult to find relevant information on how this will actually work. If you purchase a Dell Wyse 5070 it autosigns into 'user' and this is find when using RDS but with WVD the end user has to sign into the App. If another user comes along they have to sign that user out of the app and then they sign in. So if you join the device to Azure AD each user can have their own login but then the local disk is going to get full with all these user profile.
elliottchandler
IGEL Technology (where i happen to work) has IGEL OS, linux operating system, which allows you to reinstall existing endpoints and benefit features like the one you are asking for. IGEL OS has a native WVD linux client and can be user on for instance Dell 5070.
Here is how one way to do user roaming on IGEL OS: https://youtu.be/JRCNEKbV-SEBest
FredrikBrattstig Looks interesting.
