abillybob Posted March 14, 2019 Posted March 14, 2019 (edited) Hi All Got a bit of a strange issue and I know I've got it to work before so I'm getting a bit confused. I've disabled Secure Boot, Enabled CSM and Legacy Boot. But every time I PXE boot to MDT and select LiteTouch (x64) I get the following error message [ MDT has all the drivers imported also so what on earth is going on? If anyone could help I'd really appreciate it, I don't want to loose any more hair than I already am!! Thanks in advance Edited March 14, 2019 by witch
DalekSec Posted March 14, 2019 Posted March 14, 2019 You should prob crop your picture to remove the phone numbers and other details..... 2
abillybob Posted March 14, 2019 Author Posted March 14, 2019 You should prob crop your picture to remove the phone numbers and other details..... Thank you done that
Boredguy Posted March 14, 2019 Posted March 14, 2019 MDT might have the drivers, but did you regenerate the boot media to include the PXE drivers for it?
sted Posted March 14, 2019 Posted March 14, 2019 have you tried another boot image (just the standard boot.wim off a win10/server20xx dvd) as a test. i had a laptop yesterday (lenovo as it happens) that would bsd on bootup to mdt but would work fine with other images. in the end i created a new bare bones deployment share and it booted fine (driver conflict i think)
abillybob Posted March 14, 2019 Author Posted March 14, 2019 Well I've realised it's happening on every computer that tries to PXE boot now. I'm just now regenerating the boot image and I'll see if that helps!! Fingers crossed :|
DJ-1701 Posted March 14, 2019 Posted March 14, 2019 Just don't forget to replace the old one with the regenerated one in WDS.
Katy Posted March 14, 2019 Posted March 14, 2019 One of the results I found on google with that error code said it started working again after restarting the WDS server, have you tried that?
abillybob Posted March 14, 2019 Author Posted March 14, 2019 Tried all the above guys but nothing unfortunately still the same. I can't work it out. I've regenerated the boot images and made sure to re-import the new one's created but still nothing. Tried using a Windows 10 disc and imported the boot image into WDS directly from there but still gives the same error when trying to boot from that and restarted the whole server but still after it's restarted having the same issue. I really don't understand this, I've tried every boot image also the x86 and the Capture Image and all fail every time. It was working literally a week ago perfectly fine and nothings changed as far as I'm aware.
sted Posted March 14, 2019 Posted March 14, 2019 is your wds server also a dhcp server? there are some options to tick/untick depending on if it is or not (properties of the server in wds and under the dhcp tab)
abillybob Posted March 14, 2019 Author Posted March 14, 2019 is your wds server also a dhcp server? there are some options to tick/untick depending on if it is or not (properties of the server in wds and under the dhcp tab) Nah not a DHCP server, I've some how fixed it, the only thing I changed was enable variable window extension tick box under TFTP and now it seems ok.. Strange. Thank you everybody though
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now