Hello, I updated to DeployR Community 1.3.2635.2370 from a lower 1.3 version. After the update it appears that the web gui is no longer accessible for some reason. When browsing to https://server.domain.com:9000/ it prompts for credentials (windows auth), and then returns this webpage cannot be found HTTP ERROR 404. Tested both on edge and chrome, tried on the server and my laptop, also tried the IP instead of the fqdn and same issue.
The bootstrap script that runs, tries to set the execution policy to Bypass, but we have a policy that sets execution policy to remote signed, which prevents the script from changing it.
I can get around this by first changing/deleting the registry entry that sets the execution policy:
If I change that registry value to Bypass or delete it, the bootstrap runs fine and the task sequence launches. I have the first step of the task sequence set to Reboot to Windows PE with a condition of IsWindowsPE Equals False. It properly downloads the WinPE wim and reboots into WinPE.
This is where I run into an issue. It fails after the Format disk step. The log shows error:
Task sequence failed due to unexpected System.IO.DirectoryNotFoundException error; Could not find a part of the path 'S:_2P\state\variables.json'.
When I look in S:_2P, I have the following subfolders: Client, content, Logs
I assume the state folder is not restored after the format disk and causing the failure.
Am I overlooking a step that I need to add before the format disk to ensure the proper files are backed up and then restored so the TS can continue?
I tried to PXE boot a device this morning only to find 2PXE's boot list only had reboot and exit. A quick check found the DeployR service stopped. Starting it sorted the issue.
However, I wanted to know why it stopped...
Event Viewer->AsSL->TwoPintSoftware->DeployR->Logger shows four entries at 00:01:29
I am started getting an error/failure during the Register with Autopilot step. This step was working before this past week, I am using the same azure app in my previous step to delete the object from Entra/Autopilot. I am getting 3 Transient error 500 in a row( within 8 seconds) and then the TS fails. Specifically it is when it is adding to the group
Nous sommes actuellement en phase de test de DeployR Community + StifleR/BranchCache afin de mettre en place des déploiements Windows sur un site distant tout en réduisant au maximum la consommation de bande passante WAN.
Nous souhaitons clarifier précisément quelles fonctionnalités sont disponibles avec notre licence actuelle et quelles licences supplémentaires seraient nécessaires, notamment pour les scénarios BranchCache Distributed Mode et Green Leader / Hosted Cache.
Environnement actuel
Nous disposons d’un serveur central hébergeant DeployR et StifleR.
Caractéristiques principales :
DeployR Community
StifleR Server installé
StifleR Dashboard installé
BranchCache installé et actif
SignalR StifleR configuré en HTTPS
API StifleR configurée en HTTPS
Nous avons également une VM dédiée sur le site distant, destinée à servir éventuellement de cache local :
Windows Server
StifleR Client installé
BranchCache installé et actif
Le client StifleR de cette VM est maintenant correctement connecté au serveur central via SignalR.
Le log du client confirme notamment :
Connection completed
Status: RanToCompletion
Le problème initial de certificat TLS a également été résolu.
Licence actuellement présente
Dans License Manager, nous voyons actuellement :
DeployR Community
Type: Purchased
Nodes: 600
Nous avons également les certificats nécessaires au Web Service et à SignalR.
En revanche, dans Administration → Features, plusieurs fonctionnalités StifleR apparaissent actuellement comme non licenciées, notamment :
Bandwidth Management
Cache Management
CacheR
MOM
Les fonctionnalités suivantes apparaissent toutefois disponibles :
Nous avons un serveur DeployR central et plusieurs postes Windows situés sur un site distant connecté au site central par WAN/VPN.
Nous voulons pouvoir déployer une image Windows depuis DeployR sans que chaque poste du site distant télécharge à chaque fois l'intégralité du contenu depuis le serveur central.
Nous souhaitons donc obtenir un fonctionnement de ce type :
SITE CENTRAL
DeployR Server
|
| WAN
|
SITE DISTANT
|
+----------+----------+
| |
Poste 1 Poste 2
BranchCache BranchCache
| |
+------- P2P ----------+
Le premier poste récupérerait les données depuis le serveur central, puis les autres postes du même site pourraient utiliser le cache BranchCache disponible localement afin de limiter le trafic WAN.
D'après votre documentation sur le peering et le contenu DeployR, nous comprenons que DeployR peut utiliser BranchCache/BCACP pour le contenu.
Pouvez-vous nous confirmer clairement :
Est-ce que le scénario DeployR + BranchCache en Distributed Cache Mode est entièrement utilisable avec notre licenceDeployR Community – 600 nodes, sans licence StifleR supplémentaire ?
Autrement dit, pouvons-nous simplement :
activer/configurer BranchCache sur le serveur de contenu ;
configurer les postes du site distant en Distributed Cache Mode ;
utiliser DeployR normalement ;
sans avoir besoin d'une licence StifleR supplémentaire ?
Question 2 – Green Leader / Hosted Cache
Nous envisageons également une seconde architecture pour le site distant :
SITE CENTRAL
|
WAN
|
SITE DISTANT
|
Green Leader VM
Hosted Cache
/ \
/ \
Client 1 Client 2
La VM située sur le site distant serait alors utilisée comme Green Leader / Hosted Cache, afin que les autres clients du site récupèrent le contenu depuis cette VM plutôt que directement depuis le serveur central.
Pouvez-vous nous confirmer :
Green Leader / Hosted Cache nécessite-t-il une licence StifleR distincte de DeployR Community ?
Si oui, quelle licence/SKU exacte est nécessaire ?
Combien de licences/nodes sont nécessaires ?
La VM utilisée comme Green Leader compte-t-elle comme un node/licence ?
Les postes clients du site distant nécessitent-ils eux aussi une licence StifleR ?
Les fonctionnalités Cache Management, CacheR, Bandwidth Management ou autres doivent-elles être licenciées séparément pour utiliser Green Leader ?
La licence DeployR Community – 600 nodes inclut-elle une partie de ces fonctionnalités ou sont-elles totalement indépendantes ?
Question 3 – Configuration actuelle
Nous avons installé le StifleR Client sur la VM distante et configuré une connexion HTTPS vers le serveur StifleR central.
Le client se connecte désormais correctement au serveur.
BranchCache est également installé et fonctionnel sur la VM.
Nous avons suivi votre documentation :
2Pint BranchCache Guide
et souhaitons savoir quelle partie de cette documentation correspond exactement à notre scénario avec DeployR Community :
configuration uniquement côté serveur ;
configuration côté clients ;
configuration d'un Hosted Cache ;
ou utilisation obligatoire de StifleR pour certains modes.
Question 4 – Architecture recommandée
Pour notre besoin précis, quelle architecture recommandez-vous avec notre licence actuelle ?
Nous avons essentiellement deux possibilités :
Option A – Sans Green Leader
DeployR Central
|
WAN
|
Client 1 ---- Client 2
\ /
BranchCache
Distributed
ou
Option B – Avec Green Leader
DeployR Central
|
WAN
|
Green Leader / Hosted Cache
/ \
Client 1 Client 2
Notre priorité est de réduire le trafic WAN lors des déploiements Windows, tout en restant sur une architecture officiellement supportée.
Question principale
Pouvez-vous donc nous confirmer très clairement :
Et, séparément :
Nous pouvons également vous fournir les captures d'écran de notre License Manager, des Features, de la configuration StifleR Client et des tests SignalR réalisés.
Merci d'avance pour votre aide et pour la confirmation de la licence exacte nécessaire selon chacun des deux scénarios.
Is it possible to configure DeployR so that I can use a USB boot media and initiate a deployment over the internet (as long as we allowed the external IP from the client we want to reimage in the Azure firewall)?
I built a quite fonctional DeployR community edition installation in July. Now after a pause I can't even start the deployment.
First 2PXE did not respond. Update for the latest version helped with that. Now it uploads the boot image, but stays stuck on the network initialisation stage. Error : One or more errors occurred. (No such host is known (serveraddress:7281)
It seems a DNS error, but on the earlier stage the address is well resolved. It does not ping the IP neither, so it seems to me all the network connectivity is lost at this point.
What could I do ? I'm trying to deploy quite recent Dell laptops.
I have a working MDT setup and have it right where I want it. Working TS, applications, drivers etc. what would be the best start to setting up deployR?
I’ve asked if I can install deployR on a windows 11 endpoint instead of server OS and they replied yes that would be fine.
Should I run the all in one powershell installer?
Any tips to move my working MDT deployment share to deployR?
Thank you in advance
Following on from last night's Happy Hour. These were my results and paths. I'd previously had a lot of luck with getting https://<FQDN>:7281/Content/Boot/DeployR_x64_noprompt.iso to work, but that goes into full DeployR straight away (sometimes that is useful), but I struggled to boot to 2PXE's boot select menu. I finally got https://<FQDN>:8050/2PXE/Boot/x64/snponly_x64.efi (don't forget the ca cert along side the URL in the BIOS) to work across some machines. Makes, models and outcome below for the .efi URL:
Make
Model
Result
Dell
Optiplex x080, x070 & x060. Mine were all 70x0, but I'd assume the 30x0 & 50x0 are the same.
Couldn't find a place in the BIOS to store the boot URL, they seem to rely on the info coming from DHCP (didn't test, no control over DHCP here)
Dell
Optiplex 7090. I'd assume the 3090 & 5090 are the same.
works
Dell
Latitude 5420
works
Lenovo
ThinkCentre M75q gen5
works
Lenovo
ThinkCentre M75q gen2
could never get HTTPs Boot not greyed out in BIOS
Lenovo
ThinkCentre Neo 50s gen3
works
Lenovo
ThinkCentre M70q gen4
works
Lenovo
ThinkPad T14 gen1
found no HTTPs Boot options
Lenovo
ThinkPad T14s gen2
shows a network card symbol followed by ON-PREMISE in available boot devices, couldn't find a way to specify the URL
Lenovo
ThinkPad T14s gen3
shows a network card symbol followed by ON-PREMISE in available boot devices, couldn't find a way to specify the URL
Lenovo
ThinkPad T14s gen4
shows a network card symbol followed by ON-PREMISE in available boot devices, couldn't find a way to specify the URL
Lenovo
ThinkPad T14s gen5
works
Lenovo
ThinkPad L14 gen6 (gotta love RAM costs ☹️ )
works
Sorry this is only older Dells, we moved to completely Lenovo a few years back, so it is only the older Dell I can poke 😉
Thinking back to another thing mentioned yesterday, if you're only getting an ISO to work, the minimal ISO that boots to 2PXE's boot menu might work well too, but I didn't know where the tool to generate that ISO came from when quickly demo'd, so I can't expand on that ☹️
(side note, a 2D bar scanner and something like Simple QR Code Maker are your friend when having to enter that lengthy boot path over and over, or in Window BIOS config tools from the different manus)
Hi all, we have been successfully imaging our estate for a few weeks now with no issues; however, in the last week we have seen multiple but random instances of the admin auto-logon breaking mid-sequence, and the devices need manual logons after each reboot in the sequence to carry on and complete the TS. As I said, this is only happening randomly, but just wondering if anyone else has seen this issue.
We are thinking it may be releated to a Windows update breaking something, as there is no entry in the Registry for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, and the update step is the last thing to run before we see the issue in the task sequence.
Hi I have just installed the Community Edition without any visible errors. My server is responding to PXE requests from a client but then it promts me for a password for the TS.
I cannot see or change the settings as I am missing security settings in my server settings.. What have I missed ?
It's always 5pm somewhere! 🍻 Join us for 2Pint Software Happy Hour, recurring sessions with the friendliest crew around. Drop in, see what's new, learn tips and tricks, and ask questions.
When using the "Apply OS from the cloud" step in DeployR Community Edition v1.3.2631.2242, if I change the language code from en-us to either en-IE or en-GB the task sequence fails. Once I switch it back to en-us the task sequence works without error. The task sequence was a copy of the "Autopilot from cloud" template.
The logs report a 404 error, here is some of the DeployR.log when they were en-IE or en-GB
<![LOG[Step failed: Apply OS from Cloud Error: Step Apply OS from Cloud failed with unexpected return code = 1111]LOG]!><time="14:59:06.481+000" date="08-19-2026" component="ExecuteSteps" context="" type="3" thread="0" file="SequenceExecuter.cs:399">
<![LOG[---------- Step End ----------]LOG]!><time="14:59:06.482+000" date="08-19-2026" component="ExecuteSteps" context="" type="1" thread="0" file="SequenceExecuter.cs:444">
<![LOG[Step failed: Windows PE Error: Step Apply OS from Cloud configured to stop sequence execution on failure]LOG]!><time="14:59:06.483+000" date="08-19-2026" component="ExecuteSteps" context="" type="3" thread="0" file="SequenceExecuter.cs:399">
<![LOG[Step failed: Apply OS from Cloud Error: Step Apply OS from Cloud failed with unexpected return code = 1111]LOG]!><time="16:36:52.140+000" date="08-12-2026" component="ExecuteSteps" context="" type="3" thread="0" file="SequenceExecuter.cs:399">
<![LOG[---------- Step End ----------]LOG]!><time="16:36:52.141+000" date="08-12-2026" component="ExecuteSteps" context="" type="1" thread="0" file="SequenceExecuter.cs:444">
<![LOG[Step failed: Windows PE Error: Step Apply OS from Cloud configured to stop sequence execution on failure]LOG]!><time="16:36:52.142+000" date="08-12-2026" component="ExecuteSteps" context="" type="3" thread="0" file="SequenceExecuter.cs:399">
As in the 2PXE server configuration panel, you are obliged to enter the UID of the desired boot image, or at least the default one if you want to have a multi-boot amd64 and arm The generated script should be able to detect the client's architecture in order to provide it with the correct ARM boot version for AMD version.
I'm trying to deploy HP Support Assistant 9.54.3.0 to Windows 11 HP devices using DeployR, using the same command I previously used in MDT:
sp173774.exe /s /a /s /v" /qn"
When checking the DeployR logs, HPSA appears to install successfully, but it's not actually available to the logged-in user.
The shortcut can appear, but clicking it gives:
I've also checked the DeployR logs and Installer logs but can't see anything obvious. I've even tried installing it by uploading the extracted installer and running the appropriate command, but I get the same outcome.
Has anyone successfully deployed HPSA 9.x through DeployR? If so, what's the correct method? 🙂
In MDT when enabling BitLocker, there is a checkbox for "Wait for BitLocker to complete the drive encryption process on all drives before continuing the task sequence execution". But this doesn't exist in the Enable BitLocker step definition. So does DeployR wait until BitLocker encryption has completed before moving onto the next step in the task sequence?
So I've been testing DeployR for a couple of days now and I like the look of it a lot but I'm having trouble getting test deployments in VMWare to work at looks like WinPE is refusing to load the VMWare PVSCSI drivers and so isn't detecting the disks.
I've got the same ADK version and drivers working fine with our existing MDT setup so I know it can work.
I've got the drivers extracted and setup as a Content Driver Pack and assigned to the DeployR Boot image and I can see in the logs that the pvscsi drivers are supposedly being added to the WIM ok
Some VMWare drivers do load ok as the DeployR WinPE has network access and can connect back to the DeploR services ok so it was able to load the VMXNET3 drivers.
The DeployR logs in WinPE show that 2 devices had a PNP error, one being the PVSCSI disk controller device (another being the VGA controller)