LogoLogo
  • Welcome
  • StifleR
  • 2PXE Server
  • iPXE WS
  • OSD Toolkit
  • DeployR
  • Introduction
    • Your DeployR guide
  • SETUP
    • Prerequisites
    • Installation
    • Securing
      • Entra ID authentication
      • Passcode authentication
      • Certificate authentication
      • Anonymous authentication
      • Other security settings
  • Generate Windows PE Boot Images
  • Generate Linux Boot Images
  • Configuring PXE booting
    • Using 2PXE
    • Using 2PXE with iPXE Anywhere Web Service
    • Using WDS or third-party PXE servers
  • Microsoft Graph API access
  • Getting Started
    • Creating a Content Item
      • Applications
      • Driver packs
      • Operating system
    • Creating a Task Sequence
    • Performing a Bare Metal Deployment
  • Starting a task sequence in an existing OS
  • Running a task sequence from Intune
  • Reference
    • Step Definitions
      • Apply ChromeOS Flex
      • Apply IGEL image
      • Apply operating system
      • Apply operating system from cloud
      • Capture image
      • Configure operating system
      • Enable Administrator account
      • Enable BranchCache
      • Format disk
      • Inject driver pack
      • Inject drivers
      • Inject drivers from cloud
      • Install application
      • Install multiple applications
      • Install updates
      • Offline domain join
      • Prepare for capture
      • Prepare operating system
      • Reboot
      • Run command line
      • Run PowerShell script
      • Run task sequence
      • Set variable
    • Task Sequence Templates
      • Windows bare metal
      • Windows bare metal from cloud
      • Windows build and capture
      • Autopilot from cloud
      • Autopilot pre-provisioning
      • ChromeOS Flex
      • IGEL 12
  • PowerShell Modules
  • Task Sequence Variables
Powered by GitBook
On this page
  1. SETUP

Prerequisites

PreviousYour DeployR guideNextInstallation

Last updated 25 days ago

LogoLogo

About

  • Let's connect
  • Engineering team
  • Our story
  • Blog
  • Events
  • Youtube

Products

  • Product overview
  • RecoveR
  • DeployR
  • OSD Toolkit
  • iPXE Anywhere
  • StifleR
  • CacheR
  • MOM
  • RemoteR

Support

  • Resources
  • Knowledge base
  • 2Pint Software support
  • FAQs

Pricing

  • Private sector
  • Public sector
  • Services

© Copyright 2025 2Pint Software | All rights reserved

CtrlK

To use DeployR, the following components are required.

  • StifleR Server 2.14 and StifleR Dashboard 2.14. See the StifleR Server and StifleR Dashboard 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:

      • .NET Runtime 8.0.17

      • .NET Desktop Runtime 8.0.17

      • ASP.NET Core Runtime 8.0.17

    • The latest PowerShell 7.4 release, available for download from Microsoft

    • The Microsoft Assessment & Deployment Toolkit (ADK) for Windows 11 (latest release is recommended)

    • 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.

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.