> 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/deployr/1.2/release-notes.md).

# Release notes

{% updates format="full" %}
{% update date="2026-05-04" %}

## DeployR 1.2.2622.1921

* Fixed an assortment of issues related to capturing and uploading custom images.
* Added support for Windows authentication to access the DeployR server.
* Added new support for using a PowerShell secret store to manage server-side secrets that can be retrieved by a running task sequence, instead of saving those values in task sequence variables.
* Added support for using SQLite for database storage of all DeployR metadata.
* Moved to .NET 10.0.8 and PowerShell 7.6.2.  For existing DeployR Enterprise installations, these need to be installed manually before installing DeployR 1.2.
* Added a UI (via StifleR 3.1) that enables the easy importing of OEM driver packs into DeployR, creating content items that can then be managed by you.
* Added additional step definitions and scripts for Ubuntu to install the latest updates, to join a device to Active Directory, and to add an additional LUKS passphrase to an encrypted volume.
* Added support for injecting additional task sequence variables into unattend.xml files (ProductKey, RegisteredOwner, RegisteredOrganizaiton, fDenyTSConnections).
* Added support for the DeployR Community edition.
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.2pintsoftware.com/deployr/1.2/release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.