5.6 KiB
author, title, description, ms.author, ms.date, ms.topic, ms.prod, ms.technology, keywords
| author | title | description | ms.author | ms.date | ms.topic | ms.prod | ms.technology | keywords |
|---|---|---|---|---|---|---|---|---|
| TylerMSFT | Remove background task resource restrictions | Allow enterprise background tasks unrestricted access to computer resources. | twhitney | 10/03/2017 | article | w10 | uwp | windows 10, uwp, enterprise, background task, resources |
Remove background task resource restrictions
To provide the best experience for consumers, Windows provides controls that give users the choice of which experiences may run in the background.
By default, resource limits are imposed on applications. Foreground apps are given the most memory and execution time; background apps get less. Users are thus protected from poor foreground app performance and heavy battery drain.
Enterprise users want the same ability to enable or limit background activity. In Windows 10, version 1703 (also known as the Creators Update), enterprises can now configure settings via policy and provisioning that control background activity.
Background activity controls
Users have the ability to control background activity for their device through two interfaces in the Settings app: the Background apps page and the Battery usage by app page. The Background apps page has a master switch to turn background activity on or off for all apps, and provides individual switches to control each app's ability to run in the background.
The Battery usage by app page allows fine-grained tuning of background activity. Users have the ability to set background activity to by Managed By Windows, as well as turning it on or off for each app. Only devices with a battery have this page available in the Settings app. Here is the set of available controls on desktop:
Here is the set of available controls for mobile devices:
Although the user interface differs across editions of the operating system, the policy and developer interface is consistent across Windows 10. For more information about these controls, see Optimize background activity.
Enterprise background activity controls
Starting with Windows 10, version 1703, enterprises can control background activity through mobile device management (MDM) or Group Policy. The user controls discussed above can be controlled with the following policies:
./Vendor/Microsoft/Policy/Config/Privacy/LetAppsRunInBackground
./Vendor/Microsoft/Policy/Config/Privacy/LetAppsRunInBackground_ForceAllowTheseApps
./Vendor/Microsoft/Policy/Config/Privacy/LetAppsRunInBackground_ForceDenyTheseApps
./Vendor/Microsoft/Policy/Config/Privacy/LetAppsRunInBackground_UserInControlOfTheseApps
These policies control the background activity battery settings for Universal Windows Platform (UWP) apps. They enable apps to not be managed by the Windows system policies and not be restricted when battery saver is active. Applying these policies to a device will disable the user controls for the applications specified in the policies in the Settings app. See Policy CSP for more information about these policies.
An app can determine which settings are in place for itself by using BackgroundExecutionManager.RequestAccessAsync before any background activity is attempted, and then examining the returned BackgroundAccessStatus enumeration. The values of this enumeration correspond to settings in the battery usage by App settings page:
- AlwaysAllowed: Corresponds to Always Allowed in Background and Managed By User. This enables apps to run as much as possible in the background, including while the device is in battery saver mode.
- AllowedSubjectToSystemPolicy: This is the default value. It corresponds to Managed by Windows. This enables apps to run in the background as determined by Windows. If the device is currently in the battery saver state then background activities do not run.
- DeniedDueToSystemPolicy: Corresponds to Managed by Windows and indicates that the system has determined that the app cannot currently run in the background.
- DeniedByUser: Corresponds to Never Allowed in the Background. The app cannot run in the background. Either the configuration in the settings app, or enterprise policy, has defined that this app is not allowed to run in the background.
The Universal Windows Platform ensures that consumers will have great battery life and that foreground apps will perform well. Enterprises have the ability to change settings to enable scenarios specific to their business needs. Administrators can use the Background apps policies to enable or disable whether a UWP app can run in the background.