Entrevista al director (Ver anexo 7)

The ServerView Operations Manager setup may require up to four Windows accounts for installation and operation for SQL Server.

Important for all Windows accounts used:

l For a remote SQL Server, you may only use domain accounts from

a trusted domain or from the same domain as the Central Management Server.

l For a local SQL Server, predefined Windows accounts or user-

defined accounts may be used. The following Windows accounts are used:

1. The installation account.

Windows account used to start the Operations Manager installation. This account needs permission in SQL Server to create the ServerViewDB database.

2. ServerView Services account.

Windows account used to start ServerView Services. o For a local SQL Server:

Always the Local System account. o For a remote SQL Server:

During setup, specified in the windowRemote DB(for a new installation) orServerView Service Logon Information(for an upgrade installation).

The account cannot be changed in upgrade or modify installations. 3. ServerView JBoss Application Server account.

Windows account used to start theJBoss Application Serverservice. During setup, specified in the windowJBoss Service Logon Information.

The account used to start theServerView Download Service. During setup, specified in the windowUpdate Management Logon. As this account needs access to the Internet, it is recommended to use a separate account for this purpose.

Required membership in the Windows Administrator group on the CMS:

No. Account Local and Remote SQL Server

1 Installation Account Yes

2 ServerView Services Yes

3 ServerView JBoss Application No 4 ServerView Download Service Yes

Yes: must be a member of the Windows Administrator group No: need not be a member of the Windows Administrator group Predefined Windows accounts used with a local SQL Server:

No. Account Local and Remote SQL Server

1 Installation Account Administrator

2 ServerView Services LocalSystem

3 ServerView JBoss Application LocalService 4 ServerView Download Service .\Administrator SQL Server service accounts

For security reasons, the services SQL Server and SQL Server Agent service should run under an account which is not a member of the Windows group

Administrators. For a local SQL Server, local Windows accounts may be used. For a remote SQL Server, these accounts must either be domain accounts or (but only when both the CMS and the SQL Server are in the same domain) the Local System account. For security reasons, however Local System is not

recommended or further details, please"SQL Server service accounts" on page 75.

SQL Server Logins

ServerView Operations Manager uses Windows authentication to authenticate in SQL Server. Any account used for Operations Manager setup and operation must correspond to a valid login for Windows in SQL Server. The SQL Server

Administrator must add the installation account (1) and any further account to be used ((2) – (4) specified above) asSQL Server Login for Windows authenticationbefore the Operations Manager setup is started. SQL Server Permissions

The installing account (1) must also be given at least the permission to create a database in SQL Server.

Server and database roles for the installation account

The accounts used need the following server and database roles in SQL Server to successfully perform the ServerView Operations Manager database setup and operation:

Login Server Role Database Role 1 dbcreator

optional: diskadmin

Recommended in databasemsdbfor full versions of SQL Server:

l db_backupoperator(ordb_owner) l SQLAgentReaderRole

l SQLAgentUserRole

Optional in databasemasterfor all SQL Server editions: db_backupoperator(ordb_owner)

2 - -

3 - -

4 - -

Thedbcreatorserver role is required to create the ServerView database and database schema. The setup will check the role assignment and display an error message if this role is not granted. If this is the case, it will exit with rollback. The twoSQLAgentroles are highly recommended for full versions of SQL Server. They are not needed at all for SQL Server Express Editions. The ServerView setup

will try to install backup and maintenance jobs for its database ServerViewDB via SQL Server Agent procedures. If this cannot be done, the setup will display an informational message but will not exit or rollback.

Please note that backup jobs for the database ServerViewDB are especially important if you want to choose option the SQL Server Backup Mode “advanced / full” in the Operations Manager setup later on. This is because the database transaction log may grow to enormous sizes if regular backups are not performed.

When you choose the SQL Server Backup Mode “advanced / full” for the ServerView database, it is highly recommended to either assign the SQLServerAgent roles or install a backup scheme of your own.

Thediskadminserver role is optional. If granted the ServerView setup will try to create backup devices by storing the database backup files in the ServerView installation path otherwise the backups are performed within the SQL Server default backup path. The setup will not exit or roll back if the role assignment is missing.

Thedb_backupoperatordatabase role for the system database msdb is highly recommended for the full versions of SQL Server. Thedb_backupoperator database role for the master database is optional for all SQL Server editions. ServerView setup will try to perform a backup of these system databases depending on the SQL Server edition at the end of the setup.

The setup will display an informational message if the role is not granted , but it will not exit or rollback. Thedb_ownerrole comprises the permission to back up, but is the role with the highest privilege. It has permission to perform any task on the database.