topic Re: Command Line Arguments to R80.10 SmartConsole.exe in Firewall and Security Management

Command Line Arguments to R80.10 SmartConsole.exe

Arne_Boettger — Thu, 14 Dec 2017 07:25:46 GMT

Hello,

we used to launch SmartDashboard up to R77.30 for different SmartCenters from , a tool to manage connections to all kinds of devices. We launched "FwPolicy.exe connect %Hostname% %Username%".

However, on R80.10, FwPolicy.exe is no longer the right binary to launch. We discovered that we need to run , which does not seem to accept any command line arguments.

Is there a way to pass Username and Hostname to this or another binary to support directly launching a SmartDashboard for R80.10?

regards, Arne

Re: Command Line Arguments to R80.10 SmartConsole.exe

Tomer_Sole — Thu, 14 Dec 2017 08:28:27 GMT

Yes this is possible (and undocumented..sorry about that...)

See the attached file. You have to unzip it before use. It is called SmartConsole.LoginParams but you can change it to any name you like as long as it appears in the -p value below:

SmartConsole.exe -p SmartConsole.LoginParams

SmartConsole.LoginParams

Format of the XML (none of these parameters is mandatory):

<?xml version="1.0" encoding="utf-8"?>
<RemoteLaunchParemeters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Username>aa</Username>
<ServerIP>10.10.2.54</ServerIP>
<DomainName>LondonDomain</DomainName>
<ReadOnly>False</ReadOnly>
<CloudDemoMode>False</CloudDemoMode>
<DomainName>LondonDomain</DomainName>
</RemoteLaunchParemeters>

Re: Command Line Arguments to R80.10 SmartConsole.exe

Arne_Boettger — Thu, 14 Dec 2017 09:08:55 GMT

Hello Tomer,

thanks for the quick response. I have some suggestions to improve useability:

1. there is a typo in "RemoteLaunchParemeters" - maybe this should be corrected in the code and sample?

2. On a non-mds I had to leave the "DomainName" field empty

3. Now, after Launch, I receive an error message that password may not be empty. Is there a way to skip this error message and drop me directly to the usual login screen?

regards, Arne

Re: Command Line Arguments to R80.10 SmartConsole.exe

Tomer_Sole — Thu, 14 Dec 2017 10:15:38 GMT

1. You are correct

2. Yes. You can also just delete that node

3. Understandable. We will consider this for one of our next builds or releases.

Re: Command Line Arguments to R80.10 SmartConsole.exe

HeikoAnkenbrand — Fri, 24 Aug 2018 12:34:23 GMT

also works!

Regards,

Heiko

Re: Command Line Arguments to R80.10 SmartConsole.exe

Aleksandr_Nosit — Wed, 14 Oct 2020 06:16:57 GMT

Tomer,

Do we have same option for EndpointManager.exe ? R80.40 and above

Regards,

Alec

Re: Command Line Arguments to R80.10 SmartConsole.exe

PhoneBoy — Wed, 14 Oct 2020 14:05:56 GMT

As far as I know this should still work the same way in current versions.

Re: Command Line Arguments to R80.10 SmartConsole.exe

Aleksandr_Nosit — Fri, 16 Oct 2020 04:46:36 GMT

Thank You Dameon,

will give it a try

/Alec

Re: Command Line Arguments to R80.10 SmartConsole.exe

Aleksandr_Nosit — Mon, 19 Oct 2020 07:13:54 GMT

Hello again,

seems that Endpointmanager.exe is not picking up parameters file...so connection parameters are not passed to application.

/Alec

Re: Command Line Arguments to R80.10 SmartConsole.exe

G_W_Albrecht — Mon, 19 Oct 2020 07:56:32 GMT

Only Dashboard reads the parameter file, but you can use Dashboard to open Endpoint...

Re: Command Line Arguments to R80.10 SmartConsole.exe

Aleksandr_Nosit — Mon, 19 Oct 2020 08:10:31 GMT

Please ellaborate how can i do it via CLI?

Re: Command Line Arguments to R80.10 SmartConsole.exe

skeutgen — Wed, 16 Dec 2020 11:40:43 GMT

Hi everyone,

Is it known that there is an issue with the loginparams in Version R80.30 B94? We were using the xml file to login in Version B90 and before after upgrading to B94 it is not working anymore.

When I start the smartconsole without parameters it's starting just fine, but with ".\SmartConsole.exe -p path/to/login.LoginParams" Option we end up in an loop where the smartconsole window only says "starting" and some dots flying through. Also while doing this it is impossible to quit out of the windows except using task manager.

Cheers,

Sascha

Re: Command Line Arguments to R80.10 SmartConsole.exe

Feridun_ÖZTOK — Sat, 06 Mar 2021 07:51:13 GMT

Hello skeutgen,

I have same problem in R80.40 build 416. I had to delete B416 and install B398 again. The same problem exists with the R81. Did you find a solution?

Best regards,

Feridun ÖZTOK

Re: Command Line Arguments to R80.10 SmartConsole.exe

JozkoMrkvicka — Sat, 06 Mar 2021 14:52:49 GMT

see https://community.checkpoint.com/t5/Management/R81-SmartConsole-config-file-doesn-t-work/m-p/106457/highlight/true#M25134

Re: Command Line Arguments to R80.10 SmartConsole.exe

Feridun_ÖZTOK — Sat, 06 Mar 2021 15:06:47 GMT

Jozko, thanks for info. I will follow the issue under this link.

Best regards,

Feridun ÖZTOK

Re: Command Line Arguments to R80.10 SmartConsole.exe

Greg_Harewood — Fri, 17 Mar 2023 14:43:18 GMT

SO we now know that this is broken by design from R80.40 onwards.

My best effort workaround which, thank you Check Point, is far less secure than before is this:

' Usage: runsc.vbs VERSION IP USERNAME PASSWORD ' VERSION = R80.40 | R81 | R81.10 | R81.20 Set oShell = CreateObject("Wscript.Shell") oShell.Run("""C:\Program Files (x86)\CheckPoint\SmartConsole\" & WScript.Arguments(0) & "\PROGRAM\SmartConsole.exe""") WScript.Sleep(8000) oShell.AppActivate "Check Point SmartConsole" oShell.SendKeys "{TAB}" oShell.SendKeys "{TAB}" oShell.SendKeys WScript.Arguments(1) 'IP oShell.SendKeys "{TAB}" oShell.SendKeys "{TAB}" oShell.SendKeys "{TAB}" oShell.SendKeys "{TAB}" oShell.SendKeys "{TAB}" oShell.SendKeys WScript.Arguments(2) 'Username oShell.SendKeys "{TAB}" oShell.SendKeys WScript.Arguments(3) 'Password 'oShell.SendKeys "x" oShell.SendKeys "{TAB}" oShell.SendKeys "{ENTER}" Set oShell = Nothing

Can anyone improve this? Issues:

You can only have one copy of SmartConsole running, it will fail if it finds one already running
SmartConsole must already have cached arguments (not first run), as we assume that initial focus is on the password box
Only supports local SMS, ie no cloud
Relies on a timer between launch and filling in the fields, needs adjusting if you system is slow
Cannot accurately paste some characters in passwords, so requires simplification of some passwords

However, assuming simple passwords, it IS good enough to enter as an external tool in something like mRemoteNG for that magical experience of auto logon. I would very much appreciate if anyone else could improve it a little more.