SCCM update 1610 Hotfix KB4010155

Blog SCCM

SCCM update 1610 Hotfix KB4010155

An update has been released for Microsoft’s System Centre Configuration Manager on the 16 of February 2017.

This update rollup for SCCM is to fix the following known bugs and issues;


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 Groupstab 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 Detailstab 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
  • 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.

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=Falseswitch in the Configuration.xml file for Office 365.
  • The Allow clients to use Microsoft Update as a fallback sourceoption 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 ComponentsWindows UpdateDefer 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’


How to install KB4010155 update rollup for SCCM 1610

Now that you have learnt about what are the fixes for this update rollup, now lets look at how to install this next. It is quite a simple process and should take you no longer than 30 minutes.


Step 1 – Open your SCCM console.

Open your SCCM console and navigate to Administration, then expand Cloud Services and finally highlight Updates and Servicing. Your SCCM should have downloaded the update and have it ready to deploy to your SCCM infrastructure.

KB4010155 SCCM step 1


Step 2 – Run Prerequisite Check

Highlight the Configuration Manager 1610 Hotfix (KB4010155), then right click and choose Run Prerequisite Check. 

KB4010155 SCCM step 2

The prerequisite check should take no longer than five minutes as sn the background, SCCM will run and verify that you are able to install this hotfix.

kb4010155-sccm-step-3

Refresh your console until you see that the Prerequisite check passed notification.

kb4010155 sccm step 4


Step 3 – Install Update Pack (KB4010155)

Hopefully the KB4010155 update pack is compatible with your SCCM environment and you are now ready for the installation. Again, highlight the update pack, right click and choose Install Update Pack.

KB4010155 SCCM step 2

Now the Configuration Manager Updates Wizard starts up. Click Next to proceed.

KB4010155 SCCM step 5

On the Client Updates Options window, you have the option to Upgrade without Validating or to Validate in pre-production collection. In this example, Im choosing to go ahead and update without validation. Click Next when ready to proceed.

KB4010155 SCCM step 6

The next window is the License Agreement window. You have to check the checkbox to accept the license terms and privacy statement before you can continue to install. Once you have done so, click Next to continue.

KB4010155 SCCM step 7

The Summary window details your installation options. Confirm these are correct before clicking on Next and continuing and then the installation will not start.

KB4010155 SCCM step 8

Now KB4010155 will install and update your SCCM environment. Once complete you will be presented with the following screen and KB4010155 will install in the background. Keep refreshing your SCCM console to confirm when it has udpated. You can additionally view the installation progress by looking at the CMUPDATE.LOG.

KB4010155 SCCM step 9