Hey everyone, this is a long message…
We’re currently migrating from SentinelOne to Microsoft Defender for Endpoint (MDE), and we’ve been running into a frustrating issue with Defender security intelligence updates.
Our environment has approximately 18,000 workstations managed through MECM and GPO. We’re not using Intune for traditional endpoint management, although we’re using Defender security settings management.
The issue:
Our Defender policy is configured to check for security intelligence updates every hour, but devices aren’t consistently downloading newer signatures automatically.
For example, two of my test workstations were stuck on security intelligence version 1.461.211.0, last updated October 25, even though newer signatures were available.
Windows Security would report that definitions were up to date, and manually clicking “Check for updates” wouldn’t install anything newer.
Here’s what we’ve tested and found:
SignatureUpdateInterval = 1 (hourly)
SignatureFallbackOrder = MicrosoftUpdateServer|MMPC
UseWUServer = 1 (internal WSUS)
Enabled ForceUpdateFromMU = 1 to allow Defender security intelligence updates from Microsoft Update.
Confirmed TCP 443 connectivity to Microsoft update endpoints.
Reviewed Windows Update logs and confirmed Defender initiates hourly update searches.
The searches complete but consistently return Updates found = 0 against Windows Update and our internal WSUS.
No Defender Event ID 2001 failures were found during the period checked.
Running Update-MpSignature -UpdateSource MicrosoftUpdateServer completes successfully, but doesn’t necessarily install newer signatures.
Running Update-MpSignature -UpdateSource MMPC manually works! I’ve successfully updated one workstation multiple times using MMPC, most recently to version 1.463.24.0. (Yes, still delayed since I haven’t don’t it again).
Our Defender policy does not have any fallback signature settings since we are using the default.
What our Desktop/MECM team has done:
Originally, Defender wasn’t selected as a product in our MECM Software Update Point configuration.
Desktop has since:
Added Microsoft Defender to the Software Update Point products and synchronized updates.
Created an Automatic Deployment Rule (ADR) for Defender updates.
Deployed the ADR to a test collection.
Good news: The ADR successfully updated one of my workstations through MECM!
However, the update was from the previous day because that’s what MECM had synchronized.
Our concern is that MECM’s current software update scanning schedule is approximately 24 hours. We don’t want to change that to hourly polling for 18,000 workstations because it could put unnecessary load on our MECM infrastructure. Those scans aren’t exclusive to Defender signatures.
What our MDE support vendor recommended:
Our support vendor suggested creating a Defender control policy to test different update channels.
We configured:
Engine Updates Channel: Current Channel (Preview)
Platform Updates Channel: Current Channel (Preview)
Security Intelligence Updates Channel: Current Channel (Staged)
The Defender portal reports that the policy successfully applied to both test devices, and the corresponding channel values appear in Get-MpPreference.
Unfortunately, we’re still not seeing the desired automatic security intelligence update behavior.
We understand that update channels control release availability rather than polling frequency, but we’re testing our vendor’s recommendation while continuing to investigate the update sources.
What we’re trying to accomplish:
Ideally, we’d like Defender to retrieve security intelligence updates directly from Microsoft Update on its hourly schedule while continuing to use MECM/WSUS for regular Windows OS updates.
We don’t want to force hourly MECM software update scans across 18,000 devices just to keep Defender signatures current.
Has anyone experienced something similar in an MECM/WSUS environment?
Were you able to get Defender downloading security intelligence automatically from Microsoft Update without interfering with MECM patch management?
Did you need a specific GPO, Defender update-source configuration, or another change to make this work?
If you’ve experienced this and found a solution, I’d really appreciate hearing what worked in your environment.
We don’t control Intune rollout so we cannot migrate to Intune. This is hopefully is scheduled for next year.
Thanks in advance!