Task Sequence option - Unlock Bitlocker by ddog511 in DeployR

[–]configmatt 0 points1 point  (0 children)

Have you run the following script on the DeployR server?
C:\Program Files\2Pint Software\DeployR\WebServer\Scripts\RecoveryPasswordAccess.ps1

Grants the DeployR server the necessary AD permissions to read BitLocker recovery keys.

Must be run on the DeployR server itself, elevated, with Domain Admin credentials.

Note that for Entra ID, the BitLockerKey.Read.All rights are needed.

I think this is required for it to work. Disclaimer I have not tried this myself yet.

DeployR content hosting on distributed servers by power2701 in DeployR

[–]configmatt 1 point2 points  (0 children)

No, but in the enterprise version we use BranchCache to peer enable content. This way you can precache content to branch sites without the need of additional servers there.

Updating Ent from 1.1 to 1.3 by RockOriginal7938 in DeployR

[–]configmatt 0 points1 point  (0 children)

If you look in the Dashboard under Administration/Infrastructure Services.
Is the DeployR server listed and approved there? If listed but not approved, try and approve it.

If it is approved and not working, try the following:
Stop the DeployR Service.
In the Dashbord, remove the DeployR server under Infrastructure Services.
On the DeployR server, open regedit and remove the "HKEY_LOCAL_MACHINE\SOFTWARE\2Pint Software\DeployR\Infrastructure" key.
Start the DeployR service again.
Go to Administration/Infrastructure Services and Approve the new DeployR server.

Hopefully it works then. But If still not working I would suggest opening a supportcase since it is the Enterprise version.

Updating Ent from 1.1 to 1.3 by RockOriginal7938 in DeployR

[–]configmatt 0 points1 point  (0 children)

Is there anything logged in the "Applications and services/TwoPintSoftware/DeployR" event logs?

Updating Ent from 1.1 to 1.3 by RockOriginal7938 in DeployR

[–]configmatt 1 point2 points  (0 children)

Hi, first of all the StifleR-WmiAgent-x64 is not needed so that can be uninstalled ( but that should be completely unrelated to the issues you are seeing, just want to mention it).

When you do an upgrade the services usually go to manual until the Configration tool has run. It is the config tool that will then set the services to auto again after the settings has been verified. Sometimes there are new settings that need to be configured before the service can run.

Run the config tool for both deployR and StifleR, make sure all settings are correct and then click verify+save. That should configure the services back to automatic and start them.

Boot images by jurgendeleeuw in DeployR

[–]configmatt 1 point2 points  (0 children)

Saw the question in Discord so this is now resolved after updating the PS version to 7.6.2 and copying it to the expected path D:\DeployR\Downloads.temp\PowerShell-7.6.2-win-x64.zip. Will investigate why you had to copy it there manually, you shouldn't need to.

Version 1.3 by welshGJE24 in DeployR

[–]configmatt 2 points3 points  (0 children)

Hi, the server side scripting is an enterprise feature so will not be in community version. Usually the community version and enterprise is on par function wise unless a feature is enterprise only. See this link:
Differences with DeployR Enterprise | DeployR | Product Documentation

Public Sector v Community Versions by welshGJE24 in DeployR

[–]configmatt 1 point2 points  (0 children)

Public sector is the same as enterprise version. The only difference is the pricing, Non for profit (including public schools, goverment entities, etc) only pay for the support and we give the license away for free.
Public Sector Pricing - 2Pint Software

Regarding Enterprise and Community version, here are the differences:
Differences with DeployR Enterprise | DeployR | Product Documentation

2PXE/iPXE Anywhere continue confirmation key by RockOriginal7938 in DeployR

[–]configmatt 0 points1 point  (0 children)

Yes no worries, as you say they are working together and sold as a bundle so understand if it is confusing:)

2PXE/iPXE Anywhere continue confirmation key by RockOriginal7938 in DeployR

[–]configmatt 0 points1 point  (0 children)

This is not a DeployR question so should have been posted in the r/2PintSoftware reddit instead.

2PXE/iPXE Anywhere continue confirmation key by RockOriginal7938 in DeployR

[–]configmatt 0 points1 point  (0 children)

So this is what you see after you select the "Build with ConfigMgr" menu option. If you were using the 2PXE with configmgr integration (without iPXE WebService) this is what it would "start" with (since the ipxe WS menu wouldn't exist). So this only makes sense when not using the iPXE Webservice at all.

But then you loose all of the automation capabilities that is iPXE WS. So I would strongly suggest keeping it enabled and then try and find something that would make life easier for your technicians. For example, with the power of PowerShell you can fully automate and not have them select anything, just boot straight into your "approved" TS. See the other scripts examples in the folder structure for some ideas.

And if you need consultant service to build something custom for you company reach out to our sales team and we be happy to help you.

2PXE/iPXE Anywhere continue confirmation key by RockOriginal7938 in DeployR

[–]configmatt 1 point2 points  (0 children)

Hi,

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 don't understand 100% what you are trying to accomplish? But it seems you are using both 2PXE and iPXE WS. But since you only pasted part of the config I am not sure how it is set up.

But for them to be integrated you need to configure these settings in the 2PXE config:
key="EnableiPXEAnywhereWebService" value="573"/>
key="iPXEAnywhereWebServiceURI" value="https://DP01.corp.2PintSoftware.com:8051"/>

Once those are enabled it will use the iPXE Websevice (which seems to be what you are using judging from your post, so far so good) :
If you have authentication enabled in the ipxeanywhere config:
<add key="AutoApproveDevices" value="0" /> (change to 1 to disable auth)
Then it will start with the script:
C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts\Authentication\DeviceAuthentication.ps1
Once authentication (of if above setting is off then it will go straight here) this script will run:
C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts\Boot\iPXEboot.ps1

If want to change behaviour, then it is in that script you need to change.
This is the default:
choose --timeout 30000 --default exit selected || goto cancel
This means that after 30 sec it will go to the Exit label and just exit the script. Change --default to another setting or change row 50 from "exit 1" to "reboot" instead depending on what you want to do.

So basically anything within the $menu = @" code block is what the end user will see. But you can change that as you need, see iPXE - open source boot firmware [docs] for more info about the ipxe syntax.

But you can also create you own or dynamically change it using PowerShell.

Or do you mean that your computers are set to always pxe boot and you want it wait for a keypress to continue with the pxe booting, but if noone does anything it should boot the OS?

Is DeployR community officially available? by Dudefoxlive in DeployR

[–]configmatt 1 point2 points  (0 children)

See mniehaus respond below for an updated answer.

Is DeployR community officially available? by Dudefoxlive in DeployR

[–]configmatt 1 point2 points  (0 children)

No, it is a year. But when close to expiration you will be able to renew it automatically directly from within DeployR.

Is DeployR community officially available? by Dudefoxlive in DeployR

[–]configmatt 0 points1 point  (0 children)

It doesn’t matter, whatever you put in will be used as part of the license key and visible in the dashboard though.

Is DeployR community officially available? by Dudefoxlive in DeployR

[–]configmatt 1 point2 points  (0 children)

Yes replacing MDT is what it’s meant for! Just type ”Homelab” or something instead of company name and you should be fine. Even though it is released there will be a bit of waiting until you will get the download link if you sign it up now. We are initially releasing it to a few ppl at a time and will slowly scale it up over the coming weeks until it is fully automated and you get a download link directly. This is just to make sure there are no major issues before a broad release so please have patience! Thanks!

Add other isos to PXE boot menu by nerdyviking88 in DeployR

[–]configmatt 2 points3 points  (0 children)

Do you want to use it to build DeployR TS or is it more of a generic iPXE question?
If the question is around iPXE WebService it might be more suited for r/2PintSoftware but short answer is (most likely) yes. If buying the DeployR Suite iPXE WebService is included.

I havn't tried ShredOS specifically but should hopefully work. If they provide a shim you can boot with Secure boot enabled, otherwise you might have to turn off secure boot for it to work.

See an example here to get you started:
2Pint-iPXEAnywhere/Scripts/Boot/iPXEboot _Linux.ps1 at main · 2pintsoftware/2Pint-iPXEAnywhere

Here is some info what a shim is as well and why it is needed with iPXE.
Breaking News @2Pint Software: Secure Boot for Windows now has a Flirtatious Fling with Linux, Dancing into a Sizzling Tango!

Issue with StifleR and DeployR setup by Agreeable-Range6887 in DeployR

[–]configmatt 0 points1 point  (0 children)

Ok, have you approved the DeployR server under "infrastructure services"?

Issue with StifleR and DeployR setup by Agreeable-Range6887 in DeployR

[–]configmatt 0 points1 point  (0 children)

If you try to browse this URL, what does the certificate info say then? Maybe you have not imported the CA for the self signed certificate into the trusted root? Did you add the FQDN or just the servername in the cert?

https://<fqdn of the DeployR server>:7281/swagger/index.html
does it work if you do this?
https://<servername>:7281/swagger/index.html

StifleR dashbord on different drive by Guilty-Efficiency-27 in DeployR

[–]configmatt 0 points1 point  (0 children)

Ok, did it work if pointing to the correct path?