Microsoft has released the first cumulative update for SCCM Current Branch (1810), it has the number KB4486457, it applies as much to those in "First waves" as the global release.
Correction for the first wave (early update)
- Synchronization of Office 365 updates might fail after updating to the current branch of Configuration Manager, version 1810
- The process of upgrading the distribution point may fail. This causes an additional content distribution block on this server.
- All superseded updates are removed and are no longer applicable on a client, even before expiration. This issue occurs even though the "Do not expire a replaced software update until the software update is replaced for 3 months" option is enabled.
- Performance improvements have been made to the Data Replication Service for device discovery data.
- The second and successive phases of a deployment start automatically after the success of the first phase, regardless of the start-up conditions.
- The Staged Deployment Delay behavior settings are inconsistent between the properties of the Create Staged Deployment wizard and phase settings.
- When you run a service plan after selecting a product category, the filter is not added correctly.
- The Cloud Management Gateway (CMG) content service is not created correctly when the CMG role is added after updating to the current branch of Configuration Manager, version 1810.
- The option “No deployment package” is selected after modifying the properties of an automatic deployment rule (ADR). After this update rollup is applied, affected ADRs can be recreated and their properties changed without further problems.
- The Configuration Manager message processing engine (MPE) does not always process Active Directory discovery data when optional attributes are added.
- The service connection tool (serviceconnection.exe) fails and the following error message appears when you use the -connect parameter:
ERROR: System.IO.Exception: The directory is not empty.
- A user without full administrator rights may not be able to create or edit Windows Defender ATP policies, even when you add them to the Endpoint Protection Manager security role.
- The prerequisite installation checker does not allow you to retry a site installation. If a second attempt is attempted, the administrator should run the Configuration Manager Update Reset Tool (CMUpdateReset.exe) to resolve the issue.
- The processing of .bld files by the SMS_Notification_Manager component takes longer than expected. This causes delays in data processing and file processing delays in the \ inboxes \ bgb.box folder.
- After updating to the current 1810 branch of Configuration Manager, remote SQL providers that use Microsoft SQL Server 2014 or earlier may not always query the database.
- The Software Updates Patch Downloader component relaunches updates up to three times. These attempts fail and return the error code 404.
- Windows Server 2016 updates do not display correctly as available when you schedule updates for a Windows Server 2019 operating system image.
- Finding the first, last name, or full name of a user does not return any results in the Overview section of the Assets and Compliance node of the Configuration Manager console. This problem occurs even when full discovery data is available.
For the rest
- After you enable express installation file support, content may not always be downloaded from Windows Server Update Services (WSUS) servers in the following scenarios:
- Installing the Configuration Manager Client Through the Software Update Point
- Installing updates directly from WSUS
- Windows On Demand (FOD) or Language Pack (LP) Acquisition
- After you update version 1810 of the current branch of Configuration Manager, device registration may override Windows telemetry collection values previously set by Group Policy. This issue can cause a value to be switched between the full version and the base version, for example, when Group Policy is applied.
- Hardware inventory is updated to include information about add-ins for Office 365 products and stand-alone Office products.
- Desktop Analytics deployment plans show more devices in the Configuration Manager console than in the Desktop Analytics portal.
- Configuration of the Configuration Manager client might fail on a metered network connection (for example, cellular). This can happen even if the client policy settings allow these connections. An error message that resembles the following is logged in the Ccmsetup.log file on the client.
- Client deployment cannot be performed because use of the measured network is not allowed.
- Client installation might fail due to SQL Server CE schema changes.
- If an application is partially compliant and the customer sees that a dependency is installed, but the main application is not and requires a new application, the available deployment causes the following issues:
- The application is displayed as required or overdue even if the deployment is available and there is no replacement relationship.
- Clicking on Install has no effect.
- Signing in to Azure services fails when using the Create workflow in the Azure Services Wizard, even when the correct credentials are used.
- Configuration Manager configuration might fail while checking the prerequisites when installing or updating a site server. This problem occurs if the environment uses SQL Always On.
- The "Firewall Exception for SQL Server" rule indicates the failure state, and the error messages that are similar to the following are logged even if the appropriate firewall exceptions are configured.
- The alternate download server listed in the "Specify the location of the Microsoft update service on the intranet" window is not propagated to the Group Policy settings on the client.
- Downloading Office 365 updates, such as "Semi-annual Channel 1808 release for x86 Build 10730.20264" or "Monthly Channel, version 1812 for x64 Build 11126.20196" might fail. No errors are logged in the Patchdownloader.log file.
Founder of StevenBart.com - Vevey, Switzerland.
I have been in IT since 2001, I work as a Workplace Architect and mainly take care of the administration of MEMCM (SCCM), the mass deployment of workstations and applications. Learn more about me.