System Center Configuration Manager Current Branch Update rollup KB4019926

System Center Configuration Manager Current Branch Update rollup KB4019926, version 1702.

Operating system deployment

  • Starting with System Center Configuration Manager, version 1702, unknown computers that are started from media or PXE may not find task sequences targeted to them. This issue may occur if the Previous button on the “Select a task sequence to run” page is selected on the unknown computer. 
  • The ImportMachineEntry method in the Configuration Manager Software Development Kit (SDK) fails when a computer record already exists, even if the OverwriteExistingRecord property is set to True.
  • The Data Source page of the Operating System Upgrade Package properties does not load in the Configuration Manager console, and you receive an error message that resembles the following:
    Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: startIndex
  • Multiple improvements were made to the client and the task sequence engine to ensure a more consistent transition into and out of provisioning mode.
  • Windows 10 mobile Enterprise devices are not upgraded by a Windows 10 edition upgrade policy.
  • The Create Task Sequence Media operation may fail if the Configuration Manager version 1702 client is installed on the computer being captured. If the final restart step does not complete, the computer can be manually restarted to complete the operation.
  • The Install Applications task sequence step fails for HTTPS-only workgroup clients after you upgrade to Configuration Manager, version 1702. Additionally, errors that resemble the following are recorded in the smsts.log file on the client:

Software distribution and content management

  • After a secondary site is recovered, all packages are redistributed to the secondary site if any of the package contents contained invalid metadata.
  • The distmgr.log file contains excessive entries for skipped drives on distribution points with many volumes when the NO_SMS_ON_DRIVE.SMS file is present. This could lead to problems in troubleshooting issues, as important information can roll out of the logs more quickly. Messages that resemble the following are logged in the distmgr.log file:

    Ignoring drive E:\. File E:\NO_SMS_ON_DRIVE.SMS exists.
    Ignoring drive F:\. File F:\NO_SMS_ON_DRIVE.SMS exists.
    Ignoring drive L:\. File L:\NO_SMS_ON_DRIVE.SMS exists.
    Ignoring drive C:\. File C:\NO_SMS_ON_DRIVE.SMS exists.

  • Device-targeted Volume Purchasing Program (VPP) applications that require an associated mobile application management (MAM) policy are not installed. The status of the deployment is listed as “Remediation failed” in the Configuration Manager console.

Site systems

  • Internet-based clients may not scan for software updates when they connect to a Software Update Point through the Cloud Management Gateway (CMG). This issue occurs when the CMG encounters an internal server error during communication with Windows Server Update Services (WSUS). Errors that resemble the following are recorded in the scanagent.log on the client:
    ScanJob({job_guid}): CScanJob::OnScanComplete -Scan Failed with Error=0x8024401f
  • The Delete Orphaned Client Deployment State Records task is not removed at the Central Administration Site (CAS) following an upgrade from Configuration Manager version 1602 to a later version.
  • Clients do not register with Management Point replicas. Errors resembling the following are recorded in the MP_ClientIDManager.log file:
    Parse a client ID request
    CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14
    SQL Server Name     : Server.Domain.Label
    SQL Database Name   : CM_P01_REPLICA
    Integrated Auth     : True
    MPDB Method         : ExecuteSP()
    MPDB Method HRESULT : 0x80040E14
    Error Description   : Could not find stored procedure ‘spGetLockState’.
    OLEDB IID           : {guid}
    ProgID              : Microsoft SQL Server Native Client 11.0
    SQL Server Name   : {sql_server}
    Native Error no.  : 2812
    Error State       : 62
    Class (Severity)  : 16
    Line number in SP : 1

Mobile device management and Microsoft Intune


Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

  • International station mobile equipment identity (IMEI) data for existing devices is not updated in Microsoft Intune-connected environments when their discovery data records are processed.
  • Deleting an obsolete or decommissioned device that is superseded during re-enrollment removes the capacity to manage the new device. Additionally, the Exchange allow/block state cannot be changed. This issue occurs because the Exchange Active Sync (EAS) device ID is the same for both the removed and superseding device. An Exchange Connector full resync will restore management of the new device.
  • If a managed device is not compliant with conditional access policies, a notification is sent to the user. If the user takes no action to make the device compliant (such as by enrolling in Microsoft Intune), the device is blocked from Microsoft Exchange access after 10 minutes. This 10-minute period is now configurable by creating the following registry value on the site server:


    DWORD name: CAGracePeriodInMinutes
    DWORD value: number_of_minutes

Configuration Manager console

  • The username font driver host\umfd-# is listed as a potential primary user when you edit the user device affinity for Windows 10 Creators Update computers.
  • The summary data that is displayed in the Distribution Point Configuration Status window is inconsistent between a CAS and Primary site. However, the details of the data are correct. To recover the Distribution Point that has this problem, run the following script:
    exec spRebuildContentDistribution 1
  • Device Health Attestation information is not updated for clients when double-byte character set languages are used.

Update information for System Center Configuration Manager, version 1702

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 were applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.
You might also like

Leave a Reply

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More