Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 230663

Re-authenticating from a Windows client after lock

$
0
0

Hello:

 

We are currently deploying our own "Thin client" solution here which is basically on Windows 10 for the thin OS, and using the Windows version of the Horizon Client.  The users must log in with their credentials to the physical thin client itself for some required applications to run and identify the user properly, as well as GPOs, etc.

 

For users on this solution, what we are faced with is the VM and the laptop will lock their screens after 15 minutes.  This is a company policy for all machines to lock after 15 minutes for security reasons.  When unlocking, they must authenticate to the physical thin client first, then authenticate in the VM both get back to their VM.  This only happens when the user is already logged in to their VM and walks away long enough for it to automatically lock.  We have our GPOs set to pass through Windows authentication, so when they first logon initially it does pass through the credentials so the user only has to authenticate once there.  The issue is when they are already logged in and their machines lock, and they have to authenticate, it doesn't seem to pass that authentication through.

 

Unfortunately, we are kind of stuck but I was curious if there are any solutions to get around this, that are more baked in or integrated with the Horizon Client or thin clients.  If possible we don't want to purchase a 3rd party product unless necessary.  I have looked and so far do not see a built in way to handle this.  I have not yet looked at 3rd party solutions either, as this is more of a question if it's possible with what we have, basically Windows and the Horizon Client.

 

I appreciate any and all feedback if any solutions that may take care of the re-authentication.  Thanks!!


Viewing all articles
Browse latest Browse all 230663

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>