Supportability > Supported Protocols > PowerCmd Protocol > PowerCmd Protocol Troubleshooting

PowerCmd Protocol Troubleshooting

This section describes the troubleshooting for the PowerCmd protocol.

Before starting troubleshooting with the PowerCmd protocol, make sure that the following steps are performed:

  1. The Data Flow Probe machine installed .Net framework 3.5.
  • Problem: A remote host cannot be connected by the PowerCmd protocol.

    Solution: Check if the PowerCmd connection can be made between Data Flow Probe and the target host. To do so,

    1. Log in to the Data Flow Probe machine.
    2. Locate the PowerCmd.ps1 file in the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources directory.
    3. Open the Command Prompt window in the same directory.
    4. At the Command Prompt, invoke the following command:

      powershell .\PowerCmd.ps1 <machine name or ip> <username> <password>
    5. The output should be like as follows:

      powershell .\PowerCmd.ps1 1.2.3.4 admin password
      Connecting to 1.2.3.4
      MAM:Remote>hostname
      myremotehost1
      MAM:Remote>
  • Problem: The PowerCmd.ps1 file in the <DataFlowProbe_Home>\runtime\probeManager\discoveryResources directory cannot be loaded because the execution of scripts is disabled on this system.

    Solution: By default, the PowerShell scripts are not allowed to execute on the Data Flow Probe machine if the scripts are not signed. To enable the feature, refer to Step 4.