Hello Everyone
This is my setup:
1) I have a AD DS, DNS and DHCP set up in my envorioment on Windows Server 2016
2) I have MDT and WDS set up on another Windows Server 2016
3) I have Controllers (custom-made Mini Computers with boot order set to Prio 1 = PXE Boot, Prio 2 = Harddisk) that need to be staged with Windows 10 Enterprise LTSC 2019 and some custom Software.
What I did:
I configured everything in MDT for a ZeroTouch Deployment. Task Sequence and everything. Also set up WDS Server to deploy the Image from MDT on to all requesting clients without pressing F12.
I tested it with a virtual Machine in the same network.
This does work perfectly. Since the VM is empty, it will automatically try to PXE boot. No boot loop. It installs perfectly.
Now when I plug in the Controller to the network it starts the boot from PXE without having to press anything. So far so good.
But with the first reboot during the MDT installation, it loads the Image again from the WDS and starts everything again. Boot Loop
I have done a lot of research. I have found some things regarding NetbootMachineFilePath property in Active Directory.
But that means that I have to prestage the Controller, right?
What I need is, that you can just plug the Controller to the switch and let it do its thing. Without having to configure something in advance.
I read something about WDS being able to overwrite the BootProgram when ResetBootProgram parameter is set to DWORD Value 0000001. Which I have.
So that It would need an F12 press on the second time the Controller tries to boot, which would just time out and send it to the Boot Priority 2 --> Hard Disk.
I can't get this to work though. What Am I doing wrong?
Thanks for all suggestions <3
Greetings from Switzerland