Version 3.3.7 Installing VNC on a remote PC

Step 1: Install VNC locally and set the password. Download Real VNC and install it on a local PC (for this article, the version 3.3.7 was used).

During the installation process, be sure to check both: Register VNC Server as a system service Start VNC system service Click here to see a screenshot.

At the end of the installation process, you are prompted to set a password. The password you set here later be used to connect the remote PC.

If for any reason you are prompted for a password, run the following from the command line: "C: \ Program Files \ RealVNC \ WinVNC winvnc.exe \"-DefaultSettings

Also run net start from the command line and confirm VNC Server runs as a service -------------------------------- ------------------------------ ------------------

Step 2: Set up VNC on the remote PC using PsExec PsExec is a free tool to execute processes on a remote PC is needed for this procedure: http://www.microsoft.com/technet/sysinternals/Utilities/PsExec.mspx

The remote account you use must be a member of the Administrators group on the remote PC. "\ \ RemotePC" are mentioned below can be either the remote computer name or IP address.

Login to the remote PC's IPC $ share with an administrator account. If you do not include the password in plain text, you will be asked to provide a password (which will not be displayed as plain text).

NET USE \ \ RemotePC \ IPC $ / user: administrator password

Copy your local VNC files to the remote PC.

xcopy "C: \ Program Files \ RealVNC \ *.*" "\ \ RemotePC \ C $ \ Program Files \ RealVNC \ *.*" / r / i / c / h / k / e

Use regedit to export the VNC registry locale on the remote PC. Note: If you prefer, you can export the file locally and then copy it.

regedit / e "\ \ RemotePC \ C $ \ vncdmp.txt" "HKEY_LOCAL_MACHINE \ Software \ ORL"

Use PsExec to import the log file on the remote PC.

PsExec \ \ RemotePC-sid% windir% \ regedit / s C: vncdmp.txt \

Be sure to use the / s switch with regedit so that confirmation is not required on the remote PC.

You are using regedit on the remote PC to run this command. If the path of regedit is different on the remote PC, use the exact path instead of% windir% (local, not remote environmental variable).

Example: If the local machine running XP Pro and the remote PC is Windows 2000, use this command: psexec \ \ RemotePC-sid C: \ Winnt \ regedit / s C: vncdmp.txt \

Use PsExec to install the remote WinVNC service.

PsExec \ \ RemotePC-sid "C: \ Program Files \ RealVNC \ WinVNC winvnc.exe \" to install

Use PsExec to start the remote "VNC Server" service.

PsExec \ \ RemotePC-s-i-d net start "VNC Server"

You should now be able to use VNC to control the remote PC. -------------------------------------------------- ------------------------------

Notes: See also - Making VNC more secure using SSH

I want to thank Jau-Ling Chou for their input on the use of PsExec to install VNC on a remote PC.

Along with the use of PsExec, the biggest change to this article is that RealVNC VNC version 3.3.7 was used instead of version 3.3.3 of AT & T Laboratories Cambridge. Since the files are installed in different places, the command lines have changed.

To view the above method to install VNC on a remote computer does not use PsExec, click here.

Although remotely install the VNC server is configured most of the registry settings, you still need to export / import your local HKLM settings so that a VNC password is set to the remote PC.

When installing VNC locally and to install the service remotely, a WinVNC registry entry is created in HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run. This is in VNC as an application. Since VNC is already running as a service, in my opinion this is redundant and I can delete that entry.

If you have trouble using PsExec, check the website to learn the command line options. From the s - id combination worked for me, I did not try other options. You should not have to specify the user or the password you use PsExec, you are connected to the remote PC's IPC $ share as administrator.

02/02/07: Updated some URLs. 03/14/05: Added notes in step 4, you must use the correct path for regedit when local and remote paths differ 11/09/04: Fixed syntax typo in step 4,% windir% changed \ \ regedit \% windir% regedit

If you have any suggestions or comments, please send them to info@logged.com.ar