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. But, if I use \\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
