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”.
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.
To replace on-premises gateway:
Log on to the management console, get the “Gateway Name” of the old on-premises gateway version.
Log on to the newly installed on-premises web console (TMWS 3.4.1) then go to Administration > Register to Cloud Console.
Enter the following parameters:
ITEM SETTING COMMIT Display name The name for the on-premises gateway This field must be the same as the name
of the old on-premises gateway version, which you get from Step 1.
Registration token Paste or type the registration token
obtained from the management console in the text box.
The options are:
- Do not allow duplicates.
- Replace the existing
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.
- Click Register.
Check the Status of on-premises gateways.
- 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.
- 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.