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

Summary

Release version 1706 of System Center Configuration Manager Current Branch contains many changes to help you avoid issues and many feature improvements.

The "Issues that are fixed" list is not inclusive of all changes. Instead, it highlights the changes that the product development team believes are the most relevant to the broad customer base for Configuration Manager. Many of these changes were made in response to customer feedback about product issues and product improvement.

Version 1706 is available as an in-console update that can be installed at the top-tier site in a hierarchy.

For installation information, see Checklist for installing update 1706 for System Center Configuration Manager.

For more information about the changes that are included in version 1706, see What’s new in version 1706 of System Center Configuration Manager.

Issues that are fixed

Configuration Manager console

• The Configuration Manager console may exit and return an unhandled exception when a collection in the Deploy Software Wizard is selected.

   

• New tabs may not appear in the Configuration Manager Console, or third-party extensions may not be displayed as expected. This occurs when either a Configuration Manager Console update or a third-party extension is applied. The most recently installed of these software packages might overwrite features of the other.

   

• An Azure Cloud Service cannot be removed from the Configuration Manager Console if an Azure Active Directory (AAD) tenant is removed first.

   

• The Configuration Manager Console may exit and return an unhandled exception when a new boundary group relationship is added and the Console searches for a specific boundary group.

   

• The View Passcode option is missing from the Remote Device Actions shortcut menu when it is accessed through a user’s Primary Device in the Configuration Manager Console.

   

• The Configuration Manager Console may exit and return an unhandled exception when it imports drivers.

   

• The Office 365 Client Installation Wizard exits unexpectedly if the default language of the site server operating system is not a supported Office 365 language.

   

Site Systems

• After the Enable REST endpoint for all providers on this site option is selected, the REST provider does not start. Errors that resemble the following are recorded in the SMS_REST_PROVIDER.log file.

  ERROR: Failed to create com TaskExecution with error = 0X80040154

   

• Restarting the SQL Server Service causes a connection failure for the client notification server that is installed on a Management Point in an untrusted forest. Errors that resemble the following are recorded in the BgbServer.log file:

  Retrieving online resync flag from database...
  
  ERROR: SQL exception when retrieve resync flag from DB. Exception: System.Data.SqlClient.SqlException (0x80131904): The connection is broken and recovery is not possible.

   

   

• The Add Site System Roles Wizard does not allow you to specify a SQL Server port number lower than 1023 when you add a Data Warehouse Service Point. Similarly, the wizard incorrectly allows you to specify invalid port number 655536.

   

Software Distribution and Content Management

• A required deployment for the App-V client version 5.1.86.0 that is targeted to Windows 7 Service Pack 1 (SP1) fails during installation if the “Interactive Services Detection” service is running.

   

• After you remove and then add a different supersedence relationship, the Allow users to see deployments for this application and all applications that it supersedes in Application Catalog option is not enabled. Therefore, it is unavailable in the properties for a deployment.

  This could cause the installation of two versions of an application.

   

• The Automatically upgrade any superseded versions of this application option is listed incorrectly as enabled when a deployment is viewed by an administrator who has the Read-only Analyst role assigned.

   

• The Executable File Name field is case-sensitive on the Install Behavior tab of deployment type properties.

   

• The Create Deployment Type wizard does not allow you to directly input (that is, copy and paste) a Windows Application package URL.

   

Software Metering

• The end time value for a metered application is recorded incorrectly for an unexpected computer restart. In this scenario, the client may submit a software metering data file that has an end time value that is before the recorded start time. When this occurs, all metering data that is contained in that file is rejected by the site server.

   

Hardware Inventory

• The Block Size, Capacity, and Free Space values of the Win32_Volume class are reported incorrectly in kilobytes instead of megabytes.

   

• Additional attributes enabled for default hardware inventory classes are disabled after you upgrade to Configuration Manager current branch, version 1702.

   

Client

• Client upgrades may fail and return errors that resemble the following entry in the ccmsetup.log:

  MSI: Setup was unable to compile the file SmsClient.mof

  The error code is 80041002

  This occurs when an earlier version of the client provider is loaded by the Windows Management Instrumentation (WMI) provider host during a client upgrade.

   

• The Configuration Manager client may not be upgraded if the co-located Pull Distribution Point is upgraded first.

   

Site Administration

• Virtual machines that are created in Azure Resource Manager are rediscovered as new objects in Configuration Manager when they are deallocated and reallocated.

   

• Administrative users who have the Asset Manager or Company Resource Access Manager roles assigned are unable to synchronize Device Enrollment Program (DEP) devices.

   

• Newly enrolled devices may not be discovered by the Exchange Connector if an associated user is not discovered at the same time. Errors that resemble the following are recorded in the Easdisc.log file:

  ERROR: [MANAGED] Exception: Index was out of range. Must be non-negative and less than the size of the collection.~~Parameter name: index~~

  ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131502~

   

• When the “AllSigned” PowerShell execution policy is enabled for a task sequence, that task sequence may hang indefinitely.

   

Reporting

• The localized French version of the “List of Devices by Conditional Access State” report does not run. The generation of the report fails and returns an exception.
  

   

Endpoint Protection

• The Create Certificate Profile wizard may exit when you try to create a System Center Endpoint Protection (SCEP) certificate profile. An exception that resembles the following is displayed on-screen:

  System.FormatException: Input string was not in a correct format.

   

Operating System Deployment

• The issue that is described in the following Configuration Manager OSD Support Team Blog article is fixed.

  When deploying Windows 7 the Apply Driver Package task fails when the ADK is upgraded to the ADK 10 1607 or newer

   

   

• Microsoft Secure Boot Cmdlets (WinPE-SecureBootCmdlets) are now available as an optional component in the boot image properties.
   

   

• The User notification message text fields in Task Sequence properties are no longer marked as required.
   

   

• During execution of an Operating System Deployment task sequence, the client computer no longer access the Microsoft Update site to download updates and drivers. Access to Microsoft Update is reset to default after the task sequence is finished. This prevents computers from updating to drivers that were not approved as part of the deployment.
   

   

• Computers that use MAC addresses that are defined in the Duplicate Hardware Identifiers list do not receive mandatory Operating System Deployment task sequences as expected.
   

   

Software Updates

• Updates are listed in an incorrect order when they are sorted by Date Released in the Schedule Updates Wizard.
   

   

• The SMS_REPLICATION_CONFIGURATION_MONITOR throws a SQL connection pool time-out exception every minute if the SQL Database server has many CPU processors and multiple sites.
   

   

Hotfixes that are included in this update

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

• 4035759 Client update for System Center Configuration Manager current branch, version 1702

• 3205796 "System.InvalidOperationException" error when you create a configuration item for a mobile device
   

   

• 4034236 Installing an additional SMS Provider removes previous Provider information
   

   

• 4034237 The reference computer does not restart after you capture an operating system image
   

   

Dependency changes

The following dependent components that are included with Configuration Manager are updated to the specified versions:

• Silverlight is updated to version 5.1.50907.0
  

   

• The Visual C++ runtime redistributable file is updated to version 12.0.40660.0
  

   

• Json.net (newtonsoft.json.dll) is updated to version 6.0.3
  

   

References

SQL query times out or console slow on certain Configuration Manager database queries

System Center Configuration Manager Cmdlet Library changes for Current Branch 1706

What's new in version 1706 of System Center Configuration Manager

Learn about the terminology Microsoft uses to describe software updates.