Pre-release features in System Center 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 are still in active development and might receive changes until they move out of the pre-release category.
Before you can use pre-release features, you must give consent to use Pre-release features from within the Configuration Manager console before you can select and enable their use.
Giving consent is a one-time action per hierarchy that cannot be undone. Until you give consent, you cannot enable new pre-release features included with updates. After you turn on a pre-release feature, you cannot turn it off.
To give consent, in the console go to Administration > Site Configuration > Sites, and then choose Hierarchy Settings. On the General tab, choose Consent to use 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: You can enable pre-release features from within the Updates and Servicing Wizard when you are installing the update. To do so, select the pre-release features as you would any other feature.
Optionally, you can wait to enable a pre-release feature later from the Administration > Updates and Servicing > Features node of the console. In the Features node choose the feature and then choose Turn on. This option is grayed out until you give consent. (Prior to version 1702, Updates and Servicing was under Administration > Cloud Services.)
- If you have not given consent: When you're installing an update, pre-release features are visible in the Updates and Servicing Wizard but are grayed out and cannot be enabled. After the update is installed, you can view these features in the Features node. However, you cannot enable them until after you have given consent in Hierarchy Settings.
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, but it can take up to 30 minutes to complete, depending on the HMAN processing cycle. After the change is processed, you must restart the console before you can view new UI related to that feature.
The following pre-release features are available:
|Feature||Added as pre-release||Added as a full feature|
|Support for Cisco AnyConnect 4.0.07x and later for iOS||Version 1802||Version 1802 with update 4163547|
|Phased Deployments||Version 1802|
|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|