# DeployR 1.1 release notes

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

## DeployR 1.1.2614.1511

* Fixed an issue that prevented Entra ID-based authentication from PowerShell (#19783).
* Added automatic filtering of content item and task sequence architecture (e.g. do not include ARM64 items on x64 media) when creating media (#19784).
* Fixed an issue that resulted in extra logging of HEAD request errors on the DeployR server (#19782).
* Fixed an issue where task sequences did not properly set the UEFI recovery partition attributes (#19785).
  {% endupdate %}

{% update date="2026-03-31" %}

## DeployR 1.1.2613.1481

This is the initial release of DeployR 1.1.  New features and fixes included in this release:

* Improved download speeds for content being downloaded from the DeployR server.
* Added support for configuring a default keyboard layout for Windows PE (specified via the KeyboardLayoutPE entry in Bootstrap.json) and a UI for dynamically changing the keyboard layout when in Windows PE.
* Added logic to automatically compress and upload the DeployR logs to the DeployR server at the end of every task sequence.  These can be found in the content store, which is located at C:\ProgramData\2Pint Software\DeployR\Logs (or wherever you have configured in the DeployR settings).
* Added support for standalone ISO or USB media.  Selected content and task sequences will be placed on the media so that they do not need to be downloaded from the server.  In full "standalone" mode, no communication with the DeployR server is needed (so no authentication or network access is required).  In "caching" mode, authentication with the DeployR server is performed and any content not available on the media, or cloud-based content that is provided through DeployR, will be accessible.
* Added a "Run server-side PowerShell script" task sequence step to run a specified PowerShell script on the DeployR server.  This PowerShells script can access the task sequence variables from the computer running the task sequence, perform any actions needed, and then return variables back to the task sequence.
* Added the ability to import OEM driver packs into DeployR as content items managed by and downloaded from DeployR.
* Added on-disk encryption for the task sequence state information.
* Added support for deploying Windows to BIOS/MBR-based computers.
* Added an "Upgrade operating system from the cloud" step definiton and task sequence template that can be used to upgrade an existing Windows installation to a later release, with the Windows installation files automatically downloaded from Windows Update.
* Added initial support for performing an unattended installation of Ubuntu Desktop, versions 24.04 or later.
* Added support for using an ISO file for the "Apply OS" step Windows source.  This eliminates the need to extract the install.wim from the ISO before uploading this to a DeployR content item.
* Added support for running a Preinit.ps1 script in Windows PE before DeployR starts and before the network is initialized.
* Added a "Cache content" task sequence step definition and an improved "Cache All" task sequence template.  This new step definition enables more selective caching of content (e.g. content items with specific tags).
* Improved the task sequence logging to be more clear on errors and to not display any unnecssary stack traces.
* Improved the process of updating the time in Windows PE to avoid TLS errors when the computer's real-time clock is wrong.
* Added the ability to clone an existing task sequence via PowerShell using the Import-DeployRTaskSequence cmdlet with the -Clone switch.

Some changes of note:

* DeployR 1.1 now uses PowerShell 7.4.14 and .NET 8.0.25.  Be sure to upgrade your DeployR server with these releases, and completely regenerate your Windows PE boot media.
* DeployR 1.1 has changed the task sequence variable names used by DeployR itself so that they begin with an underscore.
* The offline domain join step no longer uses the computer's serial number as the default name, so a name needs to be specified via the ComputerName task sequence variable.  Also, when creating a computer object in Active Directory, the server will initially attempt to create the object without specifying that an existing object with the same name can be replaced.  Only after receiving a 2224 return code indicating that the object already exists will it try with a "replace" flag.
  {% endupdate %}
  {% endupdates %}