Release notes for Configuration Manager

Applies to: System Center 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 topic 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:

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

When using redistributable files from the CD.Latest folder, setup fails with a manifest verification error

When you run setup from the CD.Latest folder created for version 1606, and use the redistributable files included with that CD.Latest folder, setup fails with the following errors in the Configuration Manager Setup log:

ERROR: File hash check failed for defaultcategories.dll
ERROR: Manifest verification failed. Wrong version of manifest?

Workaround

Use one of the following options:

  • During Setup, choose to download the most current redistributable files from Microsoft. Use the latest redistributable files instead of the files included in the CD.Latest folder.
  • Manually delete the cd.latest\redist\languagepack\zhh folder, and then run Setup again.

Setup command-line option JoinCEIP must be specified

Applies to: Configuration Manager version 1802

Starting in Configuration Manager version 1802, the Customer Experience Improvement Program (CEIP) feature is removed from the product. When automating installation of a new site from a command-line or unattended script, setup returns an error that a required parameter is missing.

Workaround

While it has no effect on the outcome of the setup process, include the JoinCEIP parameter in your setup command line.

Note

The EnableSQM parameter for console setup is not required.

Cloud service manager component stopped on site server in passive mode

Applies to: Configuration Manager version 1806

If the service connection point is colocated with a site server in passive mode, then deployment and monitoring of a cloud management gateway doesn't start. The cloud service manager component (SMS_CLOUD_SERVICES_MANAGER) is in a stopped state.

Workaround

Move the service connection point role to another server.

OS deployment

After passive site server is promoted, the default boot image packages still have package source on the previous active server

Applies to: Configuration Manager version 1810

If you have a site server in passive mode (server B), when you promote it to active, the content location for the default boot images continues to reference the previously active server (server A). If server A has a hardware failure, you can't update or change the default boot images.

Workaround

None

Software updates

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.

Workaround

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

Changing Office 365 client setting doesn't apply

Applies to: Configuration Manager version 1802

Deploy a client setting with Enable Management of the Office 365 Client Agent configured to Yes. Then change that setting to No or Not Configured. After updating policy on targeted clients, Office 365 updates are still managed by Configuration Manager.

Workaround

Change the following registry value to 0 and restart the Microsoft Office Click-to-Run Service (ClickToRunSvc):

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\Common\officeupdate]
"OfficeMgmtCOM"=dword:00000000

Mobile device management

Applies to: Configuration Manager version 1810 and earlier

When you create a new application of type App Package for iOS from App Store, the validator doesn't accept some valid URLs for the Location. Specifically, the iOS App Store doesn't require a value for the app name section of the URL. For example, both of the following links are valid and point to the same app, but the Create Application Wizard only accepts the first:

  • https://itunes.apple.com/us/app/app-name/id123456789?mt=8
  • https://itunes.apple.com/us/app//id123456789?mt=8

Workaround

When you create an iOS app that's missing the app name from the URL, add any value as if it were the app name to the URL. For example:

  • https://itunes.apple.com/us/app/any-string/id123456789?mt=8

This action allows you to complete the wizard. The app is still successfully deployed to iOS devices. The string you add to the URL appears as the Name on the General Information tab in the wizard. It's also the app's label in the Company Portal.

You can no longer deploy Windows Phone 8.1 VPN profiles to Windows 10

Applies to: Configuration Manager version 1710

You can't create a VPN profile, using the Windows Phone 8.1 workflow, which is also applicable to Windows 10 devices. For these profiles, the creation wizard no longer shows the Supported Platforms page. Windows Phone 8.1 is automatically selected on the back-end. The Supported Platforms page is available in the profile properties, but it doesn't display the Windows 10 options.

Workaround

Use the Windows 10 VPN profile workflow for Windows 10 devices. If this option isn't feasible for your environment, contact support. Support can help you add the Windows 10 targeting.