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

Configuration Manager console

• The Configuration Manager console can terminate with an unhandled exception when using a non-English console to edit the Site System Status Summarizer database thresholds.
  

• The Office 365 Client Management node in the console may generate an exception when trying to add items to a new device collection. Exception text resembling the following is displayed.

  Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException​
  Not found , property = ResourceType​

   

• The Bulletin ID column is replaced with Article ID on default Software Update views in the Configuration Manager console.

• The Management Insights dashboard may incorrectly show Long Term Servicing Branch (LTSB) or Long Term Servicing Channel (LTSC) versions of Windows 10 as unsupported.

• The Configuration Manager console may terminate unexpectedly when there are nested folders in the Packages node. This occurs when selecting the top level folder after searching for data, such as a deployment package, in the lower level folder. An exception resembling the following is displayed on screen.

  System.NullReferenceException: Object reference not set to an instance of an object.
  at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)

   

Software Updates Management

• The software update synchronization process takes longer than expected if the Include Microsoft Surface drivers and firmware updates option is enabled.

   

• The downloading of software update content may fail with a hash mismatch error. This occurs if BranchCache is enabled on the site server, and the content for multiple update packages was uploaded to a cloud-based distribution point.
  Errors resembling the following are recorded in the ContentTransferManger.log on the client.

  CCTMJob::_ProcessContentInfo – failed to verify hash (….
  CCTMJob:_ProcessContentInfo failed. (0x87d00217)

• Phased deployments of software updates will fail if the Suppress Reboot option is enabled for both workstation and server operating systems. An error resembling the following is recorded in the sms_PhasedDeployment.log file. Note this entry is truncated for readability.

  Exception: System.Data.SqlClient.SqlException (0x80131904): Parameter ‘@SuppressReboot’ was supplied multiple times.

   

• Administrators are unable to move updates from one software update group to another if those updates are not downloaded directly, but instead distributed via BranchCache.

• Synchronization of software update points in large environments may take much longer than expected due to inefficiencies in the SQL views and indexes used during the process.

   

Client

• After removing the Application Catalog role from a site, clients may continuously request a non-existent policy from the management point. This occurs because the associated web service policy is not correctly tombstoned on the client.

• DataTransferService Jobs may fail if the client computer restarts while the job is still running. This occurs due to a timing issue during computer shutdown that results in an incorrect status being returned for a Background Intelligent Transfer Services (BITS) job.

• A client may become unmanaged if it has a wi-fi profile certificate installed, and the client is installed using the cloud management gateway.

• After performing an in-place upgrade of the operating system from Windows Server 2012 R2 to Windows Server 2016, the Configuration Manager Health Evaluation scheduled task no longer functions. Client check results are reported as failed, and attempts to run the task from Task Scheduler result in the following error.

  An error has occurred for task Configuration Manager Health Evaluation. Error message: A task or folder with this name already exists.

   

• An automated deployment rule (ADR) for an update package may fail if software update synchronization is removing expired content from the same package.

• Clients are unable to download content or policies after repeated historical download failures. The data transfer service (DTS) jobs are suspended but restarting the SMS Agent Host (ccmexec) service causes downloads to resume. When the client is in this state, errors resembling the following are recorded in the DataTransferService.log on the client.

  DTS job {guid} BITS job {guid 2} failed to download source file {filename}.exe to destination {client cache filename} with error 0x80072EE7

   

• Users are unable to search in Software Center when the client operating system is configured with the Japanese locale and calendar.

• User Deployments are not visible in Software Center when the client communicates with a Management Point that uses a replica database.

   

• A remote control session to a Configuration Manager client will fail within a few seconds of connection. This occurs if the Teredo tunneling adapter is enabled on the client.

   

Site Systems

• The SMSDPProv.log contains false errors when enhanced HTTP mode is not enabled. In this scenario, the error "Failed to verify if the cert is sccm issued, 0x800b0109" is not indicative of a problem state and can be ignored.

• The list of SMS Providers is inconsistent after promoting a passive site server to active. The failover process succeeds, but remote providers are not listed in WMI or the Registry on the recently promoted site server.

• When custom client settings are used, changes to User Device Affinity (UDA) settings are not applied unless the "User device affinity usage threshold (minutes)" setting is also changed.

• The SMS Executive service (smsexec.exe) may terminate unexpectedly when distributing multiple large (multi-gigabyte) packages at the same time to a pull distribution point.

   

Reporting

• The following reports may take significantly longer (hours) to run than expected because of an inefficiency in an associated SQL function

  • Software Distribution Content / All Active Content Distribution

  • Software Distribution - Content / Application Content Distribution Status

Software Distribution and Content Management

• Package contents are not distributed to random distribution points at secondary sites if any other site in the hierarchy is in a non-active mode. For example, if a secondary site is in Upgrade mode, distribution points at another peer secondary site may not receive package contents from the parent site. The distmgr.log at the source site contains the following entry. Note this log entry may also be recorded during normal operations.

  ~Package server is not an active site, ignore it.

• An application does not install as expected when started manually by a user and the following settings are used for the deployment type:

  • User Experience: Install for System

  • Logon requirement: Only when no user is logged on

  • Installation program visibility” Hidden

Operating System Deployment and Task Sequences

• The REG_DWORD registry value type is not correctly recognized during evaluation of task sequence conditions. For example, data in a REG_DWORD value is reported as non-existent when evaluated during an Install Application task sequence.

   

• The smspxe.log contains extraneous data on DHCPINFORM messages. This overwrites useful troubleshooting data in the log file.

• Task sequence variables can now be selected for editing using the Tab key on the keyboard

• The Run PowerShell Script step of a task sequence does not recognize the 3010 return code as a success code.

PowerShell

• The Invoke-CMClientAction cmdlet does not wake up clients as expected when the -ActionType ClientNotificationWakeUpClientNow parameter is used.

   

• The New-CMSchedule and New-CMSoftwareUpdateAutoDeploymentRules cmdlet now correctly support schedules with an offset from a base day.

• The New-CMPackageDeployment cmdlet returns “Could not find property PackageID” when a value for a Package ID is passed as a parameter.

   

• The New-CMRequirementRuleCommonValue cmdlet incorrectly adds blank spaces to the end of its value, resulting in rule evaluations failing unexpectedly.
  

• The Import-CMDriver cmdlet returns “Object reference not set to an instance of the object” when the DriverPackage parameter is used.