Installation and configuration

Before starting the configuration you will need either the X.509 public key or the Personal Information Exchange (pfx) file from your IIS or apache server. See the pages on Installation on IIS and/or Installation on Ubuntu.

After extracting the zip file, start configure.cmd in the root. This will show a screen with the following elements:

Server-side key

The first time you start the configuration, a server key is generated. This key is used as a kind of password for servers to be able to connect to the proxy. When a server can connect to the proxy it can start a session. But a session by itself doesn't do anything and causes no network traffic unless a client connects to it. You would only generate a new key when you want to disable existing server executables out there.

Client-side password

Since the client is the part of the connection that actually activates the session it is protected by a password. Needless to say it should be a good one.

Proxy URL

The Proxy URL contains the full URL by which the proxy can be reached by both client and server.

Proxy Certificate

The certificate describes the public key of the proxy-server as it is included in the client and server. Client and server do not request the public key from the proxy - they already have it with them. Besides telling the Configure program where the certificate file is located for retrieving the public key, there are 2 distinct ways for the Proxy server to load the certificate file:

1. On IIS only you can use the "Load by Subject name" option. In this case the proxy will try to load teh certificate from the personal store on the server.
2. On both IIS and apache you can use the "load by path". Specify the path to the PFX file.

Save button

The Save button stores the entered settings and applies them to the .config files of the client, server and proxy, without building executables.

Save and Build button

The Save and Build button saves and applies the settings, and builds the executables.

Build Output

The result of the build is stored under the build sub-directory:
- under private ypu'll find RemoteSupportClient.exe
- under public are all files that can be moved to the shared directory on IIS, including RemoteSupportServer.exe