Add a new ‘Run Command Line’ Step in this Group, name it ‘Set DeliveryOptimization to Bypass’ and specify the following Command Line: REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization /v DODownloadMode /t REG_DWORD /d 100Īdd another ‘Run Command Line’ Step just below the previously created one and name it ‘Set DoNotConnectToWindowsUpdateInternetLocations to 1’. After the last Windows Update Step, we can remove the Keys to restore the Initial Situation for Sysprep and Capture.Īs you see, I created a new Group called ‘Add Windows Update Settings’ just before the first Windows Update Step. The real solution here is to add the two Windows Update related Registry Keys to the Reference Machine, before the Task Sequence reaches the first Windows Update Step. In addition, when working in a large organization with a complex network, this isn’t really an easy thing to achieve. However, here it didn’t change anything unfortunately.ĭuring testing I also had limited success by connecting the Reference Machine directly to the Internet. This was necessary with Windows 10 1607, due to a broken Windows Update Agent in the Vanilla Image. What I first tried was pre-applying the latest Cumulative Update before the Task Sequence reaches the Windows Update Step. You can leave the Computer pretty much for hours in this state without it doing anything. Here I had the issue, that the Reference Computer reaches the first Windows Update Step and runs into a Timeout while searching for Updates. I recently started working with Windand used about the same Capture Task Sequence as for Windows 10 1511. MDT was configured to install Updates from a locally installed WSUS, which worked for Windows 7 up to Windows 10 1511. Over the last few weeks, I had an interesting issue regarding Windand the Installation of Windows Updating during a Capture MDT Task Sequence. UPDATE: I’ve added some ConfigMgr / SCCM related details at the end of the blog post.
0 kommentar(er)
