angrycomputingteacher Posted February 14, 2018 Posted February 14, 2018 I've spent the morning trying to get MDT to work again. I've even rebuilt my deployment share but I'm still having the same issue. Every time I get an error saying 'The network path was not found'. I'm wondering whether it's just this machine having issues. The network is part of the reason I'm rebuilding it, the wireless card won't turn on and it's not picking up group policies(name resolution policy issues). I'm PXE booting, but I get the same when running LiteTouch from within Windows. MDT is the latest version and the OS I'm trying to install is Windows 10 1703 x64. Help would be very much appreciated
FishCustard Posted February 14, 2018 Posted February 14, 2018 Test a different machine, see what that does.
angrycomputingteacher Posted February 14, 2018 Author Posted February 14, 2018 Test a different machine, see what that does. I've just run it on a VM. I still get errors.
computer_expert Posted February 14, 2018 Posted February 14, 2018 Does the account you use for accessing the MDT DS have access in both share permissions & NTFS permissions? if you hit either ctrl+f8, ctrl+f10 or f8 (I can't remember which one) when you get the error screen, this should open cmd.exe. Can you ping any servers?
angrycomputingteacher Posted February 14, 2018 Author Posted February 14, 2018 Both are set to everyone permissions so it should work. Yes, I can ping my domain controller and all other computers using the cmd.
snagrat Posted February 14, 2018 Posted February 14, 2018 It’s failing on the Core (normal) step. What is this step doing in the TS?
snagrat Posted February 14, 2018 Posted February 14, 2018 Also have you got ADK 1703 installed on the server?
free780 Posted February 15, 2018 Posted February 15, 2018 Are you using Fqdn? If your DHCP options don't add a connection DNS domain you need to do this. Try F8 check ipconfig for a IP and ping your server.
angrycomputingteacher Posted February 15, 2018 Author Posted February 15, 2018 I've got it working. When I set my static IP and DNS server, I also set my DNS Domain and I also recreated the task sequence. One of those seemed to fix it Finally can rebuild this machine.
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