I’m using WinPE 10.0.10075. That’s the latest as of yet, correct? Thanks MIke
From: <[email protected]<mailto:[email protected]>> on behalf of Michael Niehaus <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Sunday, July 26, 2015 at 1:11 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [MDT-OSD] MDT 2013 Update - Can Only Connect Using FQDN? There is another variable in place here: The version of Windows PE that is being used. With the Windows 8.1 version of Windows PE, NetBIOS/WINS name resolution and connections work just fine. But I have seen reports of issues with the Windows 10 version of Windows PE. Oddly enough, I haven’t experienced those issues myself. But I have seen comments suggesting that they are resolved in the final version of Windows PE 10. Thanks, -Michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Saturday, July 25, 2015 9:57 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] MDT 2013 Update - Can Only Connect Using FQDN? Both shares on are on the same server. Everything from ipconfig matches up on both of my test build machines. The only difference is that the one booting the MDT 2013 U1 boot ISO can only connect if using the full DNS name of the server. It isn’t name resolution though. I can open a command prompt and successfully ping the server name by itself. It’s the mapping of the connection that fails unless it uses the full DNS name. On the test machine using the original MDT 2013 ISO it can connect using only the server name. It has to have something to do with the NET USE command in the WinPE 10 environment. It cannot map to any server by simply using the netbios name. I can ping them, but NET USE will only work if I feed it a full DNS name for the server. Mike From: <[email protected]<mailto:[email protected]>> on behalf of Keith Garner <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Sunday, July 26, 2015 at 12:49 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [MDT-OSD] MDT 2013 Update - Can Only Connect Using FQDN? Sounds like WINS/DNS issues. Is wins running on both servers? Run ipconfig /all and compare both outputs. Additionally check your DNS server to see what entries it has for your server. MDT isn’t really doing anything special here, simply using the underlying OS capabilities. F8 and the command prompt are your friends in this case. :) From:[email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Saturday, July 25, 2015 9:35 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] MDT 2013 Update - Can Only Connect Using FQDN? I’m finding that using MDT 2013 Update 1 will only work if my deployment share is mapped using the FQDN, while on MDT 2013 just the server name is sufficient. Anyone else seeing this? I have a server that has 2 shares on it. One if our original MDT 2013 share. The second is a new MDT share set up for testing MDT 2013 U1. The original MDT 2013 share is managed using a VM with MDT 2013 and ADK 8.1-U1. The new MDT 2013 U1 share is managed using a VM with MDT 2013 U1 and ADK 10. I boot a machine using the original MDT 2013 ISO and I am able to authenticate without a problem. I boot a machine using the new MDT 2013 U1 ISO and I am unable to authenticate. I get the error that the network path is not found. I can open a command prompt and ping the server name successfully. When I try to manually map a drive to the MDT 2013 U1 share using NET USE it will fail, again “server/path not found” if I attempt using \\server\MDTShare<file://server/MDTShare>. But, if I use \\server.demo.com\MDTShare<file://server.demo.com/MDTShare> it works. Now, as soon as I send this I’m bound to find the answer. That’s just the way my luck is. Thanks Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCSE, MCTS, MCITP, MCSA, MS [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] [Blog<http://thesystemsmonkey.wordpress.com/>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
