Just curious, but what make/model of thin-clients are you using? Some, such as the Wyse OS/Blazer devices will all you to lock the thin-client session using the domain username/password despite the client not being part of the domain.
-Mike
Because the clients are thin clients and don't directly authenticate on the domain.
*Matthew Shrewsbury, *MCSE+Internet MCSE 2000 CCA Server+
Network Manager
-----Original Message----- *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On Behalf Of *Edward VanDewars *Sent:* Thursday, October 26, 2006 12:07 PM *To:* thin@xxxxxxxxxxxxx *Subject:* [THIN] Re: Screen save password
Why don't you set the screensaver on the client instead of the server session?
On 10/26/06, *Matthew Shrewsbury* < MShrewsbury@xxxxxxxxxxxxxxx> wrote:
We have a number of users that access a published desktop. Because of security concerns they have a screen saver kick in after 20 minutes of no activate and it requires a password.
My problem is people leave and I need to shutdown their desktop session so I shadow them and find the screen saver on. I don't have their password so I can't gracefully close down there session. Is there a screen saver that allows an admin to over ride it without logging off the session so I can close their apps gracefully? Any suggestions?
Thanks,
*Matthew Shrewsbury, *MCSE+Internet MCSE 2000 CCA Server+
Network Manager