# Upgrading SessionLimit to 2.0.17

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

1. Changes were made to the cache mechanism architecture:
   1. A Cache Interval was added.
   2. A Cache Versioning System was introduced.
   3. 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.
2. The agent now displays who initiated specific actions.
3. For 2FA-based logins:
   1. If no code is entered during the logon activity, the session will be logged of, 
   2. If no code is entered during the unlock activity, the session will be locked again.
4. 2FA policy optimization was carried out.
5. Agent has been updated to 2.0.17 version.

{% hint style="success" %}
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.
{% endhint %}

You can download the latest[ **server package here**](https://dl.easy2patch.com/dl/arksoft/SessionLimit/2.0.17/SessionLimitServer-2.0.17.1006.msi), and [**client package here**](https://dl.easy2patch.com/dl/arksoft/SessionLimit/2.0.17/SessionLimitAgent-2.0.17.msi).

{% hint style="danger" %}
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.\ <br>

![](/files/0cbrnfwLKdcls9Ciy2yy)
{% endhint %}

{% hint style="info" %}
It is possible to upgrade from any version of SessionLimit to version 2.0.17.
{% endhint %}

## Version information

### Client Package (2.0.17)

<table><thead><tr><th width="206">File Name</th><th width="133">File Version</th><th>Hash (SHA256)</th></tr></thead><tbody><tr><td>ACommon.dll</td><td>2.0.17.0</td><td>1C6E3A4620FF575F5340A6D82C6CA15566E3D3E9735A0C0A7AB5105D9E52FF20</td></tr><tr><td>SessionLimitService.exe</td><td>2.0.17.0</td><td>C3A6DC619FF3FBCE393FD01B103E8573B5D75AB5C0107ACAAA28277E4E5473DC</td></tr><tr><td>SessionLimitUI.exe</td><td>2.0.17.0</td><td>F47C7F88A9D6A3E67F299852395E8C9744D27BBA86524B4A8D3D2D0A51D0767A</td></tr><tr><td>SessionLimitWix.CA.dll</td><td>2.0.17.0</td><td>8282751DDC1DBE43C32B9704E5BC052E63446246FD088FB2D71F8AA9C3E45046</td></tr><tr><td>SessionLimitWix.dll</td><td>2.0.17.0</td><td>E891088DA70F49A7E61E32DB6D95F9C8376DFFEB12A5B60B7A4219A44F854CDE</td></tr><tr><td>SLCred.dll</td><td>2.0.17.0</td><td>4376F1DD8D166F547C43E81F275915E91F71BBD951C02D2BB64AFBAC7E74C8F0</td></tr><tr><td>SessionLimit.LanguageSettings.exe</td><td>2.0.12.0</td><td>F0D824DEF5873AE7DAD265D5A7089FEFEB36FB5A07E30C51A18FFB11762AADEB</td></tr></tbody></table>

### Server Package (2.0.17)

<table><thead><tr><th width="286">File Name</th><th width="121">File Version</th><th>Hash (SHA256)</th></tr></thead><tbody><tr><td>ACommon.dll</td><td>2.0.13.0</td><td>EE036A8BBC848F95708BFE59F127ECE12E9DDD12C2AC9129EE7AFE63A32CFC39</td></tr><tr><td>Arksoft.License.dll</td><td>2.0.17</td><td>F44E2F89D8F90168FCE2119C15FDC74EDC4100CA07FF8E32F213749B5D2020D5</td></tr><tr><td>FTW.exe</td><td>1.0.18.0</td><td>7937BAD009648E240D9FF9F5439B3C0610A24783F58B5339499725BC6FC9D0E0</td></tr><tr><td>SessionLimit.API.dll</td><td>2.0.17.0</td><td>68C3C9833E05C53B0CF214DBF1DB28543856C4261CDA4B99E005F233E9DA87B7</td></tr><tr><td>SessionLimit.API.exe</td><td>2.0.17.0</td><td>CF1EFC4038B4331E06D8712C036685EADE31612715DF29B3D58D98BE520D3728</td></tr><tr><td>SessionLimit.Common.dll</td><td>2.0.12.0</td><td>3DE1DC37ABB775073C733F5600A5A0DEA94A0CEA241D6C46393C97EC15638908</td></tr><tr><td>SessionLimit.Data.Business.dll</td><td>2.0.17.0</td><td>6436767284BED0CBB121615FD5B5814A3DE2CCC25CEC6763AC93B4BBDD61AE84</td></tr><tr><td>SessionLimit.Data.Repository.dll</td><td>2.0.17.0</td><td>20F7B27E5CD0D59EEF5D07C0333738A0681B7D9D3539189576567C2A36105243</td></tr><tr><td>SessionLimit.Model.dll</td><td>2.0.17.0</td><td>71801919AD3C1DD3D1E542971FC7AD7E4658741760D0E57DFCA3D509F27EDC51</td></tr><tr><td>SessionLimit.Web.Common.dll</td><td>2.0.17.0</td><td>1DF0E4CC451A365D814E12ACDD154F3CD66580C4602E37AEFEAE88292660629D</td></tr><tr><td>SessionLimitServerService.exe</td><td>2.0.16.0</td><td>44A54F65B256918A742741ACA698A0E051A7699A5292F8022502637F6AD7A846</td></tr><tr><td>SMS.ProviderDotNet.dll</td><td>1.0.5.0</td><td>0EC52657C154AEAE931440A63DF54C0B4167F995BC8796361348DF4A32147C8D</td></tr></tbody></table>

## Prerequisites for upgrade

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

<figure><img src="/files/iskEXPtLhz8hptSkhxNY" alt=""><figcaption><p>Install</p></figcaption></figure>

2. After the installation is completed, click Finish.

<figure><img src="/files/WlOZE1Oyafi5RQxR0vtO" alt=""><figcaption><p>Setup Completed</p></figcaption></figure>

<figure><img src="/files/TeoSlIZnVHkfOcCuDXXW" alt=""><figcaption><p>Click to stop SessionLimitServer Service</p></figcaption></figure>

3. 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.
4. Click next on Welcome screen,

<figure><img src="/files/dUilu3LLKBO5suUdf69v" alt=""><figcaption><p>Welcome screen</p></figcaption></figure>

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

<figure><img src="/files/kSoOKzpNihiuiI3tgBQd" alt=""><figcaption><p>Select Upgrade</p></figcaption></figure>

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

<figure><img src="/files/eceEDQlnNVaood4mjmph" alt=""><figcaption><p>Check Database Information</p></figcaption></figure>

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

<figure><img src="/files/IWkQ4dUOMmvCqL0Geemb" alt=""><figcaption><p>Check Prerequisites</p></figcaption></figure>

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

<figure><img src="/files/74hAVoUBWrHxn5RDpvG0" alt=""><figcaption><p>Upgrade Completed</p></figcaption></figure>

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

<figure><img src="/files/dDJm35h8zrLPPczl0RSu" alt=""><figcaption><p>Restart IIS Service</p></figcaption></figure>

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

<figure><img src="/files/whJ9SzkSz0BpR61Txr6n" alt=""><figcaption><p>Version Check</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sessionlimit.com/deployment/upgrading-sessionlimit/upgrading-sessionlimit-to-2.0.17.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.