Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

ScanMail for Exchange (SMEX) Servers do not appear in the Server Management console

    • Updated:
    • 13 Mar 2020
    • Product/Version:
    • ScanMail for Exchange 12.0
    • ScanMail for Exchange 12.0
    • ScanMail for Exchange 12.5
    • ScanMail for Exchange 12.5
    • ScanMail for Exchange 14.0
    • ScanMail for Exchange 14.0
    • Platform:
    • Windows 2008 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2012 Server Essentials
    • Windows 2012 Standard

Local or remote Exchange servers do not appear in the Server Management console. This may be caused by a connection issue involving permissions or firewall policies, or certain services that need to be running.


The following are general requirements for license and Active Directory implementation:

  • The target server must have an Activation Code.
  • Target and Local Server must be using the same Activation Code type.
  • SMEX Servers need to all all be part of the same forest.

Please go through the following list to check for the possible causes of this problem:

  • Verify the connection between the SMEX servers.
    Make sure that ping (ICMP protocol) is allowed on the servers which will report to the Server Management console.
    The current configuration for ICMP query is set to 1. If the initial query fails, then the server will not appear in the Server Management.
  • Firewall policies
    Check and make sure that the following ports are open:
    • TCP: 389 (AD) [LDAP]
    • TCP: 636 (AD) [LDAP/SSL]
    • TCP: 3268 (GC) [LDAP]
    • TCP: 3269 (GC) [LDAP/SSL]
    • TCP: 139,445
    • UDP: 137,138 (if necessary)
    Follow this procedure in using the LDP tool. This will verify the LDAP connection when SMEX master is configured to run with a domain account:
    1. Run the LDP tool.

      Run LDP tool

      Click image to enlarge.

    2. Upon opening the tool, click Connect.
    3. Input the domain controller server's FQDN or IP address in the Server field, and input port 389. Click OK.


      Click image to enlarge.

    4. Click Connection > Bind, then input the account that runs the SMEX Master Service.

      Input account

      Click image to enlarge.

    5. Click Browser > Search, and use the following parameters:
      • The Base DN should be “CN=Configuration...”, where DC would depend according to your AD environment.
      • For the Filter column, search "objectCategory=msExchExchangeServer".
      • For Scope, select Subtree.

      Search parameters

      Click image to enlarge.

    6. After the search is done, you should see the following output:


      Click image to enlarge.

      If the server could not be queried, there may be an environment issue.

  • Check for the Winreg permission (for all SMEX servers that should be listed on the server management).
    Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
    1. Open the Registry Editor.
    2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg.
    3. Click winreg Permissions.
    4. Add the SMEX Admin Group for the target domain.
    5. Select Allow for the Read permission.
  • Running services
    Make sure that the Remote Procedure Call (RPC) protocol, the "ScanMail for Microsoft Exchange Remote Configuration Server" and the “Remote Registry” services are running on the servers. SMEX utilizes these services for configuration replication. Also make sure that RPC protocol is not disabled by a Group Policy.
  • User Account
    The account used to log in to the SMEX services is part of the SMEX admin group.
Configure; Troubleshoot
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.