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

[Nur]

Description	This article describes how FortiClient successfully receives a Signature from FortiManager.
Scope	FortiClient v7.2.4, FortiManager v7.4.6.
Solution	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). update_task -s fd_01 update_task -d fd_01 Run a live debug to check the FortiClient request and response to the Signature: FMG # diag debug app fdssvrd 255  FMG # diag debug en   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 expect  FVDB01600: