StifleR
2.6
2.6
  • Start Here - StifleR 2.6
  • StifleR 2.6.x.x
    • StifleR - Release Notes
    • What's New
    • QuickStart Guide
      • Installation
        • Manual Server Installation
        • StifleR Client Installation
        • StifleR Network Locations
        • Example StifleR Rules Definition
    • Planning & Deployment Guide
      • TL;DR version
      • StifleR Overview
        • The StifleR Solution
      • Features Overview
        • Other Features
      • Technical Overview
        • StifleR Standard Features
        • StifleR Enterprise Features
      • Planning Your StifleR Implementation
        • Firewall Ports
        • Supported Clients
        • Networks in StifleR
        • Permissions
      • Installation
        • StifleR Server Installation
        • Dashboards, Client and Beacon Server Installation
        • Post Installation Checks
        • Testing Quick Start Guide
      • Troubleshooting
        • BranchCache across Subnets
      • StifleR Generic Concepts
        • Red Leader
        • Enterprise Environment - Blue Leader
      • Bandwidth Management
        • Bandwidth Tuning Monitoring and Control
      • StifleR WMI Provider
      • StifleR Feature Details
        • StifleR Enterprise Edition Features
      • Further Reading
    • StifleR Operations
      • Maintenance tasks
      • Backup and Recovery
        • Moving the StifleR Server Databases to a New Drive on the Same Server
    • 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
      • Pre-Requisites
      • Securing the StifleR SignalR Endpoint
        • Binding certificates to SSL Ports for SignalR/StifleR
      • Running SignalR with SSL
      • IIS Configuration
      • Appendix A: Certificates
        • Using IIS to create a self-signed Certificate
        • Using a full IIS Certificate
      • Appendix B:Finding the CertHash
Powered by GitBook
On this page
  • Service Driven Mode
  • Configure Delivery Optimization
Export as PDF
  1. StifleR 2.6.x.x
  2. Planning & Deployment Guide
  3. Installation

Post Installation Checks

PreviousDashboards, Client and Beacon Server InstallationNextTesting Quick Start Guide

Last updated 2 years ago

Service Driven Mode

  • Check that the 2Pint Software StifleR Client Service is Running

  • Stop and start the Service and check that it does so gracefully without error

  • Check that the service is generating Event log entries

Event Driven Mode

Check that the StifleR Scheduled task was created correctly.

Configure Delivery Optimization

WARNING: It is possible to set your Delivery Optimization Peer Caching boundaries to match your Microsoft Configuration Manager Boundary Group boundaries. It is important that you do not use this method if you are using StifleR to configure Delivery Optimization and vice versa.

If you are using Windows 10 Delivery Optimization, StifleR can ensure correct Peer to Peer boundaries are respected.

To achieve this, you need to set two parameters per subnet, the DODownloadMode and DOGroupID. These settings mirror the Policy settings for Delivery Optimization on the client systems.

The DOGroupID must be a unique GUID. You can generate a GUID using PowerShell (New-GUID command) or you could copy the GUID of the subnet itself and use that.

If you have multiple subnets within a location, and you want all StifleR clients to share content across those subnets, simply set the same Group ID for all subnets at that location.

For example, in order to configure this capability, you could run the following commands from an elevated command prompt on the StifleR Server:

wmic /namespace:\\root\stifler path Subnets.SubnetId=" xxx.xxx.xxx.xxx " set DODownloadMode=”2” 
wmic /namespace:\\root\stifler path Subnets.SubnetId=" xxx.xxx.xxx.xxx " set DOGroupID=”999999999999-9999-999999999999” 

Once the above parameters are set, the Delivery Optimization clients will only share content with other clients that have the same Group ID.

Note that as the DO group is meant to be well connected and used specifically for P2P file sharing there is no Blue Leader functionality as all members should be local.

PowerShell Snippet

This example loops through all subnets and enables Delivery Optimization Download Mode in ‘Group Mode’ (2)

It then sets the DOGroupID using the GUID for that subnet. This is the most basic configuration and means that DO will only share content with other clients on the same subnet.

$alllocs = @(gwmi -namespace root\StifleR -Query "Select * from Subnets")
foreach ($loc in $alllocs)
{
$DODownloadMode = 2
$DOGroupID = $loc.id
#Set the new subnet DODownload Mode + ID
swmi -path $loc.path -Arguments @{DOGroupID = $DOGroupID; DODownloadMode =
$DODownloadMode }
} 

Other Delivery Optimization Settings

To get the best performance from Delivery Optimization, 2Pint recommends that you set the following Policy items.

  1. Max Cache Age (in seconds) – Set this to zero (0) so that content is not removed from the cache once downloaded. The default is only 3 days

  2. Minimum Peer Caching Content File Size (in MB) – Set this to 1 to make sure that all files over 1MB in size will be shared via P2P. The default for this is 50MB or 100MB (depending on Windows 10 version) which excludes a lot of content

These are the minimum settings that we recommend for efficient Delivery Optimization Peer Caching. There are many other DO setting available – see this link for more information

Delivery Optimization for Windows 10 updates