You might know this already: Registry has a support to, on the basis of IP address, Accept, Query or Reject the connection. You could setup to Accept all connections from the support personnel IP addresses and Query the user to accept the remote for other connections.
Anyway, with the idea of getting the workstation locked before getting the screen, if a user wants to let someone in who is not from the support staff (and hence doesn't know how to unlock the workstation) he would unlock the workstation himself... Michael > -----Original Message----- > From: Gamlem, Noralf [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 28, 2001 12:46 PM > To: '[EMAIL PROTECTED]' > Subject: SV: IDEAS... RE: TightVNC 1.2.2 released > > > Since we're discussing passwords, I have another idea: > > 1. Support personell might need access to the computer even > if the user is > in front of it or not (enter a password and they're on) > 2. "Other" people could be granted access by another password > AND only after > the user has accepted a connection > > This is what we would have liked (I guess we then need at least two > passwords)... :-) > > -Noralf- > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
