# Release Notes ## September 8, 2025 ### **Release Build Versions** Beacon: 2.10.20820.2309 \ Dashboard: 2.10.20820.2032 \ Server: 2.10.20908.1504 ### **Dashboard and Reporting** * Fixed beacon measurement history logic for better tracking and reporting (18159) * Replaced BingMaps API with Online Services for geographic lookups * Fixed WiFi tracking in dashboard when WiFi7 capable clients are connected to StifleR (17478) * Added missing values in WMI for Location, NetworkGroup and Network objects (17481) * Fixed issue where networks without clients don't change their client count correctly (17479) * Fixed incorrect download count display (17480) ### **StifleR Server and Configuration** * Fixed exception in LocationServices when network is missing MAC address (18081) * Fixed issue where network save operations could occasionally fail (17484) * Removed redundant job worker, related logs and models for better performance (17898) * Fixed incorrect AppConfiguration setting for ExpectedCheckInInterval (17533) * Increased string limits in Esent entities to prevent data truncation (17451) ### **Beacons and Networking** * Beacon now supports Fully Qualified Domain Names for more flexible network configurations * Fixed WMI Service to properly show measurements on current network group only (17137) * Fixed throttling stops working on new network groups or when assigning different templates (18428) * Prevented unwanted resetting of network group bandwidth throttling settings * Fixed network card and IP information failures when adapter does not support IPv6 or when IPv6 is disabled (17483) * Fixed critical issues where clients moving between networks caused SignalR connection looping (18619, 18618, 18590) * Fixed network policy calculation failures on network groups with duplicate entries (18618) ### **Performance and Stability** * Replaced ToString with ToLogValue for better log value tracking * Fixed event log messages not working for Location in client (17577) * Corrected time calculations on BITS jobs for speed from origin metrics (17485) ## March 20, 2025 ### Release Build Versions Agent: 2.10.20313.1943\ Beacon: 2.10.20313.1939\ Dashboard: 2.10.20313.2115\ Server: 2.10.20320.0029 ### Dashboard and Reporting * Fixed an issue where StifleR Client reported wrong version (16962) * Implemented enhancements in network creation logic (14218) * Resolved an issue where BranchCache flags were not set to 0 even if all flags were removed (13739) * Fixed an issue where the SMSTS log was not visible in the dashboard (14866) * Ensured that firewall ports are properly created for Blue leaders, resolving connectivity issues (14894) ### StifleR Server and Configuration * Corrected an inconsistency where SRUM data did not match the application family name (16283) * Fixed a bug where SRUM data was not retrieved for unknown applications, ensuring accurate data collection (16285) ### Beacons and Networking * Enhanced network creation automation (16717) * Fixed issue where Green leaders are not removed when template changes (16595) * Resolved firewall ports not created for Blue leaders (14894) * Fixed an issue where LEDBat tracking did not function properly, and debug logs were not being created as expected (15427) ### Performance and Stability * Fixed an issue where Stifler Server could quit unexpectedly (10415) * Addressed DB write failures or delays that occurred during heavy load conditions (14990) ### Improvements and Enhancements * Updated NetFilter driver to version 1.7.1.5 * Security updates addressing CVE-2024-51417 ## December 18, 2024 ### Dashboard and Reporting * Resolved an issue where SRUM data was not being collected or displayed in the dashboard (13661) * Fixed dashboard template inconsistencies regarding “Cache options set” configurations (13813) * Corrected the bandwidth calculation logic, ensuring accurate representation in reports (13964) * Unlimited 0 Kb/s bandwidth setting UI has been improved for better clarity (14050) ### StifleR Server and Configuration * Fixed an issue where the StifleR server failed to bind a new web certificate (13796) * Resolved an issue preventing the deletion of cache tracks from the dashboard (13797) * Addressed a bug where BranchCache cache sizes were incorrectly configured (13821) * Resolved an issue with cache options for network groups displaying an extra dash (14999) * Resolved case sensitivity issue with group names in StifleR Server config (15426) ### Beacons and Networking * Fixed a glitch where network group details were inaccessible unless beacon details were clicked first (14438) * Resolved an issue where logs were missing (14439) * Fixed a critical issue where the Beacon Service stopped accepting requests (14219) * Corrected handling of error messages for DO group IDs (15050) * Resolved a tooltip glitch in the Templates - DO section (14188) * Addressed a configuration bug where adding a setting to the beacon config resulted in counters always displaying as 0 (14358) ### Improvements and Enhancements * Fixed an issue where the client management page returned console errors (14624) * Fixed an issue where StifleR client occasionally disconnected (15849) * Resolved duplicate network creation issue with ConfigMgr Boot Image (14431) * Added Play and Pause buttons to live tables for enhanced user control (14380) * Improved firewall configuration by ensuring that ports are created for Blue leaders (14894) * Fixed an issue where the TS-variable WellConnected2PS did not change to false during template updates (13684) * Addressed an issue where the StifleR Client occasionally disconnected from the server (15849) * Enhanced overall system stability with additional bug fixes and security updates (CVE-2023-32571, CVE-2024-30105) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.2pintsoftware.com/stifler/2.10/introduction/release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.