Troubleshooting PowerShell Remoting
PowerShell remoting is used in Exchange Server, SharePoint Server, Active Directory, MSMQ, and Biztalk Server monitors to connect to remote servers for data collection. If you are experiencing issues with PowerShell remoting, follow the steps below to troubleshoot:
Note: It is recommended to use an Administrator account for PowerShell monitoring. If you are using a non-admin user account, ensure that you have completed the steps outlined in this KB.
- Ensure that all the prerequisites mentioned in this page have been implemented.
- Ensure that the following PowerShell ports, 5985 and 5986, are open on the remote server and accessible from the server where Applications Manager is installed.
- Check if you are able to create a basic PSSession with the remote server with the following steps:
- Open the PowerShell Console with administrator privileges
- Run this command: $testSession= New-PSSession -ComputerName <REMOTE-HOSTNAME> -Credential Get-Credential
- A pop-up will appear, prompting you to enter the credentials for the remote server.
- If any error occurs, perform the necessary configuration or setup to resolve it
- If the command in step ii executes without any errors, remove the test session by running: Get-PSSession | Remove-PSSession
If you encounter any errors in step ii despite completing the prerequisites, please consult your server team or Microsoft support for assistance, as PSSession is a standard feature of Windows Server.
Once the above steps are completed and you are able to establish a basic connection, follow the steps below to run a basic connectivity script.
Open PowerShell in administrator mode on the machine where Applications Manager is installed.
Go to the <Applications Manager Home>\working\conf\application\scripts\powershell directory.
Execute the below command by replacing hostname, username and password with the credentials of the remote server used in the monitor:
.\TestConnectivity.ps1 'hostname' 'username' 'password'Retrieve the output of the above command.
If you encounter an error or recieve no data for the above script, despite being able to establish a basic connection, please contact our support team at appmanager-support@manageengine.com. Include a screenshot of the completed prerequisites, the output/error message received from the script, and latest Support Information File (SIF) from Applications Manager with 'Print all logs' enabled and the issue reproduced for analysis.
New to ADSelfService Plus?
Related Articles
Microsoft Azure VM (Windows) - Powershell Remoting Failure
To resolve the issue, follow the steps given below: Go to Monitor Actions -> Edit Monitor page and check if Enable Guest OS Monitoring option is enabled. Verify if the Username and Password are correct. Verify whether all the prerequisites are done ...Troubleshooting errors in Exchange Online (PowerShell Mode)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting errors in SharePoint Online (PowerShell mode)
Prerequisites: Ensure that you have met all the prerequisites for the Microsoft 365 monitor. From Applications Manager version 16300 onwards, Microsoft 365 monitor will use Microsoft Graph API as the primary mode of data collection. We have migrated ...Troubleshooting Data Collection Issues in SharePoint Service, Web Applications, Databases and Timer Jobs (MS Office SharePoint monitor - PowerShell Mode)
In MS Office SharePoint monitoring, data for SharePoint Services, Web Applications, Databases, and Timer Jobs is collected using PowerShell. If these metrics are missing, follow the steps below to identify and resolve the issue: 1. Verify the ...