StifleR
2.10
2.10
  • Start Here - StifleR 2.10
  • Introduction
    • StifleR Overview
      • The StifleR Solution
      • Managing Microsoft Data Transfer Services
    • Technical Overview
      • 2Pint BranchCache Administrator Guide
    • Features Overview
      • Control
      • Monitor
      • Automate
      • Other Features
      • StifleR Feature Details
    • Release Notes
  • Proof of Concept
    • Objectives and Prerequisites
    • Configure Microsoft Peer-to-Peer Components
    • Install and Configure StifleR
    • Testing and Validation
    • StifleR POC Quick Checklist
  • Planning
    • StifleR Server Considerations
    • StifleR Client Considerations
    • Firewall Ports
    • Permissions
    • Antivirus Exclusions
    • Network Topology
    • StifleR Generic Concepts
      • Client Leader Roles
        • Red Leader
        • Blue Leader
        • Green Leader
        • Examples of Leader Selection
      • Templates
      • Beacons
  • Installation
    • Overview
    • Server
      • StifleR Server Installation
      • StifleR Dashboard Installation
      • StifleR Beacon Installation
    • Client
      • StifleR Client Installation
      • Post Installation Checks
  • Configuration
    • Configuration Files
      • StifleR Server Configuration File
        • Using the AppSettings Override File
      • StifleR Client Configuration File
      • StifleR Dashboard Configuration File
    • Configuring BranchCache on Windows Server
    • Configuring Delivery Optimization
    • Configuring LEDBAT on CM DPs
    • Configuring a Beacon Server
    • Configuring StifleR SQL History
    • StifleR Network Locations
      • Automatic linking of Location, Network Groups and Networks
      • Network Topology Automation
      • Location Fields
        • Network Group Fields
          • Network Fields
    • StifleRulez.xml Configuration Guide
      • The Match – TypeData
        • When the Job Title Isn’t Suitable
        • ConfigMgr Specific Rules
      • The Setting - DownloadTypes
        • Delivery Optimization Jobs
      • Sample StifleRulez.xml
    • Securing StifleR Operations with SSL
      • Prerequisites
      • Using a Web Server Certificate
        • Requesting a Web Server Certificate
      • Using a Self-Signed Certificate
      • Preparing the StifleR Dashboard Web Site for SSL
      • Configuring StifleR to Use SSL
      • Finding the Certificate Thumbprint
    • StifleR Client Access Control Options
  • Operations
    • Dashboard
      • Overview & Navigation
        • Home Page
        • Traffic & Downloads
          • Transfers & Downloads
            • How to use query hosts search?
          • Running Sequences
          • Weekly Downloads Activity
          • History
        • Devices
          • Clients
            • Client Details
              • How to use an extended search?
          • Servers
          • StifleR Server
            • Templates Detail
        • Cache Management
        • System Resource Usage
        • Network Topology
          • Maps
          • Countries
          • Locations
            • Bandwidth Allocations and Locations
          • Network Groups
          • Networks
        • Reporting & Diagrams
    • Client Management & Remote Tools
      • Remote PowerShell Session
      • Remote Performance Counter
      • Remote WMI Browsing
      • Remote Event Log Viewer
      • Remote Netmon Session
    • Monitoring
      • StifleR server health
      • StifleR client health
      • BranchCache Testing and Monitoring
    • Maintenance tasks
    • Bandwidth Management and Allocation
      • Bandwidth Tuning Monitoring and Control
    • Backup and Recovery
      • Moving the StifleR Server Databases to a New Drive on the Same Server
    • Troubleshooting
      • StifleR Client Command Line Options
      • BranchCache across Subnets
    • StifleR WMI Provider
Powered by GitBook
On this page
  • Adding a Beacon Server to a Template
  • Manually Executing a Measurement
  1. Configuration

Configuring a Beacon Server

PreviousConfiguring LEDBAT on CM DPsNextConfiguring StifleR SQL History

Last updated 7 months ago

Prior to configuration, a Beacon Server must be installed in your environment. For more information on installing a Beacon server, see this .

Once you have validated that the Beacon server is displayed on the Beacons page you can move forward with configuration.

Adding a Beacon Server to a Template

To add a Beacon server to a template, in the StifleR Dashboard, under Devices - StifleR server select Templates. In the Network group templates list, find the template you want to modify, and select the edit icon.

In the Network group template editor, locate the "Automatic throttling and LEDBAT++ settings" section. In the Beacon field, select the pencil icon. Select the box which appears and a drop down list should open which lists the Beacon servers that have reported into StifleR. Select the Beacon Server you would like to add, and then click the green check mark to save the setting.

Once the template is applied and clients are aware of the Beacon server, they will begin measuring their bandwidth. The "Measure vs template values" setting includes two options:

  • Beacon measure wins - if set, the StifleR Server will adjust the limits based on new measurements. This makes it possible to automatically bandwidth and override the template.

  • Template wins - if set, the StifleR Server will ignore any beacon measurements and always use whatever is set in the template.

Click the pencil icon to choose which setting you would like to apply.

Manually Executing a Measurement

Beacons should receive measurements automatically, but you can also execute a measurement manually.

To manually execute a Beacon measurement, open the applicable Network Group the Beacon services by selecting the Network Group in the Network group list.

In the Network Group page, in the "Bandwidth and throttling settings" section, click the Measure Now link which should force a measurement. After a short time, this measurement should be reflected in the table on the Beacons page.

For clients to be made aware of a Beacon server, it must be added to a which applies to a that clients are within.

Template
Network Group
page