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

Create a technical support case if you need further support.

Required actions to perform before or after migrating from Hosted Email Security (HES) 1.9 to 2.0

    • Updated:
    • 22 Aug 2016
    • Product/Version:
    • Hosted Email Security 2.0
    • Platform:
    • N/A N/A
Summary

This article discusses the actions you need to do before or after migrating from HES 1.9 to 2.0.

Details
Public

The current HES administrator console has limited functionality. Do the procedure below to start using the upgraded administrator console:

  1. Update your firewall.

    To ensure that messages will be received from the HES Mail Transfer Agent (MTA), configure your firewall to accept email messages from the following HES IP addressses/CIDR blocks:

    Current:

    • 216.104.0.0/19
    • 216.99.128.0/20
    • 150.70.0.0/16

    Additional:

    • 54.219.191.0/25
    • 54.86.63.64/26
  2. Confirm your outbound server settings on the administrator console.

    If you use Outbound Filtering, confirm that the IP address of your outbound Servers displayed on the Domains screen exactly matches the IP address of your outbound Servers. Any mismatch may prevent the delivery of outbound traffic routed through the service starting soon.

  3. Update your outbound mail server HES relay Fully Qualified Domain Name (FQDN).

    If you use the HES Outbound Filtering, configure your servers to relay mail through the relay FQDN that is specified on your HES console. Using any other FQDN may prevent the delivery of outbound traffic routed through the service starting soon.

     
    If you just recently updated your outbound server IPs, kindly wait for the domain status to go back from “Modifying” to “Activated” state before pointing the smart host to the new FQDN.
  4. Update the FQDN used by the HES Web Services Client.

    If you use the HES Web Services Client to sync HES with your Active Directory, change the configuration as specified for your version of the client listed below to ensure that directory syncing will continue as expected.

    For Ruby sync Web Services Client:

    1. Confirm that the Web Services Client is not running.

      Disable any scheduled tasks (Windows) or cron jobs (Linux) if necessary.

    2. Locate the Web Services Client.

      For example, the default folder is imhs-ws-client.

    3. Using a text editor, open the imhs-config.rb file.
    4. Locate the following string:
      ROOT_URL = https://us.imhs-ws.trendmicro.com/imhs/v1.0/en
    5. Change the string to the ws FQDN that was provided to you via email.
      ROOT_URL = https://<YOUR WS-FQDDN>imhs/v1.0/en
    6. Save and close the file.
    7. Run the client or enable any scheduled tasks or cron jobs.

    For Active Directory (AD) plug-in Web Services Client:

    1. Log in to the Windows Server using credentials that allow you to stop services and modify files.
    2. Stop the following services:
      • Hosted Email Security ActiveDirectory Sync Agent
      • Hosted Email Security ActiveDirectory Sync Service
    3. Locate the Web Services Client.

      For example, the default folder is C:\Program Files (x86)\Trend Micro\Hosted Email Security ActiveDirectory Sync Client.

    4. Using a text editor, open the PluginService.exe.config file.
    5. Locate the following string:
      <add key="WS_SERVICE_URL" value="https://us.imhs-ws.trendmicro.com/imhs/v1.0/en">
    6. Change the string to the WS FQDN that was provided to you via email.

      <add key="WS_SERVICE_URL" value="https://<YOUR WS-FQDN>/imhs/v1.0/en/">

    7. Save and close the file.
    8. Restart the following services:
      • Hosted Email Security ActiveDirectory Sync Service
      • Hosted Email Security ActiveDirectory Sync Agent
  5. Update your MX record.
     
    Trend Micro recommends performing the step this step after completing all the steps above that apply to your configuration. After HES detects your MX record has been updated as directed in this step, HES marks your account as ready to upgrade.

    To ensure your HES service continues without any interruption, modify the MX record for your domain to the inbound FQDN that was provided to you via email.

Premium
Internal
Rating:
Category:
Configure; Upgrade; Update; Migrate
Solution Id:
1107135
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.


Need More Help?

Create a technical support case if you need further support.