Upgrading SessionLimit to 2.0.17
Last updated
Last updated
SessionLimit software version 2.0.17 has been released. The following changes have been made in this version.
Changes were made to the cache mechanism architecture:
A Cache Interval was added.
A Cache Versioning System was introduced.
Version tracking for five specific settings (2FA Policy, SessionProtection Policy, License, Settings and Domain) was implemented. This ensures that when a setting is updated, the corresponding cache is refreshed across all servers in a multi-server architecture.
The agent now displays who initiated specific actions.
For 2FA-based logins:
If no code is entered during the logon activity, the session will be logged of,
If no code is entered during the unlock activity, the session will be locked again.
2FA policy optimization was carried out.
Agent has been updated to 2.0.17 version.
The SessionLimit Server 2.0.17 is compatible with agents running version 2.0.13. During the transition process, you will not encounter any issues with the operation of agents on version 2.0.13. However, to avoid potential problems in future versions, it is highly recommended to upgrade the agents to version 2.0.17 as soon as possible.
You can download the latest server package here, and client package here.
In agents prior to 2.0.13, when 2FA is enabled, if the user does not enter the OTP code, the session is closed. If 2FA is used, the "Ask For Currently Open Sessions" option must be disabled in all 2FA policies. Otherwise, user sessions will be automatically closed after 1 minute of entering the OTP code.
It is possible to upgrade from any version of SessionLimit to version 2.0.17.
ACommon.dll
2.0.17.0
1C6E3A4620FF575F5340A6D82C6CA15566E3D3E9735A0C0A7AB5105D9E52FF20
SessionLimitService.exe
2.0.17.0
C3A6DC619FF3FBCE393FD01B103E8573B5D75AB5C0107ACAAA28277E4E5473DC
SessionLimitUI.exe
2.0.17.0
F47C7F88A9D6A3E67F299852395E8C9744D27BBA86524B4A8D3D2D0A51D0767A
SessionLimitWix.CA.dll
2.0.17.0
8282751DDC1DBE43C32B9704E5BC052E63446246FD088FB2D71F8AA9C3E45046
SessionLimitWix.dll
2.0.17.0
E891088DA70F49A7E61E32DB6D95F9C8376DFFEB12A5B60B7A4219A44F854CDE
SLCred.dll
2.0.17.0
4376F1DD8D166F547C43E81F275915E91F71BBD951C02D2BB64AFBAC7E74C8F0
SessionLimit.LanguageSettings.exe
2.0.12.0
F0D824DEF5873AE7DAD265D5A7089FEFEB36FB5A07E30C51A18FFB11762AADEB
ACommon.dll
2.0.13.0
EE036A8BBC848F95708BFE59F127ECE12E9DDD12C2AC9129EE7AFE63A32CFC39
Arksoft.License.dll
2.0.17
F44E2F89D8F90168FCE2119C15FDC74EDC4100CA07FF8E32F213749B5D2020D5
FTW.exe
1.0.18.0
7937BAD009648E240D9FF9F5439B3C0610A24783F58B5339499725BC6FC9D0E0
SessionLimit.API.dll
2.0.17.0
68C3C9833E05C53B0CF214DBF1DB28543856C4261CDA4B99E005F233E9DA87B7
SessionLimit.API.exe
2.0.17.0
CF1EFC4038B4331E06D8712C036685EADE31612715DF29B3D58D98BE520D3728
SessionLimit.Common.dll
2.0.12.0
3DE1DC37ABB775073C733F5600A5A0DEA94A0CEA241D6C46393C97EC15638908
SessionLimit.Data.Business.dll
2.0.17.0
6436767284BED0CBB121615FD5B5814A3DE2CCC25CEC6763AC93B4BBDD61AE84
SessionLimit.Data.Repository.dll
2.0.17.0
20F7B27E5CD0D59EEF5D07C0333738A0681B7D9D3539189576567C2A36105243
SessionLimit.Model.dll
2.0.17.0
71801919AD3C1DD3D1E542971FC7AD7E4658741760D0E57DFCA3D509F27EDC51
SessionLimit.Web.Common.dll
2.0.17.0
1DF0E4CC451A365D814E12ACDD154F3CD66580C4602E37AEFEAE88292660629D
SessionLimitServerService.exe
2.0.16.0
44A54F65B256918A742741ACA698A0E051A7699A5292F8022502637F6AD7A846
SMS.ProviderDotNet.dll
1.0.5.0
0EC52657C154AEAE931440A63DF54C0B4167F995BC8796361348DF4A32147C8D
dbOwner rights authority on the SessionLimit database during upgrade,
Local administrator on the SessionLimit server,
The Setup application is run. The setup process is started by pressing the Install button on the screen that opens.
After the installation is completed, click Finish.
At the end of the setup, the FTW application will run automatically. If it does not run, the FTW.exe application can be run manually under FTW in the installation directory (by default c:\Program Files\SessionLimit Server 2.0). When FTW runs, click yes on the screen that asks to use the existing configuration file.
Click next on Welcome screen,
Select Upgrade Existing SessionLimit 2.0.X to version 2.0.16 and then click next,
Check the database information. If there is a change, update the Server Name, Port and Database Name. Path informations are not important during the upgrade.
If there is no Fail operation shown in red on the prerequisites screen, continue by clicking Next,
After the phrase "Upgrade Completed Successfully" appears on the Installation screen, click Close to close FTW.
After the upgrade process is completed, restart IIS service on the Internet Information Services screen.
By connecting to the SessionLimit management portal, check that version 2.0.17 appears at the bottom of the page in the interface.
