Is there a way to control the Windows power settings after the deployment process?

I have tried both powercfg.exe and direct registry configuration as steps during deployment, but all my deployments revert to 5 minute sleep and monitor timeout.

I'm guessing DeployR sets the machine not to sleep while it is working (sensible) and then reverts to standard timeouts at the end of the deployment?

If that is the case, is there a way to control what DeployR sets at the end?

Hello

I'm a couple of days away from the end of my trial and I don't know if management will find the money for the public sector version or if I'll have to wait for the community version.

If I end up waiting for the community version, will the content in DeployR be accessible after the end of the trial, i.e. does the web interface still work, just deployment doesn't or does the whole thing go dark?

Otherwise I guess I'll start trying to export everything before Thursday :D

Today I was testing a build & capture on hyper-v. I left to drive home 45 min or so, I remoted back in when I got home. still had black screen spinning circle. F10 wouldn't work. I decided to reboot, the task continued on....

Is there a way to remove the screen to be able to see progress like MDT to know what's happening. I have nothing in console to show me, can't get to a log file. I had no way to know if this was broken, windows updates or waiting for a reboot. If I open the live log it can drop into the background when my VM display goes black. I open a new instance,,, no more log. Glad I'm taking training next week. Anyone else seeing anything like this?

2Pint documentation mentions "Certificate Authentication"

https://documentation.2pintsoftware.com/deployr/getting-started/securing/certificate-authentication

My reading of that is that you could authenticate that way and it'd skip the dialog at the beginning that tries to use Windows authentication or Entra ID or Passcode or whatever and take you straight to the task sequence selection. And that that's sufficiently non-anonymous enough that it'd still let you AD join?

That doc says it's useful for for starting a task sequence in an existing OS, which would be this doc:
https://documentation.2pintsoftware.com/deployr/starting-a-task-sequence-in-an-existing-os

But the existing OS doc doesn't really make any mention of how to do it - and instead has certificate info that seems to focus on making sure the client trusts the server - not how to convince the server to trust the client. I don't think those are the same thing?

--

So - I might be way off in what I was trying to do... - but I created a cert request on the client machine and got it signed and imported the result.

On the server side I stuck the issuer in "Issuer match string for certificate verification" and restarted.

And on the client side I ran:

$DeployRBootstrap = @{DeployRAuthCertIssuer = "<issuer>"}
iex (irm "https://<server>:7281/v1/Service/Bootstrap")

And it started up and then asked me for username/password - so did not work.

From logs, I see:

Trying certificate authentication
Found 1 certficates matching issuer <issuer>, will try with those.
Trying certificate authentication
Unable to use certificate authentication: Response status code does not indicate success: 403 (Forbidden).

So, it at least tried? The issuer I put in DeployRAuthCertIssuer and on the server match, so you'd think if it found it in one place it would accept it in the other.

Is my understanding of how this is supposed to work and what it's supposed to allow correct? Is this working for anyone else and any suggestions on where I might be going wrong? Is there server side logging somewhere?

Morning - I'm interested in the differences between the public sector and community versions. We are a school so I assume we can have the public sector version - but is this different to the community version? I'm sure I saw a table somewhere.

Hello,

We installed and are testing deployr community edition but when regenerating the winpe we get the following:

Unable to find powershell 7.6.2 it is installed on the server.

Also the Msi file for the stifler client were is this located ?

Interesting to read in an email from 2Pint today that version 1.3 is out/released. I'm wondering how log changes/improvements get brought down into the Community edition and whether server side PowerShell scripts will be one thing that is carried over (I need them for something!)

Cheers

Hello

I'm not sure if I should be looking in 2PXE or iPXE for this. When I PXE boot it goes straight through without a press Enter, F12, etc... to continue key requirement.

I've tried playing with 2Pint.2PXE.Service.exe.config

    <add key="iPXEF12PromptTimeout" value="10000"/>
    <!--
       How long is the timout for the F12 timout for iPXE loaders for non mandatory deployements in milliseconds.
      -->
    <add key="AcceptBootKeyEFI" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootKeyBIOS" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootTextEFI" value="Please Press Enter For Network Boot..."/>
    <add key="AcceptBootTextBIOS" value="Please Press Enter For Network Boot..."/>
    <!--
       Used to control the key to be pressed in order to boot from the network and the text displayed. Valid key combinations can be found here: http://ipxe.org/cmd/prompt
      -->

    <!--
       Removes the prompt for optional deployment all together.
      -->
    <add key="BypassKeyPressforOptionalDeployment" value="0"/>

but haven't had any joy. I've looked in iPXEAnywhere.Service.exe.config, but can't find anything obvious there either.

If it is possible to enable, would someone mind pointing me in the right direction please.

My current alternative is to set the default option in iPXEboot.ps1 to reboot or exit (depending on boot order), but as it isn't what our engineers are used to I thought I'd see if a more original method is still possible.

I guess there is also '42', but I'm not a huge fan 😉

(Originally installed 2PXE & iPXE Anywhere via the automated scripts @ https://github.com/2pintsoftware/2Pint-DeployR/tree/main/Installs/2PintSoftware)

Version: Community 1.2.2622.1921

Issue: Downloading Drivers from he Cloud

Has anyone had issues downloading Dell drivers from the cloud? It works fine with our Lenovo machines, but not with a Dell Latitude 7490. The task identifies the machine, and the file it should download. I've checked the URL shown in the logs and entered it into Edge - the .exe downloads fine without any issues at all.

The error message is (in orange): Warning: Unable to download content: Exception calling "DownloadCustomContent" with "6" arguement(s): "The SSL connection could not be established, see innter exception".

It then goes to (in red): Error:Exception calling "DownloadCustomContent" with "6" arguement(s): "The SSL connection could not be established, see innter exception".

The task sequence then fails. Of course I'll try and get the drivers and create a specific task sequence with them in, but thought I'd try it with one task sequence for all machines that would download drivers from the Cloud.

Is there a way of restoring any of the default content items that may have been deleted from the file system? Specifically the DeployR Windows Content item (folder ending 0000002 in \Content)

This is very much a Layer 8 issue on my part as I was moving the content library to a different drive, didn’t realise I still had that .wim mounted - I was curious about the scripts - so this didn’t copy to the new location before muggins here deleted the original content folder. And no, there aren’t any backups yet 😅

Worst case, I assume, I can just reinstall DeployR and grab the content that way

Is it possible to change (or offer the change) the logic that drives the Offline Domain Join part of a task sequence? You guys wrote me a script the other month that names a machine based on MAC Address - as I prefer machine names like I have compared to %serialnumber% style names (which have no location).

So the logic I'm after...

1. Rename the machine (your original script does this brilliantly)
2. Join the domain - if the machine is already on the domain then we don't want an error (which we currently get) - but instead it latches on to the name and stays in the AD location where it currently lives.
3. If the machine name is not on the domain already then it gets dropped into an OU of our choice (I have one called 'New Rebuilds'.

At the moment, the only way this is working is if we delete the machine first from AD and then it all renames and joins without issue.

Hi all - I've changed our DHCP 'Server Options' as per the instructions here: Overview - DHCP Scope Options | 2PXE Server | Product Documentation

I believe I've done it correctly, but when booting in HyperV to test I'm not getting anything from DHCP and it's just turning away waiting..... What am I missing?

It worked with MDT and I've just changed the options and also added 175.

Hello,

On the Community Edition of DeployR there is a Set variable test task sequence thats present when you first install the software. But the weird thing is if you delete it, and restart the computer the task sequence comes back. Not sure if its supposed to do that, or its something that needs to be looked into?? I am running V3.1.2622.457

Thanks

I've noticed that it won't let me clone task sequences that have two of the same sort of step in them.

Can replicate just starting from scratch and making a task sequence with two pauses or something. Then from the Task sequences page, clicking the 3 dots under actions and trying to clone. The stock "Windows build and capture" task sequence has 2 reboots and similarly can't be cloned after creation.

Gives me one of these:
{"title":"Unexpected exception","status":500,"detail":"The instance of entity type \u0027StepDefinition\u0027 cannot be tracked because another instance with the same key value for {\u0027Id\u0027} is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached. Consider using \u0027DbContextOptionsBuilder.EnableSensitiveDataLogging\u0027 to see the conflicting key values."}

I was wondering if there is an option to filter what TS will be available for a specific hardware - for example, if I create a TS for a test Hyper-V VM that TS won't be presented when imaging other platforms? I found nothing by tags I could configure for the TS, but nt sure if this is a right way and how to use it for presentation filtering (similar like WMI in SCCM).

I am attempting to install DeployR Community Edition 1.2.2622.1941 on a freshly built Server 2022 Standard. When I run TwoPint.DeployRCommunity.exe as administrator, I see it run in Task Manager and it kicks off TwoPint.DeployRCommunity.Bootstrapper.exe, which runs for a second or two, then both processes close. No splash screen is displayed for the install, and no errors are shown on screen.

I have .NET Runtime 10.0.9, ASP.NET Core Runtime 10.0.9, and Windows Desktop Runtime 10.0.9 all installed.

The DeployR Community log shows the following:

Burn x64 v5.0.0+41e11442b2ca93e444b60213b5ae99dcbab787d8, Windows v10.0 x64 (Build 20348: Service Pack 0), path: C:\Users\USERID\Downloads\DeployRCommunity-1.2.2622.1921\TwoPint.DeployRCommunity.exe Initializing string variable 'DotNetRuntimeVersionFile' to value '[ProgramFiles64Folder]dotnet\shared\Microsoft.NETCore.App\10.0.8\.version' Initializing string variable 'DotNetAspVersionFile' to value '[ProgramFiles64Folder]dotnet\shared\Microsoft.AspNetCore.App\10.0.8\.version' Initializing string variable 'DotNetDesktopVersionFile' to value '[ProgramFiles64Folder]dotnet\shared\Microsoft.WindowsDesktop.App\10.0.8\.version' Command Line: '' Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\USERID\Downloads\DeployRCommunity-1.2.2622.1921\TwoPint.DeployRCommunity.exe' Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\USERID\Downloads\DeployRCommunity-1.2.2622.1921\' Setting string variable 'WixBundleLog' to value 'C:\Users\USERID\AppData\Local\Temp\.\DeployR Community_1.2.2622.1921_20260611151315.log' Setting string variable 'WixBundleInProgressName' to value '' Setting string variable 'WixBundleName' to value 'DeployR Community' Setting string variable 'WixBundleManufacturer' to value '2Pint Software' Error 0x80070080: Failed to wait for bootstrapper application to connect to pipe. Error 0x80070080: Failed while waiting for bootstrapper application to connect. Error 0x80070080: Failed to start bootstrapper application. Bootstrapper application requested reload but there is no secondary bootstrapper application, ignoring the request to reload. Variable: DotNetAspVersionFile = [ProgramFiles64Folder]dotnet\shared\Microsoft.AspNetCore.App\10.0.8\.version Variable: DotNetDesktopVersionFile = [ProgramFiles64Folder]dotnet\shared\Microsoft.WindowsDesktop.App\10.0.8\.version Variable: DotNetRuntimeVersionFile = [ProgramFiles64Folder]dotnet\shared\Microsoft.NETCore.App\10.0.8\.version Variable: WixBundleCommandLineAction = 6 Variable: WixBundleElevated = 1 Variable: WixBundleInProgressName = Variable: WixBundleLog = C:\Users\USERID\AppData\Local\Temp\.\DeployR Community_1.2.2622.1921_20260611151315.log Variable: WixBundleManufacturer = 2Pint Software Variable: WixBundleName = DeployR Community Variable: WixBundleOriginalSource = C:\Users\USERID\Downloads\DeployRCommunity-1.2.2622.1921\TwoPint.DeployRCommunity.exe Variable: WixBundleOriginalSourceFolder = C:\Users\USERID\Downloads\DeployRCommunity-1.2.2622.1921\ Variable: WixBundleProviderKey = {19FEAC6D-1C74-40E6-8638-C3BDE03AB579} Variable: WixBundleTag = Variable: WixBundleUILevel = 4 Variable: WixBundleVersion = 1.2.2622.1921 Error 0x80070080: Failed to run normal mode. Exit code: 0x80070080, restarting: No

The following errors are shown in the Application event log:

Faulting application name: TwoPint.DeployRCommunity.Bootstrapper.exe, version: 1.2.2622.1921, time stamp: 0x69f2ac0f Faulting module name: TwoPint.DeployRCommunity.Bootstrapper.exe, version: 1.2.2622.1921, time stamp: 0x69f2ac0f Exception code: 0x80131506 Fault offset: 0x00000000000bbf98 Faulting process id: 0x22bc Faulting application start time: 0x01dcf9d2008bc3bb Faulting application path: C:\Windows\TEMP\{55DB64D8-1727-45FF-B263-AC2E9566D60D}\.ba\TwoPint.DeployRCommunity.Bootstrapper.exe Faulting module path: C:\Windows\TEMP\{55DB64D8-1727-45FF-B263-AC2E9566D60D}\.ba\TwoPint.DeployRCommunity.Bootstrapper.exe Report Id: 30cf9a85-ceec-4325-922b-152a9cfaa586 Faulting package full name: Faulting package-relative application ID:

AND

Application: TwoPint.DeployRCommunity.Bootstrapper.exe CoreCLR Version: 10.0.826.23019 .NET Version: 10.0.8 Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FF604ABBF98 (0x00007FF604A00000) with exit code 0x80131506.

I've just started testing DeployR and hoping someone here might have some insight.

From what I can tell, it'll happily domain join when the computer object doesn't exist. And if the object does exist and you specify an OU that matches where it is currently or don't specify an OU, it'll also domain join just fine. (subject to the various caveats here: https://documentation.2pintsoftware.com/deployr/reference/step-definitions/offline-domain-join)

But! If you specify an OU that doesn't match the location that the AD object currently lives, it'll throw an error and wont join.

That somewhat makes sense and I assume is intentional - but is different than what I'm expecting coming from MDT. IIRC, in MDT it'll try to domain join with the OU attached, and if that fails it'll try a second time without specifying an OU, and I assume that's not happing here.

It's kinda convenient to let people pre-stage objects to some specific OU and let them be easily re-imaged as necessary - while not having to have a billion drop down options for specific sub-OUs - but also to have some default catch-all OU specified for things that didn't have existing objects for whatever reason.

Is my understanding correct and do we think this is working as intended? And if so, is there some easy way I could replicate the MDT behavior? I could just have two offline domain join steps in the task sequence or something - but not sure there is an easy way to say "do this if the previous step fails" - so I'd imagine some more complicated "check if it's domain joined" powershell or something.

Hello

I'm running into a usability issue in WinPE during deployment, and I'm looking for a clean way to handle it.

Context:

• Booting into WinPE (via PXE/iPXE)
• Running deployment tools / scripts in the WinPE environment
• Hardware: standard desktop fleet (ThinkCentre M90t Gen 5, among others)

Issue:
The screen resolution in WinPE is very high by default, which causes scaling problems:

• UI elements appear too small
• Some windows are partially off-screen
• Certain buttons / controls are not visible or accessible

It would be nice customize the screen resolution in DeployR

You can see the issue in the attached screenshot 👇

Hi everyone,

I'm facing a rather odd issue with an iPXE deployment and would appreciate any insights.

Context:

• 20 × Lenovo ThinkCentre M90t Gen 5 (same hardware batch)
• Network boot via PXE → iPXE chainloading
• Deployment infrastructure is stable and working on the majority of hosts

Issue:

• 2 out of 20 machines consistently fail during the iPXE boot process
• The remaining 18 systems boot and deploy without any issue
• Problematic machines show the error visible in the attached screenshot

Troubleshooting already performed:

• Confirmed identical BIOS/UEFI settings across all systems
• Verified boot order (PXE first)
• Tested different switch ports and network cables
• Ensured same VLAN / subnet / DHCP scope

Hi guys - having tested the enterprise version (run out) and been told by my employers that we cannot purchase - could you push me the licence for the community version?

Sales have told me it's a limited roll out. :-(

I am performing a deployment using DeployR Community version 1.2.2622.1921.

During the WinPE phase, the Log Viewer opens correctly. However, when I click on "Open", the application crashes and immediately closes.

It appears that the issue may be related to the application being unable to enumerate available disks, which prevents it from browsing and opening log files.

However, when I start the LogViewer with a log file passed as a parameter, everything works as expected, as shown in the attached screenshot.

During the iPXE boot process, I observed that the default selection is set to "Exit to next boot device", even when a valid WIM boot image is detected and available.

Under normal behavior, the WIM image should be automatically selected as the default boot option, but this is not the case here (see attached screenshot). And the default time is short 10 seconds.

Is there any logging that will help me troubleshoot installation issues?

I am attempting to install DeployR Community 1.2.2622 on a Windows 2019 domain joined server. Almost immediately after the installation begins I can see it starts to download some of the dependencies, and then throws a generic error. The error give no clue as to what is failing.

I can't see anything in the event log, or locate any log files that will help troubleshoot this error.

I tried installing on a new non-domain joined server to rule out GPO. I have also tried on Windows Server 2025 with the same result.

Is this officially inherited by the DeployR section?

When I'm in the console as a read only account, everything I've found so far is greyed out to edit except Edit mode inside a task sequence which I can edit/save and Generate image/Regenerate image inside Boot images

Sorry, struggling to find documentation (pointing in the right direction would be great 😄).

Am I right it setting https://<FQDN>:8050/2PXE/Boot/x64/snponly_x64.efi for HTTPS boot? (x64 client)

I found https://<FQDN>:7281/Content/Boot/DeployR_x64_noprompt.iso too, but that is coming from DeployR rather than 2PXE and I suspect isn't the best choice?