PENDING Disable Windows Update during OSD - SCCM Standalone ISO file

[Deilson Oliveira]

Is it possible to temporarily disable Windows Update when deploying an SCCM image offline via ISO/USB?

Whenever the "Client for Configuration Manager" installation task is finished, the computer restarts and instead of continuing to the Tasks Sequences, it does a brief installation of some updates, reboots, checks if these installations were successful, restarts again and only then goes back to the task sequences, and it takes an absurd amount of time for the equipment's hardware not to be so recent.

The idea is not to kill Windows Update permanently, but to just disable it during the OSD (and where this Task Sequence should be placed, whether it's at the beginning, or middle)

 

[Thomas_Ehler]

Set this in your image and remove afterwards
REG ADD HKLM\Software\Policies\Microsoft\Windows\Windowsupdate /v DoNotConnectToWindowsUpdateInternetLocations /t REG_DWORD /d 1

 

[Deilson Oliveira]

Set this in your image and remove afterwards
REG ADD HKLM\Software\Policies\Microsoft\Windows\Windowsupdate /v DoNotConnectToWindowsUpdateInternetLocations /t REG_DWORD /d 1

Okay, but in which step of the task sequence does this command need to be executed? Because after the task "Apply Operating System Image" it goes to the next task which is "Setup Windows and Configuration Manager" and after that it restarts, and that's where it restarts, which starts to connect with Windows Update.

 

[Thomas_Ehler]

I'd do this in the image when prepping it. Not when installing it.
No matter if you use SCCM or MDT to capture the image, just run the above command prior to capturing the image

 

[Deilson Oliveira]

I'd do this in the image when prepping it. Not when installing it.
No matter if you use SCCM or MDT to capture the image, just run the above command prior to capturing the image

I understand, the whole point is that I do it differently. I don't install the image in a VM, I prepare and then capture using DISM, I use the original "install.wim" from the Microsoft ISO, and I apply the modifications through the Task Sequences. In this case I would have to prepare it the conventional way, and only later put it back in the Task Sequence.

 

[Thomas_Ehler]

I understand, the whole point is that I do it differently. I don't install the image in a VM, I prepare and then capture using DISM, I use the original "install.wim" from the Microsoft ISO, and I apply the modifications through the Task Sequences. In this case I would have to prepare it the conventional way, and only later put it back in the Task Sequence.

OK.. I do it the other way round and add all the VisualC runtimes, Windows updates and Office 365.
Saves me a LOT of install time (appr 35 min in total)
I only build a new one every 6 months. Rest of the time I just have SCCM offline update the Wim for me.

 

[Thomas_Ehler]

But I gather you can do what you want?
You say you run a fully self contained USB install incl TS?

Can't you just run the above Reg just after first reboot into Windows?
That's just after the "Setup Config Manager..." step?

 

[Deilson Oliveira]

But I gather you can do what you want?
You say you run a fully self contained USB install incl TS?

Can't you just run the above Reg just after first reboot into Windows?
That's just after the "Setup Config Manager..." step?

The first part of your comment I didn't understand, but the second part did, so here we go.

After finishing the step "Setup Configuration Manager..." the computer restarts, and instead of going back to the task sequences, it makes a brief connection with Windows Update and starts performing some updates, so after installing these updates, it restarts and only then does it go back to the Task Sequences.

My doubt in this part is that after installing the configuration manager, it is loaded in Full OS mode, where the mode that accesses regedit is different from the way it is accessed before installing the configuration manager, so my question would be, how could I apply this regedit configuration considering that before one step it is in WinPE and in the other it is in Full OS mode.

 

[Thomas_Ehler]

And that is a really good question..
I have not used the full offline install method much and just leave out the Windows Update step at the bottom of the TS. That seems to be enough to avoid the OSD from running any updates.
- Just went through ~50 or so logs and none performs an update.

 

[Deilson Oliveira]

And that is a really good question..
I have not used the full offline install method much and just leave out the Windows Update step at the bottom of the TS. That seems to be enough to avoid the OSD from running any updates.
- Just went through ~50 or so logs and none performs an update.

My case is different, I don't have any task that performs windows updates, I believe that after installing the configuration manager client, it automatically connects to windows update and updates (I believe it's just drivers), but this small update costs me more than 10 minutes of waiting to get back the normal tasks I created. That's why I wanted to prevent this, to save more time on offline installation.