This article discusses the necessary Service Account you need in order to run the SysKit in various environments and describes deployment scenarios that affect account requirements.
Please read this article before choosing your service account.
You can configure SysKit to run under designated domain account or local user on a particular computer. When prompted for the Service Account under SysKit Service credentials, enter a dedicated service user. It must have the proper permission to collect the required activity data and proper privileges to store data to your database.
We recommend using the domain account as the service account. In order for the account to be eligible for running the SysKit service, it must have administrative privileges and must have “Logon as a service” permission.
- Service Account: Domain account
- Setup User Account:
- This account must be a member of the Local Administrators security group on each server you plan to monitor.
- It must have “Logon as a service” permissions defined on a domain level.
This is the recommended method for most scenarios.
SQL Server setup
- You can use the Windows Authentication to access the database – the service user will be used for authentication on the SQL Server (recommended).
- SQL Server Authentication should be used only when Windows Authentication is not possible. This scenario is supported through the SysKit Configuration Wizard.
If you plan to use Windows authentication, we recommend using our Configuration Wizard to create and configure the SysKit database. The Active Directory (Windows service) user running the configuration wizard needs to have dbcreator and securityadmin privileges on the SQL Server to create and configure the database.
See SQL Permissions to learn more about SysKit SQL server database requirements.
See Configure article to learn more on how to change the Service Account or SysKit database.
Proceed to: Pre-installation Requirements.