Release notes for Configuration Manager

08/17/2020

9 minutes to read





In this article

Applies to: Configuration Manager (current branch)

With Configuration Manager, product release notes are limited to urgent issues. These issues aren't yet fixed in the product, or detailed in a Microsoft Support knowledge base article.

Feature-specific documentation includes information about known issues that affect core scenarios.

This article contains release notes for the current branch of Configuration Manager. For information on the technical preview branch, see Technical Preview

For information about the new features introduced with different versions, see the following articles:

For information about the new features in Desktop Analytics, see What's new in Desktop Analytics.

Tip To get notified when this page is updated, copy and paste the following URL into your RSS feed reader: https://docs.microsoft.com/api/search/rss?search=%22release+notes+-+Configuration+Manager%22&locale=en-us

Set up and upgrade

Client automatic upgrade happens immediately for all clients

Applies to version 1910

If your site uses automatic client upgrade, when you update the site to version 1910, all clients immediately upgrade after the site updates successfully. The only randomization is when clients receive the policy, which by default is every hour. For a large site with many clients, this behavior can consume a significant amount of network traffic and stress distribution points.

For more information on affected versions, see Client update for Configuration Manager current branch, version 1910.

Applies to version 1910

If your site includes a site server in passive mode, you may lose inventory customizations when you update the site. The site doesn't currently synchronize the configuration.mof when you fail over the site servers.

To work around this issue, manually back up and restore the site's configuration.mof.

Setup prerequisite warning on domain functional level on Server 2019

Applies to version 1906

When installing the update for version 1906 in an environment with domain controllers running Windows Server 2019, the prerequisite check for domain functional level returns the following warning:

[Completed with warning]:Verify that the Active Directory domain functional level is Windows Server 2003 or later

To work around this issue, ignore the warning.

Azure AD user discovery and collection group sync don't work after site expansion

Applies to version 1906

After you configure either of the following features:

Azure Active Directory user group discovery

Synchronize collection membership results to Azure Active Directory groups

If you then expand a standalone primary site to a hierarchy with a central administration site, you'll see the following error in SMS_AZUREAD_DISCOVERY_AGENT.log:

Could not obtain application secret for tenant xxxxx. If this is after a site expansion, please run "Renew Secret Key" from admin console.

To work around this issue, renew the key associated with the app registration in Azure AD. For more information, see Renew secret key.

Role based administration

Security scopes for certain folders don't replicate from CAS to primary sites

Applies to version 1910

After upgrade to version 1910, security scopes for folders in user collections and device collections don't get replicated from the CAS to primary sites.

Application management

Unable to get certificate for PowerShell error when deploying Microsoft Edge, version 77 and later

Applies to: Configuration Manager version 1910

If you are running the Configuration Manager console on an OS where the language is Swedish, Hungarian, or Japanese, you'll receive the following error when deploying Microsoft Edge, version 77 and later:

Unable to get certificate for Powershell

This error occurs because a scripts folder doesn't exist under the AdminConsole\bin directory for Swedish, Hungarian, or Japanese languages. The scripts folder is localized in these OS languages.

To work around this issue, create a folder called scripts in the AdminConsole\bin directory. Copy the files from your localized folder to the newly created scripts folder. Deploy Microsoft Edge, version 77 and later once the files have been copied.

OS deployment

Client policy error when you deploy a task sequence

Applies to: Configuration Manager version 2006 early update ring

When you deploy a task sequence to a client, a required task sequence doesn’t install at the deadline, and an available task sequence doesn’t appear in Software Center. You see status message 10803 with a description similar to the following error message:

The client failed to download policy. The data transfer service returned "BITS error: 'The server's response was not valid. The server was not following the defined protocol. (-2145386469).

This issue occurs when you configure the management point for HTTPS, and the device uses Configuration Manager client version 1906 or earlier.

To work around this issue, update the Configuration Manager client on the device to version 1910 or later.

Task sequences can't run over CMG

Applies to: Configuration Manager version 2002

There are two instances in which task sequences can't run on a device that communicates via a cloud management gateway (CMG):

You configure the site for Enhanced HTTP and the management point is HTTP. To work around this issue, update to version 2006. Alternatively, configure the management point for HTTPS.

You installed and registered the client with a bulk registration token for authentication. To work around this issue, update to version 2006. Alternatively, use one of the following authentication methods: Pre-register the device on the internal network Configure the device with a client authentication certificate Join the device to Azure AD



Security roles are missing for phased deployments

Applies to: Configuration Manager versions 1810, 1902

The OS Deployment Manager built-in security role has permissions to phased deployments. The following roles are missing these permissions:

Application Administrator

Application Deployment Manager

Software Update Manager

The App Author role may appear to have some permissions to phased deployments, but shouldn't be able to create deployments.

A user with one these roles can start the Create Phased Deployment wizard, and can see phased deployments for an application or software update. They can't complete the wizard, or make any changes to an existing deployment.

To work around this issue, create a custom security role. Copy an existing security role, and add the following permissions on the Phased Deployment object class:

Create

Delete

Modify

Read

For more information, see Create custom security roles

Desktop Analytics

An extended security update for Windows 7 causes them to show as Unable to enroll

Applies to: Configuration Manager versions 2002 and earlier

The April 2020 extended security update (ESU) for Windows 7 changed the minimum required version of the diagtrack.dll from 10586 to 10240. This change causes Windows 7 devices to show as Unable to enroll in the Desktop Analytics Connection Health dashboard. When you drill down to the device view for this status, the DiagTrack service configuration property displays the following state: Connected User Experience and Telemetry (diagtrack.dll) component is outdated. Check requirements.

No workaround is required for this issue. Don't uninstall the April ESU. If otherwise properly configured, the Windows 7 devices still report diagnostic data to the Desktop Analytics service, and still show in the portal.

If you use hardware inventory for distributed views, you can't onboard to Desktop Analytics

Applies to: Configuration Manager version 1902 with update rollup, and version 1906

If you have a hierarchy, and enable Hardware inventory site data for distributed views on any site replication links, after you configure the Desktop Analytics connection in Configuration Manager you'll see the following error in M365UploadWorker.log:

Unexpected exception 'System.Data.SqlClient.SqlException' Remote access is not supported for transaction isolation level "SNAPSHOT".: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action'1 wrapCloseInAction)

To work around this issue, disable Hardware inventory site data for distributed views on every site replication link.

Console unexpectedly closes when removing collections

Applies to: Configuration Manager version 1902 with update rollup

After you connect the site to Desktop Analytics, you can Select specific collections to synchronize with Desktop Analytics. If you remove a collection and apply the changes, immediately adding a new collection causes an unhandled exception. The console unexpectedly closes.

To work around this issue, when you remove a collection, select OK to close the properties window. Then open the properties again to add a new collection on the Desktop Analytics Connection tab.

Pilot status tile shows some devices as 'undefined'

Applies to: Configuration Manager version 1902 with update rollup

When you use the Configuration Manager console to monitor your pilot deployment status, pilot devices that are up-to-date on the target version of Windows for that deployment plan show as undefined in the Pilot status tile.

These undefined devices are up-to-date with the target version of the OS for that deployment plan. No further action is necessary.

Cloud services

Azure service for US Government cloud shows as public cloud

Applies to version 1910

If you create a connection to an Azure service, and set the Azure environment to the government cloud, the properties of the connection show the environment as the Azure public cloud. This issue is only a display problem in the console, the service is in the government cloud. To confirm the configuration, run the following SQL query on the site database:

Select Environment, Name, TenantID From AAD_Tenant_Ex

For the government cloud, the result of this query is 2 for the specific tenant.

Can't download content from a cloud management gateway enabled for TLS 1.2

Applies to version 1906, 1910 early update ring

If you enable a cloud management gateway (CMG) to function as a cloud distribution point and serve content from Azure storage and Enforce TLS 1.2, you may see content downloads fail.

The following errors show in the DataTransferService.log on the client:

Request to https://cmg1.contoso.com:443/downloadrestservice.svc/getcontentxmlsecure?pid=CMG00013&cid=CMG00013&tid=GUID:3fb5cf5d-28a5-4460-ab39-9184ca214369&iss=CMDP.IAAS2.CONTOSO.COM&alg=1.2.840.113549.1.1.11&st=2019-11-19T01:44:04&et=2019-11-19T09:44:04 failed with 400 Successfully queued event on HTTP/HTTPS failure for server 'cmg1.contoso.com'. Error sending DAV request. HTTP code 400, status 'Bad Request' GetDirectoryList_HTTP('https://cmg1.contoso.com:443/downloadrestservice.svc/getcontentxmlsecure?pid=CMG00013&cid=CMG00013&tid=GUID:3fb5cf5d-28a5-4460-ab39-9184ca214369&iss=CMDP.IAAS2.CONTOSO.COM&alg=1.2.840.113549.1.1.11&st=2019-11-19T01:44:04&et=2019-11-19T09:44:04') failed with code 0x87d0027e.​ Error retrieving manifest (0x87d0027e).

The following errors show in the CMGContentService.log on the server:

ERROR: Exception processing request. Microsoft.WindowsAzure.Storage.StorageException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.ComponentModel.Win32Exception: The client and server cannot communicate, because they do not possess a common algorithm...

To work around this issue:

Update the site to the globally available version of 1910, released on December 20, 2019. (If you previously updated to the 1910 early update ring, you need to update to this build when it's available.)

Alternatively, use a traditional cloud distribution point. That role doesn't enforce TLS 1.2, but is compatible with clients that require TLS 1.2.

Protection

BitLocker management appears in version 1906

Applies to version 1906

After November 21, 2019, if you update to version 1906 from version 1902 or earlier, the BitLocker management feature will be turned on and available. This feature is an optional feature starting in version 1910. It's unsupported in version 1906. If you try to use it in version 1906, you may experience unexpected results. If you don't use the feature, there's no impact.

To use the BitLocker management feature, update to version 1910.