SessionAudit
  • Infrastructure Documents
  • Overview
    • What is Session Audit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Agent Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • Single Deployment
      • Distributed Deployment
  • Deployment
    • Installing Microsoft SQL Server
    • HTTPS Certificate
    • DNS Records
    • .Net Framework 4.7.2 Download and Install
    • .NET Core 6.0.16 Download and Install
    • Internet Information Service Installation
    • Single Deployment
      • DB Creation
      • IIS and Site Settings
      • Database Permissions
    • Distributed Deployment
    • Upgrade Existing SessionAudit Installation
  • Initial Configuration
    • First time Login to SessionAudit
    • License Management
    • LDAP Settings
    • Role Management
    • Change Admin Password
  • Advanced Configuration
    • Login to the Portal with Domain Account
    • Settings
      • Server Settings
      • Agent Settings
      • LDAP Settings
      • Notification Settings
      • Syslog Settings
  • Managing
    • Dashboard (Home)
    • Tracker
    • Reporting
    • Computers
    • Role Management
    • License Management
  • Troubleshooting
    • SQL Express Usage
    • Securing Windows Server
Powered by GitBook
On this page

Was this helpful?

  1. Deployment
  2. Single Deployment

Database Permissions

Installation

PreviousIIS and Site SettingsNextDistributed Deployment

Last updated 2 years ago

Was this helpful?

After the IIS configurations and database operations are completed, you should grant the necessary permissions on the SessionAudit database in order for the Application Pools to work. Otherwise, the domain list will not appear at the login page, and the login process will not be possible by any method.

Follow the steps below to grant authorizations:

  1. Identify the Application Pool identity from the IIS Application Pools window. In this sample screen shows us, Application Pools works with LocalSystem. It means [NT AUTHORITY\SYSTEM].

  2. Open SQL Server Management Studio screen and connect to SessionAudit server.

  3. Grant db_owner privilege to SessionAudit database for the account given in Application Pool.

  4. Sample script is given below. The account used in the Application Pool must be changed at the points where "[NT AUTHORITY\SYSTEM]" appears in this script. You can use DBPermissons.sql script with the required changes.

DBPermission.sql
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS WITH DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english]
GO
USE [@DBNAME]
GO
ALTER ROLE [db_owner] ADD MEMBER [NT AUTHORITY\SYSTEM]
GO

After running this script, you can check the permissions on SQL Server Management Studio.

If you got an error when running this script about user already exist, you can discard first line of permission sql file.

Also you should change @DBNAME with your SessionAudit database name.

You can continue from the point you left in the Application Pool document.

ApplicationPool Identity