| Description | This article describes how FortiManager shows FortiGate Policy Package Status become Never Installed, and how to check back previous FortiGate Policy Package at FortiManager. |
| Scope | FortiManager. |
| Solution |
When FortiGate is added into FortiManager, FortiGate Policy Package status shows Never Installed. This is normal as initially it does not perform Import Configuration or Policy Package Installation yet.
After performing Import Configuration or Policy Package Installation, the Policy Package status will show synchronized. At FortiManager, use Policy Package Installation as a scenario, create a new Policy Package, and add FortiGate into this new Policy Package’s Installation Tagerts.
FortiManager performs Policy Package Installation, Policy Package Status will show the Policy Package name and the status becomes Synchronized.
In this example: Remove the Policy Package Installation Target, FortiGate Policy Package Status will become 'Never Installed' again.
Go to FortiManager Event Logs to check back if the previous FortiGate is using which Policy Package name.
From FortiManager Event Logs: It records the 'admin' user, at 'PolicyPackageCustom' Policy Package installation target there removed 'Wira-kvm30_FGT_v745' FortiGate device, therefore it caused FortiGate Policy Package Status to become 'Never Installed'.
|
