Can't lock local keyboard when AllowProperties=0
James M. Henderson
Fri Jul 18 01:18:00 2003
Thanx Beau - that worked fine.
> Message: 2
> From: Beau.Haefke@fedgroup.com
> Date: Wed, 16 Jul 2003 9:06:51 -0500
> To: firstname.lastname@example.org, email@example.com
> Subject: RE: Can't lock local keyboard when AllowProperties=0
> William was close on this, but VNC's documentation is a little off. In the registry key
> place the DWord "LockSettings" with an s at the end and set it to the value of 2
> also place the DWord "LocalInputsDisabled" (that's local inputs disabled) and set it to the value of 1
> This should get you all set up.
> -----Original Message-----
> From: MIME :firstname.lastname@example.org [mailto:MIME :email@example.com]
> Sent: Wednesday, July 16, 2003 12:40 AM
> To: firstname.lastname@example.org
> Subject: Re: Can't lock local keyboard when AllowProperties=0
> Thanx for the input, William.
> Unfortunately this didn't have any noticable effect.
> Is it actually possible to prevent user access to the properties dialog, as well as lock the local keyboard
> when accessing the server ? It seems odd to have two different security features that cancel each other
> I am in a school situation, & am using VNC to monitor/control classroom PCs. I want to be able to
> access a student's PC & kill any inappropriate activities (web browsing etc) without having to fight for
> control of the mouse. I also don't want students to be able to fiddle with VNC properties, for obvious
> reasons. Surely these should not be mutually exclusive aims ?
> Any help appreciated.
> Mick H.
> > -- __--__--
> > > Message: 13
> > Date: Thu, 10 Jul 2003 20:17:56 -0400 (EDT)
> > Subject: Re: Can't lock local keyboard when AllowProperties=0
> > From: "William Hooper" <email@example.com>
> > To: firstname.lastname@example.org
> > > James M. Henderson said:
> > [snip]
> > > The problem is this: On the server machine, I have set AllowProperties,
> > > AllowEditClients & AllowShutdown to in the registry - this works fine,
> > > all of those options become unavailable to the user. > >
> > > However, now the Disable Local Keyboard & Pointer function has ceased to
> > > operate, & Lock Workstation (or Logoff) when Last Client Disconnects has
> > > also stopped working.
> > [snip]
> > > Have you taken into account that AllowProperties "...stops all global
> > per-user settings"? Try changing the "InputsEnabled" and "LockSetting" in
> > the default user settings (HKLM\Software\ORL\WinVNC3\Default) or local
> > per-user settings (HKLM\Software\ORL\WinVNC3\<username>) instead.
> > > --
> > William Hooper
> > > -- __--__--