The Policy Server gets its proxy configuration from the Registry Key. Users can set their proxy configuration by following these steps:

1. Create an encrypted password using CommandLineInstallerHelper.exe.

   

   Click image to enlarge.

2. In the search box or Run window, type "regedit" then press Enter. The Registry Editor opens.
3. Go to HKEY_LOCAL_MACHINE\\SOFTWARE\\Trend Micro, Inc.
4. Create a new key named "NetworkProxy".

5. Create the following values to describe proxy setting:

   1. String value “ProxyServer”: Specifies the domain or IP of the proxy server. For example, "100.0.0.1" or "proxy.trend.com".
   2. DWORD value “ProxyPort”: Defines the proxy server port. For example, 80 (Decimal). If there is no this registry value, the default value is 80 (Decimal).
       

      To avoid any errors, ensure that the ProxyPort is using the correct format. For more information, refer to "License Expired" error shows while activating the Full Disk Encryption server license.

       

   3. DWORD value “ProxyType”: Integer value indicating proxy type:

      0: HTTP proxy.
      1: SOCKS proxy. PrModule supports both SOCKs 4 and SOCKs 5.
      If there is no this registry, the default value is 0.

   4. When you set proxy configuration in registry key, you may don’t need input the user name and password if you use http proxy (Proxy Type is 0).
   5. String value “Account”: Defines the account ID needed for proxy server authentication.

   6. String value “Password”: Defines the password for proxy server authentication. User need to input an encrypted password which must encrypted by CommandLineInstallerHelper.exe.

      

      Click image to enlarge.

The Policy Server communicates with the PR backend server in 3 parts:

1. When installing the Policy server.

2. When it is scheduled to update the license.

   After PolicyServerWindowsService starts, the license will be checked once for 10 minutes and then the license will be checked once a day.

3. When renewing the license using TMEE_LicenseRenewal.exe.

Using Renewing license tool as an example, if the user inputs an expired AC, TMEE_LicenseRenewal.exe will connect to the PR server to validate if the AC is extended. We can check Diagnostic Monitor to know if the correct proxy configuration is set to the PR module and know the return code from PR module.

Click image to enlarge.

1. If the result code is E001005A, check the connection between the ProxyServer and our license backend server. You can download the free ProxyChecker tool that allows you to test the proxy server. Here is an example:

   [54:53] Testing Started.
   Proxy Server
   Address:
   Protocol: HTTP
   Authentication: NO

   [54:53] Starting: Test 1: Connection to the Proxy Server
   [54:53] IP Address: xx.xx.xx.xx:0000
   [54:53] Connection established
   [54:53] Test passed.
   [54:53] Starting: Test 2: Connection through the Proxy Server
   [54:53] Connection to www.microsoft.com:443 established through the proxy server.
   [54:53] A default web page was successfuly loaded.
   [54:53] Test passed.
   [54:53] Starting: Test 3: Proxy Server latency
   [54:54] Latency = 27 ms
   [54:54] Test passed.
   [54:54] Testing Finished.

2. You can also use Internet Explorer's Proxy to validate the connection by following these steps:

   1. Open Internet Explorer > Internet Options > LAN Settings > Local Area Network (LAN) Settings.
   2. Configure your proxy settings and check “Use a proxy server for you LAN”.
       

      On certain environments which uses a proxy server, the "License Expired" error may occur. To resolve this issue, refer to "License Expired" error shows while activating the Full Disk Encryption server license

       
   3. Open the License Update link in your browser.

   This procedure only validates that the proxy server can connect with our license backend server.

   

   Click image to enlarge.

The PR module 1.2.0.1063 does not support request by server name through socks proxy. The PR module needs an IP address to send a request to socks proxy. Since the name of PR server - licenseupdate.trendmicro.com,cannot be resolve in the policy server side, the PR module will not send a request to the socks proxy.

The following are workarounds when you encounter this issue:

• In the policy server side add the following setting in the host file that is located in %windir%\system32\drivers\etc\hosts 66.180.84.8 licenseupdate.trendmicro.com.

  

  Click image to enlarge.

• For Windows server 2008 and later versions, make sure that the default gateway is not empty. If the gateway is empty, the OS will not try to resolve the host name.