PowerShell adapter module
The PowerShell adapter process is a part of AutoPilot AD-Utility module and is bundled under the terminal folder of the AD-Utility module.
The following table describes the process inputs for the PowerShell adapter.
PowerShell adapter process inputs
Input | Description |
---|---|
| Specifies the name of the adapter to be used for this process |
| Specifies the fully-qualified host name or IP address of the remote or the local computer |
| Specifies the PowerShell command to be executed, including arguments |
| Specifies the method of encryption used for the specified command value |
| Specifies the time, in seconds, allotted to complete the execution of the command |
| Contains the host name or the IP address of the remote or local computer |
| Contains the user name to be used for authentication on the remote host |
| Contains the password corresponding to the specified user name for authentication on the remote host |
| Specifies the method of encryption used for the password provided |
| Specifies the version of PowerShell on which the command is to be executed
Note: When you run PowerShell commands on a remote host which has PowerShell version 3.0 or 4.0 installed, the PowerShell module commands such as import-module or get-module might fail. As a workaround, you can enable the PowerShell remote commands feature to run commands. |
| Specifies whether the user profile is to be loaded |
| Specifies the PowerShell console file to be loaded |
| Specifies the supporting CharSet |
| Specifies whether to enable the remoting feature of PowerShell version 2.0 Notes
|
<log-on-with-user-credentials> | Starts a service on the remote computer
|
<impersonate-user> | Specifies whether to enable the user impersonation and allow the specified user to execute tasks by using the security context of another user (For example, BAO service running under a user account) For example, a service running as LocalSystem could access network resources by impersonating a specific user account. This account would have been configured with the necessary permissions to access a network resource, something the service would not be able to do otherwise.For more information about how user impersonation works, see Impersonation If set to true, the Service Control Manager (SCM) API is invoked with the user specified in the adapter request or configuration. By default, the xCmd utility runs under the security context of the BAO service running under a user account. When we specify Valid values: true, false (default) |
<service-launch-mode> | Specifies the mode to launch the xCommand service on a remote system By default, the xCommand utility is launched on 32-bit mode. Valid value: 64bit Note Specify 64bit only if you want to launch the xCommand service on a 64-bit image mode on the target system. BMC recommends that you do not specify any value if 64-bit is not required as it can affect the time taken for the request to execute. |
The following table describes the process output parameters for the PowerShell adapter.
PowerShell adapter outputs
Output Element | Description |
---|---|
| Contains the result returned from the adapter request
|
Comments
Log in or register to comment.