SmartConsole and Windows Server 2022 performance issue

[JasMan]

Hi,

We're running the current SmartConsole 81.10.9600.427 on a Windows Server 2016 Standard and another instance on a Window Server 2022 Standard machine. Both machines are VMs and have 24GB RAM and 8 x 2,4GHz CPUs.

Unfortunately the console in Windows Server 2022 is very slow and freezes often for 10-30 seconds during normal operations.

Example:
When I start the console in Windows Server 2016 it tooks about 5 seconds until the login appears.
When I start the console in Windows Server 2022 it tooks about 20-30 seconds until the login appears.

I choosed this example because it shows that it already happened before any connections to the MGMT servers are made.
CPU and memory are both fine.

I've already installed the console on different machines and faced the same behaviour: 2016 = fast, 2022 = slow.

Does anybody has the same issue or an idea what could causing it?

Thx.

Jas

[the_rock]

I have 2022 VM with 16 GB of ram and R81.20 console installed on it, no issues at all. 

Andy

[Timothy_Hall]

I saw this same thing in my ATC training lab.  The SmartConsole software is digitally signed, and the startup delay is caused by Certificate Path Validation timing out because the Internet can't be reached, or the relevant protocol is blocked somewhere.

You can disable this path checking in Group Policy which will massively speed up the SmartConsole startup time, but beware the security implications. To make this change check the box "Define these policy settings" then uncheck everything else:

As far as freezeups in the SmartConsole while is running, usually this is caused my manipulating a gateway/cluster object's configuration or even just viewing it.  When you hit OK/Cancel unfortunately these operations are still handled in the legacy single-threaded fwm process and not the newer cpm.  So no matter how many cores your SMS has the SmartConsole will seize up while it is blocked waiting for fwm.

[Lesley]

Could still be firewall management issue, so not an issue on the Windows server / Smart Console software.

what take are you running on fwmgmt?