StifleR Server Installation

Manual Server Installation

The easiest way is to install the server manually using the MSI. The server supports silent installation if needed, but typically you only need to run the installation on a single occasion, so automation is not usually required.
  • Requires .NET 4.7.2 to be installed on the server
  • If you want to use the same server to host the dashboards, install IIS as well
  • Installation account must have Administrator rights
  • Ensure you have the License.cab available for the installer to access
  • Set up the StifleR Administrative Security Groups
  • Ensure the needed firewall ports are opened
From an Elevated Command prompt launch StifleR.Installer64.msi.
NOTE: The installer does not check the license file currency or validity. If you select an incorrect license file the installer will continue but the StifleR service may stop soon after starting.

Automated Server Installation

If you need to automate the StifleR Server installation then you could run the following example command line from an elevated command prompt:
msiexec /i StifleR.Installer64.msi CABSOURCE=C:\Temp\License.cab /qn
Figure 5 StifleR Server Installation MSI Switches

Post StifleR Dashboards Installation – IIS Configuration

As access to the StifleR dashboards is limited by Windows Group membership there is a requirement to make some security configuration changes on the StifleR Dashboards website within IIS.
Specifically, we need to remove Anonymous access, and configure Windows Authentication. Then within Windows Authentication, ensure that the only provider that is enabled is NTLM.
You can do this manually within IIS Manager, but the easiest way is to run the following PowerShell snippet:
#Configure IIS for Authentication
$siteName = "Default Web Site/StifleRDashboard"
Write-Host "Configuring IIS for Windows Authentication"
Set-WebConfigurationProperty -filter
/system.webServer/security/authentication/AnonymousAuthentication -name enabled -
value false -PSPath IIS:\ -location $siteName
Set-WebConfigurationProperty -filter
/system.webServer/security/authentication/WindowsAuthentication -name enabled -
value True -PSPath IIS:\ -location $siteName
Write-Host "Configuring Windows Auth Providers"
#First we remove all providers - then re-add NTLM Provider only.
Get-WebConfigurationProperty -Filter
system.webServer/security/authentication/WindowsAuthentication `
-Location $siteName -Name providers.Collection | Select-Object -ExpandProperty
Value | ForEach-Object {Remove-WebConfigurationProperty -Filter
system.webServer/security/authentication/WindowsAuthentication -Location $SiteName
-Name providers.Collection -AtElement @{value=$_}}
Add-WebConfigurationProperty -Filter
system.webServer/security/authentication/WindowsAuthentication `
-Location $siteName -Name providers.Collection -AtIndex 0 -Value "NTLM"

Server Installation - Post Installation Checks

  • Check that the service running and is not stopped or in any other state
  • Manually stop and start the 2Pint Software StifileR Service and ensure that it does so gracefully
  • Navigate to the StifleR installation directory
  • 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 any expected custom installation values are present other than default
  • Open up the Windows Event Viewer MMC and check that StifleR Server events are being logged:

Ensuring WMI Is Operational

  • Open up wbemtest.exe and connect to the Root\StifleR namespace
  • Open up the StifleREngine class:
  • Ensure you can see the WMI methods:
  • Hit the Instances button:
  • You should see the default Instance of the StifleREngine with the ID of 1:
  • Select this Instance. Scroll down in the properties window. Ensure that LicensedVersion is not null and that the other values are similar to those below