> 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/setup-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 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 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 * 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](/stifler/setup/prerequisites.md#firewall-configuration) configuration and TLS/SSL certificates. Refer to [StifleR Server](/stifler/setup/installation/stifler-server-installation.md) and [StifleR Dashboard](/stifler/setup/installation/stifler-dashboard-installation.md) for installation instructions. {% hint style="info" %} 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 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 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 form [download from Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) {% endhint %} {% hint style="info" %} The latest .NET 10.0 components, available for [download from Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) {% endhint %} * DeployR 1.0 - 1.1 * NET Runtime 8.0.X * .NET Desktop Runtime 8.0.X * ASP.NET Core Runtime 8.0.X * DeployR 1.2 + * NET Runtime 10.0.8 * .NET Desktop Runtime 10.0.8 * ASP.NET Core Runtime 10.0.8 ### PowerShell {% hint style="info" %} The latest PowerShell 7.6 release, available for [download from Microsoft](https://github.com/PowerShell/PowerShell/releases) Do NOT use the PowerShell from the Windows Store or Winget. {% endhint %} PowerShell 7.6.2 for full compatibility. ### Windows ADK The Microsoft Assessment & Deployment Toolkit (ADK) for Windows 11 * Recommend 24H2 Dec Release: 10.1.26100.2454 * 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.2pintsoftware.com/deployr/1.2/setup-deployr-enterprise/prerequisites.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.