Installation and server settings

Installation

Download and run the ResSched installation file on the Windows machine acting as your server.  Read and accept the terms of use and read me screens.  Select where ResSched 10 should be installed into.  While ResSched 10 can be installed anywhere,  we recommend that you use the default folder, C:\ResSchedServer, for support and reference reasons.  DO NOT use any folders currently used by ResSched 9.9 or earlier.

After installing ResSched 10, run ressched.exe to launch it.

Initial Server Settings

ResSched 10 has two sets of settings; one for how the server connects with the user, and one for the functional requirements of the organization (Organization Settings).  There are several server settings that should be considered, but initially look to the secure and insecure ports.

If port 80 is not already used by another web application, use it as your insecure port. If it is already used, port 88 is the recommended alternative but any unoccupied port can be used.  If you have a TLS certificate for your domain,  you can use a secure port.  443 is default secured port and 8443 the recommended alternative.  If you use different ports from the default 80 and 443, you must include the port number in the calling URL (e.g. http://yourdomain.com:88)

Click Save Changes and restart ResSched.

Use the browser on your server to connect to ResSched using localhost as the URL. If you do not get the ResSched login form, the port is likely used by another application.  Port 80 is frequently occupied by the World Wide Web Publishing service for IIS.  If you don’t need IIS, turn off the service.

To use the secure port you must place  your TLS certificate file (.crt) and its key file (.key) in the folder shown as Certificates Folder.  Modern browsers are becoming more restrictive about unsecured ports so getting a TLS certificate is highly advisable.  See Using TLS.

Problems

If you can connect using your server’s browser but not from outside your server, the most likely cause is a fire wall setting or your router does not have port forwarding to your server turned on for your domain and port number.

Contact us for support.