piątek, 4 kwietnia 2008

optymalizacja f-secure na serwerach terminali

W nawiązaniu do rozmowy telefonicznej, zamieszczam poniżej sposób na wyeliminowanie zbędnych procesów z wątków użytkownika na serwerach terminalowych:

Here is the workaround for your problem.

---------------------

The FSM32.exe starts to every Terminal session under the username that created the session. FSM32.exe is needed for the GUI and to run manual scanning, but in environments that has many sessions the FSM32.exe's takes quite a bit of memory.

Workaround for this:

1. Delete the "F-Secure Manager"=""C:\Program Files\F-Secure\Common\FSM32.EXE" /splash" key under [HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun]

2. Add a shortcut "C:Program FilesF-SecureCommonFSM32.EXE" to Start -> Programs -> Startup to users that should start the FSM32.exe (GUI) or it can be added to login-script.

Also 5.52 should have the "AUA data already in use" fix, as it also comes for every user. This also can be workarounded like this:

1. Open the C:Documents & SettingsAll usersStart MenuProgramsStartup 2. Cut the "F-Secure Automatic Update"

3. Paste it to C:Documents & SettingsStart MenuProgramsStartup

That also prevents the AUA GUI starting to every user (which causes the "AUA data already in use"-dialog)

In Terminal sessions "F-Secure Automatic Update" won't run in the processes, but FSM32.exe seems to be starting it.

Brak komentarzy: