Quick start - PoC

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.

Introduction

This section provides an outline of tasks required for the setup and configuration of the 2Pint StifleR solution for a successful Proof of Concept (PoC). It is recommended that a StifleR PoC should be conducted in a dedicated test lab environment. However, if a lab is not available, the PoC can be executed in a production environment with minimal risk - but only within a small subset of computers and defined locations.

The objective for a StifleR PoC is to demonstrate how how StifleR enhances and extends Microsoft's technologies such as BranchCache, Delivery Optimization, and BITS - with the goal of reducing WAN utilization and maximizing peer-to-peer content delivery.

It’s important that the POC is driven from clear requirements. These requirements should be clearly defined and include test plans for validation.

Prerequisites

Before proceeding, it is strongly recommended to test all 2Pint Software components in a lab environment. Once validated in the lab, testing can proceed in production in a controlled and limited manner.

As part of the preparation for the PoC, ensure that:

• Required firewall ports are opened

• Antivirus exclusions are applied

• Necessary permissions are granted

Additional 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. In order to prepare for a successful PoC, it is important to enable BranchCache on all systems relevant to the PoC.

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

Installation

Prepare a suitable server to host StifleR components:

• In lab enviroments, this can be any server or VM as resource usage will be minimal

• In production environment, check StifleR Server Considerations for proper sizing and planning.

There are two installation options depending on your evaluation goals:

• Minimal Setup - For basic evaluation: StifleR Server, Dashboard, Beacon, deploy Clients and configure Network Locations.

• Full setup - For extensive testing: Install full set of StifleR components.

Configuration of Network Locations is essential for client reporting and optimal functionality.

Check List for Proof of Concept

Detail
Determine how many locations and clients will participate in the PoC.
Prepare a dedicated server (VM) to host the StifleR Server. See specific hardware requirements.
Provision a standard SSL web server certificate with the StifleR Server computer name in the Subject Name.
If using Configuration Manager, enable LEDBAT and BranchCache on the Distribution Points serving PoC locations.
Remove any existing BITS, BranchCache, and Delivery Optimization policies from clients participating in the PoC.
Open required firewall ports.
Add antivirus exclusions.
Create Active Directory administrative groups.
Provision an SSL Certificate(s) to Secure Dashboard and Client Communications.
Install StifleR components on the server.
Deploy StifleR Client to participating clients.
Review and adjust automatically created Locations, Network Groups, and Subnets in the Dashboard as clients report in. See the Configure the Network Locations page for details.
Deploy applications to test clients and refer to the Testing and Validation documentation.