Exchange Server Monitor - FAQs

Exchange Server Monitor - FAQs

1. What are the ports used in Exchange Server monitoring?

  1. WMI mode:
    1. Remote Procedure Call (RPC) (default : 135)
    2. WMI uses DCOM for remote communication. The server monitored by Applications Manager uses a random port number above 1024 by default to respond. Refer here for more details.
  2. PowerShell mode:
    1. PowerShell remoting - TCP 5985 and 5986
    2. Exchange PowerShell session - TCP 80 and 443
Note: In some cases, PowerShell remoting may work without port 5986, but ensure that ports 80 and 443 on the remote server are accessible from the AppManager server to fetch Mailbox and Database statistics.

2. What to do if you can retrieve data when running the script separately, but data collection does not happen in the Applications Manager Exchange Server monitor? 

  1. Check whether the prerequisites are done using the hostname or IP address or FQDN. Verify which of these are used to run the script and ensure the same is configured in the Exchange Server monitor. If there is a discrepancy, use the value that worked while running the script manually. Check if the Username is used along with domain name. 
  2. Refer to the following KB article for steps to Logon Applications Manager service with Administrator user to use elevated PowerShell during data collection.
  3. Try running the script directly from command prompt. Open Command Prompt as administrator in the Applications Manager server and run the below command.
Command: 
            powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile "&{& '<script-with-full-path>' <arguments>}"
Example: 
            powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile "&{& '<AppManager-Home>\working\conf\application\scripts\powershell\TestConnectivity.ps1' 'host' 'username' 'password'}"
Note: Refer to this KB for the list of scripts which are used to fetch the data in Exchange Server monitor

3. What to do if your mailbox names contain characters from other languages but appear as unknown characters (?) in the Applications Manager GUI?

  1. This issue may occur if the PowerShell Console encoding does not support the specific language. 
  2. We have supported an option in the scripts to set the PowerShell Console encoding to UTF-8, which supports most common languages.
  3. Follow these steps:
    1. Navigate to <Appmanager-Home>\working\conf\application\scripts\powershell directory and take backup of EX_Mailboxes.ps1 and EX_Mailbox_Statistics.ps1 scripts.
    2. Edit the scripts and update the line "$changeOutputEncoding = $false" as "$changeOutputEncoding = $true"
    3. Save the file and try polling the monitor again.

4. What to do if lot of files are created in C:\ drive (making the drive full) while monitoring Exchange Server via Powershell mode?

When powershell mode is used for monitoring Exchange server, the processing of commands is logged in some .psd1 files. This logging property is specified in "Local Group Policy Editor".

By default, logging is disabled. In case if the customer environment has those logging property enabled, then lot of files will be created in C:\ drive quickly making it full.

Resolution :

                  New to ADSelfService Plus?

                    • Related Articles

                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...
                    • REST API Monitor - FAQS

                      1. What to do when Basic Authentication fails in REST API monitor? When Basic Authentication fails in the REST API monitor, follow the below steps to troubleshoot the error. Ensure the credentials provided in Applications Manager (Username and ...
                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the below steps 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 this help ...
                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...
                    • Troubleshooting URL Monitor

                      When configuring a URL monitor in Applications Manager, you might encounter several errors related to accessibility, configuration, or server-side issues. Below are common errors along with step-by-step troubleshooting instructions to help you ...