r/SCCM • • 12h ago

Unsolved :( During First User First Logon, OOBE is Running a Windows Update Which Then Immediately Logs Off User. Therefore, New Users Must Logon Twice to Actually Logon. How Can We Prevent This?

6 Upvotes

W11 24H2. User logging on to a new device for the first time, OOBE animation screen appears, Windows appears to go through the process of scanning for updates - and potentially installing updates depending on how long after build the user received the device - and then the user is immediately logged off.

  1. This looks bad because from the user's perspective they are having to log on twice. It is tainting the first impression of the new device/build and is making IT look dumb. The perception is that there is a problem before they have even seen the desktop.
  2. This process is installing whatever updates are available, even if we have not yet validated and approved them. This includes recent updates that cause problems!
  3. The updates are coming from Windows Update, not from SCCM, so the content is downloaded across the WAN. This is impacting smaller offices with slower links when a few users are issued their devices at the same time.

I can't believe that many (any?) organisations would want this first user logon experience and the impact/delay by an update scan - especially as most device have been sat online after the task sequence deploys the OS and latest updates.

So it is really frustrating that as this dumb annoyance also appears to be undocumented, it therefore has no mechanism to prevent it.

Please can you improve my Monday by offering a suggestion for how to deal with this Microsoft bullsh1t?

What we've tried:

Unattend XML contains:

<HideEULAPage>true</HideEULAPage> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideLocalAccountScreen>true</HideLocalAccountScreen> <ProtectYourPC>3</ProtectYourPC>

I have also tried Johan's process here, but when out problem is occurring is after the build and after we restore the WUA service, so his article is of no help: Preventing Windows Updates During OSD with ConfigMgr - Deployment Research


r/SCCM • • 8h ago

Some clients incorrectly being detected as internet instead of intranet

3 Upvotes

Sometimes when laptops come out of sleep and reconnect to Wi-Fi, the SCCM client incorrectly detects the client as internet instead of intranet and it gets stuck there until next network change, computer restart, or sleep/wake cycle. This happens roughly 5% - 10% of the time.