This involves installing the application as a client/server installation on the server. Additionally, remote PC’s can be installed with the client only installation of Events2HVAC. Each remote client will need to be able to communicate via TCP port 5048-5049 to the server. Additionally, the client must be able to connect remotely to the Events2HVAC database and any event provider database/API and/or device API (if necessary).
A downside to installing multiple clients is you will have to maintain each client individually whenever an update is installed. Also, there are some features not available on the remote client. For example, the remote client cannot restart the windows service on the server. For this reason, you should not do initial configuration of E2H on a remote client since modifying server configuration will require restarting the service.
Note: All clients must use the same version of the software. Updates to the clients should start at the server first.
Before starting your client-only deployments, you should first create a client deployment file on the server. This file will reduce the configuration steps during the setup of the client PC.
See Also