I posted a question about the use of GPOs for VNC to the microsoft.public.win2000.group_policies newsgroup and got a handy answer from Mike Treit.
Two points that are useful: (1) Async processing can be turned off. (2) Applicable to Win2K also - the application must be GPO aware. This is something that would have to be written into the WinVNC server to be of any use. "Mike Treit [MS]" <email munged> wrote in message news:#Pg9jjWyBHA.1652@tkmsftngp04... : A "non-tattooing" ADM would be one that writes to the "policies" section of : the registry, either under Software\Policies or : Software\Microsoft\Windows\CurrentVersion\Policies. For your own apps you : should use the former location. : : The application, of course, need to know to read the registry values from : the above location. In the case of third-party software that is already : reading from a different registry location, it's not possible to create an : ADM file for that registry location that will not tattoo. : : Regarding the asynchronous policy processing in XP, you can turn that : behavior off if it is an issue by setting the following policy: : : Computer Configuration | Administrative Templates | System | Logon | Always : wait for the network at computer startup and logon : : -Mike : : -- : This posting is provided "AS IS" with no warranties, and confers no rights. : : --------------------------------------------------------------------- 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 ---------------------------------------------------------------------
