POC Objectives and Prerequisites

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

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.

Lab Testing

In order to complete a POC deployment of 2Pint StifleR in a lab environment, you will need the following:

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

  • Several packages or applications that can be used for testing purposes. Ideally no less than 500Mb in size. (1GB recommended)

• Two (preferably three) Configuration Manager client PC systems:

  • It is recommended that all client systems used for testing are physical systems and that they are configured as close as possible to those in use in the production environment.

  • These clients should reside on a separate subnet from the server system(s) and should have a fully functioning CM client installed.

  • It is recommended that some clients should reside on a subnet which has slower connectivity to a DP. This can be achieved by installing a virtual appliance such as a pfSense router, which supports bandwidth limits.

Production Environment Testing

When testing in a production environment with Configuration Manager, the following infrastructure changes are recommended to reduce the impact to normal client operations:

1. Install a new Distribution Point (DP) running on a VM.

2. Identify and assign one or two locations to the new DP using boundaries and boundary groups

3. It is recommended that a few clients should reside on a subnet with slower connectivity to the distribution point.