Summary of changes in System Center Configuration Manager current branch, version 1802


Summary


Release version 1802 of System Center Configuration Manager Current Branch contains many feature improvements and changes to help you avoid issues.

The following "Issues that are fixed" is not inclusive of all changes. Instead, it highlights the changes that the product development team believes are the most relevant to the broad customer base for Configuration Manager. Many of these changes were made in response to customer feedback about product issues and product improvement.

Version 1802 is available as an in-console update that can be installed at the top-tier site in a hierarchy.

For installation information, see Checklist for installing update 1802 for System Center Configuration Manager.

For more information about the changes that are included in version 1802, see What’s new in version 1802 of System Center Configuration Manager.

Issues that are fixed


Configuration Manager console

  • Cloud Services client settings, such as enabling a Cloud Management Gateway, can incorrectly be defined for users in the Configuration Manager console. These settings are only functional for devices.

     

  • “msg_0_0” is displayed incorrectly as the detail text on the “Check Client Detail” tab for the “Verify/Remediate client prerequisites” rule.

     

  • Co-management objects in the Configuration Manager console do not open when you double-click them.

     

  • The “Antimalware clients out of date” alert does not appear in the “All Alerts” section of the Configuration Manager console after you update to Configuration Manager current branch, version 1706 or 1710.

     

  • An exception is generated in the Configuration Manager console after you try to edit the properties of a “Windows Defender Exploit Guard” policy object.

     

  • After you update to Configuration Manager current branch, version 1710, Windows 10 mobile is not available as a supported platform for VPN profiles.

     

  • PowerShell commands that are copied from the Configuration Manager console and pasted directly into a PowerShell session do not run. This issue occurs because an invalid character is added to the beginning of the commands.

     

  • After you update to Configuration Manager version 1710, the Configuration Manager Service Manager tool does not show the full log file name in the component logging window. This issue does not affect the actual log file names. This is a display-only issue.

     

  • The built-in Software Update Manager Role security role cannot modify folders under “All Software Updates” in the Configuration Manager console.

     

  • Updates are not installed on a client when a maintenance window is available, and the grace period has expired. This issue occurs if the Delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings option is set in the properties of the application deployment.

     

  • Software update scans on Windows 10 clients result in an update of Group Policy objects on those clients. This, in turn, can increase traffic to domain controllers. Event ID 8004 is recorded in the Group Policy event log on the clients at the same time that the software update scan is initiated.

     

Software Updates Management

  • The built-in Software Update Manager Role security role cannot modify folders under “All Software Updates” in the Configuration Manager console.
     
  • Updates are not installed on a client when a maintenance window is available, and the grace period has expired. This issue occurs if the Delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings option is set in the properties of the application deployment.

     

  • Software update scans on Windows 10 clients result in an update of Group Policy objects on those clients. This, in turn, can increase traffic to domain controllers. Event ID 8004 is recorded in the Group Policy event log on the clients at the same time that the software update scan is initiated.
     

Software Distribution and Content Management

  • Content distribution from a primary site to distribution points may be slower than expected when multiple packages are created or updated in a short time. Multiple packages will display a status of In Progress.
     
  • If the SMS Executive service is restarted while the site is processing a “.fwd” file to send a package to another site, the process fails. Additionally, errors that resemble the following are recorded in the distmgr.log file on the site server:

    When this issue occurs, the package in question must be updated to send successfully to the target site.

     
  • A Site System Connection account is used incorrectly for access to SQL following a failed connection to a distribution point. This issue occurs if the following conditions are true:
    • The remote distribution point in configured to use a Site System Connection Account
    • The remote distribution is offline or otherwise inaccessible while content is being transferred.

    After the distribution point is back online, errors resembling the following are recorded in the distmgr.log file:

    The preceding log lines indicate the account that was used for the connection.

     
  • Deploying an application that has supersedence configured fails if the new application is available only on an Internet-facing distribution point. Additionally, errors that resemble the following are displayed when the status is monitored from the Configuration Manager console:

    This error is preceded by the following, several lines up in the log, when an Alternate Content Provider is used:
  • Content downloads to a client do not fail over to built-in providers if an Alternate Content Provider returns an error. Additionally, errors that resemble the following are recorded in the ContentTransferManager.log file on the client:

Reporting

  • The “Computers not discovered recently (in a specified number of days)” report may include computers that are not in the collection that is specified as a report parameter.
     
  • The “Distribution Point Usages Summary” report does not display distribution points on primary site servers.
     

     

Remote Tools

  • The Configuration Manager remote control viewer (CmRcViwer) does not display the pointer correctly when you connect to a client by using Windows DPI scaling.
     

     

Client

  • Clicking Install Date under Installed Software in Software Center does not sort items in the correct date order.
     
  • The Install Software or Install Software Update Task sequences may fail while waiting for the SMS Agent Host (ccmexec.exe) to be available. This issue can occur in environments that have many machine policies deployed. The SMS Agent Host may restart before all policy processing is complete. This leads to the failures mentioned earlier. The symptoms may also occur even if the UserPolicyReRequestDelay value is defined in the registry under the HKEY_LOCAL_MACHINE\Software\Microsoft\CCM subkey.
     
  • Clients are unable to determine their Site Version if the Tenant Name field in Azure Active Directory contains an ampersand or other nonalphanumeric character.
     
  • Clients cannot download express update installation files if the download takes longer than five minutes.
     

Site Systems

  • In a Configuration Manager environment that is not using Microsoft Intune, errors that resemble the following may be repeated in the certmgr.log file:

    Note These errors are harmless and do not affect typical site function.

     
  • Database replication between sites may fail in very large hierarchies that have multiple primary and secondary sites. In this scenario, replication may be in a failed state after you update Configuration Manager because of SQL query timeouts. Beginning with version 1802, the default time out for Replication Configuration Monitor (RCM) query timeouts is 30 minutes.

    In rare circumstances, you may have to alter this value by adjusting the SQL Query Timeout value in the registry at HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\SMS_Replication_Configuration_Monitor.

    Note The new time out value affects all RCM SQL queries, not only those used during the site update process.

     
  • The SMS Executive Service (smsexec.exe) may terminate unexpectedly. In this case, the CTemHost::Process process crashes because of registration failure of the microsoft.configurationmanager.taskexecutionmanager.dll file.

     

  • Installation of a new site to a pre-existing SQL Always On cluster may fail. Additionally, errors that resemble the following are recorded in the ConfigMgrSetup.log file:

     

  • Adding a large (tens of thousands) collection of devices to a server group may cause a backlog of state system messages on the site server.

     

  • Data replication may fail when sites in a hierarchy are updated to a new version of Configuration Manager. This issue can occur when sites in the hierarchy were previously uninstalled. The Replication Link Analyzer tool indicates the ConfigMgrRCMQueue is disabled, and the corresponding SQL error log files contain entries resembling the following:


    In this example, _SiteABC references a site that was uninstalled from the hierarchy.

     

  • Status messages from State Migration Point are discarded by the Component Status Summarizer. Messages that resemble the following are recorded in the compsumm.log file:

     

  • A backlog of files to process may appear in the “\Compsumm.box” folder on a site that has hundreds of remote distribution points and state migration points.

     

Operating System Deployment

  • The Download Package Content task sequence step does not display a newly created package in the Task Sequence Wizard. This issue occurs when the content associated with that newly created package is not yet available on a distribution point.
     

Hotfixes that are included in this update


  • 4015968 Installation of Configuration Manager Client current branch 1602 to 1702 or LSTB version 1606 fails in Windows Server 2008 SP2
     

Dependency changes


The following dependent component previously included with Configuration Manager is removed:

  • Microsoft Silverlight is no longer installed as part of the Configuration Manager client. Note that Silverlight is not removed if previously installed manually or as part of an earlier version of the Configuration Manager client.