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: <,>,:,",/,\,|,?,*,.

Open

• 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

Simpler Steps With Screenshots

Log into OneFlo

Log into OneFlo using username configured

Open

Download file

Click on the Below link to download the autoprint file

Navigate to https://portal.oneflo.com.au/PrinterConfig/download-v2-zip

Download the Zip and unzip it

Configure Folder

Copy the whole folder AutoPrint 2.3.10 into C:\Program Files (x86)\Flip Group

• if you don't have Flip group folder, you can create one

Rename folder AutoPrint - 2.3.10 something meaningful related to username. Ideally name folder AutoPrint Username

Edit Settings

1. Open folder AutoPrint-TestUser1

2. Edit file appsettings.json

3. Please open the file under admin

4. Generate Key

5. Add AutoPrintAPI Key

6. Also to Get ClientID click on below link and click on Generate new GUID and copy to update in the above file

Generate GUIDs online

7. And add ClientID to file

8. When creating a multi instance installation you will need to provide the AutoPrint service name, and for all installations it must be unique. (Alphanumeric only, limit of 50 chars)

So here I have put Autoprint-TestUser1 as here the username is unique

9. Save and Close

Create Service

Open CMD prompt as Administrator

Navigate to install directory

Activate The Client

Execute the command Autoprint.WindowsService.exe /a to activate the AutoPrint client

Create AutoPrint Windows Service

Execute the create command to link service to application

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

If the service has been installed but can’t be seen then perhaps the service does not have a logon or access to printers

eg

Check the service exists in Windows Services named OneFlo Autoprint Username

Configure the Printer Settings In OneFlo

AutoPrint - OneFlo Printer Configuration

Repeat Steps For Each User

 Please Follow this step again, for other users who are using that same workstation.

Stopping the service