Summary of changes in System Center Configuration Manager current branch, version 1610

S’applique à : System Center Configuration Manager (current branch - version 1610)

Summary


Release version 1610 of System Center Configuration Manager Current Branch contains many changes that are intended to prevent issues and improve features. The "Issues that are fixed" list is not comprehensive but does include the items that our product development team believes are the most relevant to our broad customer base. Many of these changes are in response to customer feedback about product issues and ideas for product improvement. Version 1610 is available as an in-console update to be installed at the top-most site in a hierarchy. For more information, see Checklist for installing update 1610 for System Center Configuration Manager.

Issues that are fixed

Asset Management

  • The upgrade process to Configuration Manager, current branch, may fail if there's a custom inventory class that matches the name of an existing inventory class. Errors that resemble the following are recorded in the ConfigMgrSetup.log file:
    SQL MESSAGE: spExtRenewInvGroupExtractViews - Creating inventory extraction views.
    ERROR: Failed to execute SQL Server command, error <>~
    INFO: Executing SQL Server command: <exec dbo.spExtRenewInvGroupExtractViews>
    ERROR: Failed to create extraction views for system discovery data.
    *** [42S01][2714][Microsoft][SQL Server Native Client 11.0][SQL Server]There is already an object named 'v_GS_{class_name}_Versio0' in the database.
    *** exec dbo.spExtRenewInvGroupExtractViews
    ERROR: SQL Server error: [42S01][2714][Microsoft][SQL Server Native Client 11.0][SQL Server]There is already an object named 'v_GS_{class_name}_Versio0' in the database.

  • The Dataldr.log file now suggests a group to add to the IDMIF to help troubleshoot inventory processing failures.
  • After you upgrade to Configuration Manager, version 1606, The Active Directory System and Group discovery processes generates errors when they encounter an organizational unit (OU) that contains an apostrophe. Errors that resemble the following are logged in the Adsgdis.log or Adsysdis.log files:
    *** [42000][102][Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 's'.

  • Hardware inventory does not process at a management point from a client that reports either Capacity or Free Space values that are greater than 4,294,967,295 for the Win32_Volume class.

Client

  • User notifications won't display if the Windows shell (explorer.exe) does not start within 10 seconds of the start of SCNotification.exe.
  • After a notification of a pending computer restart is displayed on a client, the notification does not appear again if the user logs out and back in without restarting.
  • The Promote Pre-production client option is unavailable in the Configuration Manager console. This occurs if the user who is starting the console isn't the same user who installed Configuration Manager, or is a Full Administrator of the site through group membership instead of direct membership.
  • The Client Cache Settings option isn't saved when you create a new custom client device setting that also contains the Client Policy option.
  • Using the Suspend BitLocker PIN entry on a restart client setting may cause BitLocker to remain suspended after the restart. This occurs randomly because of an incorrect flag that is set on the client. When this occurs, BitLocker must be enabled outside this client setting. The following sequence in the RebootCoordinator.log file indicates this issue:
    Suspended bit-locker protectors on system volume
    Bitlocker is not enabled or PIN protector is not enabled. No need to suspend.
    <client computer restarts>
    Didn't suspended bit-locker. Do nothing and return.


Software distribution and content management

  • After you recover a secondary site without a database backup, content is redistributed to all distribution points for that site.
  • During Configuration Manager client installation, the Client Cache setting is reset if the SMSClient.mof file does not compile. This causes the cache set to a path of “C:\CCM\Cache” and a size of 250 MB. An error that resembles the following is logged in the CCMSetup.log file on the client:
    MSI: Setup was unable to compile the file SmsClient.mof
    The error code is 80041002

  • Content distribution to Pull Distribution points fails if the content is referenced in more than one package and if it supersedes or is superseded by other content. Errors that resemble the following are recorded in the PkgXferMgr.log file:
    GeneratePullDPXMLNotification (( SELECT [dbo].[fnGetPullDPXMLNotification]('pkgid', 2,...
    *** [21000][512][Microsoft][SQL Server Native Client 11.0][SQL Server]Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.


Microsoft Intune and mobile device management

  • After you select the Send Sync Request option under Remote Device Actions for a mobile device, you receive an error message that resembles the following:
    Msg 535, Level 16, State 0, Line 3
    The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.

    After you dismiss this error message, there are no devices listed in the All Mobile Devices page. This error occurs when the time difference between the last synchronization request and the last active time of the device exceeds approximately 50 days.
  • The Compliant and Noncompliant Applications (iOS) page may freeze after the URL is completed for an application in the Compliant or Noncompliant applications list.
  • Debug-level logging for the Service Connection Point (Dmpuploader.log) is revised to display the return code for some error conditions.

Site systems

  • The DMPdownloader.log is filled with the following message that is repeated every 5 minutes:
    Check whether the site has intune subscription

    The presence of this repeated entry can cause useful information to be replaced in the current log file.
  • The Setup Downloader (SetupDL.exe) lets you use only a path that has up to 100 characters instead of the operating system limit of 255 characters.
  • The prerequisite check in the Updates and Servicing node may seem to freeze. The ConfigMgrPrereq.log stops at the “Checking Prerequisites” entry. This can occur during version upgrades, such as from version 1602 to 1606.
  • The prerequisite checker is updated to warn you when unsupported SQL Server versions are used for a site database.
  • The ConfigurationFlags property in Task Sequence XML policy data contains different information between sites. This results in a hash mismatch that's observed when clients try to download policy data from a site to which they aren't assigned. Error messages that resemble the following are logged in the PolicyAgent.log file on the client:
    Raising event:
    instance of CCM_PolicyAgent_PolicyDownloadFailed
    {
    ClientID = "GUID:{client_guid}";
    DateTime = "{date_time}";
    DownloadErrorInfo =
    instance of CCM_HttpDownloadMethod_ErrorInfo
    {
    HttpStatusCode = 404;
    HttpStatusText = "Not Found";
    };


Operating system deployment

  • The update status is displayed incorrectly for an operating system image that has multiple indexes. This occurs after updates are applied successfully by using the offline servicing feature. Error messages that resemble the following are logged in the OfflineServicingMgr.log file:
    *** [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ImageUpdateStatus_PK'. Cannot insert duplicate key in object 'dbo.ImageUpdateStatus'. The duplicate key value is ({package_id}, {update_id}).

  • The Windows 10 Edition Upgrade process fails on clients. Errors messages that resemble the following are logged in the CIAgent.log file:
    CIAgentJob({guid}): Client requesting CIAgentJob context info for key: PostRebootDetect
    0, HRESULT=87d00200
    CIAgentJob({guid}): HandleEvent failed (0x87d00207).

    Additionally, the PolicyPlatformClient.log contains error messages that resembles the following:
    ERROR: 0x80070002: Rule reference [Authority = [System Center Configuration Manager], PolicyName = […], Revision = 1, RuleName = […_EditionUpgrade_ProductKey_Rule_condition]] not found.

    Note These log entries were truncated for readability.
  • Trying to update a boot image with an optional component that has a dependent component fails. The update process progresses to between 20 and 30 percent before it stops. Additionally, you receive error messages that resemble the following:
    Error: The wizard detected the following problems when updating the boot image.
    • Failed to install required components into the boot image
    The SMS Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    {
    Description = "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";
    ErrorCode = 2152205056;
    ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    Operation = "ExecMethod";
    ParameterInfo = "SMS_BootImagePackage.PackageID=\"{package_id}\"";
    ProviderName = "WinMgmt";
    StatusCode = 2147749889;
    };

  • Task Sequences that contain either the Download Package Content or Upgrade Operating system tasks do not migrate from one site to another. Errors that resemble the following are logged in the Migmctrl.log file:
    ERROR: [Worker]: Entity Windows 10 1511 x64 In Place Upgrade with path SMS_TaskSequencePackage.PackageID='{package_id}}' failed with: Type SMS_TaskSequence_UpgradeOperatingSystemAction are not found.~~
    ERROR: [Worker]: Entity Download Package Content with path SMS_TaskSequencePackage.PackageID='{package_id}' failed with: Type SMS_TaskSequence_DownloadPackageContentAction are not found.~~


Configuration Manager console

  • The Configuration Manager console will exit unexpectedly when you deploy a compliance policy that does not have the Default security scope selected. The console will generate a System.InvalidOperationException exception that includes options to Abort, Retry, or Ignore.
  • After you upgrade to Configuration Manager 1606, the Edit and Remove buttons on the Supersedence tab of applications properties are disabled for some Windows application packages (.appx). This occurs when you select a superseded application in the Properties window.
  • Sorting the list of software inventory file types in the Configure Client Setting window causes the wrong item to be selected.
  • The Configuration Manager console may exit unexpectedly when you create a custom client device client setting. Additionally, you receive an unhandled exception message that resembles the following:
    Not found ,property = EnableExpressUpdates


Remote Control

  • Keyboard Translation for remote control is now off by default.

Software Updates Management

  • Office 365 Software update files for Portuguese are downloaded as Portuguese - Brazilian.

Hotfixes that are included in this update

The following hotfixes released for version 1606 are included in System Center Configuration Manager, version 1610:

  • 3186654 Description of Update Rollup 1 for System Center Configuration Manager current branch, version 1606
  • 3169945 Task Sequences or programs have an incorrect status in System Center Configuration Manager
  • 3183710 The Install Application task does not use content from the Pre-staged media in System Center Configuration
  • 3192616 Update to add Apple iOS 10 to the Supported Platforms list for System Center Configuration Manager, version 1606
  • 3207852 Update for authentication certificate in System Center Configuration Manager Asset Intelligence is available
  • 3202796 Devices enrolled in mobile device management are decommissioned in System Center Configuration Manager
  • 3205787 SMS_Executive service crashes when a SQL certificate can’t be found