A missing feature that was requested, was the ability to add encryption to the connection. Sorry it took so long, but here you go!

Please note, all changes are in reference to my original post and those files.

1. Download the latest MSRC4Plugin.dsm: http://home.comcast.net/~msrc4plugin/msrc4plugin.html
2. Place MSRC4Plugin.dsm in \client
3. Place a copy of MSRC4Plugin.dsm, renamed to MSRC4Plugin_NoReg.dsm in \host
4. Download or generate rc4.key. Place in both \client and \host
5. For the client exe, change line 6 in the helpdesk.txt file to “-id $ID -plugin -connect $IP::$PORT -noregistry”
6. For the host exe, add MSRC4Plugin.dsm and rc4.key to vncviewer.7z
7. For the host exe, change line 4 to “RunProgram=”vncviewer.exe -dsmplugin MSRC4Plugin_NoReg.dsm -autoreconnect 5 $RESTRICTED -noauto -64colors -encoding tight -proxy $IP::$PORT ID:$ID”"
8. Edit support.aspx, change line 44 to “”..\7zr a sc.7z ..\winvnc.exe ..\schook.dll ..\vnchooks.dll helpdesk.txt ..\MSRC4Plugin.dsm ..\rc4.key ..\icon1.ico ..\icon2.ico” & vbcrlf & _”
9. That should do it!

As always, I’ve included the changes for you. (You may want to generate a new rc4.key, this one is the one included from UltraVNC)

Download

How would you like a dynamically compiled single-click VNC, with no GUI, using a repeater, for free?

First off, let’s answer some questions… What is single-click? What is a repeater?

UltraVNC Single-Click is a mini UltraVNC Server that can be customized and preconfigured for download by a Customer. UltraVNC SC does not require installation and does not make use of the registry. The customer only have to download the little executable and Click to make a connection. The connection is initiated by the server, to allow easy access thru customers firewall.

Hmm, ok, and the repeater?

http://www.uvnc.com/addons/repeater.html
Basically allows you to bypass firewalls using a preconfigured server.

Rather than trying to explain it. I’ll give you an example. Lets say your name is John Doe.

Client calls you up, needing computer help / training. You tell them sure, please visit my website. Give them the url to your support page. They are prompted for a session key. They enter the session key, and click ok. Your server compiles an executable with the session key, YOUR name and the ip of YOUR repeater (if you have more than one). Meanwhile, you visit a similar page, for the host (password protected of course). You enter the same session key. The host executeable is compiled and downloaded to your computer. You run it, it connects to the repeater with the session key, and waits for the client to connect. The client runs the executable they’re given, it says “Waiting for John Doe …”, the connection establishes to the same repeater, and now you can see their desktop. Depending on your permission, you may even be able to interact with them.

While this is all happening, you could have 2 or 3 or 10 other like scenarios going on at the same time. Without having to build the helpdesk.txt file, without having to map ports to computers, without users having to be at specific computer with ports mapped and software installed.

And yes, I did mention permissions. Depending on your configuration, Bob from level one technical support may only be able to view a clients desktop, but Fred from level two may be able to interact. Keeps your liability down.

FYI- My files below are setup to disable Aero and UAC on Vista/7, and re-enable after the session ends. It’s also set up for low bandwidth use.

Here are the steps to getting things set up: (I’ll provide the files so you don’t have to do much.)

1. Set up a repeater – download
   The repeater can be ran as an application, or a system service. I have found it’s more reliable running as an application, but this does require a logon session to remain in memory. Run on any windows OS. Configure the ports.
   
   
2. Build the client executable – download my files below
   Take the standard VNC single-click executable. Run it through ResHacker, and make it look like this.
   
   
3. Set up client configs – download my files below
   Config.txt is for 7zip to know how to package and execute your executable. Helpdesk.txt needs to have some variables in it, that your other scripts will replace with the actual data, such as the ip and technicianss name. This is how the client executable knows how to connect and what to say.
4. Set up host config – download my files below
   Config.txt holds the information such as low bandwidth, permissions, etc.
   RunProgram=”vncviewer.exe -autoreconnect 5 $RESTRICTED -noauto -64colors -encoding tight -proxy $IP::$PORT ID:$ID”The variables in caps are replaced by values during compilation time. The restriction level, the ip, port, and session key / id.
5. Set up client script – download my files below in ASP.NET 2
   Build an asp or php page to compile the executable for the client. This script will need execute access on your web server. It will replace the variables in the text files with actual data. Compress all the files needed into one executable, push that file to the browser, then delete any temp files leftover on the server.
6. Set up host script – download my files below in ASP.NET 2
   This will be a lot like the script above. It will compile the host executable in a similar fashion. Here, you can set up which session keys, belong to which users, and what permissions they have.

Tips:

• Try using port 80 for your clients. This may allow them to utilize remote assistance, if their firewalls are severely locked down. I went with the default ports myself, though I may change that if I run into problems with clients being unable to connect.
• The host can save his executable as long as his session key doesn’t need to be changed. This will allow him to connect quicker to the repeater. Which by the way, will timeout after 5 minutes if no client connects.
• You’ll notice my asp.net scripts allow the use of the query string. This allows shortcuts to be made to skip having to enter the session key. Just click the shortcut, and run the exe.
• The host has the ability to create a shortcut. It will ask them where they want to save it (desktop), then future sessions, they can just click the shortcut.

Here are the things I plan on implementing:

• Allowing users to have more than one session key, so they may connect to multiple clients at the same time.

I realize this seems complicated, and its easier to just use other software out there, but hey… It’s free, and it works.

Download the files: (the web scripts are in ASP.NET 2)

• Client Files – Place in a folder on the webserver as is. (\bin\remote-support\client\)
• Client Script (support.aspx) – Place anywhere on the webserver, give full permission. Edit path inside for client files if different than above, add your technicians.
• Host Files – Place in a folder on the webserver as is. Lock this folder down! (\bin\remote-support\host\)
• Host File (support_admin.aspx) – Place anywhere on the webserver, give full permission. Lock this file down! Edit path inside for host files if different than above, add your technicians, adjust a few other things.

We use this setup at work, with a few connections a day, by a few different users.  I also use it personally for friends/family/clients and have found it to be very reliable.

If I missed anything, or you need help, feel free to comment or email me. It should be pretty straight-forward for those of you wishing to tackle this.

Update: My project has been ported to PHP/Linux. Head over to phpremotesupport.com and check it out!

Update: PHPrs is now available for download.  Get it from phpremotesupport.com or download it here.

Update: Added MSRC4 Encryption. Read about it here.

CrashPlan will let you back up to a remote server,  for a small fee, just like any other online backup software. What makes CrashPlan so unique, is that you can back up to your friends, or your other computers, for free, regardless if they’re on your LAN or not. You can back up to multiple sources as well. For example, a PC in house, and a friends PC across town. You have the convenience of a local restore being quick, and the security that your data is off-site in case of a disaster or theft. Oh, yes, your data is encrypted. No need to worry about others seeing financial and other private information.

For personal use. It’s free. Though a bit limited. You can upgrade to CrashPlan+ to make use of some great additional features, like data de-duplication, real-time backups, heavier encryption, and file versioning. However, if you want it for free, it’s still the best choice out there.

At home, I have a portable drive attached to a PC at home that is always on. The PC itself backs up to the portable drive. My laptop, as well as some friends and family computers back up to it as well. There are about 10 PC’s backing up to me at any time. Bandwidth is not an issue, after the initial backup, as only new/changed data is backed up.

We went with CrashPlan at work, as well, after I had a chance to use it for awhile. It’s cheap. The server software is free, and the client software is $60 a server. You get real-time file monitoring, data de-duplication, and file versioning. We have many servers (IIS, SQL, Exchange, File, etc). We have CrashPlan on each server backing up to a remote server over a IPSEC vpn tunnel. Here’s something to keep in mind. Restoring becomes an issue for SQL and Exchange. CrashPlan will back up files, as it sees them change. During a restore you’ll find many copies of your database and log files, and not know which log file goes with which database file. CrashPlan does not have agents for these types of applications. It simply backs up files on the drive, as they change.

We overcame this limitation by scheduling NTBackup to back up the System State, and our database directories, for each server, every night. Then told CrashPlan to back up those backup files, and exclude the database directories. Upon a restore, you choose your most recent dump, then use NTBackup to restore the dump to the proper folder, mount your database, and you’re back online. Since CrashPlan de-duplicates data, only changed bits in the dumps get sent offsite. We may have a 40GB dump that builds every night, but only changed data is backed up.

Here’s another scenario I recently set up for a client. He has 4 PCs at his office, one at home, and two laptops. We installed CrashPlan on each PC. We designated one of the PCs at work as a backup server, and the PC at home as a backup server. Then configured every PC and laptop to back up to both servers. Think about that. The PCs at the office back up locally, then offsite. His laptops back up to both. In the event of a disaster, his data is safely stored offsite, either way. If he needs to restore files, he can restore them quickly from the LAN. The initial backup took quite a few days. Once the bulk of the data was backed up, very little bandwidth is needed to maintain those backup sets.

There is so much more that CrashPlan does. I encourage you to check it out if you haven’t before.

Please. Back up your computer. I hate having clients call me up, upset, because their 10 year old PC died, and they never made a backup. Most of the time they get lucky, and the data is recoverable. There have been times where the drive was too far gone.

http://www.crashplan.com