Events
Nov 19, 11 PM - Nov 21, 11 PM
Gain in-demand skills with online sessions designed to meet the industry’s challenges head-on at Microsoft Ignite.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to: Configuration Manager (current branch)
Starting in Configuration Manager 2103, the Console extensions node allows you to start managing the approval and installation of console extensions used in your environment. Having extensions in the console doesn't make them immediately available. From a high level, the steps are:
After you approve an extension, when you open the console, you'll see a console notification. From the notification, you can start the extension installer, or use the Install option from the Console extensions node. After the installer completes, the console restarts automatically, and you can use the extension.
The old style of console extensions will start being phased out in favor of the new style since they're more secure and centrally managed. The new style of console extensions has the following benefits:
Important
If this setting is used, your old style extensions that aren't approved through the Console Extensions node will no longer be able to be used. The setting, Only allow console extensions that are approved for the hierarchy, is enabled
by default if you installed from the 2103 baseline image. The setting remains disabled
by default, if you upgraded from a version prior to 2103. If the setting was enabled in error, disabling the setting allows the old style extensions to be used again.
The Configuration Manager console needs to be able to connect to the administration service and the administration service needs to be functional.
(Introduced in version 2103)
The Console Extensions node is located under Administration > Overview > Updates and Servicing. Actions for console extensions are grouped in the ribbon and the right-click menu. Console extensions downloaded from Community hub will be shown here.
Actions for Console Extensions group:
Actions for All Sites group:
Classify group:
Local Extension group:
Note
https://developer.microsoft.com/en-us/microsoft-edge/webview2/#download-section
with the other redistributable files.Warning
If this setting is enabled
, your old style extensions that aren't approved through the Console Extensions node will no longer be able to be used. The setting, Only allow console extensions that are approved for the hierarchy, is enabled
by default if you installed from the 2103 baseline image. The setting remains disabled
by default, if you upgraded from a version prior to 2103. If the setting was enabled in error, disabling the setting allows the old style extensions to be used again.
There are three ways to get the new style of hierarchy approved console extensions into Configuration Manager:
Change the security scope for the extension. Changing the security scope is recommended for initial testing of an extension.
Approve the extension by selecting Approve Installation from the ribbon or right-click menu.
Install the extension on the local console by choosing Install.
Once the extension is installed, verify it displays and you can use it from the local console.
(Applies to Configuration Manager version 2107 or later)
Starting in Configuration Manager version 2107, you can choose to allow unsigned hierarchy approved console extensions. It's a best practice to always used signed extensions to minimize security risks and to confirm the authenticity of a console extension. However, in some cases you may need to allow unsigned console extensions due to an unsigned internally developed extension, or for testing your own custom extension in a lab. To allow import and install of unsigned hierarchy approved console extensions, you'll enable a hierarchy setting.
Note
Currently, when an unsigned extension isn't enabled for user notification, in the Console Extensions node, the Required column remains blank instead of populating a value of No.
(Introduced in 2111)
Starting in Configuration Manager version 2111, you can require a console extension to be installed before it connects to the site. After you require an extension, it automatically installs for the local console the next time an admin launches it. To require the installation of a console extension:
Users are notified when console extensions are approved for installation. These notifications occur for users in the following scenarios:
In the upper-right corner of the console, select the bell icon to display Configuration Manager console notifications.
The notification will say New custom console extensions are available.
Select the link Install custom console extensions to launch the install.
When the install completes, select Close to restart the console and enable the new extension.
Note
When you upgrade to Configuration Manager 2107, you will be prompted to install the WebView2 console extension again. For more information about the WebView2 installation, see the WebView2 installation section if the Community hub article.
(Introduced in 2111)
Starting in version 2111, the site creates status messages for events related to console extensions. Status messages improve the visibility and transparency of console extensions that are used with your site. Use these status messages to make sure your site uses known and trusted console extensions. The status messages have IDs from 54201 to 54208. They all include the following information:
There are four categories of message events:
For example, the description of status message ID 54201 is User "%1"
made console extension with ID "%2"
and version "%3"
required.
Events
Nov 19, 11 PM - Nov 21, 11 PM
Gain in-demand skills with online sessions designed to meet the industry’s challenges head-on at Microsoft Ignite.
Register now