Endpoint Mgmt Weekly — November 13, 2026

Here’s what caught my attention this week.

Configuration Manager 2609 has been pulled, a Windows security update is causing some Intune check-in delays, and Microsoft clarified something important about PowerShell scripts during Autopilot. There’s also a new version of Michael Niehaus’s Autopilot Branding tool.

Microsoft pulled Configuration Manager 2609 after a group discovery issue

Just over two weeks after making Configuration Manager 2609 generally available, Microsoft unpublished the update on November 11.

The issue involves Microsoft Entra ID Group Discovery. Under certain conditions, the update can unexpectedly remove discovery data for both Active Directory and Entra ID groups. Since collection membership can depend on that discovery data, affected collections could lose members.

There’s another upgrade consideration worth mentioning: ODBC Driver 18.7.1.1 can block site configuration when upgrading from ConfigMgr 2603 or earlier. Microsoft recommends using the validated 18.6.2.1 version and completing the 2609 upgrade before installing 18.7.1.1.

ConfigMgr 2609 release information · 2609 upgrade checklist

A Windows security update is causing Intune check-in delays

Microsoft is investigating an issue where Windows devices enrolled in Intune can miss a check-in while installing a recent Windows security update, identified as MSRC144654.

The failure happens during the update installation. Subsequent automated or manual check-ins can succeed, so affected devices eventually receive their pending policies, apps, and other changes. Microsoft recommends manually checking in after the update finishes if you need to accelerate that process.

Microsoft has confirmed the root cause and is working on a fix, currently anticipated for early December. If you’re troubleshooting devices that appear to have stopped receiving Intune changes around patch installation, this is worth checking before digging into enrollment or connectivity problems.

Microsoft service health incident IT1549049

Intune doesn’t wait for PowerShell scripts before installing Win32 apps

Microsoft updated its documentation this week to clarify how PowerShell scripts are handled during Windows provisioning.

The Intune Management Extension processes PowerShell scripts first during its startup flow, then begins Win32 app processing. However, that ordering does not guarantee that the scripts finish before app installation starts. Other device check-ins or notifications can also trigger app processing while a script is still running.

More importantly, the Enrollment Status Page doesn’t track PowerShell scripts as blocking workloads or wait for them to complete. ESP can finish even while a script is still running.

If a Win32 app depends on a script completing first, package that prerequisite with the app itself.

Microsoft’s Enrollment Status Page documentation · PowerShell scripts in Intune

A 30-minute Autopilot delay traced to Shared PC policy processing

Rudy Ooms investigated an Autopilot self-deploying deployment where the Intune Management Extension was running, but required Win32 apps didn’t start installing for roughly 30 minutes.

By correlating IME logs, Group Policy events, SharedPCSetup.log, and a Windows Performance Recorder trace, Rudy traced the delay to an interaction between Shared PC policy processing and MDMWinsOverGP.

The trace showed the MDM configuration manager holding a Group Policy reader while waiting for a Shared PC worker. That worker then needed another reader, but a waiting Group Policy writer prevented it from proceeding. The result was a deadlock-like wait that repeated in ten-minute intervals.

This is a good example of why an IME service showing as running doesn’t necessarily mean app processing is ready to begin. If you’re seeing unexplained delays during Autopilot, the Group Policy and Shared PC logs may tell you more than the app installation logs alone.

Read Rudy’s investigation

Michael Niehaus releases a redesigned Autopilot Branding tool

Michael Niehaus has released a substantial update to Autopilot Branding, the project originally published as a PowerShell script back in 2019.

The old approach had grown into a large script with a JSON configuration file that needed to be edited and packaged manually. The new version breaks the functionality into individual scripts bundled in a PowerShell module, with a UI for selecting and configuring the tasks you want to run.

There’s also a browser-based builder. You can configure the options and generate the .intunewin package entirely in the browser, without installing the module or running a separate packaging utility.

The resulting package works as a normal Win32 app in Intune, but the contents can also be extracted and used with other deployment tools. It’s MIT-licensed and a useful option for applying Windows customizations that aren’t easily handled through policy.

Michael’s announcement and walkthrough · Try the browser-based builder · GitHub repository

Endpoint Privilege Management can now handle network settings

The documented Network settings policy allows standard users to change IPv4, IPv6, gateway, and DNS settings on their network adapters without granting local administrator rights.

The experience starts in Windows Company Portal. Administrators define an EPM system settings policy and can require user confirmation, a business justification, Windows authentication, or both before a change is applied.

One practical scenario is a laptop that needs a static IP or different DNS configuration to connect at a new site. The user can make the approved change without needing an administrator to log in or providing broader elevation rights.

The feature is rolling out gradually, so it might not be available in every tenant yet.

Microsoft’s EPM system settings documentation · Rudy Ooms’s technical walkthrough

That’s it for this week.

Do you have a suggestion for this newsletter? Let me know in the comments.