diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1 deleted file mode 100644 index 73cab9e22851..000000000000 --- a/.openpublishing.build.ps1 +++ /dev/null @@ -1,18 +0,0 @@ -param( - [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", - [string]$parameters -) -# Main -$errorActionPreference = 'Stop' - -# Step-1 Download buildcore script to local -Write-Output "download build core script to local with source url: $buildCorePowershellUrl" -$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition -$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" -Invoke-WebRequest $buildCorePowershellUrl -OutFile $buildCorePowershellDestination - -# Step-2: Run build core -Write-Output "run build core script with parameters: $parameters" -$arguments = "-parameters:'$parameters'" -Invoke-Expression "$buildCorePowershellDestination $arguments" -exit $LASTEXITCODE diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index 75e746fe1161..cc766c620f99 100644 --- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 05/16/2024 +ms.date: 10/07/2024 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 @@ -362,7 +362,7 @@ For more information, see [about_Signing][04], > - `Invoke-RestMethod` > - `Invoke-WebRequest` -## Execution policy on Windows Server Core and Window Nano Server +## Execution policy on Windows Server Core and Windows Nano Server When PowerShell 6 is run on Windows Server Core or Windows Nano Server under certain conditions, execution policies can fail with the following error: diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index acffed7bbba0..63016f3d4c22 100644 --- a/reference/7.2/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 03/04/2024 +ms.date: 10/07/2024 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.2&WT.mc_id=ps-gethelp schema: 2.0.0 @@ -25,9 +25,9 @@ for the current user, or for a particular session. You can also use a Group Policy setting to set execution policies for computers and users. Execution policies for the local computer and current user are stored in the -registry. You don't need to set execution policies in your PowerShell profile. -The execution policy for a particular session is stored only in memory and is -lost when the session is closed. +PowerShell configuration files. You don't need to set execution policies in +your PowerShell profile. The execution policy for a particular session is +stored only in memory and is lost when the session is closed. The execution policy isn't a security system that restricts user actions. For example, users can easily bypass a policy by typing the script contents at @@ -137,18 +137,18 @@ execution policies are as follows: The **Process** scope only affects the current PowerShell session. The execution policy is saved in the environment variable - `$env:PSExecutionPolicyPreference`, rather than the registry. When the - PowerShell session is closed, the variable and value are deleted. + `$env:PSExecutionPolicyPreference`, rather than the configuration file. When + the PowerShell session is closed, the variable and value are deleted. - CurrentUser The execution policy affects only the current user. It's stored in the - **HKEY_CURRENT_USER** registry subkey. + **CurrentUser** configuration file. - LocalMachine The execution policy affects all users on the current computer. It's stored - in the **HKEY_LOCAL_MACHINE** registry subkey. + in the **AllUsers** configuration file. ## Managing the execution policy with PowerShell @@ -201,11 +201,11 @@ To change the PowerShell execution policy on your Windows computer, use the need to restart PowerShell. If you set the execution policy for the scopes **LocalMachine** or the -**CurrentUser**, the change is saved in the registry and remains effective +**CurrentUser**, the change is saved in the configuration file and remains effective until you change it again. If you set the execution policy for the **Process** scope, it's not saved in -the registry. The execution policy is retained until the current process and +the configuration file. The execution policy is retained until the current process and any child processes are closed. > [!NOTE] @@ -280,13 +280,13 @@ For example: pwsh.exe -ExecutionPolicy AllSigned ``` -The execution policy that you set isn't stored in the registry. Instead, it's +The execution policy that you set isn't stored in the configuration file. Instead, it's stored in the `$env:PSExecutionPolicyPreference` environment variable. The variable is deleted when you close the session in which the policy is set. You cannot change the policy by editing the variable value. During the session, the execution policy that is set for the session takes -precedence over an execution policy that is set in the registry for the local +precedence over an execution policy that is set in the configuration file for the local computer or current user. However, it doesn't take precedence over the execution policy set by using a Group Policy. @@ -371,7 +371,7 @@ For more information, see [about_Signing][04], > - `Invoke-RestMethod` > - `Invoke-WebRequest` -## Execution policy on Windows Server Core and Window Nano Server +## Execution policy on Windows Server Core and Windows Nano Server When PowerShell 6 is run on Windows Server Core or Windows Nano Server under certain conditions, execution policies can fail with the following error: diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md index 8a04d4e100f5..940fabec22d0 100644 --- a/reference/7.2/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md +++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md @@ -267,7 +267,7 @@ For more information on experimental features, see This setting controls the behavior of logging for PowerShell modules. The setting contains two subkeys: -- `EnableModuleLogging` - to enable session configurations, set the value to +- `EnableModuleLogging` - to enable module logging, set the value to `true`. When enabled, pipeline execution events for members of the specified modules are recorded in the PowerShell log files. - `ModuleNames` - Specifies the name of the modules that should be logged. diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index e96565d175d2..49f96c1ba1cb 100644 --- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 03/04/2024 +ms.date: 10/07/2024 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 @@ -25,9 +25,9 @@ for the current user, or for a particular session. You can also use a Group Policy setting to set execution policies for computers and users. Execution policies for the local computer and current user are stored in the -registry. You don't need to set execution policies in your PowerShell profile. -The execution policy for a particular session is stored only in memory and is -lost when the session is closed. +PowerShell configuration files. You don't need to set execution policies in +your PowerShell profile. The execution policy for a particular session is +stored only in memory and is lost when the session is closed. The execution policy isn't a security system that restricts user actions. For example, users can easily bypass a policy by typing the script contents at @@ -137,18 +137,18 @@ execution policies are as follows: The **Process** scope only affects the current PowerShell session. The execution policy is saved in the environment variable - `$env:PSExecutionPolicyPreference`, rather than the registry. When the + `$env:PSExecutionPolicyPreference`, rather than the configuration file. When the PowerShell session is closed, the variable and value are deleted. - CurrentUser The execution policy affects only the current user. It's stored in the - **HKEY_CURRENT_USER** registry subkey. + **CurrentUser** configuration file. - LocalMachine The execution policy affects all users on the current computer. It's stored - in the **HKEY_LOCAL_MACHINE** registry subkey. + in the **AllUsers** configuration file. ## Managing the execution policy with PowerShell @@ -201,11 +201,11 @@ To change the PowerShell execution policy on your Windows computer, use the need to restart PowerShell. If you set the execution policy for the scopes **LocalMachine** or the -**CurrentUser**, the change is saved in the registry and remains effective +**CurrentUser**, the change is saved in the configuration file and remains effective until you change it again. If you set the execution policy for the **Process** scope, it's not saved in -the registry. The execution policy is retained until the current process and +the configuration file. The execution policy is retained until the current process and any child processes are closed. > [!NOTE] @@ -280,13 +280,13 @@ For example: pwsh.exe -ExecutionPolicy AllSigned ``` -The execution policy that you set isn't stored in the registry. Instead, it's +The execution policy that you set isn't stored in the configuration file. Instead, it's stored in the `$env:PSExecutionPolicyPreference` environment variable. The variable is deleted when you close the session in which the policy is set. You cannot change the policy by editing the variable value. During the session, the execution policy that is set for the session takes -precedence over an execution policy that is set in the registry for the local +precedence over an execution policy that is set in the configuration file for the local computer or current user. However, it doesn't take precedence over the execution policy set by using a Group Policy. @@ -371,7 +371,7 @@ For more information, see [about_Signing][04], > - `Invoke-RestMethod` > - `Invoke-WebRequest` -## Execution policy on Windows Server Core and Window Nano Server +## Execution policy on Windows Server Core and Windows Nano Server When PowerShell 6 is run on Windows Server Core or Windows Nano Server under certain conditions, execution policies can fail with the following error: diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md index 130c13449da0..6a4c503b377a 100644 --- a/reference/7.4/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md +++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md @@ -267,7 +267,7 @@ For more information on experimental features, see This setting controls the behavior of logging for PowerShell modules. The setting contains two subkeys: -- `EnableModuleLogging` - to enable session configurations, set the value to +- `EnableModuleLogging` - to enable module logging, set the value to `true`. When enabled, pipeline execution events for members of the specified modules are recorded in the PowerShell log files. - `ModuleNames` - Specifies the name of the modules that should be logged. diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index 330c489d39c2..2e38f921755d 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 03/04/2024 +ms.date: 10/07/2024 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 @@ -25,9 +25,9 @@ for the current user, or for a particular session. You can also use a Group Policy setting to set execution policies for computers and users. Execution policies for the local computer and current user are stored in the -registry. You don't need to set execution policies in your PowerShell profile. -The execution policy for a particular session is stored only in memory and is -lost when the session is closed. +PowerShell configuration files. You don't need to set execution policies in +your PowerShell profile. The execution policy for a particular session is +stored only in memory and is lost when the session is closed. The execution policy isn't a security system that restricts user actions. For example, users can easily bypass a policy by typing the script contents at @@ -137,18 +137,18 @@ execution policies are as follows: The **Process** scope only affects the current PowerShell session. The execution policy is saved in the environment variable - `$env:PSExecutionPolicyPreference`, rather than the registry. When the + `$env:PSExecutionPolicyPreference`, rather than the configuration file. When the PowerShell session is closed, the variable and value are deleted. - CurrentUser The execution policy affects only the current user. It's stored in the - **HKEY_CURRENT_USER** registry subkey. + **CurrentUser** configuration file. - LocalMachine The execution policy affects all users on the current computer. It's stored - in the **HKEY_LOCAL_MACHINE** registry subkey. + in the **AllUsers** configuration file. ## Managing the execution policy with PowerShell @@ -201,11 +201,11 @@ To change the PowerShell execution policy on your Windows computer, use the need to restart PowerShell. If you set the execution policy for the scopes **LocalMachine** or the -**CurrentUser**, the change is saved in the registry and remains effective +**CurrentUser**, the change is saved in the configuration file and remains effective until you change it again. If you set the execution policy for the **Process** scope, it's not saved in -the registry. The execution policy is retained until the current process and +the configuration file. The execution policy is retained until the current process and any child processes are closed. > [!NOTE] @@ -280,13 +280,13 @@ For example: pwsh.exe -ExecutionPolicy AllSigned ``` -The execution policy that you set isn't stored in the registry. Instead, it's +The execution policy that you set isn't stored in the configuration file. Instead, it's stored in the `$env:PSExecutionPolicyPreference` environment variable. The variable is deleted when you close the session in which the policy is set. You cannot change the policy by editing the variable value. During the session, the execution policy that is set for the session takes -precedence over an execution policy that is set in the registry for the local +precedence over an execution policy that is set in the configuration file for the local computer or current user. However, it doesn't take precedence over the execution policy set by using a Group Policy. @@ -371,7 +371,7 @@ For more information, see [about_Signing][04], > - `Invoke-RestMethod` > - `Invoke-WebRequest` -## Execution policy on Windows Server Core and Window Nano Server +## Execution policy on Windows Server Core and Windows Nano Server When PowerShell 6 is run on Windows Server Core or Windows Nano Server under certain conditions, execution policies can fail with the following error: diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md index 1c340a4cae6c..94fc5d4e1213 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md @@ -267,7 +267,7 @@ For more information on experimental features, see This setting controls the behavior of logging for PowerShell modules. The setting contains two subkeys: -- `EnableModuleLogging` - to enable session configurations, set the value to +- `EnableModuleLogging` - to enable module logging, set the value to `true`. When enabled, pipeline execution events for members of the specified modules are recorded in the PowerShell log files. - `ModuleNames` - Specifies the name of the modules that should be logged. diff --git a/reference/module/index.md b/reference/module/index.md index a35993657dec..82ab914c41dd 100644 --- a/reference/module/index.md +++ b/reference/module/index.md @@ -12,7 +12,7 @@ ms.manager: sewhee ms.product: powershell ms.topic: landing-page quickFilterColumn1: powershell-7.4,windowsserver2022-ps -quickFilterColumn2: azps-12.3.0,sqlserver-ps +quickFilterColumn2: azps-12.4.0,sqlserver-ps quickFilterColumn3: graph-powershell-1.0,systemcenter-ps-2022 title: PowerShell Module Browser ---