deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-24 14:53:44 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Remove Windows SE from CSP applicability

Browse Source
This commit is contained in:
Vinay Pamnani (from Dev Box)
2025-03-12 10:39:50 -06:00
parent 32596de13b
commit aeb8f2bbd5
308 changed files with 5228 additions and 5229 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
windows/client-management/mdm/policy-csp-bits.md
View File

@ -1,7 +1,7 @@
---
title: BITS Policy CSP
description: Learn more about the BITS Area in Policy CSP.
ms.date: 02/13/2025
ms.date: 03/12/2025
ms.topic: generated-reference
---
@ -20,7 +20,7 @@ ms.topic: generated-reference
<!-- BandwidthThrottlingEndTime-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- BandwidthThrottlingEndTime-Applicability-End -->
<!-- BandwidthThrottlingEndTime-OmaUri-Begin -->
@ -86,7 +86,7 @@ Consider using this setting to prevent BITS transfers from competing for network
<!-- BandwidthThrottlingStartTime-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- BandwidthThrottlingStartTime-Applicability-End -->
<!-- BandwidthThrottlingStartTime-OmaUri-Begin -->
@ -152,7 +152,7 @@ Consider using this setting to prevent BITS transfers from competing for network
<!-- BandwidthThrottlingTransferRate-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- BandwidthThrottlingTransferRate-Applicability-End -->
<!-- BandwidthThrottlingTransferRate-OmaUri-Begin -->
@ -218,7 +218,7 @@ Consider using this setting to prevent BITS transfers from competing for network
<!-- CostedNetworkBehaviorBackgroundPriority-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- CostedNetworkBehaviorBackgroundPriority-Applicability-End -->
<!-- CostedNetworkBehaviorBackgroundPriority-OmaUri-Begin -->
@ -311,7 +311,7 @@ For example, you can specify that background jobs are by default to transfer onl
<!-- CostedNetworkBehaviorForegroundPriority-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- CostedNetworkBehaviorForegroundPriority-Applicability-End -->
<!-- CostedNetworkBehaviorForegroundPriority-OmaUri-Begin -->
@ -404,7 +404,7 @@ For example, you can specify that background jobs are by default to transfer onl
<!-- JobInactivityTimeout-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ Windows SE <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
| ✅ Device <br> ❌ User | ✅ Pro <br> ✅ Enterprise <br> ✅ Education <br> ✅ IoT Enterprise / IoT Enterprise LTSC | ✅ Windows 10, version 1809 [10.0.17763] and later |
<!-- JobInactivityTimeout-Applicability-End -->
<!-- JobInactivityTimeout-OmaUri-Begin -->