On 18 Aug 2009 at 10:19, James Hill wrote: > You could write a script to restart the service then you can > connect.
I have the VNC service set to restart itself if it dies. I just tested it here and the uvnc_server service restarts itself when I kill it from taskmgr. However, if you stop the service from the Services.MSC interface, or use "NET STOP uvnc_service" from a command-prompt, it stays stopped (XP Pro, UltraVNC, service set to restart if killed). On 17 Aug 2009 at 16:59, Robert Smith wrote: > We have users who are killing the vnc process in task manager which is > preventing management from viewing the users screens. The reason why > they need to be able to manually kill some processes, is due to the > installed accounting software that crashes quite often. The VNC service runs as a local system service, and "limited users" can't stop local system services. They CAN stop processes that they start from their login. If your accounting software can run as a "limited user" that would solve your problem. Note that you can (re)start the VNC server on a remote machine using PSEXEC, if it has already been installed and all the registry entries are present. I've done that in a pinch. > In a previous life we actually left the service stopped so there > was no tray icon (can´t remember what mix of vnc it was but it > didn´t have a "no tray icon" option from memory) and then just > remotely started it when we wanted to remote control the machine. I have the following saved tip from a few years back: ------- Included Stuff Follows ------- At 10:47 AM -0500 8/12/02, XXXXXXXXX wrote: > 1) Start->Run->Regedit > 2) HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3 > 3) Create a DWORD key called "DisableTrayIcon" > 4) Change the value of this key to a "1" > 5) Exit the VNC Server and Start it up again. --------- Included Stuff Ends --------- This doesn't hide the PROCESS, just the tray icon. If you hide the tray icon, some of your (l)users may not think it's there. Also, you may be able to rename the VNC Service to something else; if your users are looking for a process by name, they won't see WinVNC if you've named it something else like "sysspool". Note that VNC servers flying under false colors may well trigger some AV packages. Starting the service as a different user to which the end users don't have rights should do the trick as well. But the REAL solution is NOT a technical solution, it's a "personnel management" solution that involves firing a few examples IMHO. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
