• Network Topology:

  Server:192.168.84.15
  Agent:192.168.84.10
  UA:192.168.84.18

• OUS setting:

  OUS1 = 192.168.84.10,192.168.84.10,,http://192.168.84.18:21112/activeupdate

• When the server is set to use ASE=1 and useSocketHttpAdapter=0, it uses https:

  Server,ofcscan.ini
  ASE=1
  useSocketHttpAdapter=0

• Check the UA Registry:

  [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion]
  "ASE"=dword:00000001
  "UseSocketHTTPAdapter"=dword:00000000

  It also uses HTTPS.

• Check the agent's ous.ini:

  OUS1 = 192.168.84.10,192.168.84.10,,http://192.168.84.18:21112/activeupdate

  When the update source is set to use HTTP but the agent and UA use https, the agent update will fail.

• Check the database dbo.TBL_CLIENT_INFO:

  STATE_FLAG2 =0 in the database means use HTTP
  STATE_FLAG2 =2 in the database means use HTTPS

  Sometimes it is STATE_FLAG2 =0 and sometimes it is STATE_FLAG2 =2.

  

  ^{Click the image to enlarge.}

To make sure that the protocol agent used is consistent with the server, modify the UpdateSource from HTTP to HTTPs:

1. Access the web console by going to Updates > Agents > Update Source.
2. Modify the update source from HTTP to https, and then deploy it to the agents:

   https://192.168.84.18:21112/activeupdate

   In the server's ofcscan.ini, the setting is as shown below:

   ASE=1
   useSocketHttpAdapter=0

3. Update the agent and then check the agent's ous.ini.

   The update source is set with https:

   OUS1 = 192.168.84.10,192.168.84.10,,https://192.168.84.18:21112/activeupdate

4. In the agent's registry, check "ASE" and "useSocketHttpAdapter".
    

   If useSocketHttpAdapter does not exist, that's normal as its default value is 0.

   [HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion]
   "ASE"=dword:00000001
   "useSocketHttpAdapter"=dword:00000000

5. After a while, check the database dbo.TBL_CLIENT_INFO, STATE_FLAG2 =2.