- This topic has 3 replies, 2 voices, and was last updated 2 years, 5 months ago by
.
-
Posts
-
In our environment we have Dell Wyse 5070 thin clients running ThinOS. Each thin client makes a direct RDP connection to a virtual machine, no broker is being used. We save the credentials in the RDP connection properties and set “Auto-connect on start-up”.
Prior to upgrading ThinOS to 9.1_3129 (this was the first 9.x version that we introduced to our environment) everything was working as intended. The thin clients would power on and automatically connect via RDP with no user interaction. However, after upgrading it attempts to connect but then pops up an RDP Login window with the message, “RDP Session Host login, user: <username>, fresh credentials required by server”. Clicking OK in this window will allow the thin client to log in, but this user interaction needs to be avoided for these clients.
Has anyone else run into this situation, and were you able to resolve it? It doesn’t seem to actually be a setting on the VM that the thin client is connecting to, because if it was I would think a thin client running an old version of ThinOS would get the same message. However, a thin client still running ThisOS 8.6_807 connects without issue to the same VM.
Currently testing with latest versions: ThinOS 9.1.5067, BIOS 1.13.1, and Microsoft AVD 1.5_1325 and still getting that message.
Good morning
I also use the following software on my Wyse 3040:
ThinOS 9.1.5067, BIOS 3040 1.2.5, and Microsoft AVD 1.5_1325I get the same message and I have to confirm it with OK. then the connection is established.
I figured this out in our environment and it ended up being a Group Policy setting:
Computer Configuration / Policies / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Session Host / Security / Always prompt for password upon connection
The odd thing is that this policy has been in place for quite some time and doesn’t affect our thin clients running ThinOS 8.6_807. It’s only after upgrading to 9.x that it became a problem.
- You must be logged in to reply to this topic.