When using SmartConsole, changes made by an administrator are sent to the Security Management Server and held in a private session database. If the network connection is lost, the Management Server maintains the session lock and preserves all unpublished changes. Once connectivity is restored, the administrator can log back in, and SmartConsole will reconnect to the existing session, allowing them to continue their work exactly where they left off without any loss of data. This ensures administrative work is not lost due to transient network issues.

A. Rebooting and clearing the cache are unnecessary troubleshooting steps; the changes are stored on the server, not just in a local client cache.

B. Accessing a local management cache store after a reboot is not the standard procedure; session data is held server-side.

C. Changes are not lost upon disconnection because they are saved in the session on the Security Management Server, not just locally.

- Check Point. (2023). R81.20 Security Management Administration Guide. p. 58, "Concurrent Administration". The documentation explains that when an administrator edits a policy, the database is locked, and changes are saved in a private session on the server.