Skip to content

Fixes #11796 - Update policy navigation tree #11798

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 14, 2025
Merged

Fixes #11796 - Update policy navigation tree #11798

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 2 additions & 8 deletions reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes the PowerShell execution policies and explains how to manage them.
Locale: en-US
ms.date: 10/07/2024
ms.date: 02/14/2025
no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings]
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-5.1&WT.mc_id=ps-gethelp
schema: 2.0.0
Expand Down Expand Up @@ -306,16 +306,10 @@ The **Turn on Script Execution** policy settings are as follows:

The PowerShellExecutionPolicy.adm and PowerShellExecutionPolicy.admx files add
the **Turn on Script Execution** policy to the Computer Configuration and User
Configuration nodes in Group Policy Editor in the following paths.

For Windows XP and Windows Server 2003:
Configuration nodes in Group Policy Editor in the following path:

`Administrative Templates\Windows Components\Windows PowerShell`

For Windows Vista and later versions of Windows:

`Administrative Templates\Classic Administrative Templates\Windows Components\Windows PowerShell`

Policies set in the Computer Configuration node take precedence over policies
set in the User Configuration node.

Expand Down
10 changes: 2 additions & 8 deletions reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes the PowerShell execution policies and explains how to manage them.
Locale: en-US
ms.date: 10/07/2024
ms.date: 02/14/2025
no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings]
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.4&WT.mc_id=ps-gethelp
schema: 2.0.0
Expand Down Expand Up @@ -315,16 +315,10 @@ The **Turn on Script Execution** policy settings are as follows:

The PowerShellExecutionPolicy.adm and PowerShellExecutionPolicy.admx files add
the **Turn on Script Execution** policy to the Computer Configuration and User
Configuration nodes in Group Policy Editor in the following paths.

For Windows XP and Windows Server 2003:
Configuration nodes in Group Policy Editor in the following path:

`Administrative Templates\Windows Components\Windows PowerShell`

For Windows Vista and later versions of Windows:

`Administrative Templates\Classic Administrative Templates\Windows Components\Windows PowerShell`

Policies set in the Computer Configuration node take precedence over policies
set in the User Configuration node.

Expand Down
10 changes: 2 additions & 8 deletions reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes the PowerShell execution policies and explains how to manage them.
Locale: en-US
ms.date: 10/07/2024
ms.date: 02/14/2025
no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings]
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.5&WT.mc_id=ps-gethelp
schema: 2.0.0
Expand Down Expand Up @@ -315,16 +315,10 @@ The **Turn on Script Execution** policy settings are as follows:

The PowerShellExecutionPolicy.adm and PowerShellExecutionPolicy.admx files add
the **Turn on Script Execution** policy to the Computer Configuration and User
Configuration nodes in Group Policy Editor in the following paths.

For Windows XP and Windows Server 2003:
Configuration nodes in Group Policy Editor in the following path:

`Administrative Templates\Windows Components\Windows PowerShell`

For Windows Vista and later versions of Windows:

`Administrative Templates\Classic Administrative Templates\Windows Components\Windows PowerShell`

Policies set in the Computer Configuration node take precedence over policies
set in the User Configuration node.

Expand Down
10 changes: 2 additions & 8 deletions reference/7.6/Microsoft.PowerShell.Core/About/about_Execution_Policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: Describes the PowerShell execution policies and explains how to manage them.
Locale: en-US
ms.date: 10/07/2024
ms.date: 02/14/2025
no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings]
online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.6&WT.mc_id=ps-gethelp
schema: 2.0.0
Expand Down Expand Up @@ -315,16 +315,10 @@ The **Turn on Script Execution** policy settings are as follows:

The PowerShellExecutionPolicy.adm and PowerShellExecutionPolicy.admx files add
the **Turn on Script Execution** policy to the Computer Configuration and User
Configuration nodes in Group Policy Editor in the following paths.

For Windows XP and Windows Server 2003:
Configuration nodes in Group Policy Editor in the following path:

`Administrative Templates\Windows Components\Windows PowerShell`

For Windows Vista and later versions of Windows:

`Administrative Templates\Classic Administrative Templates\Windows Components\Windows PowerShell`

Policies set in the Computer Configuration node take precedence over policies
set in the User Configuration node.

Expand Down