...

To support advanced deployment scenarios, like multi-tenancy, or networking / permission issues, the service can be installed and activated manually without the MSI.

...

What does this mean?

If there are 4 separate printers, create x4 OneFlo users, one for each print queue. The sender will need to do these steps x4 times for each service on the server that has access to the printers.

Installation

• Extract .zip package to a folder

• Update the following settings in the appsettings.json file

  1. AutoprintApiKey: The API Key generated for the user via OneFlo.

  2. ClientId: THis needs to be set to a unique guid, can generate a new one at https://www.guidgen.com/

  3. AutoPrintServiceName: The service name should be unique to allow multiple instances of the service to run successfully. The name should meeting the following criteria:

     1. The name must be unique - if it is not uniquely named, the target windows service will not run. If there are existing services that are already running with the same name, this will cause issues.

     2. The name length cannot exceed 50 characters.

     3. The name should not have the following characters: <,>,:,",/,\,|,?,*,.

...

• Activate the client by running Autoprint.WindowsService.exe /activate from a command prompt in the installation directory.

• At this point the service can be run as a console app as the logged in user if required, without installing it as a windows service.

• But to install it as a windows service:

  • Run: sc.exe create "OneFlo Autoprint {custom text}" binpath=c:\ {installdirectory}\Autoprint.WindowsService.exe type= own start= auto depend= spooler

  • If the service needs to run as a user other than Local System, for instance if it needs the ability to access network printers, modify the service’s Login user manually through the services screen.

  • Start the service

What does this mean?

...

Simpler Steps With Screenshots

...