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

Create a technical support case if you need further support.

Replacing the old Trend Micro Web Security (TMWS) on-premises gateways with the new 3.4.1 version

    • Updated:
    • 19 Jan 2021
    • Product/Version:
    • Trend Micro Web Security 3.0
    • Platform:
Summary

In TMWS, you may encounter the following:

  • TMWS 3.4.1 has been successfully installed, but not registered.

    Refer to the TMWS 3.4.1 Installation Guide for more information.

  • The old on-premises gateway version status on the management console can be “Online” or “Unregistered” or ”Offline”.

    on-prem status

This article will provide the steps on how to replace the old on-premises gateways with the new version, 3.4.1 to resolve these issues.

Details
Public

To replace on-premises gateway:

  1. Log on to the management console, get the “Gateway Name” of the old on-premises gateway version.

    get Gateway Name

  2. Log on to the newly installed on-premises web console (TMWS 3.4.1) then go to Administration > Register to Cloud Console.

    Register to Cloud Console

    1. Enter the following parameters:

      ITEMSETTINGCOMMIT
      Display nameThe name for the on-premises gatewayThis field must be the same as the name
      of the old on-premises gateway version, which you get from Step 1.
      Registration tokenPaste or type the registration token
      obtained from the management console in the text box.
       
      Duplicate check

      The options are:

      • Do not allow duplicates.
      • Replace the existing
        on-premises gateway.
      For this field you must select
      “Replace the existing on-premises gateway”.
      Description(Optional) Specify a meaningful description
      to identify the on-premises gateway easily.
       

      input parameters

    2. Click Register.
  3. Check the Status of on-premises gateways.

    • On-premises web console:

      On-prem web console

    • Management console:

      Management console

  4. Once completed, users can use the new FQDN/IP address as proxy or still use the old FQDN mapping the new on-premises to the new IP address as proxy.
  5. Power Off the old on-premises gateway version.
 
  • Users do not need to re-configure the authentication settings or policies if policies exist for the old on-premises gateways.
  • Users can query the new on-premises' Raw logs, but the Raw logs of the old on-premises gateway version cannot be queried from the management console.
 
Premium
Internal
Partner
Rating:
Category:
Configure; Update
Solution Id:
000283880
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.