The policy deployment from Apex Central to Apex One Vulnerability Protection fails.
Root Cause Analysis
From Apex One agent ...\Trend Micro\iService\iVP\vp_agent*.log, we can see the errors as below shown:
2020:01:08-11:56:25:213 [VPENG][talkToVpServer:141] g_pfnTmSendHttpToOSCEServer failed, responseCode(27) 2020:01:08-11:56:25:213 [VPENG][ProcessNotify:579] talkToVpServer for heartbeat failed 2020:01:08-12:17:01:470 [VPENG][CmdProcessFn:59] FetchData failed: error=0 (0: ERROR_SUCCESS, 997: ERROR_IO_PENDING)
The logs indicate that the Apex One Agent can not communicate with Apex One Server to report Vulnerability Protections status.
To fix the issue, verify the cryptographic keys on the agent. Do the following:
- Open "secpol.msc" using Run or Command Prompt.
- Expand Security settings > Local Policies > Security Options.
- Go to "System Cryptography: Use FIPS compliant algorithms".
- Disable it and try to redeploy the policy again.
If issue persists, check the ofcipcer.dat file:
- Navigate to ..\Program Files (x86)\Trend Micro\Apex One\PCCSRV\Pccnt\Common\.
- Rename ofcipcer.dat to ofcipcer.cer.
- Check the Serial Number, it needs to be the same with the IIS binding certificate.
If they are not the same, replace ofcipcer.dat by public key. For instructions, refer to:
Configuring Apex One to use a certificate signed by corporate Certificate Authority
- Wait until agent gets the new ofcipcer.dat, then redeploy the policy.