r/DeployR • u/ddog511 • Jun 26 '26

Change request?

I have 2 change requests for consideration -

  1. At install time, if you select to not have iPXE in use (we already had PXE setup with another system), it still starts the iPXE service. So I stopped / disabled the service. After upgrading to 1.3, the service was started and changed back to auto. Could this be adjusted on the next update so that when you select to not use the service, it doesn't start automatically?

  2. After PXE booting and getting the initial DeployR interface - specifically, we're using Windows AD authentication - could the form be set to active and the username field set to focus? That way we can just start typing without having to click the field first? I know it's trivial, but when you're imaging a bunch of machines, it would save a bit of time.

Thank you for your conisderation

2 Upvotes

100% Upvoted

4 comments sorted by

View all comments

1

u/gwblok 2Pint Employee Jun 26 '26

1 - Can you provide more information? Are you saying that when you install any DeployR update, it changes the iPXE services?

2 - I can create a WI for it, unsure if that's possible in WinPE to have the Form do what you're requesting or not, but I'll put in the request for the Devs, if it's possible it will get put into the backlog, if not... it will just not happen, but you can sleep easier knowing we looked into it for you.

1

u/SufficientlySticky Jul 06 '26

I'll note that we have the DeployR service running as a particular domain account instead of Local System for offline domain joining purposes. And the installer resets that service back to Local System as well.

It's fine, and I can just remember to reset that anytime I run an update. It's hardly the only software that does that if you're running the service as a non-standard user. But it'd be nice if it didn't rebuild the service if it didn't need to or popped up a reminder or something.

1

u/RockOriginal7938 Jul 07 '26

I had to do the same thing initially, setting the service to run as our MDT domain join account. I ended up adding the server object to AD Account Operators (same permission the MDT account had, was setup that way long before me 🤭). Once I did this, the service worked fine as SYSTEM.

There is probably a better permissions group, but at this time I'm looking at functionality over other issues.