Prerequisites

DeployR integrates with StifleR and relies on several supporting components, including database services, deployment tools, and runtime dependencies. Proper configuration of these elements is required to ensure reliable operation and deployment workflows.

Before installing DeployR, ensure that the following prerequisites are in place:

FQDN

This requirement applies even in workgroup environments

The server must have a valid FQDN DNS entry.

Example: deployr.company.local

This FQDN is used for alll Service URLs and Certificate bindings.

Ports

These ports are inbound to DeployR server. (depending on the options you have installed)

7281 TCP: DeployR for secure communications from the clients

Additional port information can be found for the corrisponding compononts you're using with DeployR:

StifleR Components

You need to install only StifleR server and StifleR dashboard in order to operate DeployR, you don't need to install or configure rest of StifleR components. For monitoring you need to have StifleR client in your boot media (it's optional)

StifleR Server 3.1
StifleR Dashboard 3.1

StifleR supports Windows Server 2019 or later, and requires .NET Framework 4.8 to be installed, along with appropriate firewall configuration and TLS/SSL certificates.

Refer to StifleR Server and StifleR Dashboard for installation instructions.

Note: Ensure that the StifleR Dashboard can be accessed from the DeployR server, and you can successfully authenticate using Windows credentials. If this works from a remote computer but results in an authentication loop from the DeployR server, this could be an issue with a Windows LSA loopback setting. See https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/accessing-server-locally-with-fqdn-cname-alias-denied for more information. This is a common issue when using a CNAME alias for accessing the server, but can occur in other scenarios as well.

DeployR Server Requirements

DeployR should typically be installed on the same server as StifleR, and requires additional components to be installed and configured.

Database

DeployR 1.3+ supports MS SQL and SQLite. SQLite is part of the OS and does not require any special setup. Community Version defaults to SQLite. For Enterprise, after DeployR is installed, select SQLite from the Config Editor as your database option.

SQLite: When choosing SQLite, the database will be auto created in the DeployR Content Folder. If you move the DeployR Content folder, you will need to manually copy/move the database file DeployR.db to the new location.

MS SQL: Supported version of Microsoft SQL Server (Express edition or higher)

Used for:

Metadata storage
Deployment progress tracking

Windows features

BranchCache (optional Windows feature)

.NET Components

For DeployR versions earlier than 1.2, you must install the .NET 8.0 runtime components instead, available form download from Microsoft

The latest .NET 10.0 components, available for download from Microsoft

NET Runtime 10.0.9
.NET Desktop Runtime 10.0.9
ASP.NET Core Runtime 10.0.9

PowerShell

PowerShell 7.6.3 for full compatibility.

Windows ADK

The Microsoft Assessment & Deployment Toolkit (ADK) for Windows 11

Supported: ADK version 10.1.26100.9457 (September 2026)
Not supported: ADK version 10.1.28000.1 due to issues with driver integration.

Certificates

TLS/SSL certificates are required for secure communication

Service Account

By default, DeployR runs under the LocalSystem account . A custom service account can be used if required

Optional: Linux Deployment Support

For Linux bare metal deployments:

Windows Subsystem for Linux (WSL) is required
- The server must support:
  - Hardware-assisted virtualization
  - Or nested virtualization (for virtual machines)

Automation Scripts

Scripts to automatically install and configure prerequisites are available on GitHub:

2Pint-DeployR/Installs/Pre-Reqs/readme.md at main · 2pintsoftware/2Pint-DeployRGitHub

Last updated 9 days ago