Enable software metering on clients

However, those devices will still need Manage Endpoint Protection client on client computers enabled. Choose Yes to install and enable the Endpoint Protection client on client computers that aren't already running the client. Windows 10 or later clients don't need to have the Endpoint Protection agent installed. If the Endpoint Protection client is already installed, choosing No doesn't uninstall the Endpoint Protection client.

To uninstall the Endpoint Protection client, set the Manage Endpoint Protection client on client computers client setting to No. Then, deploy a package and program to uninstall the Endpoint Protection client. Set this option to Yes to override typical installation behaviors with maintenance windows. This setting meets business requirements for the priority of system maintenance for security purposes.

Choose Yes to disable the write filter on the Windows Embedded device, and restart the device. This action commits the installation on the device. If you choose No , the client installs on a temporary overlay that clears when the device restarts. In this scenario, the Endpoint Protection client doesn't fully install until another installation commits changes to the device. This configuration is the default.

Choose Yes to suppress a computer restart after the Endpoint Protection client installs. If the Endpoint Protection client requires a computer restart and this setting is No , then the computer restarts regardless of any configured maintenance windows. If a restart is necessary after the Endpoint Protection client installs, this setting specifies the number of hours that users can postpone the required restart.

This setting requires that you disable the following setting: Suppress any required computer restarts after the Endpoint Protection client is installed. Choose Yes if you want Configuration Manager to install only the initial definition update on client computers. This setting can be helpful to avoid unnecessary network connections, and reduce network bandwidth, during the initial installation of the definition update. Select Set Interval to specify the length of time, in minutes or hours, that legacy mobile devices poll for policy.

These devices include macOS. Enter the number of minutes that modern devices poll for policy. This setting is for Windows devices that are managed through on-premises mobile device management MDM. To enable user-based enrollment of legacy devices, set this option to Yes , and then configure the following setting:. To enable user-based enrollment of modern devices, set this option to Yes , and then configure the following setting:.

By default, this setting is Yes. For more information, see Introduction to hardware inventory. Select Schedule to adjust the frequency that clients run the hardware inventory cycle.

By default, this cycle occurs every seven days. Specify the maximum number of minutes for the Configuration Manager client to randomize the hardware inventory cycle from the defined schedule. This randomization across all clients helps load-balance inventory processing on the site server. You can specify any value between 0 and minutes.

By default, this value is set to minutes 4 hours. Specify the maximum size, in kilobytes KB , allowed for each custom Management Information Format MIF file that the client collects during a hardware inventory cycle. The Configuration Manager hardware inventory agent doesn't process any custom MIF files that exceed this size. You can specify a size of 1 KB to 5, KB.

By default, this value is set to KB. This setting doesn't affect the size of the regular hardware inventory data file. For more information, see How to configure hardware inventory. Use this setting to specify whether to collect MIF files from Configuration Manager clients during hardware inventory. For a MIF file to be collected by hardware inventory, it must be in the correct location on the client computer.

By default, the files are located in the following paths:. Manage how Windows 8 and later computers use metered internet connections to communicate with Configuration Manager. Internet providers sometimes charge by the amount of data that you send and receive when you're on a metered internet connection. Allow : All client communications are allowed over the metered internet connection, unless the client device is using a roaming data connection.

Limit : The client only communicates over the metered internet connection for the following behaviors:. On an application deployment, enable the option to Allow clients on a metered Internet connection to download content after the installation deadline. This option is only available for deployments with a purpose of Required. If the client reaches the data transfer limit for the metered internet connection, the client no longer communicates with the site.

Block : When the device is on a metered internet connection, the Configuration Manager client doesn't try to communicate with the site. This option is the default. The client always permits software installations from Software Center, regardless of the metered internet connection settings.

If the user requests a software installation while the device is on a metered network, Software Center honors the user's intent. Client install and update both work when you configure this client setting to Allow or Limit. This behavior allows the client to stay current, but still manage the client communication on a metered network.

For more information, see About client installation parameters and properties. Set this option to Yes to enable power management on clients. For more information, see Introduction to power management. Choose Yes to let users of Software Center exclude their computer from any configured power management settings.

When you enable this setting, the client configures the power settings on the computer to allow the network adapter to wake up the device. If you disable this setting, the computer's network adapter can't wake up the device.

For more information about wake-up proxy, see Plan how to wake up clients. Don't enable wake-up proxy in a production network without first understanding how it works and evaluating it in a test environment. Wake-up proxy port number UDP : The port number that clients use to send wake-up packets to sleeping computers.

Keep the default port , or change the number to a value of your choice. This number must match the number in the site Properties. If you change this number in one place, it isn't automatically updated in the other place. Windows Defender Firewall exception for wake-up proxy : The Configuration Manager client automatically configures the wake-up proxy port number on devices that run Windows Defender Firewall.

Select Configure to specify the firewall profiles. If clients run a different firewall, manually configure it to allow the Wake-up proxy port number UDP. IPv6 prefixes if required for DirectAccess or other intervening network devices. Use a comma to specify multiple entries : Enter the necessary IPv6 prefixes for wake-up proxy to function on your network.

Select Configure to enable the Configuration Manager remote control feature. Optionally, configure firewall settings to allow remote control to work on client computers. Choose whether an admin can use remote control to access a client computer that is logged off or locked.

Only a logged-on and unlocked computer can be remotely controlled when this setting is disabled. Choose whether the client computer shows a message asking for the user's permission before allowing a remote control session.

Before transferring content from the shared clipboard in a remote control session, allow your users the opportunity to accept or deny file transfers. Users only need to grant permission once per session.

The viewer can't give themselves permission to transfer the file. Choose whether local admins on the server that starts the remote control connection can establish remote control sessions to client computers. Select Set Viewers to specify the names of the Windows users who can establish remote control sessions to client computers.

Configure this setting to Yes to show an icon on the client's Windows taskbar to indicate an active remote control session. Set this option to Yes to show a high-visibility session connection bar on clients, to indicate an active remote control session. Set this option to use sound to indicate when a remote control session is active on a client computer.

Select one of the following options:. Configure this setting to Yes to let Configuration Manager manage unsolicited Remote Assistance sessions. In an unsolicited Remote Assistance session, the user at the client computer didn't request assistance to start the session.

In a solicited Remote Assistance session, the user at the client computer sent a request to the admin for remote assistance.

Choose the level of access to assign to Remote Assistance sessions that are started in the Configuration Manager console. The user at the client computer must always grant permission for a Remote Assistance session to occur.

Set this option to Yes to add users specified in the permitted viewer list to the Remote Desktop local user group on clients. Set this option to Yes to use network-level authentication NLA to establish Remote Desktop connections to client computers. NLA initially requires fewer remote computer resources, because it finishes user authentication before it establishes a Remote Desktop connection. Using NLA is a more secure configuration. NLA helps protect the computer from malicious users or software, and it reduces the risk from denial-of-service attacks.

If you deploy the Company Portal to co-managed devices, configure this setting to Company Portal. This setting makes sure that notifications from Configuration Manager and Intune both launch the Company Portal.

If a Configuration Manager notification is for a scenario that the Company Portal doesn't support, selecting the notification launches Software Center. If you install the Company Portal on a co-managed device, but configure this setting to Software Center , then notifications from Configuration Manager launch Software Center.

Notifications from Intune launch the Company Portal. This behavior may be confusing to users to interact with different portals. The behavior of the Company Portal depends upon your co-management workload configuration.

For more information, see Use the Company Portal app on co-managed devices. Set this option to Yes , and then select Customize to configure Software Center settings for your organization.

This action opens the Software Center Customization window. You can choose from 48 basic colors, or define a custom color. By default, this color is Microsoft blue Red: 0, Green: , Blue: Foreground color for Software Center : Starting in version , configure a custom color for the foreground font.

By default, this color is white Red: , Green: , Blue: For some customers, their brand color doesn't work well with the default white font color for a selected item. This setting better supports these customers and improves accessibility. Select a logo for Software Center : Enable this setting, and then Browse to select an image to appear in Software Center.

The logo for Software Center has the following requirements:. Select a logo for notifications : Starting in version , enable this setting to display a logo with notifications on devices running Windows 10 or later. Because of how the image is used, it's separate from the Software Center logo. The logo for notifications has the following requirements:. Hide unapproved applications in Software Center : When you enable this option, user-available applications that require approval are hidden in Software Center.

Hide installed applications in Software Center : When you enable this option, applications that are already installed no longer show in the Applications tab. This option is enabled by default. Installed applications are still available for review under the Installation Status tab.

The application catalog is no longer supported. This link would appear on the Installation Status tab of Software Center. Choose which tabs should be visible in Software Center. To move a tab to Visible tabs list, select Add.

To move it to the Hidden tabs list, select Remove. Select Delete Tab to remove a custom tab. Select Edit tab to change the configuration of a custom tab.

Some website features may not work in a custom tab in Software Center. Make sure to test the results before deploying this to clients. The WebView2 browser control provides improved security and user experience. For example, more websites should work with these custom tabs without displaying script errors or security warnings.

If it's not already installed, the Configuration Manager client installs the Microsoft Edge WebView2 runtime fixed version on the device. Clients download the WebView2 redistributable installation file from the management point. The installer is over MB in size. If you need to enable this setting on a large number of clients, and are concerned about the effect of network usage, predeploy the WebView2 runtime as an application. Use the software distribution features of Configuration Manager to better control the content distribution and timing of software installation.

If you don't enable this option, Software Center uses the Windows built-in Internet Explorer browser control. Configure the Default application filter as either All or only Required applications. By default, it shows all applications. Software Center always uses your default setting. Users can change this filter, but Software Center doesn't persist their preference. Set the Default application view as either Tile view or List view.

By default, it uses the tile view. If a user changes this configuration, Software Center persists the user's preference in the future. For more information on the appearance of these settings, see the Software Center user guide. Configure a schedule for when Configuration Manager reevaluates the requirement rules for all deployments.

The default value is every seven days. This setting is more invasive to the local client than it is to the network or site server. A more aggressive reevaluation schedule negatively affects the performance of your network and client computers. Microsoft doesn't recommend setting a lower value than the default. If you change this value, closely monitor performance. Start this action from a client as follows: in the Configuration Manager control panel, from the Actions tab, select Application Deployment Evaluation Cycle.

This option is set to Yes by default. For more information, see Introduction to software inventory. Select Schedule to adjust the frequency that clients run the software inventory and file collection cycles. If you want to specify the types of file to inventory, select Set Types , and then configure the following options:.

If multiple custom client settings are applied to a computer, the inventory that each setting returns is merged. Select New to add a new file type to inventory. Once the clients get the new policy by default, every 60 minutes , the client will report the usage depending of the enabled software metering rules.

For reporting, you have some built-in reports to give you a great information about the Software Metering. In our scenario, we will use Computers that have run a specific metered software program report. Select it and click Run. Choose the Month and the Year then click View Report to get the result. Hello, I have followed your guide here but when I go to run the report there is nothing to select for the Month and Year values. Is there a way to resolve this or get them to show up?

Love the guides you created for SCCM! Save my name, email, and website in this browser for the next time I comment. If you type the executable file name in the File name box, no checks are carried out to determine whether this file exists or whether it contains the necessary header information.

When possible, click Browse and select the executable file to be metered. Original File Name - The name of the executable file that you want to meter.

This name matches information in the header of the file, not the file name itself so that it can be useful in cases where the executable file has been renamed but you want to meter it by the original name. Version - The version of the executable file you that want to meter. Language - The language of the executable file to meter. The default value is the current locale of the operating system you are using. If you select an executable file to be metered by clicking the Browse button, this box is automatically filled if language information is present in the header of the file.

To meter all language versions of a file, select Any in the drop-down list. Apply this software metering rule to the following clients — Select whether you want to apply the software metering rule to all clients in the hierarchy or to the clients that are assigned to the site specified in the Site list.

Review and confirm the settings and then complete the wizard to create the software metering rule. The new software metering rule is displayed in the Software Metering node in the Assets and Compliance workspace. You can configure software metering in Configuration Manager to automatically generate disabled software metering rules from recent usage inventory data held in the site database. You can configure this inventory data so that only for applications that are used on a specified percentage of computers metering rules are created.

You can also specify the maximum number of automatically generated software metering rules allowed on the site. By default, software metering rules that are automatically created are disabled. Before you can begin to collect usage data from these rules, you must enable them. Data retention in days - Specifies the amount of time that data generated by software metering rules are kept in the site database. The default value is 90 days. Enable the option Automatically create disabled metering rules from recent usage inventory data.

Specify the percentage of computers in the hierarchy that must use a program before a software metering rule is automatically created - The default value is 10 percent. Specify the number of software metering rules that must be exceeded in the hierarchy before the automatic creation of rules is disabled - The default value is rules. In the Assets and Compliance workspace, select Software Metering , select the software metering rule to manage, and then select a management task.

Use the following table for more information about the management tasks that might require some information before you select them. Software metering in Configuration Manager includes a number of built-in reports which allow you to monitor information about software metering operations.

These reports have the report category of Software Metering. For more information about how to configure reporting in Configuration Manager, see Introduction to reporting. Additionally, you can create queries and collections based on the data stored in the Configuration Manager database by software metering. For more information about collections in Configuration Manager, see Introduction to collections.

For more information about queries in Configuration Manager, see Introduction to queries. An attacker could send invalid software metering information to Configuration Manager, which will be accepted by the management point even when the software metering client setting is disabled.

This might result in a large number of metering rules that are replicated throughout the hierarchy, causing a denial of service on the network and to Configuration Manager site servers.

Because an attacker can create invalid software metering data, do not consider software metering information to be authoritative. Software metering monitors the usage of applications on client computers.

Software metering is enabled by default.