> 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/deployr-enterprise/prerequisites.md). # 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 {% hint style="warning" %} This requirement applies even in workgroup environments {% endhint %} The server must have a valid FQDN DNS entry. * Example: deployr.company.local This FQDN is used for all service URLs and certificate bindings. ## Ports The following ports are inbound to the DeployR server, depending on the options you have installed. * 7281 TCP: DeployR for secure communications from the clients Additional port information is available in the documentation for the corresponding components you are using with DeployR: * [StifleR Firewall Ports Details Page](https://documentation.2pintsoftware.com/stifler/setup/prerequisites/firewall-ports) * [2PXE Detailed Docs](https://documentation.2pintsoftware.com/2pxe-server/planning/firewall-considerations) ## StifleR Components {% hint style="danger" %} You only need to install StifleR Server and StifleR Dashboard to operate DeployR. You do not need to install or configure the other StifleR components. For monitoring, you can optionally include the StifleR Client in your boot media. {% endhint %} * StifleR Server 3.1 (build .1006) * StifleR Dashboard 3.1 (build .1006) StifleR supports Windows Server 2019 or later, and requires .NET Framework 4.8 to be installed, along with appropriate [firewall](/stifler/3.0/setup/prerequisites.md#firewall-configuration) configuration and TLS/SSL certificates. Refer to [StifleR Server](/stifler/3.0/setup/installation/stifler-server-installation.md) and [StifleR Dashboard](/stifler/3.0/setup/installation/stifler-dashboard-installation.md) for installation instructions. {% hint style="info" %} Ensure that the StifleR Dashboard is accessible from the DeployR server and that you can authenticate successfully 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 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. {% endhint %} ## 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 supports Windows Server 2022 or later. DeployR 1.3 and later supports both Microsoft SQL Server and SQLite. SQLite is included with the operating system and does not require separate installation. Community uses SQLite by default. For Enterprise, SQLite can be selected after installation in the Configuration Editor. **SQLite storage:** The database is created automatically in the DeployR Content folder. If you move the DeployR Content folder, manually move the `DeployR.db` database file to the new location. 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 {% hint style="warning" %} For DeployR versions earlier than 1.2, you must install the .NET 8.0 runtime components instead, available from [Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) {% endhint %} {% hint style="info" %} The latest .NET 10.0 components are available from [Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) {% endhint %} * .NET Runtime 10.0.14 * .NET Desktop Runtime 10.0.14 * ASP.NET Core Runtime 10.0.14 ### PowerShell PowerShell 7.6.9 for full compatibility. DeployR 1.4 uses BCMon 3.5.2644.155 as its download engine. BCMon is included as a DeployR component and does not need to be installed separately. If you use 2PXE for PXE booting, use 2PXE build .623. ### Windows ADK The Microsoft Assessment & Deployment Toolkit (ADK) for Windows 11 * Recommended: [Windows 11 ADK September 2026 release](https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install#download-the-adk-101261009457-september-2026), version 10.1.26100.9457 * This replaces version 10.1.26100.2454 (December 2024); re-download the ADK installer and reinstall to use the September 2026 release. * ADK version 10.1.28000.1 is not recommended 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: {% embed url="" %} --- # 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/deployr-enterprise/prerequisites.md?ask=&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.