Post Installation Checks
Last updated
Last updated
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
Check that the StifleR Scheduled task was created correctly.
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:
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.
To get the best performance from Delivery Optimization, 2Pint recommends that you set the following Policy items.
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
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
