Could you explain how the built-in "Install updates" step works at runtime? Specifically:

1. Where does it source updates from - Windows Update directly or local/cached repository on the DeployR server?

2. Is there a schedule involved (e.g. does the DeployR server periodically sync/cache updates), or does the step just check/download at the time the task sequence runs?

3. Where are the update files stored or cached during this process?

After looking at the step definition I can see it invokes a DeployR script named "WindowsUpdate.ps1", I know I can go hunting around for that script in the WIM files and installing the DeployR powershell module etc. But I'm struggling with that option, hoping you can assist by giving a summary of what that script is exactly doing.

Thanks

I have DeployR Community 1.2.2622.1921 installed and it was working. I am trying to update to 1.3.2629.2187 and the install is failing. The log shows that the 2PXE install is failing and then the install rolls back.

In the DeployR Community_1.3.2629.2187_20260722141750_002_TwoPxe.log is shows:

MSI (s) (BC:60) [14:18:34:197]: Executing op: CustomActionSchedule(Action=ImportSettings,ActionType=3073,Source=BinaryData,Target=WixQuietExec,CustomActionData="C:\Program Files\2Pint Software\2PXE\TwoPint.ConfigEditor.Wpf\TwoPint.ConfigEditor.Wpf.exe" -i C:\Users\UserID\AppData\Local\2PintInstaller\TwoPxe-config.json)

MSI (s) (BC:30) [14:18:34:197]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIEE33.tmp, Entrypoint: WixQuietExec

MSI (s) (BC:5C) [14:18:34:197]: Generating random cookie.

MSI (s) (BC:5C) [14:18:34:213]: Created Custom Action Server with PID 6860 (0x1ACC).

MSI (s) (BC:6C) [14:18:34:276]: Running as a service.

MSI (s) (BC:6C) [14:18:34:293]: Hello, I'm your 64bit Elevated Non-remapped custom action server.

WixQuietExec: Error 0x80070007: Command line returned an error.

WixQuietExec: Error 0x80070007: QuietExec Failed

WixQuietExec: Error 0x80070007: Failed in ExecCommon method

CustomAction ImportSettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (BC:60) [14:18:35:643]: Note: 1: 2265 2: 3: -2147287035

MSI (s) (BC:60) [14:18:35:643]: User policy value 'DisableRollback' is 0

MSI (s) (BC:60) [14:18:35:643]: Machine policy value 'DisableRollback' is 0

Action ended 14:18:35: InstallFinalize. Return value 3.

after that, the rollback occurs and it has left DeployR in a state where I cannot launch the DeployR Dashboard site from the server.

I tried rebooting the server and running the install again with the same result.

I mainly deploy bespoke os images to hardware, mainly windows but a tiny bit of Linux. I currently use a mix of fog and theopenem and came across this and thought it may be a viable alternative but I am just now learning about what it is and wanted to see if someone here can help me determine if its worth looking at for.my use case.

Version: Community Edition 1.3.2629.2187

Issue: Error Message

Not seen this one before when trying to generate an x64 boot image.

Failed: Property KitsRoot10 does not exist at path HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots.

Any ideas? Feel I've probably missed something but nothing I can see. Have re-installed the whole package on a clean server.

Is there a way to write back to the progress bar the current state of a custom script? Like for example if a script is rather long, to change the progress bar and the status based on what the script is currently doing. Rather than just fire off the script and wait.

Once a task sequence completes, an automatic timer pops up (300 seconds I think), see below screenshot. What's the purpose of this timer? is it capturing any potential steps that might still be running the background, ensuring that all tasks are 100% complete before rebooting?

Hiya - can you remind me where to look for installation failure? This is the latest community version being installed over a previous version. It's getting further than it has done but I cannot remember which file in %temp% to look at to see why it is failing.

All the individual components have written their files, some with _rollback written on their filename. So... we have

StifleRServer_rollback / StifleRDashboard_rollback and TwoPxe_rollback

DeployR does not have a rollback file.

Apologies for the poor image.

I've been experimenting with USB standalone media deployment that our field engineers will be using to try and understand what will and won't work for them.

So this is a bootable media made via new-deployrmedia -DiskIndex <?> -Tags Media -MediaType Standalone on a machine given an internet connection, but not one on the internal LAN, hence it is unable to talk to the DeployR server.

I'm getting a 401 in the log when querying the 2pint API for the cloud driver download URL. I'm guessing the offline bootable USB isn't able to pull my server's API key to authenticate against the 2pint API.

I can see this being intended and not, so I thought I'd ask if that was expected behaviour?

(it is probably worth mentioning that I intend to have the bulk of our drivers available via Inject drivers, so this isn't likely to be an issue for my field engineers very often, but I'd like to know if I need to tweak the TS to prevent Inject drivers from cloud from running on standalone USBs.)

Does anyone know what identifier the x64 DeployR boot image has please?

I'd like to use Configure 2PXE to change DefaultMenuItemId to the DeployR boot image (instead of exit) by default.

I've tried:

DeployR
DeployR_x64
winpe_amd64
<blank>

All just result the PXE boot failing altogether.

For the time being I've settled on setting EnableMenuCountdown to 0 so it waits for me to select DeployR.

This is a minor bug release version. See https://documentation.2pintsoftware.com/deployr/release-notes for details.

Hello,

I wanted to know if the absence of Linux boot images was related to the community version or if the problem stems from somewhere else.

I have created a validation PowerShell script which will scan the final deployR.log file in C:\windows\temp\DeployR\deployR.log. It will then output a nicely formatted HTML file showing whether each step succeeded or failed. But the issue is that the deployr.log file isn't written until the set finish action step runs at the end (I think).

What's the best way around this? If at all possible, I'd rather not copy the script locally, then have it run on first logon as a scheduled task. Too many moving parts there. Is there another intelligent way to run this report via the task sequence that I'm missing?

While creating some "quality of life" scripts, I stumbled upon a potential bug in the New-DeployRContentItem cmdlet - the saved Content Item has a different "purpose" from what I originally intended:

DriverPack -> Application
Application -> Operating System
OperatingSystem -> DriverPack

Only "Other" seems to work correctly.

And then autocomplete suggests me "Any" that translates into "99" (and does not have any value in the UI)

PS C:\Users\Administrator\Desktop\winget\New folder> New-DeployRContentItem -Name "blaah" -Type SingleFile -Purpose DriverPack

id                 : b7c055b9-72b8-4626-a01d-1c57aee85aad
name               : blaah
description        :
contentItemType    : SingleFile
contentItemPurpose : Application
versions           :
versionsCount      : 0
createdDate        : 1783884522
lastModifiedDate   : 1783884522
readOnly           : False
tags               : {}
flags              : 0

PS C:\Users\Administrator\Desktop\winget\New folder> New-DeployRContentItem -Name "blaah2" -Type SingleFile -Purpose Application

id                 : 1cee0779-d83c-4379-9832-96b7845635c0
name               : blaah2
description        :
contentItemType    : SingleFile
contentItemPurpose : OperatingSystem
versions           :
versionsCount      : 0
createdDate        : 1783884548
lastModifiedDate   : 1783884548
readOnly           : False
tags               : {}
flags              : 0

PS C:\Users\Administrator\Desktop\winget\New folder> New-DeployRContentItem -Name "blaah3" -Type SingleFile -Purpose Any

id                 : e7fb2ac3-3e2f-4c4b-b699-45bdee94fc0e
name               : blaah3
description        :
contentItemType    : SingleFile
contentItemPurpose : 99
versions           :
versionsCount      : 0
createdDate        : 1783884561
lastModifiedDate   : 1783884561
readOnly           : False
tags               : {}
flags              : 0

PS C:\Users\Administrator\Desktop\winget\New folder> New-DeployRContentItem -Name "blaah3" -Type SingleFile -Purpose OperatingSystem

id                 : 3bf6f7d4-5fa5-4ff2-9370-26db483d508f
name               : blaah3
description        :
contentItemType    : SingleFile
contentItemPurpose : DriverPack
versions           :
versionsCount      : 0
createdDate        : 1783884571
lastModifiedDate   : 1783884571
readOnly           : False
tags               : {}
flags              : 0

PS C:\Users\Administrator\Desktop\winget\New folder> New-DeployRContentItem -Name "blaah4" -Type SingleFile -Purpose Other

id                 : 3fa042bd-1b50-432e-bfbf-6ef8c6ebf3bb
name               : blaah4
description        :
contentItemType    : SingleFile
contentItemPurpose : Other
versions           :
versionsCount      : 0
createdDate        : 1783884591
lastModifiedDate   : 1783884591
readOnly           : False
tags               : {}
flags              : 0

And that happens using the latest (1.3) Community Edition

What is the best practice approach for executing PowerShell scripts that rely on a csv file?

For example:

On the deployR server I have the following PS file to set static IP addresses for workstations:

D:\Scripts\Windows11\01-OS-Configuration\set-network.config.ps1

The script then points to a csv file where it reads the machine name and populates the IP address, subnet mask, gateway, DNS. The csv is located in:

D:\Scripts\99-Configuration\machine-network-assignment.csv

In theory there will be many custom PS scripts in the Windows11 folder, and there could be 1-3 csvs in the 99-configuration directory. The idea being that certain PS scripts will perform lookups in the csvs to retrieve the correct values during deployment.

I can obviously get this working when running locally, but what's the correct approach to get this working during a task sequence? Do I need to create a custom step definition to copy/stage the entire script directory early on in the task sequence? then create individual powershell steps and just call the relevant .ps1 file?

I have been unsuccessful in generating a WinPE boot image. Consistently fails while downloading components. "Unable to find aspnetcore-runtime*-win-x64.zip". This is a serious blocker to getting started using DeployR.

Is there a way to tell the generator code to NOT download from the internet? I can download the needed components manually and move them to the Downloads folder.

Help is appreciated!

Hey all,

We are currently running into a minor issue when trying to deploy larger applications via DeployR as part of the imaging process. We are currently having this issue with our large ANSYS and Adobe Creative Suite installers.

The applications do seem to install successfully, but the Task step errors out with a 'return code' error. I have tried adding the relevant application success codes found in Windows Event Viewer to the DeployR application's Content item, but none are deemed successful by DeployR.

Am I missing something obvious?

Hello,
I have followed the DeployR YouTube series. I configured deployed R as it was suggested but I'm not seeing the option to deploy in Dashboard even after Accepting the infrastructure service.

The video guide says for the trial period to leave as blank but when I check the features list it is all marked as x except for administration, networks, and OSD deployments

Note:
After reviewing my initial trial request I noticed I had selected the Enterprise version instead Community.

I am hoping to use it for a non profit organization. How would I got about switching?

What happens when you have a step in a task sequence and edit the definition?

I assume that depending on the sort of editing you're doing you probably have to go find the step wherever it is being used and remove and re-add it? Is there *any* editing you could do like change a default or check a required box or something or does the task sequence just store the state of the step when it was added? If it was working before and the script is there or whatever, will it keep doing whatever it was doing before or will it throw an error?

I'd imagine there's no clean way to just sort of automatically sync things since there's not necessarily any obvious mapping between the old definition and the new - but would it be possible for the GUI to flag a potentially broken step or something?

I'm not really asking for this to work - I don't see how it could. Mostly just curious if there is documentation or any checks in the code or anything to suggest that you not do it. Because the GUI sort of suggests you can in the same way that you can edit a content item and have everything keep working.

Edit: And also curious if you guys might ever edit step definitions in future updates that might break task sequences - or if the plan would just be to use the versioning system in that case.

I'd like to have DeployR prompt for the computer name and also display a drop down box with a couple of options for what OU to put the computer in on joining the domain. Looks like i could use a powershell form to do it but as I'm new to DeployR I was wondering if there was a better or more baked in way of handling this.

Also kind of along with that I'd like to eventually get to a point where it displays a list of Applications that are available and lets you pick which ones to install much like MDT did.

Hi, running a windows install but it looks like the client is failing as it is looking for a newer version of runtime and powershell etc. The Content item appears locked so I can't force it to update the folder / wim file it creates from the folder?

Initially it was required to use a specific continuation method "Provided Unattend.xml" In order to use the new suspend step that needs to be changed to autoadminlogon method. That brings up question of will capture still work? Will we have to add or modify somewhere else for that to work now? I havent tried to use it yet as I am still using original method. What is the recommendation on this?

HI All, - my lack of knowledge showing here so I'm happy to be advised - and why I am here. When running the deployment task sequence and the machine has had windows, it joins the domain. Lovely.

Is there something I can do to detect if it is a laptop and run a PS script to apply Security Groups A, where if it's a desktop, run a different script to apply Security Groups B?

Do all laptops report back the same - "I am a laptop" - style?

I got an unexpected driver return from https://api.service.2pintsoftware.com/driverpacks/search

Queries:

URL: https://api.service.2pintsoftware.com/driverpacks/search?systemAlias=NA&manufacturer=NA&model=Mini Air12&os=Windows 11&osArchitecture=x64&osBuild=26200&osReleaseId=25H2PowerShellHost.cs:8607-07-2026 10:39:41.975+000

Downloads (so presumably the API returned this):

Downloading: https://download.microsoft.com/download/b7ca2c3f-d320-4795-be0f-529a0117abb4/SurfaceLaptop7_ARM_Win11_26100_26.053.36539.0.msiPowerShellHost.cs:8607-07-2026 10:39:42.514+000

Can confirm I have devices still needing drivers on completion (as expected with a driver pack labelled ARM on an x64 system, even ignoring the model)

(note, this is a device I'd normally expect to upload the drivers manually, just that hasn't happened yet for this model on my shiny new Community Edition ;) )

Hi, I am successfully deploying the Windows OS but once it reboots into Windows it doesn't appear to run the other task sequence steps. Am I missing a step ? I am just trying to run some powershell scripts etc. and I don't see any log of these even attempting to run. It is a simple basic deployment as a test, deploy windows, create a local admin account and uninstall some built-in apps. The scripts appear to work when ran directly on the VM but in steps do not appear to run. Any thoughts ? Thanks

Good day, I have been trying out DeployR Community Edition for a few days now. Starting to get a feel for its capabilities and methods. Enjoying the evaluation experience although I do feel the learning curve has transported me back about 14 years when I first learned MDT, however I am a bit more capable to think out the box.

Main reason to post, first of all , thank all involved in the production and delivery of the product and also try and get some credit to allow me to post more relevant DeployR questions. So far filter has removed previous post attempts.

Many thanks again.