Single Deployment
Scope: SessionAudit 1.0
Download SessionAudit Media
You can download SessionAudit Server setup files from SessionAudit.com web page. You must have a valid license to use the product. You can contact sales@sessionaudit.com for the right to use demo or purchase.
SessionAudit Server 1.1.8
This package contains Server components and Agent components.
SessionAudit Agent 1.1.0
This package contains Only x64 bit Agent component.
SessionAudit software has the following license types.
Demo: It is the version that provides 10 users and 10 computers management for 30 days. All features are available.
Standard: 100 users and 100 computers can be managed. It can be used for the period of purchase.
Advanced: 1000 users and 1000 computer management can be provided. It can be used for the period of purchase.
Enterprise: Unlimited users and computers can be managed. It can be used for the period of purchase.
Prerequisite Checker
Below are the components that need to be checked for SessionAudit.
Installation
Run Session Audit Server Setup with RunAs Administrators privilege.
Click Next on the welcome screen,
Confirm the installation directory by clicking Next,
Start the installation by pressing the Install button,
The setup process checks for IIS requirements. If there is a missing requirement, the installation is interrupted and closed.
After the installation is complete, the Internet Information Services screen is run from the start menu. The shortcut for this application is the inetmgr command.
After the installation is completed, 2 Application Pools and 1 Web Site appear on the IIS screen. Application Pool and site are in a stopped state. It will be started after all configurations are finished.
Configuring AppSettings.json files
In order for the AgentAPI to work properly, the database connection information in the appsettings.json file should be corrected.
Right click on AgentAPI virtualDirectory and select Explore.
The appsettings.json.sample file should be duplicate and backed up. The new file is called appsettings.json. If the file extensions are hidden, "File Name Extensions" should be checked on the ribbon menu.
appsettings.json opens with notepad or a similar application. The lines in the file are filled with information suitable for the environment.
In order to edit the files in these folders, the Notepad application must be opened with the RunAs Administrator command.
"DbConnectionString": "Data Source=@SERVERNAME\\@INSTANCENAME; Initial Catalog=@DBNAME; Persist Security Info=True; Integrated Security=SSPI;pooling=true;"@SERVERNAME: NetBIOS name of SQL server
@INSTANCENAME: Instance name running on SQL Server. If the default instance is installed, this name is not entered. If SQL Server is installed as Instance, the Instance name is separated with the server name with the help of 2 backslash.
Server name and instance information can be queried with New Query in SQL Server Management Studio. If Instanced SQL Server used, Server name and Instance name should seperate with double back-slash.
SELECT @@SERVERNAME@DBNAME: Initial catalog is the database name. The created database name is the name specified in the DB Creation step.
After complete the fields in the file, save the file. Sample Connection String is below notes.
"DbConnectionString": "Data Source=SERVER\\INSTANCE; Initial Catalog=SA4SCDB; Persist Security Info=True; Integrated Security=SSPI;pooling=true;"Steps 2 to 7 should be done for WebAPI in the same way.
Last updated
Was this helpful?
