Update rollup for SCCM current branch (1802)

Microsoft have released an update rollup for System Centre Configuration Manager Current Branch (1802)!

The following issues are fixed in this update:

• 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.
• Data warehouse synchronization may be unsuccessful in large environments. The Microsoft.ConfigMgrDataWarehouse.log file contains entries that resemble the following: DATA_WAREHOUSE_SERVICE_POINT Error: 0 : {timestamp}: Arithmetic overflow error converting expression to data type int.
• The Configuration Manager console may terminate unexpectedly after you go to the Script Statusnode 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: 257, Level 16, State 3, Procedure spLogEntry, Line 0, Message: Implicit conversion from data type xml to nvarchar(max) is not allowed. Use the CONVERT function to run this query.
• 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 Customizebutton in the Default Settings pane, you receive an unhandled exception error message that resembles the following: System.IO.InvalidDataException: Invalid format in settings xml. 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.
• 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.
• 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: Caught exception System.ServiceModel.ServerTooBusyException – The HTTP service located at https://{source_url} is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later.
• 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: Generic exception : ImportUpdateFromCatalogSite failed. Arg = {guid}. Error =Thread was being aborted.
• 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: Download timed out after 5 minutes. Cancelling download job.
• 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: Failed to query IsRebootRequiredBeforeInstall property of WUA UpdateInstaller. Error = 0x80070422.
• 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 WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within the same thread.
• The New-CMCloudManagementGateway cmdlet may be unsuccessful, and you receive errors messages that resemble the following: Operation is not valid due to the current state of the object.
• The New-CMBootableMedia cmdlet does not create valid subfolders. Additionally, the CreateTSMedia.log file contains errors entries that resemble the following: Output directory “C:\\Folder1\\Folder2\” does not exist.
• 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.

There are also some known issues within this release, details can be found here.