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
  • Resulting Configuration
  • BranchCache Mode Configuration
  1. Planning
  2. StifleR Generic Concepts
  3. Client Leader Roles

Green Leader

PreviousBlue LeaderNextExamples of Leader Selection

Last updated 4 months ago

A Green Leader is a client which can function as a Hosted Cache server which can been manually specified on a template or network group.

A Green Leader can be defined by modifying a or a .

Important Note: Be aware! If a green leader is set on a template, all network groups using that template will use the Green Leader specified. This can cause unwanted traffic over locations with bad connectivity between them.

Resulting Configuration

When a client is configured to be a Green Leader, the client will be configured as such:

  • The BranchCache cache size will be configured based on the following rules:

    • If the disk size is under 128 GB, the BranchCache cache size will be set to 50GB.

    • If the disk size is above 128 GB, the BranchCache cache size will be set to 50% of the total disk size.

  • The TwoPint.PeerDist.BlueGreenLeader.exe process will be started

  • The BranchCache port to will be configured to TCP port 1336.

  • The BranchCache port will be configured to listen on port 1337 for Hosted cache traffic.

BranchCache Mode Configuration

Depending on what settings are used for the Template/Network group, the clients may behave differently:

Distributed mode (Force Hosted Cache mode = Disabled) :

If the network group contains multiple networks and the Green Leader is on a different network from the client requesting data, one of the following will occur:

  • If the network with the Green Leader or requesting client contains 4 or less clients - The clients will switch to "Hostedclient" mode and point directly to the green leader(s).

  • If the network with the Green Leader or requesting client contains 5 or more clients - The clients will send normal BC probes and internetwork connectivity will be handled by the Blue Leader clients.

Hosted client (Force Hosted Cache mode = Enabled):

In this mode the Green Leader will behave as a Hosted Cache Server. This means the client will store data in its cache and share it with requesting clients. The requesting clients are set to "Hostedclient" mode and the clients them self will not save any BC data but rather forward the data to the Green Leader (in the same way as they would have done to a Hosted Cache server).

Note: The Green Leader can both send and receive data from a BranchCache enabled WinPE client.

Template
Network Group