During a pattern update, the following error is encountered:
“Error: ActiveUpdate was unable to connect to the Network.”
Furthermore, from collected logs, TmuDump.txt shows errors on certificate verification:
"Inf 20180211 13:55:05 33260 39764 Certificate Number:1
Err 20180211 13:55:05 33260 39764 Verify certificate failure, error code=20
Err 20180211 13:55:05 33260 39764 unable to get local issuer certificate
Err 20180211 13:55:05 33260 39764 X509 certificate verification failed
Err 20180211 13:55:05 33260 39764 certificate verify not ok
Err 20180211 13:55:05 33260 39764 HttpsConnection: SSL verify peer failed
Err 20180211 13:55:05 33260 39764 TmDownloader: HTTPS connection or server authentication failed "
By default, SMEX 12.5 uses HTTPS to connect to ActiveUpdate (AU). For instances that a proxy may not be configured properly causing a pattern update failure, an alternative would be to use HTTP instead.
Follow these steps:
- Connect to the AU HTTP server, and modify the following registry key value:
Path:HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\ScanMail for Exchange\CurrentVersion
Key: AUFromHTTPSServer
Type: DWORD
Value: Set to O (default is 1.) - Enable custom update source option in the SMEX 12.5 UI by adding the following registry key:
Path:HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\ScanMail for Exchange\CurrentVersion
Key: AUFromOtherSource
Type: DWORD
Value: 1 - Verify AU manual update if it goes through.
