StifleR server installation

Prerequisites

• Review StifleR Server Requirments page for server specs, etc.

• Open the required firewall ports

• Create and populate the StifleR Administrative Security Groups

• Microsoft .NET 4.8

• Installation account must have Administrator rights

• License.cab or license key (optional at this point)

• Decide on whether the StifleR Service will be using SSL (optional at this point, but recommended). For more information on using SSL, see this page.

Optional Components

Internet Information Services (IIS):

The StifleR Server API runs its own web service, so IIS is NOT required unless:

• You will also be installing the StifleR Dashboard on the same server.

• You will be hosting the StiflerRulez site on the same server.

Installation

From an Elevated Command prompt launch StifleR.Installer64.msi. You also can launch installation as it is, installer will ask for elevation when it will be needed.

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 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. Make sure that checkbox on the down left is set to Launch configuration editor. Click Finish and enjoy a nice cup of tea, you’ve earned it.

After you will press finish, new window of configuration will popup, here you will need to do a configuration to get started. On this step you will need configure such steps as Administrators group, Read Access group, dashboard URL, AuthredirectUri, License key, WSCertificateThumbprint and SignalRCertificate thumbprint. please use seach bar to find needed configuration.

Soon as you will configure critical settings, please use Verify button and after verification please press on Save button, this will save all settings and start StifleR service.

Post Installation Checks

Checking the StifleR Service State

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

Get-Service -Name StifleRServer | Select Status

Checking the StifleR Installation Directory

• If using a licensing file for licensing, check for the License.nfo files. If this is missing the service may not be licensed properly.

• Open up the configuration file, StifleR.Service.exe.config, and check that the expected values

  are present.

Checking the Event Logs

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

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

Validate the following output:

Checking WMI Configuration

Execute the following PowerShell command to verify that the WMI Class Root\StifleR and methods were created successfully:

Get-CimClass -Namespace Root\StifleR -ClassName StifleREngine | where {$_.CimClassMethods} | Select CimClassName, CimClassMethods

Validate the following output:

Execute the following PowerShell command to get the StifleR License information:

Get-CimInstance -NameSpace Root\StifleR -ClassName StifleREngine

Validate the following output:

Checking API Permissions

To test access to the StifleR Server API, open a web browser, and enter the StifleR Server URL such as:

http(s)://servername:9000/api/test

The page should display the results of your permissions such as the example below:

Checking StiflerRules Web Site Availability

To test access to the StifleR Rules Web Site, open a web browser, and enter the StiflerRules URL such as:

http://yourserverfqdn/StiflerRules/stiflerulez.xml

The page should display the contents of the XML file such as the example below: