# StifleR Client Configuration File

The StifleR Client configuration file is used to configure global settings for the StifleR server. The config file (**StifleR.ClientApp.exe.config**) is located within in the program files directory in which StifleR Client was installed. The settings below are located within the \<appSettings> section of the file:

```
Example: 
<appSettings>
    <add key="Setting Key Value Name" value="some value"/>
</appSettings>
```

> Note: Not all values in the StifleR.ClientApp.exe.config file are documented here.  Please contact 2Pint Support prior to making changes to undocumented settings.&#x20;

You must restart the "2Pint Software StifleR Client" service for the changes in the configuration file to take effect. \
In general, numerical value 0 = False and 1 = True.\
Individual values are to be considered default.

<table><thead><tr><th width="367">Setting Key Value Name</th><th>Values and Descriptions</th></tr></thead><tbody><tr><td>AlternativeLatencyHostName</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>BlueLeaderProbePort</td><td><strong>Value:</strong> 3703<br><strong>Description:</strong> </td></tr><tr><td>BlueLeaderProxyPort</td><td><strong>Value:</strong> 1338<br><strong>Description:</strong> </td></tr><tr><td>BranchCachePort</td><td><strong>Value:</strong> 1337<br><strong>Description:</strong> </td></tr><tr><td>BranchCacheRetrievalPort</td><td><strong>Value:</strong> 1336<br><strong>Description:</strong> </td></tr><tr><td>CheckInterval</td><td><strong>Value:</strong> 30000<br><strong>Description:</strong> </td></tr><tr><td>ClientSettingsProvider.ServiceUri</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>DataPath</td><td><strong>Value:</strong> %PROGRAMDATA%\2Pint Software\StifleR\Client<br><strong>Description:</strong> The local folder in which the client stores its configuration data. </td></tr><tr><td>DebugLogPath</td><td><strong>Value:</strong> %PROGRAMDATA%\2Pint Software\StifleR\Logs\<br><strong>Description:</strong> The local folder in which the client stores the debug log. </td></tr><tr><td>DefaultDisconnectedBITSPolicy</td><td><strong>Value:</strong> 128<br><strong>Description:</strong> Default bandwidth limit (KBps) for BITS if the client is considered "<a href="../../../operations/bandwidth-management#disconnected-clients">Disconnected</a>".</td></tr><tr><td>DefaultDisconnectedDOPolicy</td><td><strong>Value:</strong> 128<br><strong>Description:</strong> Default bandwidth limit (KBps) for DO if the client is considered "<a href="../../../operations/bandwidth-management#disconnected-clients">Disconnected</a>".</td></tr><tr><td>DefaultNonRedLeaderBITSPolicy</td><td><strong>Value:</strong> 64<br><strong>Description:</strong> Default bandwidth limit (KBps) for BITS.</td></tr><tr><td>DefaultNonRedLeaderDOPolicy</td><td><strong>Value:</strong> 64<br><strong>Description:</strong> Default bandwidth limit (KBps) for DO.</td></tr><tr><td>EnableDebugLog</td><td><p>Va<strong>lue:</strong> 0 (default) 1-5<br><strong>Description:</strong> Enables debugging. This log will be fairly verbose, so remember to set it to "0" to switch it off afterwards. </p><p>0 = Disabled</p><p>1 = Errors Only </p><p>2 = Warning </p><p>3 = OK </p><p>4 = Informative </p><p>5 = Debug Errors and warnings will always be logged to the event log.</p></td></tr><tr><td>EnableDebugTelemetry</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> </td></tr><tr><td>ExpectedRedLeaderIntervalMultiplier</td><td><strong>Value:</strong> 3<br><strong>Description:</strong> </td></tr><tr><td>Features</td><td><strong>Value:</strong> EventLog, Power, PerformanceCounters, AdminElevatedTracking, AdminTracking, BranchCache, SendEndpoints, ResMon, MeasureBandwidth, LocationData, Disconnect, TcbStats, AckJobs, DOPolicy, RedLeader, BlueLeader, NotRedLeader, InterVlan, CreateBITSJobs, ExecutePowerShell ,RunCmdLine, ModifyJobs, Notify, WOL, UpdateServers, UpdateRules<br><strong>Description:</strong> A list of enabled features of the StifleR client. Add / Remove features and restart the StifleR client service. <a href="#features">See descriptions of the features below.</a></td></tr><tr><td>GreenLeaderOfferPort</td><td><strong>Value:</strong> 1339<br><strong>Description:</strong> </td></tr><tr><td>LimitWiFiSpeeds</td><td><strong>Value:</strong> 1<br><strong>Description:</strong> If a Red Leader has not checked in within this time period, another one will be elected. Value in msecs.</td></tr><tr><td>MaxPokeBandwidth</td><td><strong>Value:</strong> 128<br><strong>Description:</strong> </td></tr><tr><td>MaxPolicyChangeTime</td><td><strong>Value:</strong> 30<br><strong>Description:</strong> </td></tr><tr><td>NoJobIntervalMultiplier</td><td><strong>Value:</strong> 15<br><strong>Description:</strong> </td></tr><tr><td>NoProgressTimeout</td><td><strong>Value:</strong> 300<br><strong>Description:</strong> </td></tr><tr><td>Notifications</td><td><strong>Value:</strong> Administrator<br><strong>Description:</strong> </td></tr><tr><td>NotLeaderMaterial</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> </td></tr><tr><td>ReportOnly</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>SendGeoData</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> If value is set to 1, the client will send geolocation data to the StifleR server.</td></tr><tr><td>SignalRLogging</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> </td></tr><tr><td>SkipMandatoryWarning</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> This setting disables the countdown dialog which appears when WinPE is about to run a mandatory Task Sequence assignment. This setting is only applicable to the StifleR Client .config file when using the <a href="https://osd.docs.2pintsoftware.com/3.1.9.0/customization/adding-branchcache-to-winpe#optional-parameters">/<strong>StifleRConfig</strong></a> option with the WinPEGen.exe utility.<br>If the value is set to 1, the countdown dialog for a mandatory task sequence will be suppressed.<br>For more information, see this <a href="https://osd.docs.2pintsoftware.com/3.1.9.0/customization/adding-branchcache-to-winpe#option-to-disable-mandatory-task-sequence-warning-countdown-dialog">OSDToolkit documentation page</a>. </td></tr><tr><td>SleepBeforeSwitchingServer</td><td><strong>Value:</strong> 60000<br><strong>Description:</strong> </td></tr><tr><td>SRUMInterval</td><td><p><strong>Value:</strong> 30</p><p><strong>Description:</strong> </p></td></tr><tr><td>StiflerServers</td><td><strong>Value:</strong> http(s)://servername.domain.com:port<br><strong>Description:</strong> The StifleR web service URL and port in which clients connect to.</td></tr><tr><td>StifleRulezURL</td><td><strong>Value:</strong> http(s)://servername.domain.com/StiflerRules/StifleRulez.xml<br><strong>Description:</strong> The URL which hosts the StifleRulez.xml file. </td></tr><tr><td>UpdateRulesTimerInSec</td><td><strong>Value:</strong> 3600<br><strong>Description:</strong> The number of seconds in which the StifleR client will connect to the URL to download the StifleRulez.xml file. </td></tr><tr><td>UpdateScreenInterval</td><td><strong>Value:</strong> 2000<br><strong>Description:</strong> </td></tr><tr><td>UseBITSForRulezDownload</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> If value is set to 1, the client will use BITS to download the StifleRulez.xml file. </td></tr><tr><td>UseFilterDriver</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> </td></tr><tr><td>UseServerAsClient</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> The StifleR client can be run on a Windows Server system where, for example, you may want to monitor the Bandwidth performance of an SCCM Pull Distribution Point. the server can be monitored like any other client. It will not appear as a StifleR Server in the ‘Servers’ dashboard.</td></tr><tr><td>UseStiflerServer</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> </td></tr><tr><td>v1MaxSizeLimit</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>VPNStrings</td><td><strong>Value:</strong> VPN, Cisco AnyConnect, Virtual Private Network, SonicWall<br><strong>Description:</strong> A comma separated list of VPN client strings that the StifleR client uses to detect whether an adapter is a VPN adapter. </td></tr></tbody></table>

### Features

The Features config settings referenced above can be modified to add or remove specific features and functionality from the StifleR Client:

| Feature Name          | Description                                                                         |
| --------------------- | ----------------------------------------------------------------------------------- |
| AckJobs               | Enables the server to complete jobs                                                 |
| AdminElevatedTracking | Enables reporting of client admin and elevation data                                |
| AdminTracking         | Enables reporting of members of the local administrator group                       |
| BlueLeader            | Device is/can a blue leader, bridges network segments for BranchCache and DO        |
| BranchCache           | Enables the client/server to control the BranchCache settings                       |
| CreateBITSJobs        | Allows the server to push BITS jobs to the client                                   |
| Disconnect            | Allows the server to disconnect the client                                          |
| DOPolicy              | Enables the client/server to control the Delivery Optimization settings             |
| ExecutePowerShell     | Allows the server to send PowerShell scripts to be executed                         |
| EventLog              | Enables eventlog reading from server/dashboard                                      |
| InterVlan             | Enables Blue Leader messages, allows client to bridge other networks                |
| LocationData          | Enables server to control the network locality settings                             |
| MeasureBandwidth      | Enables the client to measure the bandwidth availability if the server asks for it  |
| ModifyJobs            | Determines if running jobs can be modified from the server/dashboard                |
| Notify                | Not used, if device notifications are enabled                                       |
| NotRedLeader          | Client can not be selected as Red Leader                                            |
| PerformanceCounters   | Enables reading performance counters from server/dashboard                          |
| Power                 | Allows server to control power state from server/dashboard                          |
| RedLeader             | Device is/can be a red leader, highest priority download on the network             |
| ResMon                | Enables resource monitor functionality                                              |
| RunCmdLine            | Allows the server to send command lines to be executed on the client                |
| SendEndpoints         | Enables the server to retrieve the list of TCP endpoints the client is connected to |
| TcbStats              | Enables the server to retrieve the TCB statistics                                   |
| UpdateRules           | Enable automatic updates of the Stifle rulez                                        |
| UpdateServers         | Allows the server to update the server connection list                              |
| WOL                   | Enables Wake-On-LAN functionality                                                   |

<br>