Windows PowerShell remote connection requirements


Before you configure and use the KM, ensure that you have the following prerequisites installed and running on the monitoring system.

How to gain access to a monitoring system and configured devices

To gain access to monitoring system and configured devices, the following prerequisites should be met:

  • .Net 3.5 and above.
  • Windows PowerShell 2.0 and above.
  • Configured user should be the domain user and local admin on the remote device that is configured to run the scripts.
  • WinRm should be installed and configured on both monitoring system and remote system that is configured to run the scripts. To configure WinRm on both systems, open command prompt as an administrator and execute Winrm quickconfig command.
  • The remote system that is configured to run the scripts should be in the TrustedHost on the monitoring system. This can be achieved using any of the two ways:
    • Using TrueSight or CMA policy. Upon selecting All or Device, the system gets listed on the TrustedHost.

      WinRM.png
    • Using the command line by running the following
      • winrm set winrm/config/client @{TrustedHosts="*"} (for all devices)
      • winrm set winrm/config/client @{TrustedHosts="{Device name} (for specific device)

How to transfer a file from a monitoring system to a remote system

To use the script file transfer feature from a monitoring system to a remote devices, the following should be enabled:

  • samba must be enabled.
  • C$ must be accessible

How to access PowerShell script from a remote system

To access the PowerShell script from a remote device for execution, the following permission should be set:

  • Set-ExecutionPolicy RemoteSigned

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*