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
  • Prerequisites
  • Installation
  • Validation
  1. Installation
  2. Server

StifleR Beacon Installation

PreviousStifleR Dashboard InstallationNextClient

Last updated 7 months ago

For more information about what a Beacon Server is and does, see this .

Prerequisites

  • Microsoft .NET 4.8

  • By default, the Beacon service listens on TCP port 5201 so this port should be open.

  • Installation account must have Administrator rights

Installation

From an Elevated Command prompt launch StifleR.Service.Beacon.Installer64.msi.

At the "Welcome" screen, feel welcomed, and then click Next.


At the "End-User License Agreement" screen, once you have reviewed the EULA, check the box: I accept the terms in the License Agreement, and then click Next.


At the "Service Logon Credentials" screen, choose the Logon Type, and then click Next.

Note: If using a local or domain account, the account must have "Logon as a Service" rights.


At the "Port Selection" screen, enter a Port Number, or accept the default port 5201, and then click the Test Port button. If the port is open, a green check mark will appear. If the port is not open, validate that the port is available. Once complete, click Next.


At the"StifleR Server(s) screen, enter the URL to the StifleR web service and port and then click Next.


At the "Destination Folder" screen, enter the path in which the StifleR Beacon server program files should be installed and then click Next.


At the "Select Firewall Configuration" screen, choose whether you would like the installer to create a firewall exception for the StifleR Beacon service port. Click Next to continue.


At the "Ready to install..." screen, click Install to begin the installation.


At the "Completed" screen, the installation wizard is complete. Click Finish and enjoy a nice cup of kombucha, you’ve earned it.

Validation

After a Beacon Server is installed, it should attempt to report into the StifleR Server. This can be validated by going into the StifleR Dashboard, under Devices - StifleR server, select Beacons. On the page will be a list of all currently configured Beacon Servers including online status, connection times, and measurement count.

Prior to a Beacon being used, you must complete the configuration by following the instructions on this page: .

Configuring a Beacon Server
page