SessionLimit v2
  • Infrastructure Documents
  • Overview
    • What is SessionLimit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Agent Requirements
      • .Net Framework 4.7.2
    • Other Requirements
    • Network Considerations
    • Design
      • Single Deployment
      • Distributed Deployment
  • Deployment
    • GMSA Account for Application Pool
    • DNS Service Record for Agent Autodiscovery
    • Installing Microsoft SQL Server
    • Internet Information Service Installation
    • .NET Core 6.0 Download and Install
    • .Net Framework 4.7.2 Download and Install
    • HTTPS Certificate
    • Installing SessionLimit 2.0
    • Upgrading SessionLimit
      • Upgrading SessionLimit 2.0.12 to 2.0.13
      • Upgrading SessionLimit 2.0.13 to 2.0.14
      • Upgrading SessionLimit to 2.0.15
      • Upgrading SessionLimit to 2.0.16
      • Upgrading SessionLimit to 2.0.17
      • Upgrading SessionLimit to 2.0.18
      • Upgrading SessionLimit to 2.1
    • First Time Wizard
    • Agent Deployment
  • Managing
    • Logging to SessionLimit 2.0
    • Dashboard (Home)
      • General Dashboard
      • My Dashboard
      • Agents Dashboard
    • Policy
      • Session Protection Policy
      • 2FA Policy
    • Limitations
    • Endpoint Management
      • Users
      • Computers
    • Settings
      • General
        • Server Settings
        • LDAP Settings
        • Notification Settings
          • General Notification
          • E-Mail
          • SMS
        • Syslog Settings
        • Syslog Message Settings
      • Advanced Settings
      • 2FA
      • Agent
    • Events
    • Reports
    • Role Management
    • License Management
      • Online License
    • Syslog
      • Logon Operations
  • Agent
    • Session Control
    • 2FA
  • Tips&Tricks
    • SQL Express Usage
    • Fixing 500.19 web.config error
    • Enable HTTPS Redirection in IIS with HSTS
    • Using GMSA Account in Application Pool
    • Give Database Access for GMSA Account
    • What are the SessionLimit protection states?
    • Securing Windows Server
Powered by GitBook
On this page
  • Version information
  • Prerequisites for upgrade
  • How to Upgrade Step by Step
  1. Deployment
  2. Upgrading SessionLimit

Upgrading SessionLimit to 2.0.16

PreviousUpgrading SessionLimit to 2.0.15NextUpgrading SessionLimit to 2.0.17

Last updated 5 months ago

SessionLimit software version 2.0.16 has been released. The following changes have been made in this version.

  1. Cache mechanism added to policies, domain settings and license controls,

  2. Performance and cache optimizations were made for the distributed deployment scenario,

  3. Interface errors were fixed,

  4. Offline time scenario updated,

  5. Verbose logging has been added,

  6. Portal session duration moved to settings in appsettings,

You can download the latest, and .

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.16.

Version information

Server package
2.0.16

SessionLimit.Web.Common.dll

2.0.16

SessionLimit.Model.dll

2.0.16

SessionLimit.Data.Repository.dll

2.0.16

SessionLimit.Data.Business.dll

2.0.16

SessionLimit.Common.dll

2.0.16

SessionLimit.API.exe

2.0.16

SessionLimit.API.dll

2.0.16

Arksoft.License.dll

2.0.16

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

Prerequisites for upgrade

  1. sysadmin rights authority on the SessionLimit database during upgrade,

  2. Local administrator on the SessionLimit server,

How to Upgrade Step by Step

  1. The Setup application is run. The setup process is started by pressing the Install button on the screen that opens.

  1. After the installation is completed, click Finish.

  1. 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.

  2. Click next on Welcome screen,

  1. Select Upgrade Existing SessionLimit 2.0.X to version 2.0.16 and then click next,

  1. 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.

  1. If there is no Fail operation shown in red on the prerequisites screen, continue by clicking Next,

  1. After the phrase "Upgrade Completed Successfully" appears on the Installation screen, click Close to close FTW.

  1. After the upgrade process is completed, restart IIS service on the Internet Information Services screen.

  1. By connecting to the SessionLimit management portal, check that version 2.0.16 appears at the bottom of the page in the interface.

server package here
client package here
Install
Setup Completed
Click to stop SessionLimitServer Service
Welcome screen
Select Upgrade
Check Database Information
Check Prerequisites
Upgrade Completed
Restart IIS Service
Version Check