StifleR client installation

This is the StifleR 2.14 (current) release documentation. For other versions, please select the Drop Down list at the Top Left and select the correct version.

If you’d like to request a trial and explore our product, please visit this page. Existing customers should use the link provided by our team to proceed.

Prerequisites

  • Windows 10 or later

  • Windows Server 2016 or later

  • Supported are x86 or x64 versions of the operating systems (x86 for Windows 10 only)

    • Professional, Enterprise, Education, or LTSC editions for client operating systems

    • Microsoft .NET 4.8 must be installed

Installation

Manual Installation

From an Elevated Command prompt launch StifleR.ClientApp.Installer64.msi.

At the "Welcome" screen, feel welcomed, and then click Next.

At the "End-User License Agreement" screen, once you have reviewed the EULA, check the box: I accept the terms in the License Agreement, and then click Next.

At the "Destination Folder" screen, enter the path in which the StifleR Beacon server program files should be installed and then click Next.

At the "Ready to install..." screen, click Install to begin the installation.

At the "Completed" screen, the installation wizard is complete. Click Finish and enjoy a nice cup of craft beer, you’ve earned it.

After finishing installation configuration tool will be opened, please configure needed settings

Unattended installation

With StifleR 2.14 we introducing option to install client unattended.

In order to achive that you will need to install one client with manual approach, after that you will be able to export settings you configured

This file would contain required settings in custom Json format, where any string value containing " " (space) is replaced with "%20", and final output is stripped of all " " (space); here is an example:

You will need to open this file with any text editor to view content of it

{"SettingsOptions":{"StifleRulezURL":"https://2pintsoftware.com/StifleRulez.xml%20","LogEventLevel":"Verbose","StiflerServers":"[\u0022http://10.10.20.101:1414\u0022]","UseServerAsClient":"True","SignalRLogging":"True"}}

In order to use this configuration together with MSI installer your will need add OPTIONS= parameter

msiexec /qn /l*v "log.log" /i StifleR-ClientAgent-x64.msi OPTIONS={"SettingsOptions":{"StifleRulezURL":"https://2pintsoftware.com/StifleRulez.xml%20","LogEventLevel":"Verbose","StiflerServers":"[\u0022http://10.10.20.101:1414\u0022]","UseServerAsClient":"True","SignalRLogging":"True"}}

With our default pattern, installer at complete would launch Config Editor, and once settings have been confirmed, Editor would set service to "Automatic Startup" and then start it.

In unattended mode, if we want the service to be started on complete, we need to pass parameter AUTOSTART=1 to MSI; note that this parameter will only be used in unattended/quiet or basic mode, and project has Config Editor support.

msiexec /quiet /l*v "log.log" /i StifleR-ClientAgent-x64.msi AUTOSTART=1 OPTIONS={"SettingsOptions":{"StifleRulezURL":"https://2pintsoftware.com/StifleRulez.xml%20","LogEventLevel":"Verbose","StiflerServers":"[\u0022http://10.10.20.101:1414\u0022]","UseServerAsClient":"True","SignalRLogging":"True"}}

Post Installation

Service Status

Open services.msc to validate that the 2Pint Software Stifler Client service is installed and running, or run the following PowerShell command and validate that the service is present and running:

Get-Service -Name StifleRClient | Select Status

Validate the following output:

Event Logging

To validate that the StifleR Server Event Logging structure has been created, execute the following PowerShell command:

Get-WinEvent -ListLog TwoPintSoftware-StifleR.ClientApp* | Where-Object { $_.RecordCount }

Validate the following output:

PreviousStifleR Beacon installationNextConfiguration

Last updated