StifleR Network Locations

Once you install the StifleR client on some test systems, they will report to the StifleR server, which will start to populate the Location information based on the data sent back from the clients.

Each ’newly discovered’ location/subnet has a set of default parameters, and for the purposes of testing, there are some configuration changes that should be made to enable optimal performance while testing.

Configure Subnet Bandwidth

On the StifleR server – run the following command from an elevated Command prompt

wmic /namespace:\\root\stifler path Subnets.SubnetId="xxx.xxx.xxx.xxx" set TargetBandwidth=xxxx

Where xxx.xxx.xxx.xxx is the subnet ID of your test location and

xxxx is the target bandwidth that you wish to allow for that subnet in Kilobits. So 1024 = 1 Mbit

The Target Bandwidth is the network total bandwidth usage limit that is defined for ALL StifleR clients at that location – so if the limit is set to 4Mbit/s – then the TOTAL bandwidth usage across all clients at that location will not exceed that limit.

Populate Subnet Summary Information

Scripted

The summary information for a subnet provides an easy to read description of the subnet in the StifleR dashboards.

Run the following commands from an elevated Command prompt.

wmic /namespace:\\root\stifler path Subnets.SubnetId="192.168.138.0" set Description=”Test
Location”
wmic /namespace:\\root\stifler path Subnets.SubnetId="192.168.138.0" set Town=”SomeTown”
wmic /namespace:\\root\stifler path Subnets.SubnetId="192.168.138.0" set Country=”USA”

You can of course substitute the entries above with those of you own choosing.

Manually through the Dashboards

From the main StifleR Menu (Top LHS matrix icon) navigate to the dashboard for the particular subnet on which you wish to add some summary information. You may then click on a field and you will be presented with an edit box into which you may enter the required details.

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=”99999999-9999-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 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; DODownloadMde = $DODownloadMode }
} 

Other Delivery Optimization Settings

In order 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.

https://docs.microsoft.com/en-us/windows/deployment/update/waas-delivery-optimization