Portable SmartConsole is a version of the SmartConsole client which is deployed without the installer of SmartConsole.
This package encapsulates all content into the directory where it is deployed so that it can be carried around in a portable device.
Another advantage of this version is that it allows side by side versions of the SmartConsole of the same release on the same computer.
Portable SmartConsole is available for Windows OS starting from R80.10.
Prerequisites
The SmartConsole installation program installs these items on your computer:
- Visual C++ (x86) 2017 Redistributable (required for R80.30 and higher)
- Visual C++ (x86) 2005 Redistributable (not required for R80.20 and higher)
- Visual C++ (x86) 2010 Redistributable
- Visual C++ (x86) 2012 Redistributable
- .NET Framework 4.5
Before installing and using a Portable SmartConsole, you must install the relevant SmartConsole GUI client on the same computer:
Important - If you install multiple Portable SmartConsole clients, you must install each of them in a different folder.
Downloads
Package |
Download |
Release Date |
Aligned With |
Portable SmartConsole for R81.20 |
(ZIP) |
21 Nov 2022 |
SmartConsole R81.20 |
Portable SmartConsole for R81.10 |
(ZIP) |
08 Jan 2023 |
SmartConsole R81.10 Build 412 |
Portable SmartConsole for R81 |
(ZIP) |
09 Jan 2023 |
SmartConsole R81 Build 564 |
Portable SmartConsole for R80.40 |
(ZIP) |
13 Nov 2022 |
SmartConsole R80.40 Build 434 |
Portable SmartConsole for R80.30 |
(ZIP) |
08 Sep 2022 |
SmartConsole R80.30 Build 109 |
Portable SmartConsole for R80.20 GA |
(ZIP) |
04 Sep 2022 |
SmartConsole R80.20 Build 130 |
Portable SmartConsole for R80.10 |
(ZIP) |
22 Dec 2021 |
SmartConsole R80.10 Build 188 |
To obtain download packages of M1 and M2, contact Check Point Support.
Deployment and Storage
-
Extract the SmartConsole package into the desired path.
Portable SmartConsole stores all user settings in the Output sub-directory.
-
To use the portable package, double-click the SmartConsole.exe file.
Note: Using the SmartConsole user settings requires "write" permissions for the Output sub-directory as well as admin permissions for legacy components (same as in installer mode).
Troubleshooting
Revision History