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

power powershellexecutionpolicy perviousversions

Browse Source
This commit is contained in:
Liz Long 2023-01-05 10:57:56 -05:00
parent ca02bf537a
commit acd6597a34
3 changed files with 2101 additions and 1478 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2107
windows/client-management/mdm/policy-csp-admx-power.md
View File

File diff suppressed because it is too large Load Diff

416
windows/client-management/mdm/policy-csp-admx-powershellexecutionpolicy.md
View File

@ -1,263 +1,321 @@
--- ---
title: Policy CSP - ADMX_PowerShellExecutionPolicy title: ADMX_PowerShellExecutionPolicy Policy CSP
description: Learn about Policy CSP - ADMX_PowerShellExecutionPolicy. description: Learn more about the ADMX_PowerShellExecutionPolicy 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/26/2020
ms.reviewer:
manager: aaroncz
--- ---
<!-- Auto-Generated CSP Document -->
<!-- ADMX_PowerShellExecutionPolicy-Begin -->
# Policy CSP - ADMX_PowerShellExecutionPolicy # Policy CSP - ADMX_PowerShellExecutionPolicy
>[!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_PowerShellExecutionPolicy-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- ADMX_PowerShellExecutionPolicy-Editable-End -->
<!--Policies--> <!-- EnableModuleLogging-Begin -->
## ADMX_PowerShellExecutionPolicy policies ## EnableModuleLogging
<dl> <!-- EnableModuleLogging-Applicability-Begin -->
<dd> | Scope | Editions | Applicable OS |
<a href="#admx-powershellexecutionpolicy-enablemodulelogging">ADMX_PowerShellExecutionPolicy/EnableModuleLogging</a> |:--|:--|:--|
</dd> | :heavy_check_mark: 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 |
<dd> <!-- EnableModuleLogging-Applicability-End -->
<a href="#admx-powershellexecutionpolicy-enablescripts">ADMX_PowerShellExecutionPolicy/EnableScripts</a>
</dd>
<dd>
<a href="#admx-powershellexecutionpolicy-enabletranscripting">ADMX_PowerShellExecutionPolicy/EnableTranscripting</a>
</dd>
<dd>
<a href="#admx-powershellexecutionpolicy-enableupdatehelpdefaultsourcepath">ADMX_PowerShellExecutionPolicy/EnableUpdateHelpDefaultSourcePath</a>
</dd>
</dl>
<!-- EnableModuleLogging-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableModuleLogging
```
<hr/> ```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableModuleLogging
```
<!-- EnableModuleLogging-OmaUri-End -->
<!--Policy--> <!-- EnableModuleLogging-Description-Begin -->
<a href="" id="admx-powershellexecutionpolicy-enablemodulelogging"></a>**ADMX_PowerShellExecutionPolicy/EnableModuleLogging** <!-- Description-Source-ADMX -->
<!--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
> * User
<hr/>
<!--/Scope-->
<!--Description-->
This policy setting allows you to turn on logging for Windows PowerShell modules. This policy setting allows you to turn on logging for Windows PowerShell modules.
If you enable this policy setting, pipeline execution events for members of the specified modules are recorded in the Windows PowerShell login Event Viewer. Enabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to True. If you enable this policy setting, pipeline execution events for members of the specified modules are recorded in the Windows PowerShell log in Event Viewer. Enabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to True.
If you disable this policy setting, logging of execution events is disabled for all Windows PowerShell modules. Disabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to False. If this policy setting isn't configured, the LogPipelineExecutionDetails property of a module or snap-in determines whether the execution events of a module or snap-in are logged. By default, the LogPipelineExecutionDetails property of all modules and snap-ins is set to False. If you disable this policy setting, logging of execution events is disabled for all Windows PowerShell modules. Disabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to False.
If this policy setting is not configured, the LogPipelineExecutionDetails property of a module or snap-in determines whether the execution events of a module or snap-in are logged. By default, the LogPipelineExecutionDetails property of all modules and snap-ins is set to False.
To add modules and snap-ins to the policy setting list, click Show, and then type the module names in the list. The modules and snap-ins in the list must be installed on the computer. To add modules and snap-ins to the policy setting list, click Show, and then type the module names in the list. The modules and snap-ins in the list must be installed on the computer.
> [!NOTE] Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
> This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting. <!-- EnableModuleLogging-Description-End -->
<!--/Description--> <!-- EnableModuleLogging-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableModuleLogging-Editable-End -->
<!-- EnableModuleLogging-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Turn on Module Logging* | Format | chr (string) |
- GP name: *EnableModuleLogging* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Windows PowerShell* <!-- EnableModuleLogging-DFProperties-End -->
- GP ADMX file name: *PowerShellExecutionPolicy.admx*
<!--/ADMXBacked--> <!-- EnableModuleLogging-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-powershellexecutionpolicy-enablescripts"></a>**ADMX_PowerShellExecutionPolicy/EnableScripts**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | EnableModuleLogging |
| Friendly Name | Turn on Module Logging |
| Location | Computer and User Configuration |
| Path | Windows Components > Windows PowerShell |
| Registry Key Name | Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging |
| Registry Value Name | EnableModuleLogging |
| ADMX File Name | PowerShellExecutionPolicy.admx |
<!-- EnableModuleLogging-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- EnableModuleLogging-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- EnableModuleLogging-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- EnableModuleLogging-End -->
<hr/>
<!--Scope--> <!-- EnableScripts-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## EnableScripts
> [!div class = "checklist"] <!-- EnableScripts-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
> * User |:--|:--|:--|
| :heavy_check_mark: 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 |
<!-- EnableScripts-Applicability-End -->
<hr/> <!-- EnableScripts-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableScripts
```
<!--/Scope--> ```Device
<!--Description--> ./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableScripts
```
<!-- EnableScripts-OmaUri-End -->
<!-- EnableScripts-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting lets you configure the script execution policy, controlling which scripts are allowed to run. This policy setting lets you configure the script execution policy, controlling which scripts are allowed to run.
If you enable this policy setting, the scripts selected in the drop-down list are allowed to run. The "Allow only signed scripts" policy setting allows scripts to execute only if they're signed by a trusted publisher. If you enable this policy setting, the scripts selected in the drop-down list are allowed to run.
The "Allow local scripts and remote signed scripts" policy setting allows any local scripts to run. And, the scripts that originate from the Internet must be signed by a trusted publisher. The "Allow all scripts" policy setting allows all scripts to run. The "Allow only signed scripts" policy setting allows scripts to execute only if they are signed by a trusted publisher.
The "Allow local scripts and remote signed scripts" policy setting allows any local scrips to run; scripts that originate from the Internet must be signed by a trusted publisher.
The "Allow all scripts" policy setting allows all scripts to run.
If you disable this policy setting, no scripts are allowed to run. If you disable this policy setting, no scripts are allowed to run.
> [!NOTE] Note: This policy setting exists under both "Computer Configuration" and "User Configuration" in the Local Group Policy Editor. The "Computer Configuration" has precedence over "User Configuration."
> This policy setting exists under both "Computer Configuration" and "User Configuration" in the Local Group Policy Editor. The "Computer Configuration" has precedence over "User Configuration." If you disable or do not configure this policy setting, it reverts to a per-machine preference setting; the default if that isn't configured is "No scripts allowed."
<!--/Description--> If you disable or do not configure this policy setting, it reverts to a per-machine preference setting; the default if that is not configured is "No scripts allowed."
<!-- EnableScripts-Description-End -->
<!-- EnableScripts-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableScripts-Editable-End -->
<!--ADMXBacked--> <!-- EnableScripts-DFProperties-Begin -->
ADMX Info: **Description framework properties**:
- GP Friendly name: *Turn on Script Execution*
- GP name: *EnableScripts*
- GP path: *Windows Components\Windows PowerShell*
- GP ADMX file name: *PowerShellExecutionPolicy.admx*
<!--/ADMXBacked--> | Property name | Property value |
<!--/Policy--> |:--|:--|
<hr/> | Format | chr (string) |
| Access Type | Add, Delete, Get, Replace |
<!-- EnableScripts-DFProperties-End -->
<!--Policy--> <!-- EnableScripts-AdmxBacked-Begin -->
<a href="" id="admx-powershellexecutionpolicy-enabletranscripting"></a>**ADMX_PowerShellExecutionPolicy/EnableTranscripting** > [!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).
<!--SupportedSKUs--> **ADMX mapping**:
|Edition|Windows 10|Windows 11| | Name | Value |
|--- |--- |--- | |:--|:--|
|Home|No|No| | Name | EnableScripts |
|Pro|Yes|Yes| | Friendly Name | Turn on Script Execution |
|Windows SE|No|Yes| | Location | Computer and User Configuration |
|Business|Yes|Yes| | Path | Windows Components > Windows PowerShell |
|Enterprise|Yes|Yes| | Registry Key Name | Software\Policies\Microsoft\Windows\PowerShell |
|Education|Yes|Yes| | Registry Value Name | EnableScripts |
| ADMX File Name | PowerShellExecutionPolicy.admx |
<!-- EnableScripts-AdmxBacked-End -->
<!--/SupportedSKUs--> <!-- EnableScripts-Examples-Begin -->
<hr/> <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- EnableScripts-Examples-End -->
<!--Scope--> <!-- EnableScripts-End -->
[Scope](./policy-configuration-service-provider.md#policy-scope):
> [!div class = "checklist"] <!-- EnableTranscripting-Begin -->
> * Device ## EnableTranscripting
> * User
<hr/> <!-- EnableTranscripting-Applicability-Begin -->
| Scope | Editions | Applicable OS |
|:--|:--|:--|
| :heavy_check_mark: 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 |
<!-- EnableTranscripting-Applicability-End -->
<!--/Scope--> <!-- EnableTranscripting-OmaUri-Begin -->
<!--Description--> ```User
./User/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableTranscripting
```
```Device
./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableTranscripting
```
<!-- EnableTranscripting-OmaUri-End -->
<!-- EnableTranscripting-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting lets you capture the input and output of Windows PowerShell commands into text-based transcripts. This policy setting lets you capture the input and output of Windows PowerShell commands into text-based transcripts.
If you enable this policy setting, Windows PowerShell will enable transcription for Windows PowerShell, the Windows PowerShell ISE, and any other applications that use the Windows PowerShell engine. By default, Windows PowerShell will record transcript output to each users' My Documents directory, with a file name that includes 'PowerShell_transcript', along with the computer name and time started. Enabling this policy is equivalent to calling the Start-Transcript cmdlet on each Windows PowerShell session. If you enable this policy setting, Windows PowerShell will enable transcripting for Windows PowerShell, the Windows PowerShell ISE, and any other
applications that leverage the Windows PowerShell engine. By default, Windows PowerShell will record transcript output to each users' My Documents
directory, with a file name that includes 'PowerShell_transcript', along with the computer name and time started. Enabling this policy is equivalent
to calling the Start-Transcript cmdlet on each Windows PowerShell session.
If you disable this policy setting, transcription of PowerShell-based applications is disabled by default, although transcription can still be enabled through the Start-Transcript cmdlet. If you disable this policy setting, transcripting of PowerShell-based applications is disabled by default, although transcripting can still be enabled
through the Start-Transcript cmdlet.
If you use the OutputDirectory setting to enable transcript logging to a shared location, be sure to limit access to that directory to prevent users from viewing the transcripts of other users or computers. If you use the OutputDirectory setting to enable transcript logging to a shared location, be sure to limit access to that directory to prevent users
from viewing the transcripts of other users or computers.
> [!NOTE] Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
> This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting. <!-- EnableTranscripting-Description-End -->
<!--/Description--> <!-- EnableTranscripting-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableTranscripting-Editable-End -->
<!-- EnableTranscripting-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Turn on PowerShell Transcription* | Format | chr (string) |
- GP name: *EnableTranscripting* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Windows PowerShell* <!-- EnableTranscripting-DFProperties-End -->
- GP ADMX file name: *PowerShellExecutionPolicy.admx*
<!--/ADMXBacked--> <!-- EnableTranscripting-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-powershellexecutionpolicy-enableupdatehelpdefaultsourcepath"></a>**ADMX_PowerShellExecutionPolicy/EnableUpdateHelpDefaultSourcePath**
<!--SupportedSKUs--> | Name | Value |
|:--|:--|
| Name | EnableTranscripting |
| Friendly Name | Turn on PowerShell Transcription |
| Location | Computer and User Configuration |
| Path | Windows Components > Windows PowerShell |
| Registry Key Name | Software\Policies\Microsoft\Windows\PowerShell\Transcription |
| Registry Value Name | EnableTranscripting |
| ADMX File Name | PowerShellExecutionPolicy.admx |
<!-- EnableTranscripting-AdmxBacked-End -->
|Edition|Windows 10|Windows 11| <!-- EnableTranscripting-Examples-Begin -->
|--- |--- |--- | <!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
|Home|No|No| <!-- EnableTranscripting-Examples-End -->
|Pro|Yes|Yes|
|Windows SE|No|Yes|
|Business|Yes|Yes|
|Enterprise|Yes|Yes|
|Education|Yes|Yes|
<!--/SupportedSKUs--> <!-- EnableTranscripting-End -->
<hr/>
<!--Scope--> <!-- EnableUpdateHelpDefaultSourcePath-Begin -->
[Scope](./policy-configuration-service-provider.md#policy-scope): ## EnableUpdateHelpDefaultSourcePath
> [!div class = "checklist"] <!-- EnableUpdateHelpDefaultSourcePath-Applicability-Begin -->
> * Device | Scope | Editions | Applicable OS |
> * User |:--|:--|:--|
| :heavy_check_mark: 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 |
<!-- EnableUpdateHelpDefaultSourcePath-Applicability-End -->
<hr/> <!-- EnableUpdateHelpDefaultSourcePath-OmaUri-Begin -->
```User
./User/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableUpdateHelpDefaultSourcePath
```
<!--/Scope--> ```Device
<!--Description--> ./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableUpdateHelpDefaultSourcePath
```
<!-- EnableUpdateHelpDefaultSourcePath-OmaUri-End -->
<!-- EnableUpdateHelpDefaultSourcePath-Description-Begin -->
<!-- Description-Source-ADMX -->
This policy setting allows you to set the default value of the SourcePath parameter on the Update-Help cmdlet. This policy setting allows you to set the default value of the SourcePath parameter on the Update-Help cmdlet.
If you enable this policy setting, the Update-Help cmdlet will use the specified value as the default value for the SourcePath parameter. This default value can be overridden by specifying a different value with the SourcePath parameter on the Update-Help cmdlet. If you enable this policy setting, the Update-Help cmdlet will use the specified value as the default value for the SourcePath parameter. This default value can be overridden by specifying a different value with the SourcePath parameter on the Update-Help cmdlet.
If this policy setting is disabled or not configured, this policy setting doesn't set a default value for the SourcePath parameter of the Update-Help cmdlet. If this policy setting is disabled or not configured, this policy setting does not set a default value for the SourcePath parameter of the Update-Help cmdlet.
> [!NOTE] Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
> This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting. <!-- EnableUpdateHelpDefaultSourcePath-Description-End -->
<!--/Description--> <!-- EnableUpdateHelpDefaultSourcePath-Editable-Begin -->
<!-- Add any additional information about this policy here. Anything outside this section will get overwritten. -->
<!-- EnableUpdateHelpDefaultSourcePath-Editable-End -->
<!-- EnableUpdateHelpDefaultSourcePath-DFProperties-Begin -->
**Description framework properties**:
<!--ADMXBacked--> | Property name | Property value |
ADMX Info: |:--|:--|
- GP Friendly name: *Set the default source path for Update-Help* | Format | chr (string) |
- GP name: *EnableUpdateHelpDefaultSourcePath* | Access Type | Add, Delete, Get, Replace |
- GP path: *Windows Components\Windows PowerShell* <!-- EnableUpdateHelpDefaultSourcePath-DFProperties-End -->
- GP ADMX file name: *PowerShellExecutionPolicy.admx*
<!--/ADMXBacked--> <!-- EnableUpdateHelpDefaultSourcePath-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 | EnableUpdateHelpDefaultSourcePath |
| Friendly Name | Set the default source path for Update-Help |
| Location | Computer and User Configuration |
| Path | Windows Components > Windows PowerShell |
| Registry Key Name | Software\Policies\Microsoft\Windows\PowerShell\UpdatableHelp |
| Registry Value Name | EnableUpdateHelpDefaultSourcePath |
| ADMX File Name | PowerShellExecutionPolicy.admx |
<!-- EnableUpdateHelpDefaultSourcePath-AdmxBacked-End -->
<!--/Policies--> <!-- EnableUpdateHelpDefaultSourcePath-Examples-Begin -->
<!-- Add any examples for this policy here. Examples outside this section will get overwritten. -->
<!-- EnableUpdateHelpDefaultSourcePath-Examples-End -->
## Related topics <!-- EnableUpdateHelpDefaultSourcePath-End -->
[ADMX-backed policies in Policy CSP](./policies-in-policy-csp-admx-backed.md) <!-- ADMX_PowerShellExecutionPolicy-CspMoreInfo-Begin -->
<!-- Add any additional information about this CSP here. Anything outside this section will get overwritten. -->
<!-- ADMX_PowerShellExecutionPolicy-CspMoreInfo-End -->
<!-- ADMX_PowerShellExecutionPolicy-End -->
## Related articles
[Policy configuration service provider](policy-configuration-service-provider.md)

1056
windows/client-management/mdm/policy-csp-admx-previousversions.md
View File

File diff suppressed because it is too large Load Diff