ServerView Event Manager installation
3.6 Preparations and important steps before you start the installation
3.9.7 Adding a user account with SQL Server administrator rights
User accounts can also be checked and added later via SQL Server Management Studio.
Adding accounts must be done before the Operations Manager installation.
In SQL Server Management Studio you will find the authorized SQL Server administrators underSecurity–Server Roles–sysadminand selection of Propertiesfrom the context menu.
You can add a user account with SQL Server administrator rights as follows: 1. Check if the account to be added is already present in the list of valid SQL
Server logins.
2. If the account is not present:
1. SelectNew Loginfrom the context menu.
2. On theGeneralpage, enter the name of the Windows user under Login nameorName. You can keep the other settings.
3. Switch to theServer Rolestab.
4. SelectsysadminorSystem Administratorsas the server role and click OK.
3. If the user account is already present: 1. SelectSecurity–Logins–<login>. 2. SelectPropertiesfrom the context menu.
3. Switch to theServer Rolestab and select thesysadmincheckbox. 4. Then clickOK.
3.10
SQL Server 2012
As of Operations Manager version 6.30, you can install the ServerView database into an SQL Server 2012 instance on a Windows Server 2008 or later operating system version.
SQL Server 2012 must be installed before installing Operations Manager.
3.10.1
Hardware and software requirements
3.10.1.1 Hardware requirements
For a detailed overview of the hardware requirements for installing SQL Server 2012, please refer tohttp://msdn.microsoft.com, and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2012" 3.10.1.2 Software requirements
l Operating systems supported for SQL Server 2012:
Windows Server 2012 Windows Server 2008 R2 SP1
Windows Server 2008 SP2
l Microsoft .NET Framework 3.5 SP 1 and .NET Framework 4.0
For details on how to acquire these packages for the relevant operating system, please refer tohttp://msdn.microsoft.com, and quick-search the website for "Hardware and Software
Requirements for installing SQL Server 2012".
l Windows Installer as of version 4.5
l Windows PowerShell as of version 2.0 is required for installing Database
Engine components and SQL Server Management Studio, which is a database administration software.
For details on how to install and enable SQL Management Studio, please refer to the website mentioned above.
Proceed as follows:
l In case of Windows Server 2008 SP2:
Search in the Microsoft Download Center forWindows Power Shell 2.0 and download it.
l In case of Windows Server 2008 R2:
Windows Power Shell 2.0 is part of the Windows Server 2008 R2 installation. (SelectAll Programs-Accessoires-Windows PowerShell.)
l In case of Windows Server 2012:
Windows Power Shell 3.0 is part of the Windows Server 2012 installation.
3.10.2
Editions
You can use the following editions, among others, depending on your performance requirements and budget:
l Express Edition
SQL Server 2012 Express is the successor to SQL Server 2008 Express. SQL Server 2012 Express is free and available from the Microsoft Download Center. The database size limit for SQL Server 2012 Express is 10 GB.
The full versions are:
l Standard Edition l Enterprise Edition
3.10.3
Setting up a service account
If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", see"Overview of Windows accounts and access rights" on page 101and"SQL Server service accounts" on page 63.
3.10.3.1 Operations Manager service accounts
When you install SQL Server 2012, you will see instructions in theDatabase Engine Configurationwindow on how to add Windows user accounts which will later be used as Operations Manager service accounts
By doing this, you will add SQL Server administrator rights to these accounts. You can also specify the Windows user accounts after SQL Server installation, but before Operations Manager installation. Follow the instructions in"Adding a user account with SQL Server administrator rights" on page 83.
Using a local SQL Server 2012 you must add the following Windows user accounts to SQL Server 2012:
l Account under which you will be logged on the system during the
Operations Manager installation.This account must have Windows administrative rights.
l Account in the Operations Manager installation windowUpdate
Management Logon Information. This account must have Windows administrative rights. Usually you will add the Administrator account.
l The Local System Account (NT AUTHORITY\SYSTEM). Locally,
ServerView Services will be installed to use this account. 3.10.3.2 SQL Server service accounts
When you install SQL Server 2012, you must specify a service account in the Server Configurationwindow. It is advisable to set up one or more service accounts before the installation.
You require service accounts for the following services:
l SQL Server Database Service
l SQL Server Agent (not for SQL Server Express) l SQL Server Browser
Bear in mind the following if you are installing SQL Server and Operations Manager on the same system:
l Do not use theNetwork Serviceaccount.
The Operations Manager installation will be cancelled if SQL Server runs under theNetwork Serviceaccount.
l To increase the security of the SQL Server installation, the services should
run under a local Windows user account. Do not assign it to the administrator group. Local Windows user accounts have the lowest privileges.
Microsoft recommends that user accounts that are used to log on as a service have thePassword never expiresoption activated and that they have strong passwords. Otherwise, follow the Microsoft documentation "How to: Change the Password of the Accounts Used by SQL Server" if the SQL Server is running under an account for which the password is to be changed.
l There are, however, a few exceptions for using a local Windows user
account:
o If remote procedure calls, replication, backing up to network drives, and heterogeneous SQL joins that involve remote data sources are to be used on the server, a local Windows account is not sufficient. o In fail cluster installations, local system and local service accounts are
not allowed.
l If you do not want to set up a local Windows user account, you can use a
system account. Proceed as follows:
o SelectLocal Systemfor the servicesSQL ServerandSQL Server Agent.
The local system account (Local System) is an integrated account with very high privileges. You should therefore use the system accounts with appropriate caution.
l If you install SQL Server and Operations Manager on different systems, the
SQL Server services must run under a domain user account without
administrator rights. Microsoft recommends that user accounts that are used to log on as a service have thePassword never expiresoption activated and that they have strong passwords. Otherwise, follow the Microsoft documentation "How to: Change the Password of the Accounts Used by SQL Server" if the SQL Server is running under an account for which the password is to be changed.
After the SQL Server 2012 installation you can still assign service accounts later with the SQL Server Configuration Manager.
For more information on service accounts, see the SQL Server 2012 Books Online.