So I updated my MDT 2013 inplace with U1 to test Windows 10

everything seems to go through fine until I boot the PXE
didn't connect for the longest time and then it said the credentials are bad.  Odd because it was just working.  tried to map the drive, no luck.

Created a new deployment share just for Win10 and left the customsettings and bootstrap.ini default so I would get the prompt for username, password, domain.  I've had this share running for sometime and when I try a net use I get System error 53 has occurred. The network path was not found.

Even when I try to map a physical machine, I get the same.. All of this is running in VMware Workstation.  I can ping the machines and get successful pings

• Edited by IKnowSomeMDT Friday, May 08, 2015 2:26 AM

I installed the ADK before MDT ( I only learned about MDT U 1 from researching why my Win 10 images were still failing)

it is getting an IP address.. I also created a new VM for this so I'm stumped.. It's like there is something wrong with the DNS, I'll roll it back tonight and go from there.

Just looked at your blog.. Looks to be some good info so I'll look at that tonight if I can.

• Edited by IKnowSomeMDT Friday, May 08, 2015 6:20 PM

Tks for the compliments! :)

Well...try the rollback than and send some news please.

started from scratch,
installed Windows 10 adk
installed MDT 2013 update 1
pulled over just windows 10
booted, still can't connect
removed update 1 and windows 10 ADK
installed windows 8 adk and MDT 2013
no issues - same credentials

update to this
On my physical machine I can open up windows explorer and go to the deploymentshare w/o issue and without using any credentials at all
using either versions of ADK or MDT
removed WDK and 2013
reinstalled WKD 10 and 2013 u1
fails - with me inputting the credentials and adding them to bootstrap.ini


checked the LiteTouch.log file >
Error - no credentials were returned from LTICredentials.hta, so no connection is possible.
Unable to connect
Connection OK.  Possible cause: invalid credentials and then

in other logs Wizard/BDD - keep seeing the network path was not found

In ZTI Gather - it says Unable to determine Windows SKU while in Windows PE ?
at the end says ZTIGather processed successful

noticed that NETBIOS is disabled on the ADK10 2013 Update 1 but enabled in ADK8 & 2013.  I'm beginning that is the key.

• Edited by IKnowSomeMDT Sunday, May 10, 2015 5:03 AM

Well, that really can be the key...
On the config where you get the error, can you open up a command prompt and try to do something like a net use to see the result?