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
  1. Configuration
  2. Configuration Files
  3. StifleR Server Configuration File

Using the AppSettings Override File

PreviousStifleR Server Configuration FileNextStifleR Client Configuration File

Last updated 1 year ago

The contains multiple settings that are often modified and tweaked after the StifleR server is installed. Unless the file is backed up, these changes may be lost during an upgrade or re-installation. Even in the scenario in which the config file is backed up, it is not safe to restore it after an upgrade, because new .config settings may be introduced in newer versions.

To solve this issue, 2Pint has provided the option of using an AppSettings Override configuration file. This file can contain all of the settings which are stored in the StifleR config file and will essentially override them if the file is present. These settings will also override any settings defined when running the installation wizard except for the installation directory.

The file is read when the "2Pint Software StifleR Server" service starts.

The file must be named appSettings-override.xml and must be located in the StifleR Server installation folder. This file does not exist by default, and must be created by the administrator. The file will be preserved and will not be deleted during an uninstall, upgrade, or fresh installation.

The acceptable key values which can be added are documented on the page.

The syntax of the file is as follows:

<?xml version="1.0" encoding="utf-8"?>
<!-- PUT THIS FILE IN THE BIN DIRECTORY OF THE SERVICE TO OVERRIDE SETTINGS WITHOUT EDITTING THE APP.CONFIG DIRECTLY -->
<appSettings>
  <add key="NewLocationDatabasePath" value="E:\2Pint_Data\StifleR\Server\Databases\Location" />
  <add key="MainDatabasePath" value="C:\ProgramData\2Pint Software\StifleR\Server\Databases\Main" />
  <add key="HistoryDatabasePath" value="C:\ProgramData\2Pint Software\StifleR\Server\Databases\History" />
  <add key="SignalRCertificateThumbprint" value="1234567890abcdef1234567890abcdefg1234567"/>
  <add key="WebServiceCertificateThumbprint" value="1234567890abcdef1234567890abcdefg1234567"/>
 </appSettings>

StifleR Server Configuration File
StifleR Server Configuration File