Table of Contents
SmartConsole introduces an automatic update mechanism that keeps SmartConsole updated within the same major version (updatable SmartConsole).
When an updated version is available, it is downloaded and installed automatically in the background without interrupting the current session (except for requiring administrative permissions, see below).
The updated version will be used the next time SmartConsole is launched.
The previous version is kept to allow uninterrupted work by the currently running SmartConsole.
User settings (for example, recently connected servers and their fingerprints) are kept between updated versions.
SmartConsole configuration file (
SmartConsole.exe.config) is not preserved during these updates. The previous configuration can be found in the previous version's location (see the "Directory Structure" section below).
The build number scheme has changed from a 9-digit number (for example, 995000020) to a 4-number structure (for example, 81.0.9500.20).
The new number appears in the main login window and in the "About" window.
Each update version (including the originally installed) is installed in a sub-folder in the SmartConsole installation folder (for example,
C:\Program Files (x86)\CheckPoint\R81\81.0.9500.20\).
The "PROGRAM" folder (for example,
C:\Program Files (x86)\CheckPoint\R81\PROGRAM\) is now a link (an NTFS directory junction) to the latest version.
Note - The two latest update versions are kept in the SmartConsole installation folder.
If SmartConsole is installed in a system-protected folder (for example, "
C:\Program Files (x86)"), administrative permissions are required to install the update.
Disabling Automatic Updates
It is possible to disable the automatic SmartConsole updates in one of these ways:
Using a kill-switch in the SmartConsole configuration file:
- Open the SmartConsole configuration file SmartConsole.exe.config in an advanced text editor (like Notepad++).
C:\Program Files (x86)\CheckPoint\SmartConsole\R81\PROGRAM\SmartConsole.exe.config
- In the <killSwitchSettings>...</killSwitchSettings> section, add this line:
<add key="ApplicationAutomaticUpdates" value="True"/>
- Save the changes in the file.
- Close the file.
Using a Windows Registry key:
- Click the Start menu (or press the Windows+R keys).
- Enter regedit and click that application (in the Run window, click OK).
- In the Registry Editor, in the top field, delete the current path and paste this path:
- In the left pane, click this key:
where <Rxx> is a major version.
- In the right pane, right-click an empty space > click New > click DWORD (32-bit) Value.
- Enter the name AutomaticUpdateEnabled and press Enter.
- Double-click the new key.
- In the Value data field, enter 0 and click OK.
- Close the Registry Editor.
SmartConsole must be installed on a local NTFS volume.
When you start a legacy application directly from the SmartConsole installation folder
C:\Program Files (x86)\CheckPoint\SmartConsole\, you must start the application from the version folder (for example:
C:\Program Files (x86)\CheckPoint\SmartConsole\R81\81.0.9500.5\) and not from the "PROGRAM" folder (for example:
C:\Program Files (x86)\CheckPoint\SmartConsole\R81\PROGRAM\).
This prevents a possible unexpected exit of legacy applications while SmartConsole updates itself (Issue ID CIS-3291).
Problem: Update is not starting long after it has been published
Possible cause 1: The required "PROGRAM" folder is missing.
Details: The "PROGRAM" folder (junction) is an essential part of the update mechanism. If it does not exist, the update mechanism cannot work.
Open an elevated Windows Command Prompt (as administrator).
Run this command to create the required symbolic link:
Important - Enter the path to the actual installation directory and the latest update version on your computer.
mklink /J "<DISK>:\<INSTALLATION_FOLDER>\PROGRAM" "<DISK>:\<INSTALLATION_FOLDER>\<BUILD>"
Example for the version R81 and the build 81.0.9500.549:
mklink /J "C:\Program Files (x86)\CheckPoint\SmartConsole\R81\PROGRAM" "C:\Program Files (x86)\CheckPoint\SmartConsole\R81\81.0.9500.549"
Possible cause 2: 3rd party HTTPS inspection interferes with the connection to DownloadCenter (updates.checkpoint.com).
Details: SmartConsole refuses to create a connection to DownloadCenter (updates.checkpoint.com) if the TLS certificate is different from the expected one.
: In the file UpdateCheck_*.xml (file name my vary) at C:\ProgramData\Check Point\SmartConsole [version]\ where “State” is “NoInfo” and “UpdateCheckError” is “FDT_COULD_NOT_CONNECT” or “FDT_LOCAL_CERT_PROBLEM”, e.g.
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.