Re: Unlock Workstation without closing current session
From: NobodyMan (none_at_none.net)
Date: 03/24/04
- Next message: Carey Frisch [MVP]: "Re: Hide folders"
- Previous message: lisa: "help! please! windows not starting properly!"
- In reply to: Please reply to newsgroup.: "Re: Unlock Workstation without closing current session"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 23 Mar 2004 19:12:31 -0500
On Mon, 22 Mar 2004 18:42:22 -0500, "Please reply to newsgroup."
<"Please reply to newsgroup."> wrote:
>NobodyMan wrote:
>
>> On Sun, 14 Mar 2004 20:57:35 -0500, "Please reply to newsgroup."
>> <"Please reply to newsgroup."> wrote:
>>
>>
>>>NobodyMan wrote:
>>>
>>>
>>>>On Mon, 08 Mar 2004 21:53:07 -0500, "Please reply to newsgroup."
>>>><"Please reply to newsgroup."> wrote:
>>>>
>>>>
>>>>
>>>>>Steve Shurber wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Is there any way for another user to unlock a system (that has been
>>>>>>locked either via the "Lock Workstation" in Ctrl-Alt-Del or a
>>>>>>timed-out screensaver) without closing the current user session?
>>>>>>
>>>>>>Any ideas are welcome.
>>>>>>
>>>>>>Steve
>>>>>
>>>>>Yeah. Any administrator can unlock the computer.
>>>>
>>>>
>>>>Nope. Won't work. When the administrator unlocks the terminal it
>>>>terminates the session and logs out the current user.
>>>>
>>>>This is a good reason to always save your work, even if you plan on
>>>>locking your terminal. Sysadmins have to do work on terminals - and
>>>>if I give you over a week notice when it will be done, and you decide
>>>>to leave that huge Excel spreadsheet open, unsaved, and lock your
>>>>terminal/walk off during that time, don't get upset when I come by and
>>>>ruin your day.
>>>
>>>That's good to know about locking the computer. It certainly makes
>>>sense that it closes the person's work and logs off, but Windows should
>>>save the document before logging off.
>>
>>
>> That's a double edged sword. There is always the situation where the
>> user edits something but changes their mind about wanting to save it,
>> or wants to save it to a different file. If a logoff forces the
>> system to save open files, then the current content would overwrite
>> the old file - which could be disastrous as well.
>
>Then I guess the best solution would be to have Windows save the file
>under a different but similar name in the same folder when the machine
>is forced to log off.
Closer, but no cigar. The person may be working on a file located in
a folder where they have permission to read but not save changes to,
or into. They modify the file, intending to save it on their computer
somewhere else, but have to leave and lock the terminal. User X now
comes along and logs them off. The computer can't save the file in
the current folder, and doesn't know what the original person intended
as it can't read minds. What's a machine to do?
Don't scoff. This happens more often than you think.
The point is, in a multi-user environment, you should always save your
work prior to walking off and/or locking the terminal.
- Next message: Carey Frisch [MVP]: "Re: Hide folders"
- Previous message: lisa: "help! please! windows not starting properly!"
- In reply to: Please reply to newsgroup.: "Re: Unlock Workstation without closing current session"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
