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
  • Choosing a Database Host
  • Setting Permissions for the SQL Database
  • Required SQL Permissions
  • Enabling SQL History in the StifleR Server Configuration File
  • Configuring the History Database Configuration String
  • Restarting the StifleR Server Service
  1. Configuration

Configuring StifleR SQL History

PreviousConfiguring a Beacon ServerNextStifleR Network Locations

Last updated 10 months ago

Enabling SQL History in StifleR means that all data transfers will be logged to a defined SQL database. This extends the visibility of historical client content downloads, but requires additional components.

Choosing a Database Host

The SQL History feature requires a SQL database and host. The SQL database can be hosted on a remote SQL server or installed on the StifleR server. SQL Express can be used, but depending on the number of clients and content downloads, the database size may exceed the 10 GB limit of SQL Express.

Setting Permissions for the SQL Database

The SQL History feature will attempt to write to the SQL database using the user context in which the StifleR Server service is running. For example, if the StifleR Server service is running as "Local System" (default) then the computer account ($ComputerName) of the StifleR server needs to be granted access to SQL. If the StifleR Server service is running under a service account, the service account will need to be granted access.

Required SQL Permissions

The StifleR Server computer or service account will need db_creator permissions to the SQL instance to create and manage the SQL database.

Enabling SQL History in the StifleR Server Configuration File

To enable StifleR SQL History, you will need to edit the (StifleR.Service.exe.config) by setting the SQLHistory value to 1.

<add key="SQLHistory" value="1"/>

Configuring the History Database Configuration String

In the same StifleR Server Configuration File, you must define the database server and instance name and optionally the database name.

See the below example of the connection string you should edit in your .config file:

<connectionStrings>
    <add name="StifleR" providerName="System.Data.SqlClient" connectionString="Server=DBSERVER\DBINSTANCE;Trusted_Connection=Yes;DATABASE=StifleR"/>
</connectionStrings>    

Restarting the StifleR Server Service

After editing and saving the StifleR.Service.exe.config file, for the changes to take effect, restart the "2Pint Software StifleR Server" service.

Important: The StifleR SQL History database will not automatically be created after service restart. The database will be created when a client attempts to download content and reports the download status to the StifleR server.

StifleR Server Configuration File