I'm in the process of building a Windows 7 SOE to be deployed using SCCM 2007 R2. The advertisement originally had the Distribution Points tab setting as "Download content locally when needed by running task sequence". When the advertisement uses this setting it works. I was watching a video on technet recently about Windows 7 deployment and it said I should use "Access content directly from a distribution point when needed by the running task sequence" as the task sequence wipes the hard disk (which it does). However when the advertisement uses this setting, when the system restarts after performing the "Setup Windows and ConfigMgr" step, it shows the "BOOTMGR is missing" message. The issue happens on my physical test machine (a Dell Latitude E5500) but not on my virtual test machine (running under ESX 4.1). Is there anything I can do to resolve this or should I not be using the setting that causes the error? Thanks.

Hello - May be, you can go through below blog to ensure that you are doing correct and not mising anything like boot image configuration? http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/ Anoop C Nair

Hello - May be, you can go through below blog to ensure that you are doing correct and not mising anything like boot image configuration? http://www.windows-noob.com/forums/index.php?/topic/667-deploy-windows-7/ Anoop C Nair Hi, I've tried duplicating the settings more closely in that link and it still happens on the physical test machine. The documentation in the link is slightly different to what I'm doing as it's a capture and deploy while I"m just doing a direct deploy from the normal Windows 7 wim.

Hello - Have you looked into SMSTS.log? Did you try to enable the F8 troubleshooting option? You can go through the below link for more details? http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/Anoop C Nair

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I tried looking at the logs and couldn't see anything obvious at the time. For the time being I'm sticking with the setting that works.