0

There are a few other posts (e.g. Remotely set VNC service password ) on that subject but they are narrow to one specific VNC software/version.

I have a situation whereby I have about 500 PCs on a Windows Domain and they are setup with a mix of VNC versions - RealVNC4, UltraVNC, TightVNC, and each of different versions.

So some use an ini file (like most recent version of UltraVNC), some use Registry and they use different section of the registry.

Anyone knows of a script/tool that will just try all options and set the password?

Community
  • 1
ETL
  • 6,513
  • 1
  • 28
  • 48
  • 2
    I sincerely doubt that such a tool exists. I suspect you're going to be forced to write something yourself to handle all the disparate versions you've got. You could easily write something that just updates all of them. – Evan Anderson Feb 17 '14 at 19:14

2 Answers2

1

No such tool exists.

And before you run off and try to write a script yourself to do something monumentally silly (like trying a bunch of different credentials on 500 VNC servers and reporting the results back), the only solution to this that isn't going to be ridiculously painful or involve a bunch of manual work is below.

  1. Write a script/GPO to uninstall all the VNC servers in your environment.
    • My experience with those VNC servers tells me you can check against registry keys to get the specific application and version installed, and then use that to call the (proper) uninstaller.
  2. Determine a standard VNC server deployment you desire.
    • Including the credentials you wish these servers to have, of course.
    • Depending on which VNC server you decide to push out, it may be easier to just install the server with the installer, and then copy .ini files containing the settings and credentials to all your clients (via GPP).
  3. Write a GPO to install the VNC server to all your clients.
    • Probably best to do with a computer startup script.
    • Again, use a registry key to check if it's installed before calling the installer.
  4. Update script as needed for new versions.

This is going to be vastly better than trying to deal with multiple VNC server vendors in multiple configurations, and should even be relatively easy to manage, compared to what you have now, which I wouldn't even try to deal with. You're definitely in a situation where it's going to be vastly easier to build right from scratch than repair.

HopelessN00b
  • 53,795
  • 33
  • 135
  • 209
  • I like your view - it probably would take me as long to put together a program/script that changes the password to all scenarios than to disable/uninstall vnc and install one of my choosing and one that integrates with ActiveDirectory so I don't have to do this again. – ETL Feb 17 '14 at 22:27
0

For the record, below is the script which I used to disable VNC on all computers (ran the script for all computers on the domain):

@ECHO OFF
:: Find out what VNC services exists
for /f "tokens=1" %%f in ('psservice \\%1 ^| egrep -i "vnc|tvnserver" ^| grep "SERVICE_NAME" ^| sed "s/SERVICE_NAME: //"') do (
    echo %%f
        psservice \\%1 stop %%f
        psservice \\%1 setconfig %%f disabled
)

That requires Sysinternals and UnixTools.

ETL
  • 6,513
  • 1
  • 28
  • 48