Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

Summary

This article describes the issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1702.

↑ Back to the top


Issues that are fixed

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. The SMSTS.log shows the following error:

    There are no task sequences available to this computer. Please ensure you have at least one task sequence advertised to this computer"
    Unspecified error (Error: 80004005; Source: Windows)


    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:
    Notice:
    System.ArgumentOutOfRangeException
    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:

    Policy Evaluation failed, hr=0x87d00269
    MP list missing in WMI after policy evaluation

     

After the update is installed on site servers, any operating system boot images should be updated. To update boot images, follow these steps:

  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select Update Distribution Points.

    Note This action updates all distribution points and may have an adverse effect on environments that contain many distribution points.
  5. Repeat steps 3 and 4 for all boot images that were previously distributed.

For more information about how to update boot images, see the Manage Boot Images with System Center Configuration Manager topic in the Configuration Manager documentation.

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
    =======================================
    MP_ClientIDManager
    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : ServerName
    SQL Database Name   : DatabaseName
    Integrated Auth     : True
    MPDB ERROR - EXTENDED INFORMATION
    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
    MPDB ERROR - INFORMATION FROM DRIVER
    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

  • 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:
    Registry location: HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\COMPONENTS\SMS_EXCHANGE_CONNECTOR

    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 on the Central Administration Site (CAS:
    exec spRebuildContentDistribution 1
  • Device Health Attestation information is not updated for clients when double-byte character set languages are used.

↑ Back to the top


Update information for System Center Configuration Manager, version 1702

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 is listed in the Configuration Manager console. See Install in-console 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')

Note

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

↑ Back to the top


File information

File attributes

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

 For System Center Configuration Manager current branch, version 1702

File name File version File size Date Time Platform
Adaloperationprovider.dll 5.0.8498.1711 103,320 12-Apr-2017 01:50 x64
Adaloperationprovider.mof Not applicable 1,521 12-Apr-2017 01:50 Not applicable
Adminui.azureservices.dll 5.1702.1112.1004 246,184 12-Apr-2017 01:50 x86
Adminui.bootimage.dll 5.1702.1112.1004 404,384 12-Apr-2017 01:50 x86
Adminui.cloudsubscriptionsignin.dll 5.1702.1112.1004 69,048 12-Apr-2017 01:50 x86
Adminui.collectionproperty.dll 5.1702.1112.1004 1,413,552 12-Apr-2017 01:50 x86
Adminui.createapp.dll 5.1702.1112.1004 428,448 12-Apr-2017 01:50 x86
Adminui.editionupgrade.dll 5.1702.1112.1004 75,688 12-Apr-2017 01:50 x86
Adminui.enrollmenthelper.dll 5.1702.1112.1004 47,016 12-Apr-2017 01:50 x86
Adminui.osdcommon.dll 5.1702.1112.1004 437,664 12-Apr-2017 01:50 x86
Adminui.ps.dcm.dll 5.1702.1112.1004 224,664 12-Apr-2017 01:50 x86
Basesql.dll 5.0.8498.1711 311,192 12-Apr-2017 01:50 x64
Basesvr.dll 5.0.8498.1711 3,805,080 12-Apr-2017 01:50 x64
Baseutil.dll 5.0.8498.1711 1,440,664 12-Apr-2017 01:50 x64
Ccmctm.dll 5.0.8498.1711 879,000 12-Apr-2017 01:50 x64
Ccmeval.exe 5.0.8498.1711 1,088,920 12-Apr-2017 01:50 x64
Ccmsetup-sup.cab Not applicable 747,406 12-Apr-2017 01:50 Not applicable
Ccmsetup.cab Not applicable 9,650 06-Apr-2017 23:23 Not applicable
Ccmsetup.exe 5.0.8498.1711 1,952,944 12-Apr-2017 01:50 x86
Ccmsetupactiond.dll 5.0.8498.1711 1,824,664 12-Apr-2017 01:50 x64
Ccmutillib.dll 5.0.8498.1711 747,416 12-Apr-2017 01:50 x64
Certificate.dll 5.0.8498.1711 98,712 12-Apr-2017 01:50 x64
Certmgr.dll 5.0.8498.1711 454,552 12-Apr-2017 01:50 x64
Client.msi Not applicable 38,965,248 12-Apr-2017 01:50 Not applicable
Cloudproxyservice.cab Not applicable 9,378,338 12-Apr-2017 01:50 Not applicable
Cmupdate.exe 5.0.8498.1711 20,170,136 12-Apr-2017 01:50 x64
Complrelayendpoint.dll 5.0.8498.1711 320,408 12-Apr-2017 01:50 x64
Configmgr1702-client-kb4019926-x64.msp Not applicable 7,720,960 12-Apr-2017 01:50 Not applicable
Createtsmediaadm.dll 5.0.8498.1711 2,376,088 12-Apr-2017 01:50 x64
Ddm.dll 5.0.8498.1711 283,544 12-Apr-2017 01:50 x64
Ddrprov.dll 5.0.8498.1711 178,584 12-Apr-2017 01:50 x64
Distmgr.dll 5.0.8498.1711 1,048,984 12-Apr-2017 01:50 x64
Dmpdownloader.dll 5.0.8498.1711 33,688 12-Apr-2017 01:50 x64
Easdisc.dll 5.0.8498.1711 149,912 12-Apr-2017 01:50 x64
Exportcontent.dll 5.0.8498.1711 1,052,056 12-Apr-2017 01:50 x64
Fsp.msi Not applicable 3,948,544 12-Apr-2017 01:50 Not applicable
Hman.dll 5.0.8498.1711 983,960 12-Apr-2017 01:50 x64
Lsutilities.dll 5.0.8498.1711 854,424 12-Apr-2017 01:50 x64
Mcs.msi Not applicable 11,132,928 12-Apr-2017 01:50 Not applicable
Microsoft.configurationmanagement.applicationmanagement.wsfb.appconverter.dll 5.1702.1112.1004 41,488 12-Apr-2017 01:50 x86
Microsoft.configurationmanagement.exe 5.1702.1035.1002 389,568 12-Apr-2017 01:50 x86
Microsoft.configurationmanager.azureroles.proxyservice.dll 5.0.8498.1711 60,312 12-Apr-2017 01:50 x86
Microsoft.configurationmanager.cloudconnection.proxyconnector.dll 5.0.8498.1711 83,864 12-Apr-2017 01:50 x86
Microsoft.configurationmanager.dmpconnector.messagedownload.dll 5.0.8498.1711 103,320 12-Apr-2017 01:50 x86
Microsoft.configurationmanager.managedbase.dll 5.1702.1080.1003 211,408 12-Apr-2017 01:50 x86
Mp.msi Not applicable 11,288,576 12-Apr-2017 01:50 Not applicable
Offlineservicingmgr.dll 5.0.8498.1711 176,024 12-Apr-2017 01:50 x64
Pkgxfermgr.dll 5.0.8498.1711 377,240 12-Apr-2017 01:50 x64
Prereqcore.dll 5.0.8498.1711 3,827,096 12-Apr-2017 01:50 x64
Pulldp.msi Not applicable 9,699,328 12-Apr-2017 01:50 Not applicable
Pulldpcmgr.dll 5.0.8498.1711 764,824 12-Apr-2017 01:50 x64
Setupcompletetemplate.cmd Not Applicable 1,756 12-Apr-2017 01:50 Not applicable
Setupcore.dll 5.0.8498.1711 21,537,688 12-Apr-2017 01:50 x64
Setuprollbacktemplate.cmd Not applicable 1,757 12-Apr-2017 01:50 Not applicable
Sitecomp.exe 5.0.8498.1711 757,144 12-Apr-2017 01:50 x64
Sitestat.dll 5.0.8498.1711 122,776 12-Apr-2017 01:50 x64
Smp.msi Not applicable 6,021,120 12-Apr-2017 01:50 Not applicable
Smsdp.dll 5.0.8498.1711 3,415,960 12-Apr-2017 01:50 x64
Smsdpmon.exe 5.0.8498.1711 1,967,000 12-Apr-2017 01:50 x64
Smsfileisapi.dll 5.0.8498.1711 299,416 12-Apr-2017 01:50 x64
Smsprov.dll 5.0.8498.1711 12,673,432 12-Apr-2017 01:50 x64
Smspxe.dll 5.0.8498.1711 606,104 12-Apr-2017 01:50 x64
Smstsvc.exe 5.0.8498.1711 3,652,504 12-Apr-2017 01:50 x64
Smswdstp.dll 5.0.8498.1711 290,200 12-Apr-2017 01:50 x64
Tokenmgr.dll 5.0.8498.1711 456,600 12-Apr-2017 01:50 x64
Tscore.dll 5.0.8498.1711 2,828,184 12-Apr-2017 01:50 x64
Tsmanager.exe 5.0.8498.1711 332,696 12-Apr-2017 01:50 x64
Tsmbootstrap.exe 5.0.8498.1711 576,920 12-Apr-2017 01:50 x64
Update.sql Not applicable 175,962 12-Apr-2017 01:50 Not applicable
Windowsupdatesettings.resx Not applicable 6,475 12-Apr-2017 01:50 Not applicable
Windowsupdatesettings.xml Not applicable 11,994 12-Apr-2017 01:50 Not applicable
_smsprov.mof Not applicable 694,014 12-Apr-2017 01:50 Not applicable
Adaloperationprovider.dll 5.0.8498.1711 87,960 12-Apr-2017 01:50 x86
Adaloperationprovider.mof Not applicable 1,521 12-Apr-2017 01:50 Not applicable
Adminconsole.msi Not applicable 62,361,600 12-Apr-2017 01:50 Not applicable
Adminui.azureservices.dll 5.1702.1112.1004 246,184 12-Apr-2017 01:50 x86
Adminui.bootimage.dll 5.1702.1112.1004 404,384 12-Apr-2017 01:50 x86
Adminui.cloudsubscriptionsignin.dll 5.1702.1112.1004 69,048 12-Apr-2017 01:50 x86
Adminui.collectionproperty.dll 5.1702.1112.1004 1,413,552 12-Apr-2017 01:50 x86
Adminui.createapp.dll 5.1702.1112.1004 428,448 12-Apr-2017 01:50 x86
Adminui.editionupgrade.dll 5.1702.1112.1004 75,688 12-Apr-2017 01:50 x86
Adminui.enrollmenthelper.dll 5.1702.1112.1004 47,016 12-Apr-2017 01:50 x86
Adminui.osdcommon.dll 5.1702.1112.1004 437,664 12-Apr-2017 01:50 x86
Adminui.ps.dcm.dll 5.1702.1112.1004 224,664 12-Apr-2017 01:50 x86
Baseutil.dll 5.0.8498.1711 990,616 12-Apr-2017 01:50 x86
Ccmctm.dll 5.0.8498.1711 631,192 12-Apr-2017 01:50 x86
Ccmeval.exe 5.0.8498.1711 769,944 12-Apr-2017 01:50 x86
Ccmsetup-sup.cab Not applicable 747,406 12-Apr-2017 01:50 Not applicable
Ccmsetup.exe 5.0.8498.1711 1,952,944 12-Apr-2017 01:50 x86
Ccmsetup.msi Not applicable 3,014,656 12-Apr-2017 01:50 Not applicable
Ccmsetupactiond.dll 5.0.8498.1711 1,278,360 12-Apr-2017 01:50 x86
Ccmutillib.dll 5.0.8498.1711 559,512 12-Apr-2017 01:50 x86
Certificate.dll 5.0.8498.1711 80,792 12-Apr-2017 01:50 x86
Client.msi Not applicable 31,150,080 12-Apr-2017 01:50 Not applicable
Complrelayendpoint.dll 5.0.8498.1711 245,656 12-Apr-2017 01:50 x86
Configmgr1702-adminui-kb4019926-i386.msp Not applicable 4,984,832 12-Apr-2017 01:50 Not applicable
Configmgr1702-client-kb4019926-i386.msp Not applicable 5,742,592 12-Apr-2017 01:50 Not applicable
Consolesetup.exe 5.0.8498.1711 271,768 12-Apr-2017 01:50 x86
Createtsmediaadm.dll 5.0.8498.1711 1,687,448 12-Apr-2017 01:50 x86
Ddrprov.dll 5.0.8498.1711 140,184 12-Apr-2017 01:50 x86
Exportcontent.dll 5.0.8498.1711 782,232 12-Apr-2017 01:50 x86
Lsutilities.dll 5.0.8498.1711 632,216 12-Apr-2017 01:50 x86
Microsoft.configurationmanagement.applicationmanagement.wsfb.appconverter.dll 5.1702.1112.1004 41,488 12-Apr-2017 01:50 x86
Microsoft.configurationmanagement.exe 5.1702.1035.1002 389,568 12-Apr-2017 01:50 x86
Microsoft.configurationmanager.managedbase.dll 5.1702.1080.1003 211,408 12-Apr-2017 01:50 x86
Pulldp.msi Not applicable 7,127,040 12-Apr-2017 01:50 Not applicable
Pulldpcmgr.dll 5.0.8498.1711 584,600 12-Apr-2017 01:50 x86
Scclient.pages.dll 5.0.8498.1711 696,216 12-Apr-2017 01:50 x86
Setupcompletetemplate.cmd Not applicable 1,756 12-Apr-2017 01:50 Not applicable
Setuprollbacktemplate.cmd Not applicable 1,757 12-Apr-2017 01:50 Not applicable
Smsdp.dll 5.0.8498.1711 2,425,752 12-Apr-2017 01:50 x86
Smsdpmon.exe 5.0.8498.1711 1,316,760 12-Apr-2017 01:50 x86
Smsfileisapi.dll 5.0.8498.1711 247,192 12-Apr-2017 01:50 x86
Smspxe.dll 5.0.8498.1711 459,672 12-Apr-2017 01:50 x86
Tscore.dll 5.0.8498.1711 2,050,456 12-Apr-2017 01:50 x86
Tsmanager.exe 5.0.8498.1711 257,944 12-Apr-2017 01:50 x86
Tsmbootstrap.exe 5.0.8498.1711 440,728 12-Apr-2017 01:50 x86
Windowsupdatesettings.resx Not applicable 6,475 12-Apr-2017 01:50 Not applicable
Windowsupdatesettings.xml Not applicable 11,994 04-Apr-2017 23:57 Not applicable

 

↑ Back to the top


References

Learn about the terminology Microsoft uses to describe software updates.

↑ Back to the top


Applies to

This article applies to the following:

  • System Center Configuration Manager current branch, version 1702

↑ Back to the top


Keywords: kbQFE, kbfix, kbsurveynew, kbExpertiseInter

↑ Back to the top

Article Info
Article ID : 4019926
Revision : 42
Created on : 9/13/2018
Published on : 11/10/2018
Exists online : False
Views : 352