Installation
This section provides a step-by-step process to install each component of the StifleR platform. 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:
Install StifleR Server – Core engine managing all operations.
Install StifleR Dashboard – Web UI for monitoring and configuration.
Install Action HUB – Dynamic, real-time actions across the StifleR ecosystem.
Install Beacon – Gathers telemetry and identifies active subnets.
Install StifleR Client – Client that monitors network activity, reports and enforces policies.
Install WMI Agent (optional) – Agent that replaces traditional WMI.
Install CacheR (optional) – content tracking and pre-caching.
Prerequisites for Configuration Manager
If Configuration Manager is being used as part of the PoC, the following additional setup is required. Detailed configuration steps can be found on the linked documentation pages.
BranchCache is the key Microsoft peer-to-peer technology which StifleR optimizes. It is important to enable BranchCache on all relevant systems.
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 distribution point your test clients will obtain their deployment content from.
As well as BranchCache, StifleR can utilize download jobs which use Microsoft's Delivery Optimization (DO) peering technology.
This step is optional
Microsoft integrated LEDBAT technology into Configuration Manager distribution points several years ago. LEDBAT is a bandwidth congestion control technology that allocates unused bandwidth to reduce network congestion when load is high. See the link below for more information on enabling LEDBAT:
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":
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 to avoid affecting any test clients.
Configure target bandwidth
Configure subnet description
Configure Delivery Optimization
Last updated