# Objectives and Prerequisites

## Introduction

This section provides an outline of tasks required for the setup and configuration of the 2Pint StifleR solution in order to execute a Proof of Concept (POC). It is recommended that a StifleR POC be conducted in a test lab environment. If a test lab is unavailable, a 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 StifleR can enhance and extend Microsoft's BranchCache, Delivery Optimization, and BITS technologies with the goal of reducing WAN utilization and maximize 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 <a href="#toc30142818" id="toc30142818"></a>

We recommend that all testing of 2Pint Software components should be installed and verified in a separate lab environment before implemented in a production environment. Once tested and verified in the lab, in can then be tested in the production environment. If a test lab is unavailable, the POC can be executed in a production environment in a controlled manner.&#x20;

### **StifleR Server**&#x20;

Prepare a suitable server to act as the StifleR Server. If testing in a small lab, this can be any server for the purposes of testing as the load will be very light. If implementing in a production environment, check out the [StifleR Server Considerations](https://documentation.2pintsoftware.com/stifler/2.10/planning/stifler-server-considerations) page for sizing information.

### Lab Testing <a href="#toc30142820" id="toc30142820"></a>

In order to complete a POC deployment of 2Pint StifleR in a lab environment, you will need the following depending on whether you will be testing with Intune and/or Configuration Manager:

{% tabs %}
{% tab title="Intune" %}

* A functioning Intune instance with several applications that can be used for testing purposes. Ideally no less than 500Mb in size (1GB recommended).
* Choose 2-3 subnets with 3 or more client PCs each that are registered with Intune:
  * Ideally two of the subnets should be in the same location which have good connectivity with one another.
  * It is recommended that some clients should reside on a subnet which have slower connectivity to an Internet gateway.
    {% endtab %}

{% tab title="Configuration Manager" %}

* Microsoft Configuration Manager Primary Site server:
  * This server will provide all of the CM Roles such as a Management Point, Distribution Point, etc. on a single server.
* Configure 2-3 subnets with 3 or more client PCs each that are Configuration Manager clients.
  * Ideally two of the subnets should be in the same location which have good connectivity with one another.
  * It is recommended that some clients should reside on a subnet which has slower connectivity to a DP. In a lab environment, this can be achieved by installing a virtual appliance such as a pfSense router, which supports bandwidth limiting.&#x20;
* Choose several applications that can be used for testing purposes. Ideally no less than 500Mb in size (1GB recommended).
  {% endtab %}
  {% endtabs %}

### Production Environment Testing <a href="#toc30142821" id="toc30142821"></a>

In order to complete a POC deployment of 2Pint StifleR in a production environment, you will need to consider the following depending on whether you will be testing with Intune and/or Configuration Manager:

{% tabs %}
{% tab title="Intune" %}

* A functioning Intune instance with several applications that can be used for testing purposes. Ideally no less than 500Mb in size (1GB recommended).
* Choose 2-3 subnets with 3 or more client PCs each that are registered with Intune:
  * Ideally two of the subnets should be in the same location which have good connectivity with one another.
  * It is recommended that some clients should reside on a subnet which have slower connectivity to an Internet gateway.
    {% endtab %}

{% tab title="Configuration Manager" %}

* Choose 2-3 subnets with 3 or more client PCs each that are Configuration Manager clients.
  * Ideally two of the subnets should be in the same location which have good connectivity with one another.
  * It is recommended that some clients should reside on a subnet which have slower connectivity to a Distribution Point.
* Choose several applications that can be used for testing purposes. Ideally no less than 500Mb in size (1GB recommended).
  {% endtab %}
  {% endtabs %}