This article gives you an overview of the steps you will need to perform in order to prepare your server environment for the SysKit Monitor installation.
Pre Installation Requirements
The installation process consists of a few easy steps that you need to perform in order to get the SysKit Monitor up and running.
Configure Active Directory
SysKit Monitor requires a service account in order to run. We recommend creating a dedicated Windows account for this purpose.
- This account needs to have administrative privileges on each server you plan to monitor. You can configure this manually or via Group Policy.
- This account needs to have the Logon as a service privileges.
As a best practice, we recommend setting a service user that is in the Adminstrators or Domain Admins group.
Configure SQL Server
The Installation wizard will create a database automatically. The user running the setup wizard needs to have the proper privileges to create new databases on the SQL Server (dbcreator or sysadmin).
During configuration you will be prompted to select the authentication type for SQL Server. You can choose between Windows integrated authentication and SQL Server authentication.
If you are running the SysKit in a domain environment, we strongly recommend using Windows authentication. SQL Server authentication should only be used in workgroup environments or in case of security restrictions in your domain.
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 Monitor SQL server database requirements.
If you cannot obtain such privileges, install the SysKit Monitor database manually (or your DBA will create a DB).
You need to create an empty database that will be used to store the SysKit Monitor data:
- Open the SQL Management Studio.
- Select SQL Server name > Databases.
- Right click Databases and select New Database.
- Type a name in the Database name field, e.g. SysKit_Monitor.
- On the Options page, choose Simple as the Recovery Model.
- Click OK to create a new database.
The service user that will be used for running the SysKit Monitor Service needs to have db_owner membership assigned on the newly created database. See SQL Permissions to learn more.
Proceed to: Installation Guide.
SQL Server authentication
SQL Server authentication is used in environments without the Active Directory domain or if the SQL Server is outside the domain. Before installing the SysKit Monitor with SQL Server authentication, you need to perform additional steps to create a SQL user, which will be used to connect to the database.
How to create a SQL Server login
To use SQL Server authentication instead of Windows authentication please do the following: 1. Connect to the SQL Server using SQL Server Management Studio. 2. Right-click on the Security folder, point to New and select Login. 3. In the new dialog box, select SQL Server authentication and in Login name field type a new SQL Server login. 4. Fill in the Password and Confirm password fields.
You need to remember the login name and password as you will use them to connect to the SQL Server using SQL Server authentication.
- Select Server Roles page on the left side and make sure the user has dbcreator role.
- Click OK and return to the Configuration Wizard > Database Configuration step.
- If you are using the existing database, expand Databases folder and then expand the database which you are trying to configure.
- Expand the Security folder and then the Users folder.
- If the Login name you created in step 3. is not in the Users list, right-click the Users folder and click New user. In the Username and Login name enter the same Login name from step 3.
- Select Membership page, give user db_owner role and click OK.