An update is available to administrators who opted in through a PowerShell script to the first wave (early update ring) deployment for System Center Configuration Manager current branch, version 1706. You can access the update in the Updates and Servicing node of the Configuration Manager console.
This update addresses important late-breaking issues that were resolved after version 1706 became available globally.
This update does not apply to sites that downloaded version 1706 from August 8, 2017 or later. Therefore, it will not be listed in the Administrator Console for those sites.
Issues that are fixed
- 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][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.
Update information for System Center Configuration Manager, version 1706
This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using first wave (Fast Ring) builds of version 1706 that were downloaded between July 13, 2017, through August 21, 2017.
To verify which first wave build is being used, look for a Package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. This update applies to first wave installations of version 1706 from packages that have the following GUIDs:
This same update also applies to customers in the Configuration Manager Technology Adoption Program (TAP). Those customers need to run the SCCMTAP.exe utility to return sites to the production update ring.
Note on client versions
- The generally available version of Configuration Manager, version 1706 (Package GUID B7700D5C-D16F-40DA-BB0D-A8C5A90822B9) shows a client version of 5.00.8540.1000 in the Configuration Manager console. This update (Package GUID C81C693D-33CF-4497-BB40-D4801ABBF284), displays a client version of 5.00.8540.1007. However, both packages have the same client; this update rollup just uses a more specific versioning scheme.
You do not have to restart the computer after you apply this update.
Update replacement information
This update replaces update 4039380.
Additional installation information
- 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 the version of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
If a value of 1 (one) is returned, the site is up-to-date and has all the hotfixes applied on its parent primary site.
If a value of 0 (zero) is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.
If you use the Service Connection Tool, you have to specify the -downloadsiteversion or -downloadhotfix parameters to make sure this update is downloaded. Refer to Use the Service Connection Tool for System Center Configuration Manager for additional information.