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

Applies to: System Center Configuration Manager 1710

Summary


Release version 1710 of System Center Configuration Manager Current Branch contains fixes and feature improvements.

The "Issues that are fixed" list isn't 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.

Notes

Issues that are fixed and improvements


Configuration Manager console

  • The Configuration Manager console may close unexpectedly after it connects to the site server through a remote connection.

     

  • When the Configuration Manager console is started, an Event ID 1 message may be logged in the Application event log that resembles one of the following:

     

  • If a configuration baseline is moved from one folder to another folder, a duplicate of that baseline is created in the Configuration Manager console. Additional attempts to move one of the baselines results in an error message that resembles the following:

     

  • Displaying and searching for packages in the Configuration Manager console is slower than expected in an environment that has thousands of packages.

     

  • Site administrators who lack full administrative rights can no longer see application configuration policies in the Application Management node of the Configuration Manager console. This issue only affects policies that were created before the site is upgraded; new policies are available in the console.

     

  • The Define Custom Colors button is unavailable in the Software Center client settings. Additionally, the company name and colors that are selected for the computer restart window aren't applied.

     

  • The "View Passcode" option isn't available on the Remote Devices Actions menu when viewed from the Primary Devices screen.

     

  • PowerShell script execution status isn't displayed in the Configuration Manager console. This issue occurs if the script output is longer than expected.

     

  • The Description field of the Content Locations tab in Package Properties doesn't correctly display Unicode characters.

     

Software Distribution and Content Management

  • Available applications that are deployed to users may be enforced incorrectly on a computer. This issue seems to occur randomly and is associated with the following conditions:

    • A frequent Application Deployment Evaluation Cycle (for example, every 30 minutes instead of the default 7 days).
    • The computer shuts down or restarts before the evaluation cycle is finished.
    • No user is logged on after the computer starts, and the prior evaluation cycle is finished.
  • Content that is associated with Automatic Deployment Rules (ADR) may not update on remote distribution points. This issue can occur if multiple ADR’s reference the same content for different packages. In this scenario, two (or more) packages may update the same content at the same time. This results in an update failure, and errors resembling the following are logged in the distmgr.log file:

     

Hardware Inventory

  • Hardware inventory processing fails for clients when the disk size or free space value is in the petabyte range. Errors resembling the following are logged in the dataldr.log file on the site server:

     

  • The WMI Provider Host process (wmiprvse.exe) may close unexpectedly on Windows Server 2016 computers that have the Configuration Manager client installed. This issue occurs if the collection of the SMS_Windows8ApplicationUserInfo class is enabled in hardware inventory.

     

  • Collection of the BIOSVersion property in the Win32_BIOS class is enabled for default hardware inventory data.

     

Client

  • Improvements are made to client data processing and deployment state messages to improve the upgrade results for pre-production clients.

     

  • Files in the "\CCM\Temp" folder on a Configuration Manager client may fill all available hard disk space. This issue occurs in Configuration Manager environments where support for express installation files (express updates) is enabled, and the BITS job to download associated content times out continuously. The DeltaDownload.log file on the client contains log sequences that resemble the following. Note the contentid_value placeholder changes as the sequence is repeated.

     

  • Clients may not download task sequence policy data when the management point and distribution points are co-located and the Windows BranchCache feature is enabled on the same server.

     

Site Systems

  • The Configuration Manager database upgrade process may fail because of errors associated with Asset Intelligence indexes. Errors resembling the following are recorded in the CMUpdate.log file.

    Note Table names may vary.

     

  • The DMPDownload.log file now records specific information, such as the thumbprint, of Microsoft Intune certificates. This simplifies troubleshooting certificate renewal scenarios.

     

  • The SMS Executive service may close unexpectedly when the Software Update Point role is installed on a server that's running Windows 2008 R2.

     

  • After Configuration Manager is upgraded, the site server may log errors resembling the following in the sitestat.log file for any remote distribution points.

    Note These entries can be ignored, and the distribution point role won't be deleted.

     

  • Errors resembling the following are recorded in the CMGService.log file on a server that has the cloud management gateway role installed.

    Note These errors can be safely ignored.

     

  • The BgbServer.log file may contain repeated entries that resemble the following:


    Note These entries are harmless. However, the volume of messages may result in important troubleshooting information rolling out of the current logs.

     

Operating System Deployment

  • When an operating system deployment task sequence is running on a computer, that computer may contact the Microsoft Update site for drivers or updates. This issue can occur even if the administrator has specified other drivers for use with the Apply Driver Package or Auto Apply Drivers tasks.

    This behavior can now be prevented by setting the new _TsDoNotConnectToWindowsUpdateInternetLocations task sequence variable to TRUE.

    This variable writes the DoNotConnectToWindowsUpdateInternetLocations DWORD value under the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
  • Computers that perform an in-place upgrade to a new version of Windows 10 by using an operating system deployment task sequence may be caught in a restart loop. This issue can occur because of a timing issue when the \SMSTSPostUpgrade folder is removed before other aspects of the task sequence are finalized. Specifically, the folder is removed before the following registry changes are made to values under HKEY_LOCAL_MACHINE\System\Setup.

    • The reg_sz value referencing setupcomplete.cmd under CmdLine is cleared.
    • The SetupType Dword value is changed from 2 to 0.
  • After Configuration Manager current branch version 1706 is upgraded, operating system deployment by using a Multicast-enabled distribution point (DP) fails if the client and DP are on different subnets. When this issue occurs, a log entry starting with the following text is recorded in the smsts.log on the client:

Hotfixes that are included in this update


  • 4022061 Policies that contain Android requirement rules are evaluated incorrectly for compliance against all devices in Configuration Manager

     

Dependency changes


The following dependent component that's included with Configuration Manager is updated to the specified version:

  • microsoft.windowsazure.storage.dll is updated to version 6.2.0.0

References


Learn about the terminology Microsoft uses to describe software updates.