deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

sensors servermanager servicing

Browse Source
This commit is contained in:
Liz Long 2023-01-05 09:34:50 -05:00
parent 7268626854
commit cd5b6f0258
3 changed files with 607 additions and 511 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

500
windows/client-management/mdm/policy-csp-admx-sensors.md
View File

@ -1,290 +1,338 @@
--- ---
title: Policy CSP - ADMX_Sensors title: ADMX_Sensors Policy CSP
description: Learn about Policy CSP - ADMX_Sensors. description: Learn more about the ADMX_Sensors Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 10/22/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_Sensors-Begin -->
# Policy CSP - ADMX_Sensors # Policy CSP - ADMX_Sensors
> [!TIP] > [!TIP]
> These are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md). > Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
> >
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy). > You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
> >
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). > The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/> <!-- ADMX_Sensors-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_Sensors-Editable-End -->
<!--Policies--> <!-- DisableLocationScripting_2-Begin -->
## ADMX_Sensors policies ## DisableLocationScripting_2
<dl> <!-- DisableLocationScripting_2-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-sensors-disablelocationscripting-1">ADMX_Sensors/DisableLocationScripting_1</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<dd> <!-- DisableLocationScripting_2-Applicability-End -->
<a href="#admx-sensors-disablelocationscripting-2">ADMX_Sensors/DisableLocationScripting_2</a>
</dd>
<dd>
<a href="#admx-sensors-disablelocation-1">ADMX_Sensors/DisableLocation_1</a>
</dd>
<dd>
<a href="#admx-sensors-disablesensors-1">ADMX_Sensors/DisableSensors_1</a>
</dd>
<dd>
<a href="#admx-sensors-disablesensors-2">ADMX_Sensors/DisableSensors_2</a>
</dd>
</dl>
<!-- DisableLocationScripting_2-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Sensors/DisableLocationScripting_2
```
<!-- DisableLocationScripting_2-OmaUri-End -->
<hr/> <!-- DisableLocationScripting_2-Description-Begin -->
<!-- Description-Source-ADMX -->
<!--Policy-->
<a href="" id="admx-sensors-disablelocationscripting-1"></a>**ADMX_Sensors/DisableLocationScripting_1**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * User
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting turns off scripting for the location feature.
If you enable this policy setting, scripts for the location feature won't run.
If you disable or don't configure this policy setting, all location scripts will run.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Turn off location scripting*
- GP name: *DisableLocationScripting_1*
- GP path: *Windows Components\Location and Sensors*
- GP ADMX file name: *Sensors.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-sensors-disablelocationscripting-2"></a>**ADMX_Sensors/DisableLocationScripting_2**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting turns off scripting for the location feature. This policy setting turns off scripting for the location feature.
If you enable this policy setting, scripts for the location feature will not run. If you enable this policy setting, scripts for the location feature will not run.
If you disable or don't configure this policy setting, all location scripts will run. If you disable or do not configure this policy setting, all location scripts will run.
<!-- DisableLocationScripting_2-Description-End -->
<!--/Description--> <!-- DisableLocationScripting_2-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableLocationScripting_2-Editable-End -->
<!-- DisableLocationScripting_2-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Turn off location scripting* | Format | chr (string) |
- GP name: *DisableLocationScripting_2* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Location and Sensors* <!-- DisableLocationScripting_2-DFProperties-End -->
- GP ADMX file name: *Sensors.admx*
<!--/ADMXBacked--> <!-- DisableLocationScripting_2-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="admx-sensors-disablelocation-1"></a>**ADMX_Sensors/DisableLocation_1**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | DisableLocationScripting |
| Friendly Name | Turn off location scripting |
| Location | Computer Configuration |
| Path | Windows Components > Location and Sensors |
| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
| Registry Value Name | DisableLocationScripting |
| ADMX File Name | Sensors.admx |
<!-- DisableLocationScripting_2-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DisableLocationScripting_2-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DisableLocationScripting_2-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DisableLocationScripting_2-End -->
<hr/>
<!--Scope--> <!-- DisableSensors_2-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## DisableSensors_2
> [!div class = "checklist"] <!-- DisableSensors_2-Applicability-Begin -->
> * User | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DisableSensors_2-Applicability-End -->
<hr/> <!-- DisableSensors_2-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Sensors/DisableSensors_2
```
<!-- DisableSensors_2-OmaUri-End -->
<!--/Scope--> <!-- DisableSensors_2-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting turns off the sensor feature for this computer.
If you enable this policy setting, the sensor feature is turned off, and all programs on this computer cannot use the sensor feature.
If you disable or do not configure this policy setting, all programs on this computer can use the sensor feature.
<!-- DisableSensors_2-Description-End -->
<!-- DisableSensors_2-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableSensors_2-Editable-End -->
<!-- DisableSensors_2-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DisableSensors_2-DFProperties-End -->
<!-- DisableSensors_2-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | DisableSensors |
| Friendly Name | Turn off sensors |
| Location | Computer Configuration |
| Path | Windows Components > Location and Sensors |
| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
| Registry Value Name | DisableSensors |
| ADMX File Name | Sensors.admx |
<!-- DisableSensors_2-AdmxBacked-End -->
<!-- DisableSensors_2-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- DisableSensors_2-Examples-End -->
<!-- DisableSensors_2-End -->
<!-- DisableLocation_1-Begin -->
## DisableLocation_1
<!-- DisableLocation_1-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :x: Device <br> :heavy_check_mark: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DisableLocation_1-Applicability-End -->
<!-- DisableLocation_1-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_Sensors/DisableLocation_1
```
<!-- DisableLocation_1-OmaUri-End -->
<!-- DisableLocation_1-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting turns off the location feature for this computer. This policy setting turns off the location feature for this computer.
If you enable this policy setting, the location feature is turned off, and all programs on this computer are prevented from using location information from the location feature. If you enable this policy setting, the location feature is turned off, and all programs on this computer are prevented from using location information from the location feature.
If you disable or don't configure this policy setting, all programs on this computer won't be prevented from using location information from the location feature. If you disable or do not configure this policy setting, all programs on this computer will not be prevented from using location information from the location feature.
<!-- DisableLocation_1-Description-End -->
<!--/Description--> <!-- DisableLocation_1-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableLocation_1-Editable-End -->
<!-- DisableLocation_1-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Turn off location* | Format | chr (string) |
- GP name: *DisableLocation_1* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Location and Sensors* <!-- DisableLocation_1-DFProperties-End -->
- GP ADMX file name: *Sensors.admx*
<!--/ADMXBacked--> <!-- DisableLocation_1-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="admx-sensors-disablesensors-1"></a>**ADMX_Sensors/DisableSensors_1**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | DisableLocation |
| Friendly Name | Turn off location |
| Location | User Configuration |
| Path | Windows Components > Location and Sensors |
| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
| Registry Value Name | DisableLocation |
| ADMX File Name | Sensors.admx |
<!-- DisableLocation_1-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DisableLocation_1-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DisableLocation_1-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DisableLocation_1-End -->
<hr/>
<!--Scope--> <!-- DisableLocationScripting_1-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## DisableLocationScripting_1
> [!div class = "checklist"] <!-- DisableLocationScripting_1-Applicability-Begin -->
> * User | Scope | Editions | Applicable OS |
|:--|:--|:--|
| :x: Device <br> :heavy_check_mark: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DisableLocationScripting_1-Applicability-End -->
<hr/> <!-- DisableLocationScripting_1-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_Sensors/DisableLocationScripting_1
```
<!-- DisableLocationScripting_1-OmaUri-End -->
<!--/Scope--> <!-- DisableLocationScripting_1-Description-Begin -->
<!--Description--> <!-- Description-Source-ADMX -->
This policy setting turns off scripting for the location feature.
If you enable this policy setting, scripts for the location feature will not run.
If you disable or do not configure this policy setting, all location scripts will run.
<!-- DisableLocationScripting_1-Description-End -->
<!-- DisableLocationScripting_1-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableLocationScripting_1-Editable-End -->
<!-- DisableLocationScripting_1-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DisableLocationScripting_1-DFProperties-End -->
<!-- DisableLocationScripting_1-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | DisableLocationScripting |
| Friendly Name | Turn off location scripting |
| Location | User Configuration |
| Path | Windows Components > Location and Sensors |
| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
| Registry Value Name | DisableLocationScripting |
| ADMX File Name | Sensors.admx |
<!-- DisableLocationScripting_1-AdmxBacked-End -->
<!-- DisableLocationScripting_1-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- DisableLocationScripting_1-Examples-End -->
<!-- DisableLocationScripting_1-End -->
<!-- DisableSensors_1-Begin -->
## DisableSensors_1
<!-- DisableSensors_1-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :x: Device <br> :heavy_check_mark: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DisableSensors_1-Applicability-End -->
<!-- DisableSensors_1-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_Sensors/DisableSensors_1
```
<!-- DisableSensors_1-OmaUri-End -->
<!-- DisableSensors_1-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting turns off the sensor feature for this computer. This policy setting turns off the sensor feature for this computer.
If you enable this policy setting, the sensor feature is turned off, and all programs on this computer can't use the sensor feature. If you enable this policy setting, the sensor feature is turned off, and all programs on this computer cannot use the sensor feature.
If you disable or don't configure this policy setting, all programs on this computer can use the sensor feature. If you disable or do not configure this policy setting, all programs on this computer can use the sensor feature.
<!-- DisableSensors_1-Description-End -->
<!--/Description--> <!-- DisableSensors_1-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DisableSensors_1-Editable-End -->
<!-- DisableSensors_1-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Turn off sensors* | Format | chr (string) |
- GP name: *DisableSensors_1* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Location and Sensors* <!-- DisableSensors_1-DFProperties-End -->
- GP ADMX file name: *Sensors.admx*
<!--/ADMXBacked--> <!-- DisableSensors_1-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
<!--Policy--> **ADMX mapping**:
<a href="" id="admx-sensors-disablesensors-2"></a>**ADMX_Sensors/DisableSensors_2**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | DisableSensors |
| Friendly Name | Turn off sensors |
| Location | User Configuration |
| Path | Windows Components > Location and Sensors |
| Registry Key Name | Software\Policies\Microsoft\Windows\LocationAndSensors |
| Registry Value Name | DisableSensors |
| ADMX File Name | Sensors.admx |
<!-- DisableSensors_1-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- DisableSensors_1-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- DisableSensors_1-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- DisableSensors_1-End -->
<hr/>
<!--Scope--> <!-- ADMX_Sensors-CspMoreInfo-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): <!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_Sensors-CspMoreInfo-End -->
> [!div class = "checklist"] <!-- ADMX_Sensors-End -->
> * Device
<hr/> ## Related articles
<!--/Scope--> [Policy configuration service provider](policy-configuration-service-provider.md)
<!--Description-->
This policy setting turns off the sensor feature for this computer.
If you enable this policy setting, the sensor feature is turned off, and all programs on this computer can't use the sensor feature.
If you disable or don't configure this policy setting, all programs on this computer can use the sensor feature.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Turn off sensors*
- GP name: *DisableSensors_2*
- GP path: *Windows Components\Location and Sensors*
- GP ADMX file name: *Sensors.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--/Policies-->
## Related topics
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md)

482
windows/client-management/mdm/policy-csp-admx-servermanager.md
View File

@ -1,252 +1,288 @@
--- ---
title: Policy CSP - ADMX_ServerManager title: ADMX_ServerManager Policy CSP
description: Learn about Policy CSP - ADMX_ServerManager. description: Learn more about the ADMX_ServerManager Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 09/18/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_ServerManager-Begin -->
# Policy CSP - ADMX_ServerManager # Policy CSP - ADMX_ServerManager
<hr/>
<!--Policies-->
## ADMX_ServerManager policies
> [!TIP] > [!TIP]
> This is an ADMX-backed policy and requires a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](../understanding-admx-backed-policies.md). > Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
> >
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](../understanding-admx-backed-policies.md#enabling-a-policy). > You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
> >
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). > The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<dl> <!-- ADMX_ServerManager-Editable-Begin -->
<dd> <!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<a href="#admx-servermanager-do_not_display_manage_your_server_page">ADMX_ServerManager/Do_not_display_Manage_Your_Server_page</a> <!-- ADMX_ServerManager-Editable-End -->
</dd>
<dd>
<a href="#admx-servermanager-servermanagerautorefreshrate">ADMX_ServerManager/ServerManagerAutoRefreshRate</a>
</dd>
<dd>
<a href="#admx-servermanager-donotlaunchinitialconfigurationtasks">ADMX_ServerManager/DoNotLaunchInitialConfigurationTasks</a>
</dd>
<dd>
<a href="#admx-servermanager-donotlaunchservermanager">ADMX_ServerManager/DoNotLaunchServerManager</a>
</dd>
</dl>
<!-- Do_not_display_Manage_Your_Server_page-Begin -->
## Do_not_display_Manage_Your_Server_page
<hr/> <!-- Do_not_display_Manage_Your_Server_page-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- Do_not_display_Manage_Your_Server_page-Applicability-End -->
<!--Policy--> <!-- Do_not_display_Manage_Your_Server_page-OmaUri-Begin -->
<a href="" id="admx-servermanager-do_not_display_manage_your_server_page"></a>**ADMX_ServerManager/Do_not_display_Manage_Your_Server_page** ```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_ServerManager/Do_not_display_Manage_Your_Server_page
```
<!-- Do_not_display_Manage_Your_Server_page-OmaUri-End -->
<!--SupportedSKUs--> <!-- Do_not_display_Manage_Your_Server_page-Description-Begin -->
<!-- Description-Source-ADMX -->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting allows you to turn off the automatic display of Server Manager at sign in.
If you enable this policy setting, Server Manager isn't displayed automatically when a user signs in to the server.
If you disable this policy setting, Server Manager is displayed automatically when a user signs in to the server.
If you don't configure this policy setting, Server Manager is displayed when a user signs in to the server. However, if the "Do not show me this console at logon" (Windows Server 2008 and Windows Server 2008 R2) or “Do not start Server Manager automatically at logon” (Windows Server 2012) option is selected, the console isn't displayed automatically at a sign in.
> [!NOTE]
> Regardless of the status of this policy setting, Server Manager is available from the Start menu or the Windows taskbar.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Do not display Server Manager automatically at logon*
- GP name: *Do_not_display_Manage_Your_Server_page*
- GP path: *System\Server Manager*
- GP ADMX file name: *ServerManager.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-servermanager-servermanagerautorefreshrate"></a>**ADMX_ServerManager/ServerManagerAutoRefreshRate**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting allows you to set the refresh interval for Server Manager. Each refresh provides Server Manager with updated information about which roles and features are installed on servers that you're managing by using Server Manager. Server Manager also monitors the status of roles and features installed on managed servers.
- If you enable this policy setting, Server Manager uses the refresh interval specified in the policy setting instead of the “Configure Refresh Interval” setting (in Windows Server 2008 and Windows Server 2008 R2), or the “Refresh the data shown in Server Manager every [x] [minutes/hours/days]” setting (in Windows Server 2012) that is configured in the Server Manager console.
- If you disable this policy setting, Server Manager doesn't refresh automatically. If you don't configure this policy setting, Server Manager uses the refresh interval settings that are specified in the Server Manager console.
> [!NOTE]
> The default refresh interval for Server Manager is two minutes in Windows Server 2008 and Windows Server 2008 R2, or 10 minutes in Windows Server 2012.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Configure the refresh interval for Server Manager*
- GP name: *ServerManagerAutoRefreshRate*
- GP path: *System\Server Manager*
- GP ADMX file name: *ServerManager.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-servermanager-donotlaunchinitialconfigurationtasks"></a>**ADMX_ServerManager/DoNotLaunchInitialConfigurationTasks**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting allows you to turn off the automatic display of the Initial Configuration Tasks window at a sign in on Windows Server 2008 and Windows Server 2008 R2.
If you enable this policy setting, the Initial Configuration Tasks window isn't displayed when an administrator signs in to the server.
If you disable this policy setting, the Initial Configuration Tasks window is displayed when an administrator signs in to the server.
If you don't configure this policy setting, the Initial Configuration Tasks window is displayed when an administrator signs in to the server. However, if an administrator selects the "Do not show this window at logon" option, the window isn't displayed on subsequent logons.
<!--/Description-->
<!--ADMXBacked-->
ADMX Info:
- GP Friendly name: *Do not display Initial Configuration Tasks window automatically at logon*
- GP name: *DoNotLaunchInitialConfigurationTasks*
- GP path: *System\Server Manager*
- GP ADMX file name: *ServerManager.admx*
<!--/ADMXBacked-->
<!--/Policy-->
<hr/>
<!--Policy-->
<a href="" id="admx-servermanager-donotlaunchservermanager"></a>**ADMX_ServerManager/DoNotLaunchServerManager**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting allows you to turn off the automatic display of the Manage Your Server page. This policy setting allows you to turn off the automatic display of the Manage Your Server page.
- If you enable this policy setting, the Manage Your Server page isn't displayed each time an administrator signs in to the server. If you enable this policy setting, the Manage Your Server page is not displayed each time an administrator logs on to the server.
- If you disable or don't configure this policy setting, the Manage Your Server page is displayed each time an administrator signs in to the server. If you disable or do not configure this policy setting, the Manage Your Server page is displayed each time an administrator logs on to the server. However, if the administrator has selected the "Don’t display this page at logon" option at the bottom of the Manage Your Server page, the page is not displayed.
<!-- Do_not_display_Manage_Your_Server_page-Description-End -->
However, if the administrator has selected the "Don’t display this page at logon" option at the bottom of the Manage Your Server page, the page isn't displayed. <!-- Do_not_display_Manage_Your_Server_page-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
> [!NOTE]
> Regardless of the status of this policy setting, Server Manager is available from the Start menu or the Windows taskbar.
<!-- Do_not_display_Manage_Your_Server_page-Editable-End -->
<!--/Description--> <!-- Do_not_display_Manage_Your_Server_page-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- Do_not_display_Manage_Your_Server_page-DFProperties-End -->
<!--ADMXBacked--> <!-- Do_not_display_Manage_Your_Server_page-AdmxBacked-Begin -->
ADMX Info: > [!TIP]
- GP Friendly name: *Do not display Manage Your Server page at logon* > This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
- GP name: *DoNotLaunchServerManager*
- GP path: *System\Server Manager*
- GP ADMX file name: *ServerManager.admx*
<!--/ADMXBacked--> **ADMX mapping**:
<!--/Policy-->
<!--/Policies--> | Name | Value |
|:--|:--|
| Name | Do_not_display_Manage_Your_Server_page |
| Friendly Name | Do not display Manage Your Server page at logon |
| Location | Computer Configuration |
| Path | System |
| Registry Key Name | Software\Policies\Microsoft\Windows NT\CurrentVersion\MYS |
| Registry Value Name | DisableShowAtLogon |
| ADMX File Name | ServerManager.admx |
<!-- Do_not_display_Manage_Your_Server_page-AdmxBacked-End -->
## Related topics <!-- Do_not_display_Manage_Your_Server_page-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Do_not_display_Manage_Your_Server_page-Examples-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md) <!-- Do_not_display_Manage_Your_Server_page-End -->
<!-- DoNotLaunchInitialConfigurationTasks-Begin -->
## DoNotLaunchInitialConfigurationTasks
<!-- DoNotLaunchInitialConfigurationTasks-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DoNotLaunchInitialConfigurationTasks-Applicability-End -->
<!-- DoNotLaunchInitialConfigurationTasks-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_ServerManager/DoNotLaunchInitialConfigurationTasks
```
<!-- DoNotLaunchInitialConfigurationTasks-OmaUri-End -->
<!-- DoNotLaunchInitialConfigurationTasks-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to turn off the automatic display of the Initial Configuration Tasks window at logon on Windows Server 2008 and Windows Server 2008 R2.
If you enable this policy setting, the Initial Configuration Tasks window is not displayed when an administrator logs on to the server.
If you disable this policy setting, the Initial Configuration Tasks window is displayed when an administrator logs on to the server.
If you do not configure this policy setting, the Initial Configuration Tasks window is displayed when an administrator logs on to the server. However, if an administrator selects the "Do not show this window at logon" option, the window is not displayed on subsequent logons.
<!-- DoNotLaunchInitialConfigurationTasks-Description-End -->
<!-- DoNotLaunchInitialConfigurationTasks-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DoNotLaunchInitialConfigurationTasks-Editable-End -->
<!-- DoNotLaunchInitialConfigurationTasks-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DoNotLaunchInitialConfigurationTasks-DFProperties-End -->
<!-- DoNotLaunchInitialConfigurationTasks-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | DoNotLaunchInitialConfigurationTasks |
| Friendly Name | Do not display Initial Configuration Tasks window automatically at logon |
| Location | Computer Configuration |
| Path | System > Server Manager |
| Registry Key Name | Software\Policies\Microsoft\Windows\Server\InitialConfigurationTasks |
| Registry Value Name | DoNotOpenAtLogon |
| ADMX File Name | ServerManager.admx |
<!-- DoNotLaunchInitialConfigurationTasks-AdmxBacked-End -->
<!-- DoNotLaunchInitialConfigurationTasks-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- DoNotLaunchInitialConfigurationTasks-Examples-End -->
<!-- DoNotLaunchInitialConfigurationTasks-End -->
<!-- DoNotLaunchServerManager-Begin -->
## DoNotLaunchServerManager
<!-- DoNotLaunchServerManager-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- DoNotLaunchServerManager-Applicability-End -->
<!-- DoNotLaunchServerManager-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_ServerManager/DoNotLaunchServerManager
```
<!-- DoNotLaunchServerManager-OmaUri-End -->
<!-- DoNotLaunchServerManager-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to turn off the automatic display of Server Manager at logon.
If you enable this policy setting, Server Manager is not displayed automatically when a user logs on to the server.
If you disable this policy setting, Server Manager is displayed automatically when a user logs on to the server.
If you do not configure this policy setting, Server Manager is displayed when a user logs on to the server. However, if the "Do not show me this console at logon" (Windows Server 2008 and Windows Server 2008 R2) or “Do not start Server Manager automatically at logon” (Windows Server 2012) option is selected, the console is not displayed automatically at logon.
Note: Regardless of the status of this policy setting, Server Manager is available from the Start menu or the Windows taskbar.
<!-- DoNotLaunchServerManager-Description-End -->
<!-- DoNotLaunchServerManager-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- DoNotLaunchServerManager-Editable-End -->
<!-- DoNotLaunchServerManager-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- DoNotLaunchServerManager-DFProperties-End -->
<!-- DoNotLaunchServerManager-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | DoNotLaunchServerManager |
| Friendly Name | Do not display Server Manager automatically at logon |
| Location | Computer Configuration |
| Path | System > Server Manager |
| Registry Key Name | Software\Policies\Microsoft\Windows\Server\ServerManager |
| Registry Value Name | DoNotOpenAtLogon |
| ADMX File Name | ServerManager.admx |
<!-- DoNotLaunchServerManager-AdmxBacked-End -->
<!-- DoNotLaunchServerManager-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- DoNotLaunchServerManager-Examples-End -->
<!-- DoNotLaunchServerManager-End -->
<!-- ServerManagerAutoRefreshRate-Begin -->
## ServerManagerAutoRefreshRate
<!-- ServerManagerAutoRefreshRate-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
<!-- ServerManagerAutoRefreshRate-Applicability-End -->
<!-- ServerManagerAutoRefreshRate-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_ServerManager/ServerManagerAutoRefreshRate
```
<!-- ServerManagerAutoRefreshRate-OmaUri-End -->
<!-- ServerManagerAutoRefreshRate-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to set the refresh interval for Server Manager. Each refresh provides Server Manager with updated information about which roles and features are installed on servers that you are managing by using Server Manager. Server Manager also monitors the status of roles and features installed on managed servers.
If you enable this policy setting, Server Manager uses the refresh interval specified in the policy setting instead of the “Configure Refresh Interval” setting (in Windows Server 2008 and Windows Server 2008 R2), or the “Refresh the data shown in Server Manager every [x] [minutes/hours/days]” setting (in Windows Server 2012) that is configured in the Server Manager console.
If you disable this policy setting, Server Manager does not refresh automatically. If you do not configure this policy setting, Server Manager uses the refresh interval settings that are specified in the Server Manager console.
Note: The default refresh interval for Server Manager is two minutes in Windows Server 2008 and Windows Server 2008 R2, or 10 minutes in Windows Server 2012.
<!-- ServerManagerAutoRefreshRate-Description-End -->
<!-- ServerManagerAutoRefreshRate-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ServerManagerAutoRefreshRate-Editable-End -->
<!-- ServerManagerAutoRefreshRate-DFProperties-Begin -->
**Description framework properties**:
| Property name | Property value |
|:--|:--|
| Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- ServerManagerAutoRefreshRate-DFProperties-End -->
<!-- ServerManagerAutoRefreshRate-AdmxBacked-Begin -->
> [!TIP]
> This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | ServerManagerAutoRefreshRate |
| Friendly Name | Configure the refresh interval for Server Manager |
| Location | Computer Configuration |
| Path | System > Server Manager |
| Registry Key Name | Software\Policies\Microsoft\Windows\Server\ServerManager |
| Registry Value Name | RefreshIntervalEnabled |
| ADMX File Name | ServerManager.admx |
<!-- ServerManagerAutoRefreshRate-AdmxBacked-End -->
<!-- ServerManagerAutoRefreshRate-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- ServerManagerAutoRefreshRate-Examples-End -->
<!-- ServerManagerAutoRefreshRate-End -->
<!-- ADMX_ServerManager-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_ServerManager-CspMoreInfo-End -->
<!-- ADMX_ServerManager-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

132
windows/client-management/mdm/policy-csp-admx-servicing.md
View File

@ -1,87 +1,99 @@
--- ---
title: Policy CSP - ADMX_Servicing title: ADMX_Servicing Policy CSP
description: Learn about Policy CSP - ADMX_Servicing. description: Learn more about the ADMX_Servicing Area in Policy CSP
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa ms.author: vinpa
ms.date: 01/05/2023
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article
ms.prod: windows-client ms.prod: windows-client
ms.technology: itpro-manage ms.technology: itpro-manage
author: vinaypamnani-msft ms.topic: reference
ms.date: 09/18/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_Servicing-Begin -->
# Policy CSP - ADMX_Servicing # Policy CSP - ADMX_Servicing
> [!TIP]
> Some of these are ADMX-backed policies and require a special SyncML format to enable or disable. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
>
> You must specify the data type in the SyncML as &lt;Format&gt;chr&lt;/Format&gt;. For an example SyncML, refer to [Enabling a policy](./understanding-admx-backed-policies.md#enabling-a-policy).
>
> The payload of the SyncML must be XML-encoded; for this XML encoding, there are a variety of online encoders that you can use. To avoid encoding the payload, you can use CDATA if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect).
<hr/> <!-- ADMX_Servicing-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_Servicing-Editable-End -->
<!--Policies--> <!-- Servicing-Begin -->
## ADMX_Servicing policies ## Servicing
<dl> <!-- Servicing-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-servicing-servicing">ADMX_Servicing/Servicing</a> |:--|:--|:--|
</dd> | :heavy_check_mark: Device <br> :x: User | :x: Home <br> :heavy_check_mark: Pro <br> :heavy_check_mark: Enterprise <br> :heavy_check_mark: Education <br> :heavy_check_mark: Windows SE | :heavy_check_mark: Windows 10, version 2004 [10.0.19041.1202] and later <br> :heavy_check_mark: Windows 10, version 2009 [10.0.19042.1202] and later <br> :heavy_check_mark: Windows 10, version 21H1 [10.0.19043.1202] and later <br> :heavy_check_mark: Windows 11, version 21H2 [10.0.22000] and later |
</dl> <!-- Servicing-Applicability-End -->
<!-- Servicing-OmaUri-Begin -->
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_Servicing/Servicing
```
<!-- Servicing-OmaUri-End -->
<hr/> <!-- Servicing-Description-Begin -->
<!-- Description-Source-ADMX -->
<!--Policy-->
<a href="" id="admx-servicing-servicing"></a>**ADMX_Servicing/Servicing**
<!--SupportedSKUs-->
|Edition|Windows 10|Windows 11|
|--- |--- |--- |
|Home|No|No|
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs-->
<hr/>
<!--Scope-->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"]
> * Device
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting specifies the network locations that will be used for the repair of operating system corruption and for enabling optional features that have had their payload files removed. This policy setting specifies the network locations that will be used for the repair of operating system corruption and for enabling optional features that have had their payload files removed.
If you enable this policy setting and specify the new location, the files in that location will be used to repair operating system corruption and for enabling optional features that have had their payload files removed. You must enter the fully qualified path to the new location in the "Alternate source file path" text box. Multiple locations can be specified when each path is separated by a semicolon. If you enable this policy setting and specify the new location, the files in that location will be used to repair operating system corruption and for enabling optional features that have had their payload files removed. You must enter the fully qualified path to the new location in the ""Alternate source file path"" text box. Multiple locations can be specified when each path is separated by a semicolon.
The network location can be either a folder, or a WIM file. If it's a WIM file, the location should be specified by prefixing the path with “wim:” and include the index of the image to use in the WIM file, for example, “wim:\\server\share\install.wim:3”. The network location can be either a folder, or a WIM file. If it is a WIM file, the location should be specified by prefixing the path with “wim:” and include the index of the image to use in the WIM file. For example “wim:\\server\share\install.wim:3”.
If you disable or don't configure this policy setting, or if the required files can't be found at the locations specified in this policy setting, the files will be downloaded from Windows Update, if that is allowed by the policy settings for the computer. If you disable or do not configure this policy setting, or if the required files cannot be found at the locations specified in this policy setting, the files will be downloaded from Windows Update, if that is allowed by the policy settings for the computer.
<!-- Servicing-Description-End -->
<!--/Description--> <!-- Servicing-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- Servicing-Editable-End -->
<!-- Servicing-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Specify settings for optional component installation and component repair* | Format | chr (string) |
- GP name: *Servicing* | Access Type | Add, Delete, Get, Replace |
- GP path: *System* <!-- Servicing-DFProperties-End -->
- GP ADMX file name: *Servicing.admx*
<!--/ADMXBacked--> <!-- Servicing-AdmxBacked-Begin -->
<!--/Policy--> > [!TIP]
<hr/> > This is an ADMX-backed policy and requires SyncML format for configuration. For details, see [Understanding ADMX-backed policies](./understanding-admx-backed-policies.md).
**ADMX mapping**:
| Name | Value |
|:--|:--|
| Name | CloudFulfillmentGPO |
| Friendly Name | Specify settings for optional component installation and component repair |
| Location | Computer Configuration |
| Path | System |
| Registry Key Name | Software\Microsoft\Windows\CurrentVersion\Policies\Servicing |
| ADMX File Name | Servicing.admx |
<!-- Servicing-AdmxBacked-End -->
<!--/Policies--> <!-- Servicing-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- Servicing-Examples-End -->
## Related topics <!-- Servicing-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md) <!-- ADMX_Servicing-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_Servicing-CspMoreInfo-End -->
<!-- ADMX_Servicing-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)