Hi JonLambert, thank you for the reply. I've disabled the devices in the BIOS, and specified the FQDN in the Bootstrap.ini, and no change. Any other thoughts?
Main Topics
Browse All TopicsI upgraded MDT to 2010 Beta 2, with no problems. I deployed an image that I've been using, and it worked fine, but during the final login into the OS (Vista), at the end of deployment, I receive "A connection to the deployment share (\\Server\Distribution$) could not be made. The deployment will not proceed."
To fix this (assuming this is a network timeout issue), I did the common fix with the modified startnet.cmd, put it in E:\ExtraFiles\Windows\Syst
The startnet.cmd contains the following:
wpeutil InitializeNetwork
ping localhost
wpeinit
Unfortunately, same issue exists even with that modified startnet.cmd. I'm unable to complete deployment because the computer continuously logs back in, bypassing the logon prompt, and continues to throw the "the deployment will not proceed" message out there.
Any idea of what I could try? I know it's not a network issue, as by the time the message even comes up, all of the Windows Updates have downloaded, I'm able to browse network resources and the internet, and in fact all devices show up fine in Device Manager. Any ideas? Thanks guys!
BTW, I did the upgrade, and even added new Windows Updates to MDT, got rid of tons of drivers and only imported the drivers for all the Intel Desktop motherboards we have...no HP laptops or anything else. The ISO is only 260megs. I had had issues before with putting too many drivers in, causing a timeout in Windows PE, resulting in a failure. I wanted to keep it slim this time around...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: JonLambertPosted on 2009-08-18 at 00:17:02ID: 25120685
This can happen because of some of the network connection validation script code in MDT 2010 seems to have some issues if you have devices that are DHCP capable, but don't have an IP address. Try disabling any Wireless/Bluetooth/Firewir e devices in the BIOS and retry the build.
Another thing to try is specifying the FQDN of the Deployment Server in all locations in you specifiy the Deployment Server (such as BootStrap.ini), I've seen this cause issues with MDT 2010 on some networks.