r/SCCM • • 11d ago

2609 unpublished

Thumbnail learn.microsoft.com
40 Upvotes

r/SCCM • • Sep 28 '26

Configuration Manager 2609 Available in Early Update Ring

Thumbnail learn.microsoft.com
43 Upvotes

r/SCCM • • 8h ago

SCCM Task Sequence fails after second reboot (TrustedInstaller/CBS) – Anyone else experiencing this?

3 Upvotes

Hi everyone,

We're experiencing an intermittent issue with SCCM/MECM non-OSD Task Sequences on Windows Server 2016.

During the Install Software Updates step, SCCM initiates the first reboot and the Task Sequence resumes successfully.

However, Windows sometimes triggers a second reboot through TrustedInstaller/CBS. After that, the Task Sequence occasionally fails to resume with:

Task Sequence Manager could not initialize Task Sequence Environment. Error 0x80070002

Interestingly, the _SMSTaskSequence directory and TSEnv.dat are still present.

The option "Retry this step if computer unexpectedly restarts" is enabled (5 retries), but doesn't always help.

The issue is intermittent. During our latest patching cycle, 4 out of 16 Task Sequences failed.

We already have an open Microsoft Support case, but no solution yet.

Has anyone experienced the same issue with non-OSD Task Sequences? Any known workaround or fix?


r/SCCM • • 2d ago

OSD - Gather and Upload Autopilot Hash During Imaging

6 Upvotes

Hello, I have PCs that we deploy the OS to and then have to manually gather the hash before running autopilot. We're using SCCM to deploy the OS, drivers, updates, other steps etc, but I would like to be able to upload the device hash during the task sequence - automatically. When I have the autopilot powershell script run during the TS it fails. However, if I walk over and manually run the powershell script by hand, it works fine. I have an App Reg with proper permissions, and have proven it works if I do it manually with the App Reg. I even tried creating a package with all the required modules and scripts, but no luck. Has anyone else gotten this to work? I'd love to have this process as close to zero touch as possible.


r/SCCM • • 2d ago

Windows 11 Education ARM64 Media for ConfigMgr OSD?

3 Upvotes

Anyone know where to get Windows 11 Education ARM64 media? I’m only seeing x64 under Volume Licensing.

I downloaded Microsoft’s public ARM64 ISO, but the install.wim only has Home, Home Single Language, and Pro. I need Education for ConfigMgr OSD.

Am I overlooking a VL download somewhere, or is Education ARM64 supposed to be handled differently?


r/SCCM • • 2d ago

Discussion .NET 8/9 going end of support, how are you working out what still needs it?

5 Upvotes

Seeing where .NET is installed is simple enough. What we’re stuck on:

which app actually depends on the runtime

whether it uses the system runtime or bundles its own

whether it’s safe to remove

who owns the app

dotnet --list-runtimes and searching for runtimeconfig.json and hostfxr files got us partway. But we keep hitting apps that ship their own runtime, the same product on different versions in different places, and owners who don’t know what their app needs. Endpoints are way worse than servers. Anyone with a decent-sized Windows estate, how are you building a software inventory of what depends on what? We’ve got SCCM and Defender, and axonius is in the RFP we’re drafting for software inventory, since it would merge what both of them see into one record per device. Which app actually loads which runtime is still a manual check either way. Are you handling this as a vuln problem or a lifecycle problem?


r/SCCM • • 3d ago

Windows PowerShell 5.1 Deprecation

40 Upvotes

Main article: Windows PowerShell 5.1 Deprecation

Windows PowerShell 5.1 is deprecated. It's no longer in active development. Windows PowerShell 5.1 is still part of Windows, and it's still supported. It will continue to receive security updates according to the lifecycle of each version of Windows. Scripts and tools that rely on it will continue to run.

Windows PowerShell 5.1 will be removed from a future version of Windows. Timing will be based on usage data and communicated in advance.

Microsoft recommends upgrading to PowerShell 7, the upgrade from Windows PowerShell 5.1. For more information, see Migrating from Windows PowerShell 5.1 to PowerShell 7.

Get testing your scripts with pwsh.exe instead of powershell.exe, I guess. Looks like PSAppDeployToolkit has a /core switch you can use to invoke PowerShell 7 instead from the .exe. What else might be an issue?


r/SCCM • • 3d ago

Mecm 2609 and broken 3rd party updates

11 Upvotes

Prior to upgrading our MECM used third-party software update catalogs and syncronized with dell. This worked 100%

We upgraded to 2609 and now when i force a sync nothing happens, the sync date remains prior to upgrading MECM.

On the WSUS server, which is the only SUP role, the sms_isvupdates_syncagent.log reports no error but repeats:

Unable to connect to site database, this can be ignored if not running on the default SUP or third party updates is disabled.

My mecm, wsus and sql server all have odbc driver 18.6.2.1 and ole db driver 19.4.2.0

Things ive checked:
I confirmed the dell cert isnt blocked.

In component status everything is green/OK

On the WSUS server i can launch WSUS Adminstrator MMC and it connects to the database no problem.

The sql connection logs show no failures.

The wsus computer has permissions to the mecm database: dbreader/writer, dbowner, public, smsroleAITool, smsdbroleSUP and smascmusers. And for the wsus database: dbreader/writer, public, dbowner and webservice

Remember it worked before the upgrade with no other changes. I suspect it has something to do with the latest odbc drivers and forcing encryption so i added the sql server cert to trusted root certification authority on both wsus and mecm servers.


r/SCCM • • 3d ago

Discussion Patching Windows servers when exploits drop every week, what’s your cadence now?

3 Upvotes

Newish sysadmin here, trying to figure out what normal looks like in 2026. With how fast exploits are coming out, is monthly Patch Tuesday still enough, or are people going weekly or even faster for some boxes? What I’m really trying to get right is patch prioritization. Some servers are internet facing, some run stuff nobody wants rebooted, and treating them all the same feels wrong. We’ve got Defender for Endpoint, and our IT director wants to bring in axonius to rank servers by exposure, since it would show which ones face the internet and who owns them. It won’t pick the reboot windows for us though, so right now I’m still mostly deciding by gut. How are you splitting it? Different rings by exposure, by business impact, something else?


r/SCCM • • 3d ago

Unsolved :( System.Net.WebException: Unable to connect to the remote server (WSUS error)

Post image
2 Upvotes

Hello,

For the past few days, we have been seeing errors in our MECM environment in both WCM.log and wsyncmgr.log stating that the site server is unable to establish a remote connection to the WSUS server.

The issue appeared suddenly. The last successful synchronization was working normally, and approximately one hour later the synchronization started failing without any known changes being made to the MECM or WSUS configuration.

According to the logs, the primary site server can no longer connect to the Software Update Point (SUP) where WSUS is installed. The error reported is essentially:

"Remote connection failed" / "Unable to connect to the remote server"

We have already verified the following:

  • WSUS services are running.
  • IIS is running correctly.
  • The WSUS website is bound to HTTPS on port 8531.
  • The WSUS server is actively servicing clients and has many established connections on port 8531.
  • The SSL certificate is valid and not expired.
  • DNS resolution works correctly between the servers.
  • Both servers are located in the same subnet (10.100.206.0/24).
  • ARP resolution works correctly between the two servers.

However, the following behavior is extremely unusual:

  • The primary site server and the SUP server can no longer ping each other.
  • TCP connections between the two servers fail in both directions.
  • Test-NetConnection to port 8531 fails from the site server.
  • Even SMB/RPC related ports such as 445 and 135 cannot be reached between these two servers.
  • Other servers in the environment can successfully reach the SUP server.
  • WSUS clients can still connect to the SUP and are actively communicating with it.

We also tested Windows Firewall rules and even created explicit allow rules between the two servers, but the behavior did not change.

At this point, the issue does not appear to be related directly to WSUS, IIS, certificates, or DNS. It looks more like a communication problem that affects only these two specific servers, despite them being in the same subnet.

Has anyone experienced something similar before, or are there any additional areas (VMware networking, NSX, endpoint security, Windows networking, etc.) that we should investigate?

Thanks.


r/SCCM • • 3d ago

ARM64 OSD - T14s Gen 7 won't boot WinPE 26100, but WinPE 28000 works

3 Upvotes

I’m starting to look at ARM64 imaging for the first time and currently only have one ARM device to test with, a Lenovo ThinkPad T14s Gen 7.

Our environment is ConfigMgr 2603 with KB39398030 and KB3794246 installed. I upgraded our ADK to 10.1.26100.9457 with the matching WinPE add-on. The WinPE included with this ADK is 10.0.26100.1. I created a separate ARM64 boot image and assigned it to an ARM test task sequence.

When PXE booting the T14s, I verified in SMSPXE.log that ConfigMgr sees the ARM architecture (Client Arch: 000b / architecture 12), selects the ARM64 boot loader (smsboot\arm64\bootmgfw.efi), and selects my ARM64 boot image. The boot image loading bar gets to the end, the screen goes black, the Lenovo splash screen appears again, and the computer then boots back into the installed Windows OS and displays the Windows logon screen.

I tested the SCCM ARM64 boot image both with and without Lenovo’s WinPE driver package for the T14s Gen 7. I also created SCCM bootable USB media using the ARM64 image and had the same result.

To take ConfigMgr completely out of the equation, I created multiple vanilla ARM64 WinPE USB media directly from the ADKs:

  • ADK 10.1.26100.9457 / WinPE 10.0.26100.1: will not boot. The image loads, the screen goes black, the Lenovo splash screen appears again, and the computer falls back to the installed Windows OS.
  • WinPE 10.0.26100.1 + Lenovo’s ARM WinPE drivers: same result.
  • WinPE 10.0.28000.1: successfully boots into WinPE, reaches a command prompt, and sees the internal SSD.

So with standalone, non-SCCM USB media, this T14s will boot into WinPE when the media is built from the 28000 ADK/WinPE, but it will not boot into WinPE when built from the supported 10.1.26100.9457 ADK / WinPE 10.0.26100.1.

A few other things I’ve ruled out:

  • Secure Boot has been tested both enabled and disabled with the same result.
  • For the ConfigMgr boot image, I tested Use Windows Boot Loader signed with Windows UEFI CA 2023 both enabled and disabled.
  • The T14s Gen 7 is running the latest Lenovo BIOS.

Microsoft currently lists ADK 26100.x as supported with ConfigMgr, while the 28000 branch is not currently listed as supported with any ConfigMgr Current Branch release. I’m reluctant to move our ConfigMgr environment to 28000 when Microsoft currently shows it as unsupported.

Has anyone else run into newer ARM hardware that won’t boot the supported 26100 ARM64 WinPE but will boot 28000? Is anyone currently using 28000 WinPE/ADK with ConfigMgr OSD despite it not currently being supported?

Any other thoughts, tips, or things I should try with 26100 would also be appreciated. I’d also be interested in experiences with this particular T14s Gen 7, or recommendations for another Lenovo or Dell ARM model that might be a better device to test with. We’re a Lenovo/Dell shop, so I’d prefer to stay with one of those vendors if I pick up another ARM device for testing.


r/SCCM • • 4d ago

How do you deal with devices that stop reporting in - stale ConfigMgr clients?

14 Upvotes

Curious how you handle machines that go quiet for weeks - remote staff, devices in drawers, loaners. How long before a stale record counts as 'lost', do you automate cleanup, and does hardware inventory ever match reality?


r/SCCM • • 5d ago

Feedback Plz? MBAM post-SCCM

11 Upvotes

I've got a conundrum I'd like some advice on.

We're in the middle of a migration from SCCM to BigFix (I know sounds kinda crazy, though BigFix is working out really, really well for us). Unfortunately BigFix does not do BitLocker management well. Especially reporting. Long term we plan to use Entra to manage/report on BitLocker, but we're unable to hybrid join our machines right now. Working through that with Okta and MS, but that's going to take significantly longer than it will to complete BigFix.

So, current plan is to leave a bare bones SCCM setup behind solely to manage BitLocker. We'll still deploy the SCCM client, but disable Software Center.

Questions I have are:

  1. What infrastructure do I need to leave behind? Since we can deploy the SCCM client with BigFix (man that sounds messed up) do I even need any DP's? We don't have CAS or anything, just the 1 site server, 3 DP's, and a cloud gateway. Ideally I'd like to leave just the primary site server behind and that's it.
  2. Am I over thinking this? Is there a simpler solution I am missing? The critical part of all of this for us is a custom report I created that lists machines that are encrypted but do not have an escrowed key. If there's a simpler solution that can provide the same reporting, I'm all ears. We've got about 5,000 workstations to manage. Only other thing I can think to do is stand up standalone MBAM. Sounds like a horrible idea since it's end of support, but it is only temporary.

r/SCCM • • 5d ago

Discussion Planning to upgrade from SQL Server 2016 to SQL Server 2025 - any gotchas to watch for?

9 Upvotes

Been putting this off for a while but now that any new versions don't support SQL Server 2016 it's time.

Simple environment. One primary site server with SQL Server on same VM. MP and DP on a different VM. Few other DPs around the world.

I know I have to reinstall SSRS after the ugprade but anything else I need to watch out for before doing in-place uprade?


r/SCCM • • 5d ago

PXE network SCCM hp rj45 to Usb-a imaging issue

3 Upvotes

Just wondering if anyone has thoughts on SCCM to image HP laptops using hp RJ to usbA adapter, domain joining is failing i think thru mac address pass thru, 2 in 1 usb c adapter works fine.


r/SCCM • • 5d ago

Updates during and post imaging issue

6 Upvotes

Has anyone solved how to stop any type of updates from occurring during or just post an image. The image seems to go out to the internet instead of going to our wsus which would stop it from doing these updates because we don't have those published to our wsus. This is causing unwanted drivers and security etc . Updates to apply. I have tried the keys available out there in all parts of the task sequence with no luck.


r/SCCM • • 5d ago

23H2 OOB

0 Upvotes

Is Windows 11 23H2 patch not available in SCCM to deploy?


r/SCCM • • 6d ago

Some clients incorrectly being detected as internet instead of intranet

6 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.


r/SCCM • • 5d ago

How do you provision laptops for fully remote hires who never visit an office?

0 Upvotes

Do you image laptops in-house and ship them, use Autopilot for remote hires while keeping SCCM for office staff, or take a different approach?

Where does the handoff between IT and the employee tend to break down, and what have you changed to make it more reliable? Interested in workflows rather than product recommendations.


r/SCCM • • 6d 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?

9 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 • • 8d ago

.DLL's blocked...nobody's fessing up.

33 Upvotes

So, we applied an SCCM hotfix, which triggered upgrades on all our DP's, great, all went well...except for 3 DP's over in AP sites. pckgxfermgr.log shows "ContentAuthModule.dll" failed to copy to the DP's inetsrv dir, DP is now broken on those 3 DPs - can't finish the update.

I performed some troubleshooting, found out that any .dll copied from the US primary (or any server in the same site) to the DP's get's the SMB session dropped, effectively blocking the .dll from being copied, figured...ok, AV, some security agent on the server is misidentifying the .dll as malware and blocking it. no big deal, remove the AV and another security agent for good measure, double check there are no filters, GPO's, or any other apps, server features, etc. that might be blocking the dll...reboot, try again, still getting blocked. No windows defender active on the servers.

Tried a few things to narrow it down...created .txt files of various sizes, those copy fine, other files copy - .exe, .mof, etc. - tried sneaking a dll in zipped, nope, tried, renaming a .dll to .txt, nope, tried, copying the file starting as a dll, but renaming it to something else on the destination..nope, tried copying as the system account...nope.

To make matters more infuriating, yesterday I had brief windows of success...some were directly after I removed the security apps - so I was like yah! that was it! Nope. issue came back, regardless.

The random successes kept happening yesterday - today - 100% failure every time.

I contacted the FW team..."the logs show no dropped packets, we don't have active NAC policies...it's not us." Contacted the security team - nothing logged regarding the blocks, no policies deployed that would do such a thing.

Opened a case with MS - they pretty much came to the same conclusion - after running wireshark captures, netsh dumps, reviewing smb event logs and so on - it has to be some sort of SMB/DLP policy inspecting traffic. I would blame riverbed...but they dumped those appliances years ago.

I'll have to see if the traffic is passing through some sort of web gateway maybe, or maybe some sdwan optimization policy was implemented incorrectly.

Feel free to share your thoughts on this one...we've got to get these DP's fixed, I did try copying the dll over manually using onedrive, but it didn't seem to like it, didn't magically finish the DP update as it was meant to. Probably not the only .dll it needs.


r/SCCM • • 9d ago

Rummaged through old open-source ConfigMgr tools in my home lab and came out with Layer8: free right-click tools for the console

55 Upvotes

Back in 2016, when I was new to this field, Roger Zander’s Client Center and Collection Commander were some of the first tools I used. Since then I’ve used Right Click Tools at a few different jobs. At some point I wanted to know how this stuff actually works under the hood, so I started taking one apart.

That turned into Layer8, a free extension for the ConfigMgr console. It started as a fork of Peter Szalatnay’s ConfigMgr Quick Tools, and I’ve been building on it in my home lab ever since.

What’s in it right now:

  • Client actions on a device or a whole collection: the standard cycles, plus Quick Status (who’s signed in, uptime, free space, IP, client version), Find Software (Chrome < 131), pending restart, missing updates, client health and repair, Send Message, Defender and BitLocker status. You get one row per device (done, offline, or why it failed), with Run Again on Failed and Copy Results for Excel.
  • System Information: overview, programs, updates, services, drivers, profiles and local admins, without remoting in. Read-only.
  • Windows Security: Defender, Firewall and BitLocker status. It never shows recovery passwords. Suspend/Resume BitLocker for BIOS updates.
  • LAPS (Windows LAPS, encrypted or not, plus legacy) and BitLocker recovery key lookup from AD
  • Install Application on a device like Software Center, and Error Lookup for those lovely 0x87D... codes
  • Deployments: Retry Failed Devices, Copy Failed Devices with error codes
  • Driver Manager: Dell, HP and Lenovo driver packs. Lenovo’s checks each download against Lenovo’s signed catalog.
  • Collections: Add/Remove Resources List (paste names), plus collection evaluation stats

Nothing gets installed on the devices you manage beyond the ConfigMgr client. On the console side it installs as an MSI, or as a cab you import and approve as a console extension, so it works if you have “Only allow console extensions that are approved for the hierarchy” turned on. There’s also a script to strip features out of the cab (say you don’t want LAPS or BitLocker key lookup in your console at all).

Screenshots of everything: https://github.com/JBoogieman/layer8/blob/master/docs/TOUR.md

Repo and releases: https://github.com/JBoogieman/layer8

A couple of disclaimers:

  • It’s a lab project. It’s been tested against ConfigMgr 2509 with a couple of Windows 11 clients, not a big production environment. STATUS.md in the repo lists exactly what’s been tested and what hasn’t.
  • It’s not affiliated with Microsoft or Recast, and it’s not trying to replace RCT.

I’m not selling anything. I just like breaking things and fixing them. If it’s useful to you, awesome. Fork it, rebrand it, rip pieces out, whatever you want.

If there’s a feature you’d like to see, or something’s broken, open an issue or let me know here.


r/SCCM • • 9d ago

Discussion failed update scan for co-managed devices

3 Upvotes

I want to share my findings, as I couldn't find anything for it and maybe my logic is false and something else fixed it. or I just couldn't find/ misunderstood my findings.

we have co-managed devices, which are hybdrid-joined if that matters here. and here are the workload configs. please don't tell me to switch them, we are in the transition and can't do it right now, and that's not the topic here. we are on Configuration Manager 2603 Hotfix Rollup (KB39169655), KB40345593 not installed, as we were testing 2609 and don't have an issue without the hotfix

-we have a gpo which sets the "SetPolicyDrivenUpdateSourceFor*" keys to wsus.
-have have mdmwinsovergpo policy in intune
-we added the same "SetPolicyDrivenUpdateSourceFor*" via intune in the policy, where we allow optional features and repair content to be downloaded via MSUpdate

-we had for a little time the WUServer set via "Update Service Url" in the same policy, as we were troubleshooting, which deleted the key completely, why we removedit from intune"

the clients started to don't get updates and didn't show up as required in SCCM under software updates. we tried anything we could find from the internet and finally fixed it, by deleting the "SetPolicyDrivenUpdateSourceFor*" and "Update Service Url" keys from the the intune policy and the clients started to work again.

Our conclusion is that the clients get the gpo, then intune policy overwrites it, as mdmwinsovergpo is set, but as the windows update policies workload is still on configuration manager it breaks the update policies and take no set key and breaks the wuahandler.

As of now that would be the only thing that would explain it and as I said, maybe we just didn't find or misunderstood the findings from the internet. I hope it can help someone who faces the same issues. Maybe someone like u/Rudyooms could try and verify my findins and write a blog about it ;-) or you can tell me what article/blog/forum I missed or misunderstood and didn't find the fix


r/SCCM • • 8d ago

TS apply issue

Post image
0 Upvotes

Ok I've tried everything, it works on my laptop but not this pc, its a dell optiplex 3070 sff with the storage drivers and all, but there goes the error, I've literally tried everything, it happens at the "apply operating system" step MAY HAVE BEEN SOLVED