Requirements and installation
In order to run the agent correctly, the following setup is required.
Hard- en software requirements
- Windows Server 2012 64 bit or 2016 64 bit with 8 GB Ram, minimal of 2 CPU cores with 2.40 GhZ, 150 GB hard drive;
- Connection to the internet (possibly via a proxy);
- An internet and intranet registered DNS A. The DNS A record refers to the server on which the agent is installed;
- A public usable SSL certificate
- A web server. E.g. IIS, NginX, etc. which contains at least the configuration described in 1.2.
Authorization requirements
- It will need the rights to retrieve data from the given system;
Installation agent
The following steps must be taken to get the agent working correctly.
- Register a DNS record referring to the customer server on which traffic is coming in;
- Install a browser SSL certificate for the registered DNS record;
- In a web server, set the configuration where the following things are set. An example configuration for NginX is shown in appendix 1:
- HTTP redirect to HTTPS;
- SSL certificaat for all the traffic;
- Redirect any incoming request to the agent (port 7070);
- Create a separate folder in which the salureconnect_agent.exe is placed;
- Create a user who has the necessary rights to the folder where the agent is located and who has the rights as mentioned in the Requirements.
- Test the agent if it’s working by opening a Powershell window in the folder where the salureconnect-agent.exe file is located. Start the agent by just executing .\salureconnect-agent.exe. You can add 2 parameters if you want
- --listen: The default IP where the agent listens on is 127.0.0.1. You can change this IP with this parameter. For example: .\salureconnect-agent.exe -- listen 0.0.0.0;
- --port: The default port where the agent listens on is 7070. You can change this port with this parameter. For example: .\salureconnect-agent.exe -- listen 0.0.0.0 -- port 5005
- --ssl: Add the parameter --ssl true to enforce encryption. You can (you don't have to) also change the port to e.g. 443. This looks like this: `salureconnect-agent.exe --ssl true --port 443`
- --certfolder: When SSL is enforced, the agent needs a certificate to actually encrypt traffic. Make sure you have a certificate and a key file in a folder on the server where the agent is running. For example, in the certs folder. After you place the certificates in the folder, add the following parameter: --certfolder <folder certs>. Suppose you placed the certificates on c:certs, then the parameter becomes `--certfolder c:certs`. Combined with the previous parameter, the whole thing now looks like this: `salureconnect-agent.exe --ssl true --certfolder c:\agentcerts --port 443`. The certificates should be named as follows:
- salureconnect_agent_cert.pem
- salureconnect_agent_key.pem
Note that if you use the ssl parameter, the certfolder parameter is mandatory.
Create Task
- Create a task in the Windows Task Scheduler with the following settings:
- General
- Run with newly created user;
- Check “Run wheter user is logged on or not”;
- Do not check “Run with highest privileges”
- Triggers:
- Begin the task: At Startup
- Delay task for: 15 minutes
- Actions:
- Action: Start a program
- Program/Script: The full path to the salureconnect-agent.exe. Add the parameters (see step 6) if wanted.
- Start in: The directory where the salureconnect-agent.exe is placed
- Settings
- Uncheck “Stop the task if it runs longer than:”;
- Save the windows task and run it.