Set the default source path for Update-Help

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 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: 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.

Set the default source path for Update-Help

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 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: 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.

Turn on Module Logging

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 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 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. 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.

Turn on Module Logging

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 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 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. 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.

Turn on Script Execution

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 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. 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. “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. “

Turn on Script Execution

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 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. 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. “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. “