StifleR VPN based clients work slightly differently to regular clients...here's how.
There are several different levels of Read and Administrator access that can be applied to Dashboard Administrators. This article identifies the various Global and Location specific security group membership required to grant each level of Administrative access.
The upgrade from a StifleR Server 2.0.2 and StifleR Agent 1.9.11 environment to StifleR Server 188.8.131.52 and StifleR Agent 184.108.40.206 installation sees a number of changes particularly in relation to the Performance and Resource client data that the v2.3 server consumes and visualises. This means that in an upgrade scenario the 1.9 StifleR Client objects lack some data required by the v2.3 server for full dashboard management. This article provides a high level overview of a simple lab upgrade.
This article discusses expected behavior in StifleR when clients are installed onto, or moved to, a previously unknown subnet.
Some IIS settings are required to help show ID at the door.
Linking a Subnet with another creates a virtual Parent Location object. You link the Child subnet to the Parent. Currently StifleR only supports Many to One relationship in a simple Parent – Children relationship. This relationship allows for two or more subnets to be treated as a single entity for bandwidth and other management tasks. This is a required action for StifleR Enterprise as the Blue Leaders and Red Leaders use this information for the Inter-VLAN transfer of BranchCache data.
Dashboards not updated after upgrade
Very handy for troubleshooting when the Windows Service wont start
Installation Error seen after upgrade from v1.7
This article gives a brief overview of how the bandwidth for a particular site is divided between active (Downloading) clients
Here are some handy URLs to test connectivity and show settings
Installation fails when using a custom app pool
This article provides a set of instructions for the upgrade of older versions of StifleR (1.8 or lower) to the latest 1.9.x.x release.
StifleR Enterprise - Red and Blue Leaders everywhere
StifleR Server Service will not stop
Some log files just don't know how to (w)rap!
Power is precious – but so is content transfer. 33% is the happy medium.
After re-installation duplicate client entries may appear in the dashboards. (Usually only seen in testing)
Under certain circumstances the StifleR Server Service may not release memory in a timely fashion which may cause resource issues. Recycle the StifleR Server Service to release resources.
StifleR no longer uses the BITS schedule settings - Legacy information only