> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/introduction/release-notes.md).

# Release notes

{% updates format="full" %}
{% update date="2026-08-26" %}

## StifleR 3.1.2634.667

* \- Added MOM 2.4 support: the proxy address is now delivered to clients via location policy
* Added roaming client grouping by country
* Added certificate-based application authentication for the Graph API, with secret-based authentication retained for backward compatibility
* Improved performance by reducing overhead during Graph API token acquisition
* Simplified the DeployR task sequence editor to prevent unintended deletions
* Updated bundled third-party components to address reported security vulnerabilities
* Fixed beacon bandwidth measurements failing on some clients
* Fixed RemoteR connecting only to the first client opened in a tab, so remote tools now connect for each client opened
* Fixed RemoteR disconnect notifications being shown for a client other than the one currently open
* Fixed clients being shown as offline in Client Search after reconnecting
* Fixed server-side AgentId assignment logic
* Fixed dashboard charts not rendering when recreated, which could leave network group bandwidth usage graphs empty
* Fixed extended browser caching of the dashboard, so updated dashboard files and configuration are picked up after an upgrade
* Fixed OSD task sequence progress not displaying when no peer-to-peer transfer data was available
* Fixed task sequence step definition options ordering
* Fixed multi-line log record parsing in the log viewer
* Fixed script paths for PowerShell scripts in Settings
* Fixed the DeployR content item filter and entity version selection
* Removed a duplicate version label from the DeployR content item version selection
  {% endupdate %}

{% update date="2026-07-07" %}

## StifleR 3.1.2627.641

* Added roaming client grouping by country
* Added MOM 2.4 proxy address to clients via location policy
* Improved performance by reducing overhead during Graph API token acquisition
* Fixed OSD task sequence progress not displaying when no peer-to-peer transfer data was available
* Fixed task sequence step definition options ordering
* Fixed DeployR entity version selection in the content item, step definition, and task sequence pickers
* Fixed DeployR content item filtering
* Fixed multiline log record parsing for log entries spanning multiple lines in task sequence logs
* Fixed script paths for PowerShell (.ps1) scripts in Settings
* Fixed server-side AgentId assignment logic
* Fixed clients incorrectly shown as offline in Client Search after reconnecting
  {% endupdate %}

{% update date="2026-06-22" %}

## StifleR 3.1.2626.583 

* Introducing Role-Based Access Control (RBAC)
* Migrated to new licensing platform
* Added client read-only mode via feature-based policy
* Added 2PXE infrastructure services and DeployR Community support
* Improved OIDC sign-in reliability and dashboard authentication handling
* Security improvements and vulnerability fixes
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://documentation.2pintsoftware.com/stifler/introduction/release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.