Production 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.

This section provides a step-by-step process to install each component of the StifleR platform and whether you're evaluating via Proof of Concept or implementing a full production deployment, this is the correct order of installation to get a clean and functional environment.

Order of Installation

For a standard StifleR implementation, the recommended order for deploying and configuring each component is as follows:

1. Install StifleR Server - Core engine managing all operations.

2. Install StifleR Dashboard - Web UI for monitoring and configuration.

3. Install Action HUB - Dynamic, real-time actions across the StifleR ecosystem.

4. Install WMI Agent - Agent that replaces traditional WMI.

5. Install Beacon - Gathers telemetry and identifies active subnets.

6. Install StifleR Client - Client that monitor network activity, report and enforce policies.

Prerequisites for Configuration Manager

If Configuration Manager is being used as part of the PoC, the following additional setup are required. Detailed configuration steps can be found on the linked documentation pages.

Enabling BranchCache

BranchCache is the key Microsoft peer-to-peer technology in which StifleR manages the best. It is important to enable BranchCache on all systems relevant.

• If using Configuration Manager, enable BranchCache on all Servers / CM Distribution Points

• If you have a simple lab environment, you should perform this step (if required) on all your Distribution Points.

• If you are planning on testing in a production environment, make sure that you perform this step ONLY on the relevant DP where your test clients will obtain their deployment content.

See: Configuring BranchCache on Windows Server

Enabling DO

As well as BranchCache, StifleR can utilize download jobs which use Microsoft's Delivery Optimization (DO) peering technology.

See: Configuring Delivery Optimization

Enabling LEDBAT

This step is Optional

Microsoft integrated LEDBAT technology into Configuration Manager distribution points several years ago. LEDBAT is a bandwidth congestion control technology which is designed to use unused bandwidth and to reduce network congestion when load is high. See the below page for more information on LEDBAT and how to enable it:

See: Enabling LEDBAT on CM DPs

BITS Policy

Check for and remove any BITS policy that has been set within Configuration Manager and/or Active Directory. Such settings can interfere with the efficient operation of the automated Bandwidth mechanisms in StifleR.

In the Configuration Manager console, BITS settings can be configured in "Client Settings":

Make sure that this is set to No (default setting), as this configures a local BITS policy on the clients which we do not want.

Remove any BITS AD Group Policy (if configured) Within the Active Directory Group Policy Editor, go to: Computer Configuration -> Policies -> Administrative templates -> Network -> Background Intelligent Transfer Service (BITS)

Ensure that there are no BITS policies configured. If present, remove them from effecting any test clients.

Configure the Network Topology

• Configure Target Bandwidth

• Configure Subnet Description

• Configure Delivery Optimization