Windows 10: Endpoint Configuration Manager aka SCCM does not pull correct versions of cumulative...

We use Endpoint Configuration Manager MECM to deploy required patches for Windows 10 workstations. The majority of our workstations are running Windows 10 Enterprise, version 1903. When I search MECM Software Library for "2020-10 Cumulative Update for Windows", I find expired updates for Windows 10 version 1703, 1709, and 1803. There is nothing available for 1903 or later.


If my categories, products, etc. are getting these expired versions, why would the same settings get supported versions of these patches?


I have attempted to create new Automatic Deployment Rules and adjusted many other settings. These types of settings, however, seem to be downstream of the actual problem. If the patch is not available within my list of all software updates, I would think my Software Update Point site configurations were flawed. My settings include all classifications along include the following product selections:

Windows 10

Windows 10 and later drivers

Windows 10 and later upgrade & servicing drivers

Windows 10 S. version 1903 and later, Servicing Drivers

Windows 10 S. version 1903 and later, Upgrade & Servicing Drivers

Windows 10 version 1903 and later

Windows 10 version 1903 and later, Servicing Drivers

Windows 10 version 1903 and later, Upgrade & Servicing Drivers

What else could I be missing considering that I am able to download and deploy expired versions of the patches I desperately need?

:)

 

Endpoint configuration manager

- -

Hi,

This consumer oriented community isn't the place to be asking an Endpoint question.

Please look through these search results at TechNet to decide which forum there would be the most appropriate for your question.

Technet forums

Don

 

Update 1612 for Configuration Manager Technical Preview Branch – Avail

Source: https://blogs.technet.microsoft.com/...available-now/

 

Managing Windows Defender with SCCM

Hi everyone,

We are looking into testing Windows Defender to replace our current AV solution. Our environment is Windows 10 (1703) and SCCM Current branch (1702 - build 8498)

From reading the various documents (Deploy, manage, and report on Microsoft Defender Antivirus - Windows security) it seems that Windows Defender is managed via installing the SCCM Endpoint protection
point site role. where I am confused is that I was under the impression that endpoint protection referred to the discontinued System Center Endpoint Protection client however it seems that this is what MS uses as a generic label for the AV / malware tools
nowadayas.

I just wanted to check whether this is still the correct way to do this in order to manage the inbuilt Windows Defender client on Win 10 (1703) machines. Are there any pitfalls to be aware of? I intend to test this on a small subset of machines as a proof
of concept.

My other question is whether anyone here is using Windows Defender ATP and what their thoughts were on this, has it provided you with easier management / better reporting? I do like the look of "cloud" security center. However we are currently on E3 licenses
and ATP requires E5.

Many thanks in advance.

A