# Prerequisites

To use DeployR, the following components are required.

* StifleR Server 3.0 and StifleR Dashboard 3.0.  See the [StifleR Server](https://documentation.2pintsoftware.com/stifler/2.14/setup/production-installation/stifler-server-installation) and [StifleR Dashboard](https://documentation.2pintsoftware.com/stifler/2.14/setup/production-installation/stifler-dashboard-installation) documentation for the installation requirements and procedures. 
  * Note that StifleR supports these OS versions: Windows Server 2019 or above; Windows 11; Windows 10 LTSC 2019 or later
  * StifleR requires .NET Framework 4.8, IIS, and has specific firewall and certificate requirements
* DeployR 1.0 itself (which should normally be installed on the same server as StifleR) requires:
  * A supported version of Microsoft SQL Server, Express edition or higher.  This database is used to store DeployR metadata and progress tracking information.
  * The BranchCache optional component
  * The latest .NET 8.0 components, available for [download from Microsoft](https://dotnet.microsoft.com/en-us/download/dotnet/8.0): 
    * .NET Runtime 8.0.21
    * .NET Desktop Runtime 8.0.21
    * ASP.NET Core Runtime 8.0.21
  * The latest PowerShell 7.4 release, available for [download from Microsoft](https://aka.ms/powershell-release?tag=lts)
    * Do not use PowerShell 7.5.X or higher, it needs to be 7.4.X
  * The Microsoft Assessment & Deployment Toolkit (ADK) for Windows 11 
    * Recommend 24H2 Dec Release: 10.1.26100.2454
    * We've experienced issues with 10.1.28000.1 with driver integration.
  * Certificates for secure communication (TLS/SSL)
  * For Linux bare metal deployment support, the Windows Subsystem for Linux (WSL) is needed, so the server needs to either support hardware-assisted virtualization, or in the case of a virtual machine, nested virtualization

Note that the DeployR service will normally execute using the LocalSystem account.  A separate service account can be used if desired.

{% 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 <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.
{% endhint %}

Automated Scripts to setup using defaults for all of the pre-reqs can be found on our github:\
<https://github.com/2pintsoftware/2Pint-DeployR/blob/main/Installs/Pre-Reqs/readme.md>