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

It is recommended to install the following hotfix before you install the update rollup to prevent an issue with clients getting stuck in Provisioning Mode.

For more information, see New deployments are unavailable in Software Center on Configuration Manager clients.

Client

• Internet-only clients can't connect to management points or distribution points when proxy auto-configuration is used, and they change networks without restarting. This is seen most frequently on notebook computers that are put into sleep or standby states when you move from one location to another.
  
  Messages resembling the following are recorded in the internetproxy.log file when the computer is active on the new network:
  Couldn't find proxy information for SYSTEM or currently logged on user.
  Either system or user is using auto proxy, skip checking.
  m_pCachedProxy, HRESULT=8000ffff
  Failed to get proxy for url 'https://dc.contoso.com/ccm_system/request'. Error 0x8000ffff
  This error condition can be resolved by restarting the SMS Agent Host (ccmexec) service, or the computer.
• The Content Transfer Manager component of the Configuration Manager client repeatedly checks for content after the client roams to a location without available distribution points. This may trigger increased CPU activity on the client.

Microsoft Intune and Mobile Device Management

• Communication between a Configuration Manager site server and the Microsoft Intune service may fail randomly. Errors that resemble the following are recorded in the dmpdownloader.log file:
  ERROR: DmpDownloader:AcknowledgeMessages: Failed to acknowledge messages..
  Exception: System.AggregateException: One or more errors occurred.
  ---> Microsoft.Management.Services.Common.ServiceTooBusyException: FromAsyncWithCancel was cancelled for service: https://intune_url/StatelessConnectorService -
  Operation ID (for customer support - Operation ID (for customer support): {guid} ---> System.TimeoutException:
• After integrating Lookout mobile threat protection with Microsoft Intune, Windows devices are incorrectly displayed in the Device Threat Protection Compliance Status (iOS/Android) charts in the Administrator Console.

Site systems

• The Microsoft.Management.Services.ClientManagementService.Host.exe process doesn't start if the Process ID (PID) assigned by Windows is greater than 32,767. If this occurs, errors that resemble the following are recorded in the SMS_DM_Enrollmentservice.log file:
  Determining if CMService is up and running
  CMService is not up and running, restarting it
  ERROR: \\server_name\Source\Software Updates\OS Deployment Software Updates\{guid}\EnrollmentService\Microsoft.Management.Services.ClientManagementService.Host.exe.config does not exist.
  ERROR: Handle Exception. System.IO.DirectoryNotFoundException…
• After you upgrade to Configuration Manager current branch, version 1610, the cloud management gateway connection point doesn't start. Restarting the SMS Executive service may resolve the issue. Errors that resemble the following are recorded in the SMS_Cloud_ProxyConnnector.log file:
  ERROR: Found exception Microsoft.ConfigurationManager.CommonBase.CMException: Worker assembly doesn't exist Microsoft.ConfigurationManager.CloudConnection.ProxyConnector, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.~~   at Microsoft.ConfigurationManager.TaskExecutionManager.TaskExecution.Initialize(String componentName)
• When you configure the SQL Server Service Broker for a database replica server, execution of the sp_BgbConfigSSBForRemoteService stored procedure fails.
• Installing the Service Connection Point on a computer that's not a site server triggers CPU usage of 100%.

Operating system deployment

• Deployment of the Windows 10 Anniversary Update (1607) to Windows 10 clients triggers a "0x80091007 (Hash value is not correct)"error. Even after you refresh the image content on distribution points, errors that resemble the following are recorded in the CAS.log file.
  Raising event:
  [SMS_CodePage(437), SMS_LocaleID(1033)]
  instance of SoftDistHashMismatchEvent

Software distribution and content management

• The transfer of package contents between sites over slow network connections fails intermittently.
• Every time content is sent to a distribution point, site control data is updated unnecessarily. This causes multiple site components to unexpectedly wake up for data processing.

Administrator console

• After you add a new boundary to the Default-Site-Boundary-Group, that group is no longer listed on the Boundary Groups tab of the boundary properties. After this update is installed, boundaries cannot be added to the Default-Site-Boundary-Group.
• Individual threat details are not displayed as expected on the Device Threat Protection Details tab of the Devices screen in the Administrator console.
• The UpdatesDeployment.log file contains errors that resemble the following:
  Failed to get SDM CI for update (Site_{guid}/SUM_{guid}) from type store, error = 0x80070002
  Failed to GetSupersededUpdatesFromDigest for the update
  These errors have no functional effect and can be ignored.
   
• After you upgrade to Configuration Manager current branch, version 1610, resolving conflicting records fails for non-mobile device clients. Errors that resemble the following are recorded in the DDM.log file:
  Processing file {filename}.PDR
  CClientRegistrationRecord::LoadRecord - Client registration record does not contain all required fields.
  CDiscoverDataManager::GetRegRecord - The registration record could not be loaded.  Bad RDR.
  Failed to read registration request file.
  Moving bad file {filename}.PDR to ...\inboxes\auth\ddm.box\regreq\BAD_DDRS\{filename}.PDR.
  CDiscoverDataManager::ProcessDDRs_PS - Moved bad DDR

Software updates

• When an Alternate Content Provider encounters an error or retry condition while downloading an Office 365 job, the client does not fall back to the default download system as expected.
• After you start installation of Office updates from Software Center, users do not receive a notification message to exit all open Office 365 applications. This behavior occurs even with the forceappshutdown=False switch in the Configuration.xml file for Office 365.
• The Allow clients to use Microsoft Update as a fallback source option doesn't work as expected when you use it in a software update deployment or automatic deployment rule (ADR). Clients don't fall back to Microsoft Update.
• Computers that are running Windows 10 Anniversary Update unexpectedly download Feature and Quality Updates from the Internet. This behavior occurs if the clients are using Configuration Manager for software updates, and either of the following Group Policy settings are also configured (enabled or disabled) under Windows Components, Windows Update, Defer Windows Updates:
  • Select when Feature Updates are received
  • Select when Quality Updates are received
  After this update is applied, an error message that resembles the following is recorded in the WUHandler.log file during a software update scan on the client:
  Group Policy for Windows Update for Business is configured. Please set all Group Policy for Windows Update for Business to 'Not Configured'

Software update packages can now be hosted on cloud-based distribution points.

This update is available for installation in the Updates and Servicing node of the Configuration Manager console. If the service connection point is in offline mode, you must reimport the update so that it's listed in the Configuration Manager console. See "Install Updates for System Center Configuration Manager" for detailed 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 that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')

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 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.

Prerequisites

You should have update 4016483 installed before you install this hotfix.

For more information, see the Updates for System Center Configuration Manager topic on TechNet.

Learn about the terminology Microsoft uses to describe software updates.