Update rollup for System Center Configuration Manager current branch, version 1810

Applies to: System Center Configuration Manager (current branch - version 1810)

Notice


This update rollup was initially released to first wave (early update ring) customers on January 25, 2019. Starting on February 8, 2019, the update rollup is available to all customers who installed the globally available release.

Summary


This article describes issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1810. This update applies both to customers who opted in through a PowerShell script to the first wave (early update ring) deployment and customers who installed the globally available release.

For more information about changes in Configuration Manager version 1810, see What’s new in version 1810 of Configuration Manager current branch and Summary of changes in System Center Configuration Manager current branch, version 1810.

Issues that are fixed


First wave issues

  • Synchronization of Office 365 updates may fail after you update to Configuration Manager current branch, version 1810. Errors messages that resemble one of the following are recorded in the WSyncMgr.log file:
  • The distribution point upgrade process may fail. This causes a block of additional content distribution to that server. Errors messages that resemble the following are recorded in the distmgr.log file:

  • All superseded updates are removed and no are longer applicable on a client, even before expiration. This issue occurs even if the Do not expire a superseded software update until the software update is superseded 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 start conditions.

  • Phased deployment deadline behavior settings are inconsistent between the Create Phased Deployment Wizard and the Phase Settings properties.

  • When you run a Servicing Plan after you select 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 you update to Configuration Manager current branch, version 1810.

  • The No deployment package option is selected after you change the properties of an Automatic Deployment Rule (ADR). After this update rollup is applied, affected ADRs can be re-created and their properties changes without any further issue.

  • The Configuration Manager Message Processing Engine (MPE) may not always process Active Directory discovery data when optional attributes are added. Errors that resemble the following are recorded in the SMS_Message_Processing_Engine.log:

  • The Service Connection Tool (serviceconnection.exe) fails and you receive the following error message when you use the -connect parameter:

  • A user without Full Administrator rights may be unable to create or edit Windows Defender ATP Policies, even when you add them to the Endpoint Protection Manager security role.

  • The Prerequisite Installation Checker incorrectly gives the option to retry a site installation again. If a second retry is tried, the administrator must run the Configuration Manager Update Reset Tool (CMUpdateReset.exe) to resolve the issue.

  • Processing of .bld files by the SMS_Notification_Manager component takes longer than expected. This leads to delays in processing data and a backlog of files in the \inboxes\bgb.box folder.

  • After you update to Configuration Manager current branch, version 1810, remote SQL providers who use Microsoft SQL Server 2014 or an earlier version may not always query the database. Errors that resemble the following are recorded in the smsprov.log:

  • The Software Updates Patch Downloader component retries updates, up to three times. These retries fail and return error code 404.

  • Windows Server 2016 updates are displayed incorrectly as available when you schedule updates to a Windows Server 2019 operating system image.

  • Searching for a user’s first or last name, or full name, returns no results from the Overview section of the Assets and Compliance node of the Configuration Manager console. This issue occurs even when full discovery data is available.


 Globally available release issues

  • After you enable support for express installation files, content may not always download from Windows Server Update Services (WSUS) servers in the following scenarios:
    • Configuration Manager client installation through Software Update Point
    • Installing updates directly from WSUS
    • Windows Feature on Demand (FOD) or Language Pack (LP) acquisition
  • After you update to Configuration Manager current branch, version 1810, device enrollment can overwrite Windows telemetry collection values that were previously set by Group Policy. This issue can cause value toggling between full and basic, for example, when Group Policy is applied.

  • Hardware inventory is updated to include information about add-ins for Office365 and standalone Office products.

  • Desktop Analytics deployment plans show a larger device count in the Configuration Manager console than in the Desktop Analytics Portal.

  • Configuration Manager client setup may fail over a metered (for example, cellular) network connection. This may occur even if client policy settings allow for those connections. An error message that resembles the following is recorded in the Ccmsetup.log file on the client:

  • Client setup may fail because of SQL Server CE schema changes. Errors that resemble the following are recorded in the Ccmsetup-client.log on the client:

  • If an application is in a partly compliant state, and the client sees that a dependency is installed but the main application is not and requires re-enforcement, available deployment causes the following issues:

    • The application is displayed as required or past due even though the deployment is available and there is no supersedence relation.

    • Clicking Install has no effect.

  • Sign in to Azure services fails when you use the Create Workflow in the Azure Services Wizard, even when correct credentials are used.

  • Configuration Manager setup may fail the prerequisite check during installation or an update of a site server. This issue occurs if the environment uses SQL Always On.

    The “Firewall exception for SQL Server” rule shows a status of failed, and errors messages that resemble the following are recorded, even if the correct firewall exceptions are configured:

  • The alternative download server that is listed in the "Specify intranet Microsoft update service location" window is not propagated to the Group Policy settings on the client.

  • The download of Office 365 updates, such as “Semi-annual Channel Version 1808 for x86 Build 10730.20264” or “Monthly Channel Version 1812 for x64 Build 11126.20196” may fail. No errors are logged in the Patchdownloader.log file. However, entries that resemble the following are logged in the AdminUI.log log:

Update information for System Center Configuration Manager, version 1810


This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using first wave (Fast Ring).

Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed.

To determine whether a TAP build is being used, look for a Package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. The update applies to installations of version 1810 from packages that have the following GUIDs:

  • 699975FE-B5BA-43EB-8BE9-E2399F2F309A
  • 85475BAD-8669-4D36-8D64-C625BFE7DEDB
  • ACF6EECC-1C94-44E3-887E-D3349775816D
  • C8799F92-DC23-42A0-96FA-1862414C3967
     

Restart information

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any previously released update.

Additional installation information

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites that are located under that primary site automatically receive this update.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')

If the value 1 is returned, the site is up-to-date by having all the hotfixes applied on its parent primary site.

If the value 0 is returned, the site does not have all the fixes that are applied to the primary site installed. In this case, you should use the Recover Secondary Site option to update the secondary site.

File information


References


Install Updates for System Center Configuration Manager

Learn about the standard terminology Microsoft uses to describe software updates.