Problem

As the Windows Runner is provided in the form of a MSI file, and as the Windows Runner implements settings from its registry last, one cannot simply perform a MSI install followed by additional portable installations. 

 

Solution

The following steps provides a tested approach that accomplishes this goal after installing "Microsoft .NET 8.0.0 - Windows Server Hosting" or higher on the Windows device that will be hosting these Runners. 

1) Create and authorise the Runner objects within RN1's front-end(s) and make note of each Runners back-end URL and enrollment token: 

2) Download the Windows Runner MSI from one of your RN1 instances

3) Rename the MSI so as to conserve character length

4) Perform a MSI administrative install against the MSI to extract its contents: 

5) Create folders on the Windows device that will be hosting these Runners

6) Copy the extracted MSI contents to those folders: 

7) At a minimum, edit the following appSettings.json file settings within each folder: 

• Each running MUST have their own SQLite database
• If the Runner has to go through a proxy, make sure to change the protocol to STOMP after editing the proxy settings

8) Modify and run the following "Service Control Manager Configuration Tool" command lines for each Runner from within an administrative command window: 

sc create RaynetOneService14 DisplayName= "Raynet One Runner Service 14" start= auto binPath= "C:\Program Files (x86)\Raynet\Portable Windows Runner 14\Raynet.One.Runner.Service.exe"

sc description RaynetOneService14 "This service is responsible for executing tasks assigned by the parent Raynet One 14 instance."

• If the service needs to use a custom account then add the relevant parameters to the first command line

9) Start the services

 

Note

It is currently not possible to change the location of the Runners logs directory, which means that each Runner will share the same location but will have their own log file: