Hi!
in section "Checking FortiManager databases" of "FortiManager Upgrade Guide", I see: "Before running integrity check commands, ensure ... no objects are locked." but does not say how to achieve this if there are many ADOMs, many Devices, many Policy Packages and many Objects. What's Fortinet’s recommendation for achieving this?
Thanks!
Hi ,
This is useful to be checked in Case you are working in Workspace or workflow mode where to do any changes you must lock the ADOM first, so for example if one of the ADOMs were locked prior doing that command, this will lead in failure in verifying the objects there
I didn’t ask why, I asked how.
Hi Alex,
Well that depends on whether you have workspace or workflow enabled
if yes, then you need to check ADOMs by clicking on it on top right and see if any ADOM has a lock on it and if that is the case then you need to unlock it to not interrupt the checking
Created on 11-22-2024 10:30 AM Edited on 11-22-2024 10:35 AM
Hi! Thanks but I don’t think you understand the extent of the question. There are more object types that can be locked than ADOMs.
Hi @AlexFerenX ,
When the object is locked, other administrators will see a red lock icon next to the object in GUI.
However, I couldn't find a way to find all the locked objects at a time.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1737 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.