VNC Server that can be used from command line?

Question

I'm looking for a replacement for a custom vnc server that we have been using in my company for a long time. I need a simple executable that can be run from command line by an IT Support software without the user noticing it (our application will warn the user, we don't want him to see we are using that VNC sever).

I need it to support Windows and preferably also OSX. The only option I've found is UltraVNC, but I can't configure it from command line to accept loopback connections without authentication.

We have already a whole VNC Viewer + VNC Repeater + Bouncers architecture, and the only missing piece is the VNC Server.

Do you know any solution you could suggest me? I'm afraid I'll end up developing a new VNC server myself, may be based on an open source one.

EDIT: When I said I don't want the user to notice this VNC server, I should have added that I don't want him even noticing the installation. So better if it can be installed silently or can be executed as a portable executalbe (for instance, ultravnc can be installed and ran as a service from command line, or simply executed quietly, with only a notification icon; its problem is that I can't run it without authentication).

Answer 1

RealVNC can be started from the command line without messages or user interaction.

To start VNC Server in User Mode from the command line without displaying the status dialog, run:

"vncserver.exe"

To start VNC Server in Service Mode from the command line without displaying the status dialog, run:

"vncserver.exe -start"

http://kb.realvnc.com/questions/194/Starting+VNC+Server+from+the+command+line+with+no+status+dialog

Using a tool such as psexec you should be able to execute this remotely without issue.

Is this what your looking for or is there something else missing from the puzzle?

Update

What Scott says is correct, more or less. If you have correct rules applied to any firewall running on the system, and no restrictions on where system apps can be run from, you should be able to simply place the executable in the file structure remotely and execute it remotely.

If you need to configure settings and such, RealVNC has a crappy but adequate remote distribution tool that works pretty well for installing/updating the RealVNC server to systems, as well as copy/pasting configurations to the systems. You may have to pony up for the enterprise license, but when I last compared VNC tools, RealVNC was far and away the superior, more polished, and more brain-dead simple of the products and was worth investing company money in. It may not be for you though.

But, the crux of the matter is that, so long as there is no configuration blocking the placement or running of the VNC executable, you'll only need to drop it and run it, all remotely, all though standard backdoors, and, if properly configured, all without any sort of user interaction, notification, or any other visual clues as to what your devious self in IT is doing in their backend. ;)