Summary of changes in Microsoft Endpoint Configuration Manager current branch, version 1910

Applies to: Microsoft Endpoint Configuration Manager (current branch)

Summary


Release version 1910 of Microsoft Endpoint Configuration Manager current branch contains fixes and feature improvements.

The "Issues that are fixed" list 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.

Notes

  • The globally available release of Configuration Manager version 1910 was revised on Friday January 17, 2020 to include a fix for the following issue.

    • Automatic client upgrade. If your site uses automatic client upgrade, when you update the site to version 1910, all clients immediately upgrade after the site updates successfully. The only randomization is when clients receive the policy, which by default is every hour. For a large site with many clients, this behavior can consume a significant amount of network traffic and stress distribution points. This is corrected with the January 17 revision.
      A separate hotfix will be published for customers that installed the original globally available release version of Configuration Manager current branch, version 1910 prior to January 17. Additional information will be posted here when available.
      Customers using the original 1910 release can work around this issue by temporarily disabling automatic client upgrade, and using other client upgrade methods.

This revised version has a package GUID of 4CE24C49-E6B0-4B4F-9AD8-CA31FF269F23 To verify which build is installed, add the Package GUID column to the details pane of the Updates and Servicing node in the console.

Issues that are fixed


Site Systems

  • After expanding a stand-alone primary site into a hierarchy, replication may fail between the central administration site (CAS) and other sites. This occurs due to conflicts in replication groups added after the expansion.
  • During the site update process the perquisite checker incorrectly reports a warning regarding Active Directory permissions. A message resembling the following is logged even though the site server machine account has the correct permission.
  • The Site Backup maintenance task can be enabled without configuring a path for backup files; this results in the task failing until a path is added.
  • Hyper-V Production Checkpoints may fail for virtualized Configuration Manager site servers due a timeout condition in the SMSWriter service.
  • The SMS_MESSAGE_PROCESSING_ENGINE.log on a secondary site server may record the following error approximately every five minutes. Note this is log entry is not indicative of a true problem state on the site server.
  • The extraction process for the Data Replication Service (DRS) may fail in large environments. Errors resembling the following are recorded for the failing configuration group.
  • In environments with many distribution points, the Component Status Summarizer log – compsumm.log – may quickly fill with entries resembling the following. Note these messages are not indicative of a problem state, but may cause other relevant data to be overwritten in the log file.
  • New database indexes are added to reduce the likelihood of Data Replication Service (DRS) backlogs.

Operating System Deployment and Task Sequences

  • The timeout period used in a task sequence to wait for complete startup of the SMS Agent Host service (ccmexec) is now configurable using as a variable. The SMSTSWaitCcmexecOperationalTimeout task sequence variable can be configured with a value in seconds. The default value if nothing is specified is 30 minutes.
  • The SetupComplete.cmd file may contain an unexpected NULL character after modification during a task sequence. This can block other applications, such as System Center Virtual Machine Manager, from later updating that file.

  • Windows 10 Upgrade task sequences may fail with error 80041010 due to a timing condition. Errors resembling the following are recorded in the smsts.log on the client.

  • The Enable BitLocker task sequence step fails if there are any existing volumes encrypted with BitLocker. This occurs even if the “Current operating system drive” is the only one selected for encryption.

  • After a site recovery, the distribution manager component may record errors resembling the following in the distmgr.log file.

    Additionally, the CertMgr.log contains entries resembling the following.

    These errors do not impact typical content distribution scenarios but may lead to errors in sites with enhanced HTTP enabled.

  • If you deploy a task sequence for PXE or media (USB or DVD), the client does not receive the associated policy. An error resembling the following is recorded in the smsts.log file on the client.

  • An operating system deployment task sequence may not resume when the client computer restarts after installation of the Configuration Manager client. Errors resembling the following are recorded in the smsts.log file.

     

Product Feedback

  • The UploadOfflineFeedback utility now supports the use of a proxy server.
    The following additional command line parameters are available to enable proxy server support.

     

Hardware Inventory

  • Hardware inventory data using the KernelModeTime property of the Win32_Process class is not displayed in Resource Explorer.

     

PowerShell

  • The Set-CMSoftwareUpdateDeployment PowerShell cmdlet is updated to resolve issues with several parameters.

     

  • The Get-CMDevice cmdlet does not return a device entry unless a collection is also specified as a parameter.

  • After using the Set-CMTSStepDownloadPackageContent cmdlet to add a driver package, later attempts to edit the task sequence return an error resembling the following in the Configuration Manager console.

  • The Import-CMDriver cmdlet fails if the source location specified in the -Path parameter contains a txtsetup.oem file.

  • Wildcards do not work as expected in the ScriptName parameter of the Get-CMScript PowerShell cmdlet.
     

  • The New-CMSoftwareUpdateAutoDeploymentRule PowerShell cmdlet does not support the “No deployment package” option seen in the Create Automatic Deployment Rule Wizard.

  • Software Update Point proxy settings are not affected when using the Set-CMSiteSystemServer cmdlet with the relevant proxy parameters.

     

Reporting and Data Warehouse

  • The SCCMReporting.log file may increase in size beyond the maximum log file size. Depending on the activity recorded in the file, it may consume all available free space on the host drive.
  • Data for applications that are upgraded or reinstalled is not reported in the Data Warehouse as expected.

Configuration Manager console

  • Configuration Manager administrators may be able to see and delete deployment settings for an automatic deployment rule when they do not have permissions on the target collection.
  • The Task Sequence Editor is updated to allow for more efficient memory usage, reducing the chance of “Out of memory” errors when saving large task sequences.

Software Distribution and Content Management

  • An Install Package or Install Application task run via stand-alone media will fail if either of the following conditions is true.
    • The Active Directory schema is not extended when using the media in the same domain.
    • The standalone media is run in a domain different from which it was created.​​

 

  • In an environment with many active pull-distribution points (Pull DP), a deadlock or hang condition on one Pull DP may halt content transfer to all others.

     

Client

  • Users are prompted for authentication as soon as they open Software Center if a custom tab is enabled, instead of when they access the custom tab. This occurs if Common Access Card authentication is required for the web page displayed on the custom tab.
  • Client language pack files are removed after repairing the Configuration Manager client with the ccmrepair.exe utility.
  • Windows Update for Business Policy deployments will fail with error 0x8004100c in the WUfBHandler.log file when targeted to client computers running the May 2019 Update of Windows 10 (version 1903) or later.
  • Content is not available for tasks sequences when the client is on an intranet network, and the Always Internet Facing (CCMALWAYSINF) parameter is set to 1.

Co-management

  • The option to enable co-management is not available after updating to Configuration Manager current branch, version 1910. This occurs if co-management was previously enabled with automatic client enrollment and/or client workloads configured for Pilot, and the co-management policy was deleted prior to updating to version 1910.

Software Updates Management

  • Individual operating system security updates may still appear as Required in the Configuration Manager console even after the corresponding monthly quality rollup is installed. This is the result of an error with the update status summarizer stored procedure and occurs if the synchronization schedule between the software update point and Windows Server Update Services (WSUS) is configured on a monthly interval.

     

Hotfixes that are included in this update


  • KB 4517869: Update Rollup for System Center Configuration Manager current branch, version 1906

References


Learn about the terminology Microsoft uses to describe software updates.