When logging in for the first time to a Security management Server through SmartConsole, a fingerprint is saved to the:

The fingerprint is not stored on the Security Management Server in a .fgpt file; it is stored on the SmartConsole client machine so the client can independently validate the server's identity on future sessions.

SmartConsole does not use the Windows registry to store the fingerprint; it uses its own application-level cache for this purpose.

A fingerprint is absolutely saved - omitting this step would eliminate the trust anchor needed to detect a spoofed or unauthorized management server on subsequent connections.

SmartConsole stores the Security Management Server's certificate fingerprint in its local application cache after the administrator accepts it on first login. On subsequent connections, SmartConsole compares the server's presented fingerprint against this cached value to detect potential man-in-the-middle attacks, functioning similarly to SSH host key verification.