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

Á við um: System Center Configuration Manager (current branch - version 1802)

Summary


This article describes the issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1802.

Issues that are fixed


  • In System Center Configuration Manager current branch, version 1802, conditional access compliance reporting fails for intranet clients if a proxy is required. This failure occurs even if the proxy settings are defined on the Network tab of Configuration Manager properties in the client Control Panel item.

    Additionally, errors entries that resemble the following are recorded in the ComplRelayAgent.log file on the client:

     

  • Data warehouse synchronization may be unsuccessful in large environments. The Microsoft.ConfigMgrDataWarehouse.log file contains entries that resemble the following:

     

  • The Configuration Manager console may terminate unexpectedly after you go to the Script Status node in the Monitoring workspace.

     

  • Synchronization of Unified Update Platform (UUP) files may time-out on a Central Administration site or primary site.

     

  • After you apply this update rollup, files that are associated with UUP packages will be downloaded only one time to a site server if the same file is already present in the local package source cache.

     

  • A multicast operating system deployment task sequence that is initiated from Software Center is unsuccessful if it is used together with a distribution point that is configured for HTTPS traffic.

     

  • After you update to Configuration Manager current branch, version 1802, the Run Script feature does not work with spaces in the script parameters.

     

  • After you update to Configuration Manager current branch, version 1710 or a later version, the SMSTSDownloadProgram variable does not function as expected in conjunction with applications or software updates. This issue occurs on clients in provisioning mode. It prevents an Alternate Content Provider from being specified in the task sequence.

     

  • SQL Server replication may be unsuccessful in a hierarchy after a secondary site is deleted and uninstalled. When this occurs, the ConfigMgrRCMQueue replication queue is disabled, and the SQL error log contains entries that resemble the following:

     

  • The Application Management option is not available for OneNote for Android when you deploy it in a Configuration Manager and Microsoft Intune hybrid environment.

     

  • After you update to Configuration Manager current branch, version 1802, Software Center settings cannot be customized from the Configuration Manager console. When you click the Customize button in the Default Settings pane, you receive an unhandled exception error message that resembles the following:


    This error occurs if a custom logo is specified before you install the version 1802 update.

     

  • Management points cannot communicate with a specified Device Health Attestation service if a proxy server is required.

     

  • The operating system is reinstalled on an existing Configuration Manager client, If the same host name is maintained that is registered in Azure Active Directory, Conditional Access compliance scenarios may start to fail.

     

  • Configuration Manager Data Warehouse synchronization may be unsuccessful when it processes inventory summarization. This issue can occur because the tempdb database on the server that is running SQL Server is running out of space while stored procedures are running.

     

  • The Configuration Manager client installation may be unsuccessful in a co-management scenario. This issue can occur if the installation is initiated from Microsoft Intune to an Azure Active Directory-joined client. Additionally, errors entries that resemble the following are recorded in the ccmsetup.log file on the client:

     

  • If the Enable clients to use a cloud management gateway option is set to No in an environment that has multiple management points and cloud management gateways in use, the client cannot process any location service requests. Additionally, errors entries that resemble the following are repeated in the ClientLocation.log file on the client:


    Note This message is intended to read, "...is not allowed to be used..." 

     

  • When you edit nested task sequences, changes that you make in a child task sequence are not automatically reflected in the parent task sequence.

     

  • Task sequences may hang and return a status of “Installing” in Software Center on a client. This issue occurs if there is insufficient space in the Configuration Manager client cache, and the currently cached content is 24 hours old or newer.

     

  • Content may not distribute to a cloud-based distribution point if the package contains several hundred files (for example, an Endpoint Protection Definition Update). Additionally, the PkgXferMgr.log file contains errors entries that resemble the following:

     

  • Synchronization of updates to a remote Software Update Point may be unsuccessful  if hundreds of files are being imported. For example, this issue may occur when you import Microsoft Surface drivers. Additionally, errors entries that resemble the following are recorded in the wsyncmgr.log file, and the synchronization process fails 15 minutes after it starts:

     

  • The download of express installation files for Windows 10 may time out in some environments. This issue can occur when Delivery Optimization (DO) or the Background Intelligent Transfer Service (BITS) are throttled. Additionally, messages that resemble the following are recorded in the DeltaDownload.log file:

     

  • Uninstall content for an application is not updated in the content library. This issue occurs if the content is modified after the original deployment type is created.

     

  • Applications may not install through a task sequence in environments that use a management point that is configured for HTTPS traffic and have a cloud management gateway enabled.

     

  • After a restart, an installation of a Windows Feature Update, such as Windows 10 Version 1803, through Windows Software Update Services (WSUS) may be reported as having failed. Error 0x80070422 is displayed in Software Center even though the operation was successful. Additionally, errors entries that resemble the following are recorded in the WUAHandler.log file:

     

  • When the Add-CMDeviceCollectionDirectMembershipRule cmdlet is used to add a client resource to an existing collection, it may unexpectedly remove nested Include or Exclude membership rules. This causes the collection to contain incorrect clients.

     

  • After you upgrade to Configuration Manager current branch, version 1802, the Export-CMDriverPackage cmdlet may not correctly generate the expected driver package.

     

  • The New-CMCloudDistributionPoint cmdlet may be unsuccessful, and you receive errors messages that resemble the following:

     

  • The New-CMCloudManagementGateway cmdlet may be unsuccessful, and you receive errors messages that resemble the following:

     

  • The New-CMBootableMedia cmdlet does not create valid subfolders. Additionally, the CreateTSMedia.log file contains errors entries that resemble the following:

     

  • After you connect to a client through a Remote Control session and you the Keyboard Translation feature enabled, the language bar on the client is no longer visible. It can be restored after you log off and back on, or by making a change to the keyboard language through Control Panel.

     

  • The Endpoint Protection Client does not install on Windows 10 ARM-based devices.

Additional hotfixes included in this update rollup


4295281 Internet-based Configuration Manager clients can't scan for updates after upgrade to Configuration Manager current branch, version 1802

Update information for System Center Configuration Manager, version 1802


This update is available for installation in the Updates and Servicing node of the Configuration Manager console.

Restart information

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

Update replacement information

This update replaces previously released update KB 4132447. For first wave customers, after this update rollup is applied, update KB 4132447 may still appear in the Updates and Servicing node with a state of “Ready to Install”. This can be safely ignored.

Known issues for first wave customers

First wave customers who installed this update before June 14, 2018, without first applying update 4132447 are unable to upgrade the Configuration Manager console. Error entries that resemble the following are recorded in the AdminUI.ExtensionInstaller.log:

AdminUI.ExtensionInstaller.exe Warning: 0 : Downloaded file does NOT match Hash, delete the file.
AdminUI.ExtensionInstaller.exe Error: 0 : Microsoft.ConfigurationManagement.ManagementProvider.SmsException\r\nDownloaded file does NOT pass Hash validation.

This issue does not occur for customers who download and install this update rollup on or after June 14, 2018. 

To resolve this issue, manually update the Configuration Manager console installation file (AdminConsole.msi). To do this, follow these steps:

  1. Verify that update 4132447 is listed in the “Ready to install” state in the Updates and Servicing node of the Configuration Manager console. If KB 4132447 is not listed, select Check for Updates. For service connection points in Offline mode, download and then import the update by using the service connection tool.
  2. Copy the <SMSROOT>\EasySetupPayload\b15738e1-039c-4769-91d2-3043fba4e579\smssetup\bin\i386\AdminConsole.msi file to the following locations:
    • <SMSRoot>\bin\i386\AdminConsole.msi
    • <SMSRoot>\tools\ConsoleSetup\AdminConsole.msi

Other considerations

If the service connection point is in Offline mode, you must reimport the update so that it is listed in the Configuration Manager console. For more information, see Install in-console updates for System Center Configuration Manager.

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 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')


Notes

  • If a value of 1 is returned, the site is up-to-date, with all the hotfixes applied on its parent primary site.
  • If a value of 0 is returned, the site does not have all the fixes that were applied to the primary site installed. In this case, you should use the Recover Secondary Site option to update the secondary site.

File information