Pre-release features in Configuration Manager
Applies to: System Center Configuration Manager (Current Branch)
Pre-release features are features that are in the current branch for early testing in a production environment. These features are fully supported, but still in active development. They might receive changes until they move out of the pre-release category.
Before using pre-release features, give consent to use pre-release features. Giving consent is a one-time action per hierarchy that you can't undo. Until you give consent, you can't enable new pre-release features included with updates. After you turn on a pre-release feature, you can't turn it off.
In the Configuration Manager console, go to the Administration workspace, expand Site Configuration, and select the Sites node.
Click Hierarchy Settings in the ribbon.
On the General tab of Hierarchy Settings Properties, enable the option to Consent to use pre-release features. Click OK.
Enabling pre-release features
When you install an update that includes pre-release features, those features are visible in the Updates and Servicing Wizard with the regular features included in the update.
If you have given consent
In the Updates and Servicing Wizard, enable pre-release features. Select the pre-release features as you would any other feature.
Optionally, wait to enable pre-release features later from the Features node under Updates and Servicing in the Administration workspace. Select a feature, and then click Turn on in the ribbon. Until you give consent, this option isn't available for use.
If you haven't given consent
In the Updates and Servicing Wizard, pre-release features are visible but you can't enable them. After the update is installed, these features are visible in the Features node. However, you can't enable them until you give consent.
In a multi-site hierarchy, you can only enable optional or pre-release features from the central administration site. This behavior ensures there are no conflicts across the hierarchy.
If you gave consent at a stand-alone primary site, and then expand the hierarchy by installing a new central administration site, you must give consent again at the central administration site.
When you enable a pre-release feature, the Configuration Manager hierarchy manager (HMAN) must process the change before that feature becomes available. Processing of the change is often immediate. Depending on the HMAN processing cycle, it can take up to 30 minutes to complete. After the change is processed, restart the console before using the feature.
|Feature||Added as pre-release||Added as a full feature|
|Enhanced HTTP site system||Version 1806|
|Mobile apps for co-managed devices||Version 1806|
|Package Conversion Manager||Version 1806|
|Support for Cisco AnyConnect 4.0.07x and later for iOS||Version 1802||Version 1802 with update 4163547|
|Phased Deployments||Version 1802||Version 1806|
|Run Task Sequence Step||Version 1710||Version 1802|
|Windows Defender Exploit Guard||Version 1710||Version 1802|
|Device Health Attestation assessment for conditional access compliance policies||Version 1710||Version 1802|
|Create and run PowerShell scripts from the Configuration Manager console||Version 1706||Version 1802|
|Manage Microsoft Surface driver updates||Version 1706||Version 1710|
|Device Guard management with Configuration Manager||Version 1702|
|Task sequence content pre-caching||Version 1702||Version 1710|
|Check for running executable files before installing an application||Version 1702||Version 1706|
|Data Warehouse service point||Version 1702||Version 1706|
|Peer Cache for content distribution to clients||Version 1610||Version 1710|
|Cloud management gateway||Version 1610||Version 1802|
|Microsoft Operations Management Suite Connector||Version 1606||Version 1802|
|Servicing a cluster aware collection (service a server group)||Version 1602|
|Conditional access for PCs managed by System Center Configuration Manager||Version 1602||Version 1702|