Upgrading SessionLimit 2.0.14 to 2.0.15
Last updated
Last updated
SessionLimit software version 2.0.15 has been released. The following changes have been made in this version.
Performance improvements were made to capture multi-logon operations,
Lock, Unlock and Logoff events added to syslog messages,
Updated syslog message sending engine,
Verbose Logging added,
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 "Is Open Session Effect" 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.15.
| Server package | 2.0.15 |
|---|---|
SessionLimit.Web.Common.dll | 2.0.15 |
SessionLimit.Model.dll | 2.0.15 |
SessionLimit.Data.Repository.dll | 2.0.15 |
SessionLimit.Data.Business.dll | 2.0.15 |
SessionLimit.Common.dll | 2.0.15 |
SessionLimit.API.exe | 2.0.15 |
SessionLimit.API.dll | 2.0.15 |
Arksoft.License.dll | 2.0.15 |
SMS.ProviderDotNet.dll | 1.0.5 |
NugetPackageArksoft.Captcha.dll | 1.0.8 |
| Client package | 2.0.13 |
|---|---|
SessionLimitService.exe | 2.0.13 |
SessionLimitUI.exe | 2.0.13 |
ACommon.dll | 2.0.13 |
SessionLimitWix.CA.dll | 2.0.9 |
SessionLimitWix.dll | 2.0.9 |
SLCred.dll | 2.0.13 |
SessionLimit.LanguageSettings .exe | 2.0.12 |
sysadmin 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 Welceme screen,
Select Upgrade Existing SessionLimit 2.0.X to version 2.0.154 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.15 appears at the bottom of the page in the interface.
