VNC Central is a program that will simplify the management of a large group of remote computers by allowing you to launch applications between them. You can, for example, have a local vnc viewer to connect to a remote computer running vnc central or vice-versa have a remote vnc server to connect to a vnc viewer in listen mode running on your computer (solving great part of server side firewall/router problems).
VNC Central however is not made only for vnc server/clients applications, in fact you can use any application you like, for example you can launch a ftp client to connect to the remote server or have a remote ftp client to connect to your local server. You just need an application that accepts remote ips as command line parameters, nothing more.
VNC Central interface is very simple, there's a main listbox that shows all the connected computers, if you want to launch an application you just have to right-click a computer and select it. It also supports automatic dyndns update, so if you need to connect your vnc central to another that runs on a pc without a static ip you can just configure a dyndns to solve the problem.
VNC Central can be used for many different purposes since, as I already wrote before, it doesn't only supports vnc client/server, in fact it supports any application that accepts command line parameters.
For example you can:keep track of connected customers and take control of their computer when you need to run a manteinance program (defrag or whatever) on different computers at once just control the pcs in your lan
set up a vnc central network to bypass firewalls: you can link them in any way you like, you can link a vnc central that acts like a server to another vnc central that also acts like a server for example the important thing is that you must not create closed connection loops.
And by connection loops I mean that you can't connect a vnc central connected to more than one vnc central belonging to the same vnc central network. Probably this will be fixed in next versions.
What's New in This Release: [ read full changelog ]
· Made the settings dialog bigger
· Moved all the notification settings from remote requests to a new settings sections
· Added an "advanced settings" section
· Replaced registry entries with a .xml file for an easier deployment
· Added autolaunch/autoexecute options even to the classic vnc central setup (the one without UltraVNC)
· Now the VNC Central setup (the one without UltraVNC) automatically copies, if present, the "VNC Central.xml" configuration file from the setup directory to the install directory and it also copies and executes, if present, the Deploy.exe file (you can do a sfx file that installs all the applications that vnc central will launch)
· Moved all the settings dialog in a dll to reduce the main executable size
· Removed splash screens from the setup to make it smaller
· Using windows notification sound instead of the custom notification sound
· Removed the useless About Image that just wasted space
· Fix: When right clicking on multiple selected centrals in the main dialog the available actions will be checked against firewall conflicts of all the selected centrals and not only against the selected central with the focus status
· Fixed seldom crash when all the automatic connections were deleted at once
· Fixing win98 tray icon not working issue
· Fixed connection error messagebox
· Adding an unique id system to prevent double connections of the same vnc central to the same vnc centrals network that could mess up all the other vnc centrals (thanks mick for the report)
· Fixed connected centrals tree grouping by hierarchy only the centrals directly connected
· Added a protection to avoid users inserting password with spaces
· When multiple selections or actions are selected in the settings dialog and the delete button is used they are all deleted instead of only the first one
