[English]Administratoren, die beim SCCM 1705 System Center Configuration Manager current branch, version 1706 für die erste Deployment-Welle optiert haben, bekommen nun Update 2 im Updates and Servicing-Node der Configuration Manager-Konsole angeboten.
Anzeige
Update KB4036267 (Update 2 for System Center Configuration Manager Version 1706, first wave, August 31, 2017) adressiert die letzten Probleme, die beim Final Release-Prozess der Version 1706 gefunden wurden. Hier die Liste der Fixes:
- After the option to choose a mass storage driver in the properties of an Apply Driver Package task sequence step is selected, an unhandled exception may occur. In this case, you receive an error message that resembles the following:Object reference not set to an instance of an object.
- Multiple shortcut menu options, such as "Size Column to Fit" and "Sort By" are not localized in the Configuration Manager console.
- After you upgrade to Configuration Manager version 1706, first wave, the \inboxes\bgb.box\bad folder may start to accumulate .bgb files that are larger than 50 MB. These files can be safely deleted. After you install this update, any new .bgb files will be smaller.
- If a client computer changes from an Internet location to an intranet location while content is downloading from a cloud-based distribution point, the download fails. For a client upgrade package, the content transfer manager job continues to retry and cannot download the required files.
- During a site upgrade, content replication between sites may slow down and generate a backlog. A review of SQL activity indicates that the SMS Policy Provider is blocking other threads. Additionally, messages that resemble the following are recorded in the policypv.log file on the site server:
*** exec spProcessCrpNotifications
*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Query timeout expired
Failed to execute SQL cmd exec spProcessCrpNotifications - The Software Updates Dashboard node of the Configuration Manager console appears to hang while loading, and takes mopre one minute to fully load.
- Pull Distribution Points may take longer than expected to upgrade because of a deadlock condition that occurs when you update content distribution status tables.
- The Software Center does not open on Windows 7-based computers. Errors messages that resemble the following are recorded in the SCClient.log file:
Unhandled exception was caught.
(Microsoft.SoftwareCenter.Client.SingleInstanceApplication at OnGetException)
Exception System.Windows.Markup.XamlParseException: Could not load file or assembly 'SCClient.Common - Clients that have not reported compliance status are not presented with the Azure Active Directory (AAD) authentication prompt for conditional access.
- Cumulate Updates for Windows Server 2016 now have a default maximum run time of 60 minutes.
- You receive the following error message in the Configuration Manager Service Manager console when you try to query or restart components local to the site server:
Error communication with component.
- Custom property pages do not load in the Create Package, Create Package from Definition, and Create Task Sequence wizards in the Configuration Manager console.
- After you upgrade to Configuration Manager version 1706, first wave, creating Prestaged Media for an operating system deployment can cause the deletion of local user directories (under both \Users and \ProgramData). The deletion occurs on the system on which the media is being created.
- Boot images do not update if the Windows ADK version 1703 is used together with Configuration Manager version 1706, first wave.
Weitere Details finden sich in KB4036267. Bleibt die Frage, ob irgend einer meiner Blog-Leser für diese Option votiert hat? (via)
Anzeige
