Alright, lots of questions here. Let me break it down. I used SingleClick for the past 4 years on XP with no problems and like the fact that it would automatically connect and on the support controlled computer it would ask if you want to accept the connection.
This is because SingleClick would make a reverse connection to a running UltraVNC Viewer which usually required network setup such as port forwarding to the specific computer running the Viewer.
If you have the SingleClick Viewer running on a laptop that you bring on the road it can be difficult if not impossible for the reverse connection to happen.
Before I get blasted on the ethical ways of doing remote support, I want to explain that these are highly customized embedded
systems, and are NOT
end user computers. They will be installed in server racks, with no mouse/keyboard attached and only have a single output. I'd rather not get into a discussion on the purpose of the configuration of the systems as I'm not here for that. Thank you.[/b]
No problem, usually everyone around here is pretty nice compared to the rest of the internet. On ChunkVNC, the InstantSupport.exe opens and presents a support ID on the screen. I like this a lot, but it doesn't help me in my situation because I have systems in the field that would need remote support started unattended. Meaning either knowing the support ID beforehand or not requiring a support ID. Having an easy access for remote support into the system is essential for our product support.
Is there a way to start InstantSupport.exe with a command line of the support ID to use so it will not auto-generate? This way I can run it knowing before hand the ID it will reserve on the repeater and I can then type that in and connect.
Is there a way to have InstantSupport.exe use the same support ID each time that is unique to each system? This way I will also know before hand the ID it will reserve on the repeater.
As a last resort, the CMS software running on the system can get a screenshot and the support tech can possibly get the ID from that by the system uploading the screenshot to the CMS server, but it's a step I would like to avoid. Expanding on this, I could even put some smarts in and try to get the ID into text form from the screenshot since it's black text on white and could be put through optical character recognition software.
Keep in mind that ChunkVNC is simply a wrapper for UltraVNC, all it is doing is setting up an UltraVNC Server and making a reverse connection to the repeater.
ChunkVNC compiles itself from source which is what get's installed on your computer, you are free to modify the program to work any way you wish.
My goal is to create a support tool for going in and out of customer computers quickly and I haven't currently been focused on permanent installs such as how logmein works.