Technical Tip: How to ensure that FortiClient receives a Signature from FortiManager when FortiManager acts as a Local FDS

When FortiManager acts as local FDS, the FortiClient needs to request the Signature from FortiManager and FortiManager will push the Signature. This article uses the Vulnerability Signature as an example.

FortiClient Signature ID on FortiManager:

FVDB00000 --- AntiVirus Signatures

FVDB01300 --- AntiVirus Extended

FVDB01900 --- AntiVirus Pallas

FVDB01600 --- Vulnerability

FVDB01500 --- IRDB Signature

FCIC00101 --- ICDB Signature

To confirm the FortiClient request signature, run the following debug commands from CMD (inside the FortiClient Folder).

Run a live debug to check the FortiClient request and response to the Signature:

FMG # diagnose debug app fdssvrd 255 
FMG # diagnose debug enable

Based on the behavior shown, it is possible to confirm that the FortiClient sent the request, that the FortiManager received the request, and that the FortiManager pushed the Signature.

If FortiClient does not request any Signature, the debug will show that no Vulnerability Signature has been requested from FortiClient.

• FortiClient not sending FVDB01600 request:

• FortiManager pushes the Signature that has been requested from FortiClient, except FVDB01600:

Related article:

Technical Tip: How to configure FortiManager as FortiGuard server for FortiClient and EMS