3.4.3 Windows PowerShell Communication Setting

To use the operation component "Execute arbitrary command" or "Collect fingerprint", which uses Windows PowerShell communication, execute the operation shown below.

In order to give directions to each server using PowerShell in the operation component, the following Management Server/Business Server settings are required.
- Management Server settings
  1. Start Windows PowerShell as the administrator.
    Start->> All Programs >> Accessory >> Windows PowerShell >> Windows PowerShell >> Execute the setup as an administrator.
  2. Specify the business server machine name and the IP address and enter the command below. Press "y" to update TrustedHosts on the WinRM client.
    For a single business server:
    Set-Item WSMan:\localhost\Client\TrustedHosts -value "<Business server machine name>,<Business server IP address>"
    For multiple business servers:
    Specify the machine name and IP address in pairs and separate using commas, as shown below.
    "Set-Item WSMan:\localhost\Client\TrustedHosts -value "<Business server 1 machine name>,<Business server 1 IP address>,<Business server 2 machine name>,<Business server 2 IP address>,..."
  3. Enter the following command, then press "y" to set the PowerShell script execution policy as "RemoteSigned".
    Set-ExecutionPolicy remotesigned
  - Note 1: If the Management Server operating system is 64-bit, start Windows PowerShell (x86) as the administrator before configuring the settings.
- Business Server settings
  1. Start Windows PowerShell as the administrator.
    Start >> All Programs >> Accessory >> Windows PowerShell >> Windows PowerShell >> Execute the setup as an administrator.
  2. Enter the following command, then press "y" to allow the WinRM service.
    Enable-PSRemoting
  - Note 1: After "y" is pressed, the content may be checked again. In this case, press "y" again.
  Note
  If the business server has 64-bit architecture, use the PowerShell below and execute each of the PowerShell commands as an administrator.
  - If the 32-bit edition of Systemwalker Runbook Automation Agent is installed on the business server: x86 PowerShell
  - If the 64-bit edition of Systemwalker Runbook Automation Agent is installed on the business server: 64-bit PowerShell
When using a PowerShell to execute commands for a different server, a maximum limit is set for the following items on that server. The business server may require expansion depending on the command being executed.
- Maximum memory size for each command being executed
  When executing batch files, this includes the memory used by processes started up by the start command from the batch file, or the cmd.exe process.
- The number of processes generated simultaneously from a single command (including child processes)
- The number of connections that can be established simultaneously by a single connecting user
  The number of 'execute arbitrary command' operation components specifying the same connecting user that can be executed simultaneously for the same business server.
Use the commands below to check the values set in the business server.
- Maximum memory size for each command being executed:
```
Get-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB
```
- Number of processes generated simultaneously by a single command:
```
Get-Item WSMan:\localhost\Shell\MaxProcessesPerShell
```
- Number of connections that can be established simultaneously by a single connecting user:
```
Get-Item WSMan:\localhost\Shell\MaxShellsPerUser
```
When using "execute arbitrary command" in an operation component to issue the commands below, execute a command to extend the settings on the business server.
- When specifying a large value for the memory size when java is executed and then executing a java command
- When specifying a command that increases the memory size by specifying a large-scale file
- When the manual for the specified command states that a large amount of memory will be used
The examples below show how to extend various settings.
- Example: Extend the maximum memory size to 2000M.
```
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 2000
```
- Example: Extend the maximum number of simultaneous processes to 100.
```
Set-Item WSMan:\localhost\Shell\MaxProcessesPerShell 100
```
- Example: Extend the maximum number of simultaneous connections per user to 500.
```
Set-Item WSMan:\localhost\Shell\MaxShellsPerUser 500
```
  Note
  If the business server has 64-bit architecture, use the PowerShell below and execute each of the PowerShell commands as an administrator.
  - If the 32-bit edition of Systemwalker Runbook Automation Agent is installed on the business server: x86 PowerShell
  - If the 64-bit edition of Systemwalker Runbook Automation Agent is installed on the business server: 64-bit PowerShell
Refer to "Running Remote Commands" in Microsoft Corporation's online "TechNet" library for further information on configuring settings.