These are the most common Ranger licensing unlock scenarios, with links to additional information:

Scenario 1: You have a new license, and you are unlocking it for the first time.

Scenario 2: You reinstalled Windows or performed a factory reset on your workstation.

Scenario 3: You moved to a different workstation, or replaced the workstation motherboard.

Scenario 4: The Windows Registry entries that Ranger uses, was modified in an unexpected way.

Question: Can I switch Ranger driver options files based on the scanner model?  I would like to use one file when connected to a Digital Check TS 230 or TS 240 scanner, and a different driver options file when connected to a TS 4120.

Answer:
"Ranger for Digital Check TS-series" supports the following check scanner models:
TS200, TS210, TS215, TS220, TS230, TS240, TS300, TS350, TS400, TS500, TS4120, CX30, and BX7200

You can tell Ranger to switch driver options file by calling:

Ranger.SetDriverOptionsFileName(file path)

With this in mind, I would take the following approach:

1. Save a copy of the "DigitalCheck-TSSeries.ini" file, that you would like to use with TS 230/240 scanners, and rename it to something like "DriverOptions_TS230_TS240.ini". Then copy the new INI file to one of your application folders.

2. On Windows 10 and later, the default location of is:
C:\ProgramData\Silver Bullet Technology\Ranger\Scanner Plug-ins\DigitalCheck-TSSeries\DigitalCheck-TSSeries.ini

3. Repeat this step for the TS 4120.  Make another copy of "DigitalCheck-TSSeries.ini" and rename it to something like "DriverOptions_TS4120.ini". Then copy the new INI file to one of your application folders.

4. After calling Ranger.Startup(), and after Ranger reaches the "ChangeOptions" state then...

5. In your application code, obtain the scanner model by calling:

ModelName = Ranger.GetTransportInfo("General", "Model")

6. Then tell Ranger which driver options INI file you would like to use, based on the model name, by calling:

Ranger.SetGenericOptionsFileName(ini file path)


Pleas note: Ranger only reads from its INI files when you call:

Ranger.EnableOptions()


When multiple check scanning applications are installed on the same workstation, and they both write to the same default Ranger INI files, you can never be sure which options the other application set.

Because of this possibility, it is best to make and use a private copy of Ranger's default INI files.  Use the following calls to point Ranger to your private files:

Ranger.SetGenericOptionsFileName(file path)
Ranger.SetDriverOptionsFileName(file path)


Good luck, and happy scanning!
Bryan Clark

---

By default, the Ranger.dll is installed in the same location as Ranger.ocx:

Quote(64bit OS): C:\Program Files (x86)\Silver Bullet Technology\Ranger\Ranger.dll

Quote(32bit OS): C:\Program Files\Silver Bullet Technology\Ranger\Ranger.dll

If your application is not using the default path or Ranger installer for placement of files, the easiest place to put Ranger.dll for an application to load is in the default paths searched by Windows for a LoadLibrary call. The first of these paths is the same path as the executable file itself so your code could just be LoadLibrary("Ranger.dll") in that instance.

The best practice is to provide a fully qualified path to the Ranger.dll to ensure you load the DLL you intend to load.

For more information on LoadLibrary search order,


Ranger.dll requires there to be a Scanner Plug-ins folder in the same location as the Ranger.dll so that plug-ins may be located and loaded properly.

Ranger Installation Options

Silver Bullet Technology, Inc. has the ability to use Web Socket Secure (WSS) communications with its Ranger Remote client/server platform. This security layer requires the use of signed certificates to create this secure connection. For the security certificates to be the most secure, they need to be created by the entity integrating and deploying Ranger Remote as part of its solution.

Steps to create a security certificate

WSS requires that the browser has a root certificate of authority (CA) to communicate securely to another (server) process which uses a server side certificate compatible with the CA. The following is an example on how to create the certificates using OpenSSL.

NOTE: Apple's Safari is moving to a 398 day certificate expiration policy effective September 1, 2020. Any 2 year certificates created before August 31st will still work until their issued expiration date.

OpenSSL Windows Example:
OpenSSLBatchScript.zip->createWindowsCertificate.bat
Ensure to set the path to the openssl.cnf within the createWindowsCertificate.bat file before running. An example can be found commented in the createWindowsCertificate.bat.

Windows Open SSL binaries:
https://wiki.openssl.org/index.php/Binaries

OpenSSL OSX Example:
OpenSSLBatchScript.zip->createfilesMac.sh
OpenSSL is installed on Mac by default

Ranger Remote certificate setup

RangerRemote involves inter-process communication between a Ranger host application (Ranger Remote server) and a Ranger client running in a browser. The most commonly used method of portable inter-process communication with a browser is a websocket (WS) connection.

A websocket connection can be secure or insecure. A websocket secure (WSS) connection uses SSL certificates to secure data transmitted on the socket. WSS requires a SSL certificate at each end of the socket communications; a server certificate for the server, and a root certificate of authority (CA) for the browser.

In a typical installation, where Ranger Remote client and server are both installed on the same workstation, the workstation's local loopback address (127.0.0.1) is used for the WS/WSS.

Server Side Certificate and WSS
To setup Ranger Remote to use WSS, RangerRemote Server's configuration file (RangerServerConfig.ini) will need to be modified to specify the chosen secure port, typically 9003s, and the path to the server certificate.
Default Windows install ini location:
C:/ProgramData/Silver Bullet Technology/Ranger/Ranger Remote/RangerServerConfig.ini
Default Mac install ini location:
/Library/RangerRemote/RangerServerConfig.ini

To setup Ranger Remote for WSS:
1) Stop the Windows service or Mac daemon.
2) Edit RangerServerConfig.ini
3) In RangerServer.ini change value in section [Server Connection] of windows key ListeningPorts=9003s  (or other desired port, appended with a lower case. The client side (browser) will now need to point to this same port when attempting to connect.
4) In RangerServerConfig.ini, change value in section [Server Connection] of key
WIN: SslCertificatePath = C:\Program Files (x86)\Silver Bullet Technology\Ranger\Ranger Remote\Certificates\server.pem (or different path to server certificate file)
MAC: SslCertificatePath = /Library/RangerRemote/server.pem (or different path to server certificate file)
5) Save RangerServerConfig.ini
6) Restart Windows service or Mac Daemon.

Client Side/Web Browser Certificate Setup
Windows:
1) Use Windows command prompt by typing command in the Windows Start menu search field. Right click Command Prompt in the resultant list and choose Run as administrator.
2) Use certutil in the command prompt
certutil.exe  -addstore -f "Root" "[path][CA certificate name.pem]"
example:  certutil.exe  -addstore -f "Root" "c:\rootCA.pem"

OSX:
1) Open the Applications folder by either holding the command+shift+A keys or selecting from the top finder menu Go->Applications.
2) Navigate to the Utilities folder and select Keychain Access.app.
3) Open Keychain Access.app.
4) Ensure Category->Certificates is highlighted in the bottom left column.
5) Ensure Keychains->login is highlighted in the top left column.
6) Drag the client side certificate into the main window.
7) Right click the newly added certificate from the main Window and select Get Info.
Click the trust turnout and set Always Trust to SSL.

1) Open the Windows Event Viewer application.

2) Expand the folder named "Applications and Services Logs."

3) Expand the folder named "Microsoft."

4) Right-Click the "RdmCorp" event thread.

5) Select the "Save all events as..." option.

6) Save the file to your preferred location.

1) Run the the MagTek demo application as Administrator.

Excella-STX_Demo.exe is found at the following path:
C:\Program Files (x86)\MagTek\Excella-STX-ImageSafe

2) Select your device from the Select Device drop-down and select connect.

3) Once connected click on the "Options" tab and select "Process Configuration..."

4) Check the box next to the "API Log Enabled" option.

Press the Ok box and proceed to scan items, the log will be generated when the demo application is shutdown. The log will be placed in the same folder as the application.

Please remember to run the MagTek demo application as Administrator or the log will not be generated.

Silent Install - /S - http://www.sbulletsupport.com/index.php?topic=83.0

When ranger is installed silently no dialog is shown to the user.

So you could embed the ranger installer within your own script, extract it and run it from your install script. To run the Ranger install silently you simply need to tack on a "/S" as a command line parameter when running the executable. For example: C:\RangerInstaller.exe /S. The command line parameter is case sensitive, so you will need to make sure that it is an upper case S.

Set Installation Folder - /D=C:\ - http://www.sbulletsupport.com/index.php?topic=267.0

In order to specify a destination directory when running the installer in silent mode, the /D switch should be used as follows:

[installer].exe /S /D=C:\Program Files\[directory]

Additional information about the NSIS command line parameters
http://nsis.sourceforge.net/Docs/Chapter3.html

Where can I find the Ranger.DLL file?