We have multiple clients that work in the healthcare sector.Is there any user friendly method to have a kiosk-like mode when people just fill in their creds (2 times no problem) and can log on to their desktop?Right now we see that thinclients with the Remote Desktop App need to subscribe to the web feed with their user, when another user comes in, they need to reregister their web feed again etc etc.This makes switching users quite the hassle. We are using Windows 10 IoT Enterprise clients, ofcourse the HTML5 client would be a good solution but we see that thinclients struggle to keep up with performance on HTML5, therefore we can only use the Remote Desktop App. Anyone?

knowlite : Yes, the explanation helps! If I'm understanding you correctly, the web client sign in and sign out experience is easy, since the user just needs to log out in the top right corner or close the browser completely. However, the performance isn't optimal and you'd like that same ease of experience for the desktop client. I'm not sure if we have anything right now to address that, but I've forwarded this thread internally to the appropriate folks to see if they have anything to comment.

knowlite : Quick question back to you. Is the ask for: Easier logoff of existing user, or Easier logon for new user Also, are there any other actions the user takes to "claim" the kiosk like some sort of badge in?

Hi Christian,We would like a solution for WVD similar to the RDS thinclients in use today.This means that the thinclient is user independant (no login needed) and that the user needs to login on the WVD environment (just like the WVD webclient). Right now we have the following issues:a. Using HTML5 client, the login process is pretty similar but thinclients struggle with HTML5 performance because the client has such low system resources (even the latest Dell/HP Win 10 IoT Enterprise ones)b. Using the Remote Desktop App, a user needs to register to the web feed every time, which is cumbersome. This can be resolved with domain joining the client but this does not help users forgetting to log out twice (once from WVD, once from thinclient).I hope my explanation is a bit more clear now.

Thanks, much appreciated!I know that W10 IoT Enterprise clients together with WVD are a rather new solution so I suppose more solutions will become available in the coming months. I've read that Igel is developing a Linux thinclient for WVD, which may offer a resolution for our issue.

knowlite Sorry for the dumb question but I have been struggling with even getting the WVD Remote Desktop client to run on Windows 10 Enterprise LTSC in kiosk mode. Do you mind me asking how you got that working?

Thinclients on shared workspaces | Microsoft Community Hub

14 Replies

Christian_Montoya
Microsoft
Dec 30, 2019
knowlite : Quick question back to you. Is the ask for:

Easier logoff of existing user, or

Easier logon for new user

Also, are there any other actions the user takes to "claim" the kiosk like some sort of badge in?
- knowlite
  Iron Contributor
  Dec 30, 2019
  Hi Christian,
  We would like a solution for WVD similar to the RDS thinclients in use today.
  This means that the thinclient is user independant (no login needed) and that the user needs to login on the WVD environment (just like the WVD webclient).
  
  Right now we have the following issues:
  a. Using HTML5 client, the login process is pretty similar but thinclients struggle with HTML5 performance because the client has such low system resources (even the latest Dell/HP Win 10 IoT Enterprise ones)
  
  b. Using the Remote Desktop App, a user needs to register to the web feed every time, which is cumbersome. This can be resolved with domain joining the client but this does not help users forgetting to log out twice (once from WVD, once from thinclient).
  
  I hope my explanation is a bit more clear now.
  - Brattstig
    Brass Contributor
    Aug 31, 2020
    Hi knowlite,
    
    If you still need help on this, here is how it could look on a IGEL OS endpoint (Thin Client).
    IGEL OS endpoint boots, automatically starts the WVD client and ask for credentials
    User Fred logs in and reconnects to his running desktop automatically
    User Fred disconnects session
    IGEL OS endpoints automatically restarts the WVD client and waits for next user
    User Fred2 logs in and gets automatically connected to his desktop (reconnected)
    I recorded a video on this scenario which you can find here: https://youtu.be/JRCNEKbV-SE
    If you need assistance or have any questions, reach out to me!
    Best
    Fred

Forum Discussion

Thinclients on shared workspaces

14 Replies

Resources