|
| 1 | +<?xml version="1.0" encoding="utf-8"?> |
| 2 | +<policyDefinitionResources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" revision="1.0" schemaVersion="1.0" xmlns="http://www.microsoft.com/GroupPolicy/PolicyDefinitions"> |
| 3 | + <displayName>PowerShell Core</displayName> |
| 4 | + <description>This file contains the configuration options for PowerShell Core</description> |
| 5 | + <resources> |
| 6 | + <stringTable> |
| 7 | + <string id="AllScripts">Allow all scripts</string> |
| 8 | + <string id="AllScriptsSigned">Allow only signed scripts</string> |
| 9 | + <string id="EnableScripts">Turn on Script Execution</string> |
| 10 | + <string id="EnableScripts_Explain">This policy setting lets you configure the script execution policy, controlling which scripts are allowed to run. |
| 11 | + |
| 12 | +If you enable this policy setting, the scripts selected in the drop-down list are allowed to run. |
| 13 | + |
| 14 | +The "Allow only signed scripts" policy setting allows scripts to execute only if they are signed by a trusted publisher. |
| 15 | + |
| 16 | +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. |
| 17 | + |
| 18 | +The "Allow all scripts" policy setting allows all scripts to run. |
| 19 | + |
| 20 | +If you disable this policy setting, no scripts are allowed to run. |
| 21 | + |
| 22 | +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." |
| 23 | + |
| 24 | +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 "Allow local scripts and remote signed scripts."</string> |
| 25 | + <string id="PowerShell">PowerShell Core</string> |
| 26 | + <string id="RemoteSignedScripts">Allow local scripts and remote signed scripts</string> |
| 27 | + <string id="SUPPORTED_WIN7">At least Microsoft Windows 7 or Windows Server 2008 family</string> |
| 28 | + |
| 29 | + <string id="EnableModuleLogging">Turn on Module Logging</string> |
| 30 | + <string id="EnableModuleLogging_Explain"> |
| 31 | + This policy setting allows you to turn on logging for PowerShell Core modules. |
| 32 | + |
| 33 | + If you enable this policy setting, pipeline execution events for members of the specified modules are recorded in the PowerShell Core log in Event Viewer. Enabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to True. |
| 34 | + |
| 35 | + If you disable this policy setting, logging of execution events is disabled for all PowerShell Core modules. Disabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to False. |
| 36 | + |
| 37 | + If this policy setting is not configured, the LogPipelineExecutionDetails property of a module determines whether the execution events of a module are logged. By default, the LogPipelineExecutionDetails property of all modules is set to False. |
| 38 | + |
| 39 | + To add modules to the policy setting list, click Show, and then type the module names in the list. The modules in the list must be installed on the computer. |
| 40 | + |
| 41 | + 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. |
| 42 | + </string> |
| 43 | + |
| 44 | + <string id="EnableTranscripting">Turn on PowerShell Transcription</string> |
| 45 | + <string id="EnableTranscripting_Explain"> |
| 46 | + This policy setting lets you capture the input and output of PowerShell Core commands into text-based transcripts. |
| 47 | + |
| 48 | + If you enable this policy setting, PowerShell Core will enable transcription logging for PowerShell Core and any other |
| 49 | + applications that leverage the PowerShell Core engine. By default, PowerShell Core will record transcript output to each users' My Documents |
| 50 | + directory, with a file name that includes 'PowerShell_transcript', along with the computer name and time started. Enabling this policy is equivalent |
| 51 | + to calling the Start-Transcript cmdlet on each PowerShell Core session. |
| 52 | + |
| 53 | + If you disable this policy setting, transcription logging of PowerShell-based applications is disabled by default, although transcripting can still be enabled |
| 54 | + through the Start-Transcript cmdlet. |
| 55 | + |
| 56 | + If you use the OutputDirectory setting to enable transcription logging to a shared location, be sure to limit access to that directory to prevent users |
| 57 | + from viewing the transcripts of other users or computers. |
| 58 | + |
| 59 | + 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. |
| 60 | + </string> |
| 61 | + |
| 62 | + <string id="EnableScriptBlockLogging">Turn on PowerShell Script Block Logging</string> |
| 63 | + <string id="EnableScriptBlockLogging_Explain"> |
| 64 | + This policy setting enables logging of all PowerShell script input to the Microsoft-Windows-PowerShell/Operational event log. If you enable this policy setting, |
| 65 | + PowerShell Core will log the processing of commands, script blocks, functions, and scripts - whether invoked interactively, or through automation. |
| 66 | + |
| 67 | + If you disable this policy setting, logging of PowerShell script input is disabled. |
| 68 | + |
| 69 | + If you enable the Script Block Invocation Logging, PowerShell additionally logs events when invocation of a command, script block, function, or script |
| 70 | + starts or stops. Enabling Invocation Logging generates a high volume of event logs. |
| 71 | + |
| 72 | + 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. |
| 73 | + </string> |
| 74 | + |
| 75 | + <string id="EnableUpdateHelpDefaultSourcePath">Set the default source path for Update-Help</string> |
| 76 | + <string id="EnableUpdateHelpDefaultSourcePath_Explain">This policy setting allows you to set the default value of the SourcePath parameter on the Update-Help cmdlet. |
| 77 | + |
| 78 | +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. |
| 79 | + |
| 80 | +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. |
| 81 | + |
| 82 | +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. |
| 83 | + </string> |
| 84 | + <string id="ConsoleSessionConfiguration">Console session configuration</string> |
| 85 | + <string id="ConsoleSessionConfiguration_Explain">Specifies a configuration endpoint in which PowerShell is run. This can be any endpoint registered on the local machine including the default PowerShell remoting endpoints or a custom endpoint having specific user role capabilities.</string> |
| 86 | + |
| 87 | + <!--<string id="PowerShell">PowerShell Core</string>--> |
| 88 | + </stringTable> |
| 89 | + <presentationTable> |
| 90 | + <presentation id="EnableScripts"> |
| 91 | + <checkBox refId="UseWindowsPowerShellPolicySetting">Use Windows PowerShell Policy setting.</checkBox> |
| 92 | + <dropdownList refId="ExecutionPolicy" noSort="true">Execution Policy</dropdownList> |
| 93 | + </presentation> |
| 94 | + <presentation id="EnableModuleLogging"> |
| 95 | + <checkBox refId="UseWindowsPowerShellPolicySetting">Use Windows PowerShell Policy setting.</checkBox> |
| 96 | + <text>To turn on logging for one or more modules, click Show, and then type the module names in the list. Wildcards are supported.</text> |
| 97 | + <listBox refId="Listbox_ModuleNames" required="false">Module Names</listBox> |
| 98 | + <text>To turn on logging for the PowerShell Core core modules, type the following module names in the list:</text> |
| 99 | + <text>Microsoft.PowerShell.*</text> |
| 100 | + <text>Microsoft.WSMan.Management</text> |
| 101 | + </presentation> |
| 102 | + <presentation id="EnableTranscripting"> |
| 103 | + <checkBox refId="UseWindowsPowerShellPolicySetting">Use Windows PowerShell Policy setting.</checkBox> |
| 104 | + <textBox refId="OutputDirectory"><label>Transcript output directory</label></textBox> |
| 105 | + <checkBox refId="EnableInvocationHeader">Include invocation headers:</checkBox> |
| 106 | + </presentation> |
| 107 | + <presentation id="EnableScriptBlockLogging"> |
| 108 | + <checkBox refId="UseWindowsPowerShellPolicySetting">Use Windows PowerShell Policy setting.</checkBox> |
| 109 | + <checkBox refId="EnableScriptBlockInvocationLogging">Log script block invocation start / stop events:</checkBox> |
| 110 | + </presentation> |
| 111 | + <presentation id="EnableUpdateHelpDefaultSourcePath"> |
| 112 | + <checkBox refId="UseWindowsPowerShellPolicySetting">Use Windows PowerShell Policy setting.</checkBox> |
| 113 | + <textBox refId="SourcePathForUpdateHelp"> |
| 114 | + <label>Default Source Path</label> |
| 115 | + </textBox> |
| 116 | + </presentation> |
| 117 | + <presentation id="ConsoleSessionConfiguration"> |
| 118 | + <textBox refId="ConsoleSessionConfigurationName"> |
| 119 | + <label>ConsoleSessionConfigurationName</label> |
| 120 | + </textBox> |
| 121 | + </presentation> |
| 122 | + </presentationTable> |
| 123 | + </resources> |
| 124 | + |
| 125 | +</policyDefinitionResources> |
0 commit comments