ServerView Operations Manager V8.40

Transcription

1 Installation Guide - English FUJITSU Software ServerView Suite ServerView Operations Manager V8.40 Installing ServerView Operations Manager Software under Windows (Operations Manager, Update Manager, Event Manager) Edition June 2018

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2008 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and trademarks Copyright FUJITSU LIMITED All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat project logo are trademarks of the Apache Software Foundation.

3 Contents 1 Introduction Target groups and objectives Technical requirements Last-minute changes/corrections Management console Central management station (CMS) What's new ServerView Suite link collection Documentation for the ServerView Suite Typographic conventions Product names - conventions 14 2 PRIMERGY server management Architecture Installation on the central management station Installation on the managed servers Integration options of Operations Manager 21 3 Installing ServerView Operations Manager ServerView Operations Manager components Tomcat web server Calling and ports used Role-based user administration Global user management using an LDAP directory service ApacheDS Active Directory Managing certificates Cipher suite settings Web browser Administrative user "svuser" Preparations and important steps before you start the installation Installing the Microsoft Windows SNMP service Installing Java Runtime Environment Installation options for SQL Server 33 Installation under Windows 3

4 Contents Locally on the management station Remotely on a different system Installing SQL Server on a domain controller Setting SQL Server memory option SQL Server Hardware and software requirements Hardware requirements Software requirements Editions Setting up a service account Installing SQL Server 2014 Express edition Installing SQL Server 2014 Express Management Studio Installing SQL Server 2014 Enterprise/Standard edition Adding a user account with SQL Server administrator rights SQL Server Hardware and software requirements Hardware requirements Software requirements Editions Setting up a service account Operations Manager service accounts SQL Server service accounts Installing SQL Server 2012 Express edition Installing SQL Server 2012 Express Management Studio Installing SQL Server 2012 Enterprise/Standard edition Adding a user account with SQL Server administrator rights SQL Server 2008 (R2) Software requirements Editions Setting up a service account Operations Manager service accounts SQL Server service accounts Installing SQL Server 2008 (R2) Express edition Installing SQL Server 2008 R2 Express Management Studio Installing SQL Server 2008 (R2) Enterprise/Standard/Workgroup edition Adding a user account with SQL Server administrator rights Configuring a remote SQL Server Troubleshooting for Remote SQL Server Messages after clicking Next in the Remote DB dialog 72 Installation under Windows 4

5 Contents Messages after the Ready to Install the Application dialog during execution of SQL Script ExecDefRecBcp.sql Messages after the Click Install to begin installation dialog during execution of SQL Script ServerConfig.sql or SVSQLDbCreation.sql Messages after the Click Install to begin installation dialog during execution of GrantLoginJBoss.sql Operations Manager installation without SQL Server "sysadmin" access Overview of Windows accounts and access rights Configuration steps Tasks to be performed by the Windows Administrator on the CMS Select the SQL Server Tasks to be performed by the SQL Server Administrator Further configuration steps for a remote SQL Server Further procedure on the management station Upgrade installations of SQL Server Upgrading to later SQL Server versions Upgrading the SQL Server instance Moving the ServerView database Upgrading SQL Server 2012/2014 Express to SQL Server 2012/ Upgrading SQL Server 2008 Express to SQL Server Installing Operations Manager on Windows Terminal Server/Remote Desktop Services Installation check list Installation process Menu-driven installation of Operations Manager software Modify installation of Operations Manager software Upgrade installation of Operations Manager Uninstalling the Operations Manager software ServerView services Collecting diagnostics data ServerView Status gadget for Windows ServerView database Configuration file ServerViewDB.ini Connection to the ServerView database is interrupted Managing the ServerView database Backing up the ServerView database Backup jobs for the ServerView database Requirements for executing jobs 136 Installation under Windows 5

6 Contents Editing and tracking the progress of the backup jobs Checking the existence of backup files Checking the contents of the backup files Restoring the ServerView database Restoration via SQL Server Management Studio Checking the database backup SQL Server Express - database limit Monitoring measures in Operations Manager Measures for solving the problem Moving the ServerView database from local to remote SQL Server Requirements on the remote server Configuration steps Changing the load distribution Error diagnostic Log file Important information in the event of an error Growth of the ServerViewDB_log.LDF file Exporting the ServerView database Command Line Interface Installing Operations Manager software via the command line Database management via sqlcmd Checking the product version and language of SQL Server Restoring the ServerView database Backing up/restoring the ServerView database via command line tool Backing up the ServerView database Restoring the ServerView database Software License Agreement for End User 167 Installation under Windows 6

7 1 Introduction ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use the hypervisors VMware ESXi or Hyper-V installed. The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular web browser and the Java Runtime Environment. Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans and power supply. It monitors and controls the power consumption, analyzes the performance and utilization data and updates the server configuration. The security concept of Operations Manager includes role-based user management based on three underlying concepts: Global user management via an LDAP directory service (Lightweight Directory Access Protocol) Role-Based Access Control (RBAC) Single Sign-On (SSO) based on a Centralized Authentication Service (CAS) With RBAC you can tailor your security concept to the organizational structure of your company by assigning a task-oriented authorization profile to each role. SSO means that you only need to authenticate yourself once. Once you have done this successfully, you are given access to all ServerView components without having to sign on to any of them again. Server management with Operations Manager offers important benefits to operators of a comprehensive server network: Higher productivity thanks to high failsafety of the servers Reduced costs through automated monitoring of the IT infrastructure Flexible expansion possibilities for the servers, as Operations Manager can be easily adjusted to changed conditions Shorter downtimes thanks to simplified error analysis Guarantees energy-efficient and, where possible, uninterruptible server operation Quicker response times in the event of errors Installation under Windows 7

8 1.1 Target groups and objectives Reduction in total cost of ownership (TCO) through efficient use of network components and their resources Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system 1.1 Target groups and objectives This manual is intended for system administrators, network administrators and service technicians that have a basic knowledge of hardware and software. The manual documents the requirements for the use of Operations Manager that are specific to the operating system and describes the installation of the products ServerView Operations Manager, ServerView Update Manager and ServerView Event Manager. Installation under Windows 8

9 1.2 Technical requirements 1.2 Technical requirements Last-minute changes/corrections Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 2. You have the following options: On the DVD switch to the directory SVSSoftware Software ServerView Windows ServerView_S2. Start the DVD and select ServerView Software Products in the Welcome dialog. In the web browser window select ServerView- Operations Manager - Info Management console Standard PC, LAN with http access Microsoft Windows with any popular web browser. SUSE/Red Hat Linux with default web browser released with distribution Java Runtime Environment (JRE) V1.7.0_55 or higher Central management station (CMS) Hardware PRIMERGY server PRIMEQUEST server CELSIUS workstation Processors with at least two cores Main memory: at least 4 GB RAM 100 MBit-LAN At least 100 GB free disk space Graphics 1280 x 1024 (recommended minimum height is 800 px) Installation under Windows 9

10 1.2 Technical requirements Software Microsoft Windows Server 2016 Standard/Essentials/Datacenter (but no Server Core installation) Microsoft Windows Server 2012 all editions (but no Server Core installation) Microsoft Windows Server 2012 R2 all editions (but no Server Core installation) Microsoft Windows Server 2008 all editions (but no Server Core installation) Microsoft Windows Server 2008 R2 all editions (but no Server Core installation) Database Local under Windows: Included with the ServerView package: Microsoft SQL Server 2014 Express Additionally supported: o o o o Microsoft SQL Server 2008 Standard, Workgroup, Enterprise, Express Microsoft SQL Server 2008 R2 Standard, Workgroup, Enterprise, Express Microsoft SQL Server 2012 Standard, Enterprise, Express Microsoft SQL Server 2014 Standard, Enterprise, Express Remote under Windows o o o o Microsoft SQL Server 2008 Standard, Workgroup, Enterprise Microsoft SQL Server 2008 R2 Standard, Workgroup, Enterprise Microsoft SQL Server 2012 Standard, Enterprise Microsoft SQL Server 2014 Standard, Enterprise The ServerView database size limit depends on the used SQL Server edition. With a database size of 4 GB up to 200 servers can be managed (e.g. with Microsoft SQL Server 2008 Express). Java Runtime Environment Java Runtime Environment (JRE) V1.8.0_131 or higher JRE 1.8.0_ bit and JRE 1.8.0_ bit have WebView problems and therefore are not to be used with Operations Manager. It is recommended to use the JRE provided on the ServerView Suite DVD 2. Installation under Windows 10

11 1.3 What's new 1.3 What's new This edition of the manual applies to ServerView Operations Manager as of V8.30 and replaces the online manual "ServerView Operations Manager V Installation under Windows", edition September The manual features the following changes and enhancements: The section "Technical requirements" on page 9 has been updated. The section "Tomcat web server" on page 25 has been extended. The following sections are new: o "Global user management using an LDAP directory service" on page 28 o "ApacheDS" on page 28 o "Active Directory" on page 28 The section "Menu-driven installation of Operations Manager software" on page 103 has beesn improved. 1.4 ServerView Suite link collection Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers. Under ServerView Suite, links are offered on the following topics: Forum Service Desk Manuals Product information Security information Software downloads Training Installation under Windows 11

12 1.4 ServerView Suite link collection Software downloads includes the following downloads: o o o Current software statuses for the ServerView Suite as well as additional Readme files. Information files and update sets for system software components (BIOS, firmware, drivers, ServerView Agents and ServerView Update Agent) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express. The current versions of all documentation on the ServerView Suite. You can retrieve the downloads free of charge. Under PRIMERGY Server, links are offered on the following topics: Service Desk Manuals Product information Spare parts catalogue Access to the ServerView Suite link collection You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager. Select Help Links on the start page or the menu bar. 2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server. You access the start page of the online documentation via the following link: In the selection list on the left, select x86 Servers. On the right, click PRIMERGY ServerView Links under Selected documents. 3. Via the ServerView Suite DVD 2. In the start window of the ServerView Suite DVD 2, select the option ServerView Software Products. On the menu bar select Links. This opens the start page of the ServerView Suite link collection. Installation under Windows 12

13 1.5 Documentation for the ServerView Suite 1.5 Documentation for the ServerView Suite The documentation can be downloaded free of charge from the Internet. You will find the online documentation at under the link x86 Servers. ServerView Sitemap For an overview of the documentation to be found under ServerView Suite as well as the filing structure, see the ServerView Suite Sitemap: 1. In the selection list on the left, select x86 Servers and then Software. 2. On the right, select ServerView Suite. 3. Click ServerView Suite Sitemap under Selected documents. 1.6 Typographic conventions The following typographic conventions are used: Convention Explanation Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices. Indicates additional relevant information and tips. bold monospace monospace semibold blue continuous text pink continuous text <abc> [abc] [key] Indicates references to names of interface elements. Indicates system output and system elements for example, file names and paths. Indicates statements that are to be entered using the keyboard. Indicates a link to a related topic. Indicates a link to a location you have already visited. Indicates variables which must be replaced with real values. Indicates options that can be specified (syntax). Indicates a key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, for example,[shift] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols. Installation under Windows 13

14 1.7 Product names - conventions Screenshots Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands. 1.7 Product names - conventions In this document, product names used in the text are abbreviated as follows: Windows Server 2016 Product name Microsoft Windows Server 2016 Standard Microsoft Windows Server 2016 Essentials Microsoft Windows Server 2016 Datacenter Microsoft Windows Storage Server 2016 Standard Notation in the text Windows Server 2016 Windows Table 1: Product names - Windows Server 2016 Windows Server 2012 and 2012 R2 Product name Microsoft Windows Server 2012 Standard Microsoft Windows Server 2012 Essentials Microsoft Windows Server 2012 Datacenter Microsoft Windows Server 2012 Foundation Microsoft Windows Server 2012 R2 Standard Microsoft Windows Server 2012 R2 Essentials Microsoft Windows Server 2012 R2 Datacenter Microsoft Windows Server 2012 R2 Foundation Microsoft Windows Storage Server 2012 Standard Notation in the text Windows Server 2012 Windows Table 2: Product names - Windows Server 2012 and 2012 R2 Installation under Windows 14

15 1.7 Product names - conventions Windows Server 2008 and 2008 R2 Product name Microsoft Windows Server 2008 Standard Microsoft Windows Server 2008 Enterprise Microsoft Windows Server 2008 Datacenter Microsoft Windows Server 2008 Foundation Microsoft Windows Web Server 2008 Microsoft Windows Small Business Server 2008 Standard Microsoft Windows Small Business Server 2008 Premium Microsoft Windows Server 2008 Standard x64 Edition Microsoft Windows Server 2008 Enterprise x64 Edition Microsoft Windows Server 2008 Datacenter x64 Edition Microsoft Windows Server 2008 Foundation x64 Edition Microsoft Windows Small Business Server 2008 Standard x64 Edition Microsoft Windows Small Business Server 2008 Premium x64 Edition Microsoft Windows Server 2008 R2 Standard Microsoft Windows Server 2008 R2 Enterprise Microsoft Windows Server 2008 R2 Datacenter Microsoft Windows Server 2008 R2 Foundation Microsoft Windows Web Server 2008 R2 Microsoft Windows Small Business Server 2008 R2 Standard Microsoft Windows Small Business Server 2008 R2 Premium Table 3: Product names - Windows Server 2008 and 2008 R2 Notation in the text Windows Server 2008 Windows Server 2008 x64 Windows Server 2008 R2 Windows Installation under Windows 15

16 1.7 Product names - conventions Linux Product name Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 12 Table 4: Product names - Linux Virtualization software Notation in the text Red Hat Linux RHEL6 RHEL7 SUSE Linux SUSE Linux SLES11 or SLES 11 SUSE Linux SLES12 or SLES 12 Linux Product name Microsoft Hyper-V Server Microsoft Hyper-V Server 2008 R2 Notation in the text Hyper-V Server Hyper-V Server 2008 R2 Hyper-V VMware ESXi 5.5 ESXi 5.5 VMware VMware ESXi 6.0 ESXi 6.0 VMware ESXi 6.5 ESXi 6.5 Citrix XenServer Red Hat Enterprise Linux 5 Xen Red Hat Enterprise Linux KVM Table 5: Product names - Virtualization software Citrix XenServer Xen Server KVM Installation under Windows 16

17 1.7 Product names - conventions ServerView Suite Software Products Product name ServerView Installation Manager ServerView Installation Manager ServerView Operations Manager ServerView Inventory Manager ServerView Archive Manager ServerView Event Manager ServerView Threshold Manager ServerView Performance Manager ServerView Virtual-IO Manager ServerView Fabric Manager ServerView Update Manager ServerView Download Manager ServerView Online Diagnostics ServerView System Monitor irmc (integrated Remote Management Controller) irmc S2 / irmc S3 / irmc S4 / irmc S5 (integrated Remote Management Controller) ServerView Remote Management Frontend PrimeUp installation tool PRIMERGY Support Package Local Service Concept Fujitsu DeskView Integration in Microsoft System Center Configuration Manager Notation in the text Installation Manager Installation Manager Operations Manager Inventory Manager Archive Manager Event Manager Threshold Manager Performance Manager Virtual-IO Manager or VIOM Fabric Manager Update Manager Download Manager Online Diagnostics System Monitor irmc irmc S2/S3/S4/S5 Remote Management Frontend PrimeUp PSP LSC DeskView-Integration Table 6: Product names - ServerView Suite Software Products Installation under Windows 17

18 2.1 Architecture 2 PRIMERGY server management 2.1 Architecture The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers. Figure 1: Architecture of ServerView Operations Manager Management console A Java Web Start-based console allows you to manage the servers and display the determined data. All you need is a popular web browser to download the starter file for Java Web Start. The following can be used as a browser: Microsoft Windows with any popular web browser SUSE/Red Hat Linux with default web browser released with distribution The Java Runtime Environment must also be installed. Installation under Windows 18

19 2.1 Architecture Central management station (CMS) On the CMS ServerView Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the CMS and integrated in Operations Manager. The CMS (and thus ServerView Operations Manager with its components) may also run in Windows-based or Linux-based virtual machines (VM) that use hypervisors such as VMware ESXi, Microsoft Hyper-V, and Red Hat Enterprise KMV. The global user management of the ServerView Suite and of the irmc each centrally stores users for all CMS / irmc in the directory of an LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the CMS and irmc that are connected to this server in the network. The ServerView Suite currently supports the following directory services: ApacheDS Microsoft Active Directory During the installation of ServerView Operations Manager you have the option to choose ServerView s internal directory service (ApacheDS) or an existing external directory service (Active directory). For further information about the use of directory services with ServerView, see the "User Management in ServerView" user guide. The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation: SQL Server 2014 Express under Windows Server PostgreSQL under Linux However, other Microsoft SQL Server databases can be used under Windows. The Java Runtime Environment is required on the CMS. How to install ServerView Operations Manager is explained in the following manuals: Installing ServerView Operations Manager Software under Windows Installing ServerView Operations Manager Software under Linux Managed servers On the managed servers, ServerView Agents, ServerView CIM Providers, or ServerView Agentless Service should be installed, which supply the information to the CMS. ServerView RAID Manager and ServerView Update Agent should be also installed on the managed servers. The installation of ServerView Agents on virtual machines (VMs) is not released. Installation under Windows 19

20 2.2 Installation on the central management station The ServerView Agents are available for Windows, Linux, and Citrix XenServer. ServerView CIM Providers are available for Windows, Linux, and VMware ESXi. ServerView Operations Manager currently only supports ServerView CIM Providers for VMware ESXi. How to install them is explained in the following manuals: ServerView Agents for Windows ServerView Agents for Linux Installation ServerView ESXi CIM Provider ServerView CIM Providers for Windows, Linux, and VMware ESXi 2.2 Installation on the central management station Operations Manager (incl. ServerView Update Manager and ServerView Event Manager) must be installed on a management station in order to monitor the PRIMERGY servers via PC or notebook with a standard web browser. You can install Operations Manager on the following operating systems: Windows, SUSE Linux Red Hat Linux The Operations Manager software is supplied on the ServerView Suite DVD 2. An Installation Wizard is provided for installation under Windows. This covers the installation of Operations Manager, Update Manager, and Event Manager. In addition, the Wizard permits separate installation of the Operations Manager software on different servers. Installation can also occur in the Windows command line mode. A description of the installations on the management station can be found in "Installing ServerView Operations Manager" on page 23 and in "Installing Operations Manager software via the command line" on page Installation on the managed servers The following components must be installed on the managed servers, which supplies information to the central management station: ServerView Agents, ServerView CIM Providers, or ServerView Agentless Service The ServerView Agents are available for Windows, Linux, and Citrix XenServer. CIM Providers are available for Windows, Linux, and VMware ESXi. The installation is Installation under Windows 20

21 2.4 Integration options of Operations Manager described in the "ServerView Agents for Windows", "ServerView Agents for Linux", "ServerView CIM Providers for Windows, Linux, and VMware ESXi" installation and user guides. ServerView Agentless Service is available for Windows and Linux. The installation is described in the "ServerView Agentless Management" overview. The ServerView System Monitor is installed automatically (via the ServerView Agents installation) and allows you to monitor and check some server information locally on the server. A detailed description can be found in the "ServerView System Monitor" user guide. ServerView Update Agent To keep the managed servers up-to-date by Update Management functions the ServerView Update Agent must be installed on the managed servers. How to do this is described in the "ServerView Update Management" user guide. ServerView RAID Manager The ServerView RAID is used to monitor and manage the RAID controllers integrated in PRIMERGY servers. A detailed description can be found in the "RAID Management" user guide. Additional installations ServerView Online Diagnostics During installation of the ServerView Agents for Windows, Online Diagnostics is also installed. You can use Online Diagnostics to perform a series of hardware tests on a managed PRIMERGY server from the remote workstation. When installing the ServerView Agents (for Windows) in Expert mode, you can choose whether to install additional components, including Asset CLI, Configuration Tools, Prime Collect and ServerView System Monitor. 2.4 Integration options of Operations Manager The use of standardized protocols and interfaces means that Operations Manager can easily be integrated into other management systems. The Operations Manager integration modules ensure the output of detailed information on the status of the PRIMERGY servers on the console of the connected management system. PRIMERGY servers can thus be managed with a central enterprise management console (Single Point of Administration). Additional management functions such as network management, application management and software distribution can also be used without any problem for PRIMERGY servers. Installation under Windows 21

22 2.4 Integration options of Operations Manager Integration modules are available for the following management systems: IBM Tivoli TME 10 Framework TE/C IBM Tivoli NetView HP OpenView Network Node Manager HP Operations Manager Microsoft MOM and SCOM 2007 Microsoft SMS and SCCM 2007 Nagios and BMC Patrol VMWare vcenter 5.1 PRIMEPOWER ServerView Suite Some integration modules (e.g. Microsoft SMS, MOM) are provided on the ServerView Suite DVD 2 and can be automatically installed on the management station when the Operations Manager software is installed. This is provided that the relevant management software is already installed on the system. The description of this is provided in "Menudriven installation of Operations Manager software" on page 103. The other integration modules (e.g. HP Operations Manager, IBM Tivoli TME NetView) are available on the special ServerView Integration CD. For further information on the integration modules, see the corresponding integration manuals and the "ServerView Integration" data sheet. Installation under Windows 22

23 3 Installing ServerView Operations Manager This chapter describes how to install Operations Manager (incl. ServerView Update Manager and ServerView Event Manager) on the management station under Windows operating systems. If Update Manager (up to version 4.71) is already installed on the management station, it must be uninstalled before installation of the Operations Manager software, otherwise the installation will abort. If ServerView Agents are installed on the management station, you must install the current ServerView Agents before installing Operations Manager. The relevant software is supplied on the ServerView Suite DVD 2. The products can be installed together on a central management station, or separately on different computers. An upgrade installation is only supported from an existing Operations Manager version or later. All Operations Manager versions < must first be upgraded to version or later. Installation under Windows is user-friendly and menu-driven and is based on the Microsoft Windows Installer Technology (see "Menu-driven installation of Operations Manager software" on page 103). Installation can also occur in the Windows command line mode. An editable script for installation without a dialog - silent installation - is provided for this purpose (see "Installing Operations Manager software via the command line" on page 161). Installation under Windows 23

24 3.1 ServerView Operations Manager components 3.1 ServerView Operations Manager components ServerView Operations Manager installation When you install ServerView Operations Manager, the following ServerView components are also automatically installed: ServerView Configuration Manager With ServerView Configuration Manager, you can make system-dependent configurations on a managed server. (Only supported for servers on which the ServerView Agents are installed.) ServerView Archive Manager With Archive Manager you can record system and operating data of PRIMERGY servers and store it centrally. This data can then be checked and evaluated. ServerView Inventory Manager With Inventory Manager you can retrieve data of a managed server or multiple servers and display it on the screen. You can also export the data from Operations Manager and store it in various formats (e.g. CSV, ODBC). ServerView Performance Manager With Performance Manager you can monitor the performance of specific server components. Performance Manager works on the basis of rules. The centrally created rules can be executed on any number of servers. ServerView Threshold Manager With Threshold Manager you can monitor one or more managed PRIMERGY servers and any virtual machines running on them centrally from the management station on the basis of threshold values. ServerView Remote Management Frontend ServerView Remote Management Frontend provides a web-based work environment for the remote management of PRIMERGY servers. ServerView Update Manager installation When you install Update Manager, the following ServerView Operations Manager components are also installed: Update Manager With Update Manager you can install and update software across an entire domain via a central management station. Installation under Windows 24

25 3.2 Tomcat web server Repository Manager With Repository Manager you can manage the update repository. Download Manager With Download Manager you can conveniently obtain the latest statuses of firmware, BIOS, drivers and ServerView Agents for your servers. Configuration With Configuration you can set global parameters for Update Manager. ServerView Event Manager installation When you install Event Manager, the following ServerView Operations Manager components are also installed: Alarm Monitor Alarm Monitor displays all incoming alarms for the selected servers and server groups in the Operations Manager main window. Alarm Configuration The Alarm Configuration component lets you define settings for alarm handling. You can define alarm rules, filter rules and general settings. 3.2 Tomcat web server As of ServerView Operations Manager version 7.11, the web server used is Tomcat. As of ServerView Operations Manager version 7.11, the JBoss web server is no longer supported. The necessary files for Tomcat are automatically installed when the Operations Manager software is installed (see "Installing Tomcat via Fujitsu Software ServerView Application Server Setup wizard" on page 107). Tomcat is configured as a standalone service ServerView ApplicationService, which you can start and stop via the Windows start menu: Select Administrative Tools Services. You can also start and stop the service via the following command: %windir%\system32\net.exe start "ServerViewApplicationService" %windir%\system32\net.exe stop "ServerView ApplicationService" Installation under Windows 25

26 3.2 Tomcat web server Automatic deletion of Tomcat access logs Log files localhost_access_log.<yyyy-mm-dd>.log are written in the directory <installation_path>\tomee\logs. A separate log is created for each day. In previous versions they were never deleted. Tomcat includes automatic deletion. In the directory <installation_path>\tomee\svconf the sv-com-config.xml configuration file describes the parameters: <ns0:filenameprefix>localhost_access_log.</ns0:filenameprefix> List of file name prefixes, qualifying the files that are to be checked for deletion. The default is a list with the single entry "localhost_access_log.". <ns0:testinterval>12:00</ns0:testinterval> Test interval, measured in minutes. The test interval can range between 1 minute and 24 hours. The behavior of the automated file deletion depends on the specified value: Number [ ] File checking begins when Tomcat starts up, and is repeated at the specified time interval. Time [hh:mm] The test interval is 24 hours and the file checking occurs every day at the specified time. (The values for hh range from 00 till 23.) The default is 12:00, i.e. files are checked every day at noon. <ns0:maxage>10080</ns0:maxage><!-- one week --> Maximum age of a log file, measured in minutes. Any file matching an entry in the filenameprefix list which is older than this value is deleted. The default is 10080, i.e. seven days. If no value is specified in the configuration file, the value 4320, i.e. three days, is used Calling and ports used The entry address of Operations Manager begins with the prefix https. Port Used for 3169 http (When trying to access this port, Operations Manager versions older than V4.92 are automatically redirected to port 3170.) 3170 https (The port must be unlocked in the firewall.) TLS v1.1, TLS v1.2, and SSLv2Hello are supported. Installation under Windows 26

27 3.2 Tomcat web server Port Used for 3171 Update Management (The port must be unlocked in the firewall to allow Update Management.) 3172 Remote Connector Service (Server Configuration Manager, Power Monitor, etc.) (The port must be unlocked in the firewall.) 3173 ServerView RAID Manager 1473 non-ssl port of ServerView s directory service (ApacheDS) 1474 LDAPS, if ApacheDS is configured as directory service PostgreSQL database server (only for Linux) 9363 used by Operations Manager to contact XEN daemons 16509, used by the KVM service TomEE (shutdown port) For detailed security information see the White Paper Secure PRIMERGY Server Management. To gather information, Operations Manager accesses the following ports of all network nodes of a subnet which is specified on ServerBrowser and managed servers. Port Used for 80 Citrix 135 Hyper-V 161 SNMP 443 VMware 623 BMC (irmc) 3172 ServerView Remote Connector 5988 VMware 5989 VMware 9363 XEN (up to SLES 11) KVM, XEN (as of SLES 12) KVM, XEN (as of SLES 12) Installation under Windows 27

28 3.2 Tomcat web server Role-based user administration Tomcat enables a role-based user administration which is based on the principle of least privilege. This means that no user should have more privileges than are necessary for using a particular ServerView component or performing a particular ServerView-specific task. For further information on role-based user administration, see the "User Management in ServerView" user guide Global user management using an LDAP directory service The global user management of the ServerView Suite is based on using an LDAP directory service. Users are stored and managed centrally for all related CMS by means of the LDAP directory service. The directory service provides all data needed for authentication and authorization. During the installation of ServerView Operations Manager you have the option to choose ServerView Operations Manager s internal directory service (ApacheDS, see "ApacheDS" on page 28) or an existing external directory service (Active directory, see "Active Directory" on page 28). For further information about the use of directory services with ServerView, see the "User Management in ServerView" user guide ApacheDS If you select ServerView Operations Manager s own preconfigured directory service ApacheDS during the installation of ServerView Operations Manager, the setup installs ApacheDS as its own directory service (see "Select Directory Server window" on page 110). Role Based Access Control (RBAC) is already implemented in the ApacheDS directory service. ApacheDS provides the predefined user roles Administrator, Monitor, Operator, and UserAdministrator, each of them being dedicated to one of the predefined users Administrator, Operator, Monitor, and UserManager, respectively. You can of course align your security concept with your organization s structure by creating additional users, roles, and role-to-user assignments Active Directory If you want to use an already configured directory service such as Active Directory, you can determine during ServerView Operations Manager installation which strategy will be used for your ServerView user management (see "Select Directory Server window" on page 110): Installation under Windows 28

29 3.2 Tomcat web server RBAC management User authentication and user authorization are managed within the same "external" directory service (e.g. Active Directory). RBAC management with authentication and authorization within Active Directory requires that you import the authorization data of the ServerView user management, i.e. the declarations of privileges, roles and departments, from an LDIF file into the domain controller (LDIF import). unified RBAC management User authentication is managed via the "external" directory service (e.g. Active Directory) whereas user authorization is managed via the "internal" preconfigured directory service of ServerView Operations Manager (ApacheDS). Therefore, unified RBAC management requires no LDIF import of user authorization data Managing certificates To communicate with the Tomcat web server, web browsers always use an HTTPS connection (i.e. a secure SSL connection). Therefore, the Tomcat web server needs a certificate (X.509 certificate) to authenticate itself at the web browser. The X.509 certificate contains all the information required to identify the Tomcat web server plus the public key of the Tomcat web server. For further information on managing certificates, see "User Management in ServerView" user guide Cipher suite settings Cipher suites and SSL protocols used by ServerView Application Server can be configured during ServerView Operations Manager installation (see "Security Configuration window" on page 109). There are three defined configuration sets available: Modern (strongest cipher suite set) Intermediate Old (weakest cipher suite set) These three cipher suite sets are equivalent to the Modern/Intermediate/Old sets defined in the Mozilla document Modern settings are the most secure. Only the latest SSL protocol version TLSv1.2 is allowed. So it will pass vulnerability scannings without errors. The Intermediate configuration set allows TLSv1.2, TLSv1.1 and TLSv1.0. If a client which can be connected to ServerView Operations Manager allows only the SSL protocol version SSLv3, the Old configuration set should be selected. Installation under Windows 29

30 3.3 Web browser Otherwise a connection cannot be established. This set is the weakest cipher suite set and allows TLSv1.2, TLSv1.1, TLSv1.0, and SSLv3. By default the Intermediate set is configured. The configuration of the cipher suites and SSL protocols is stored in the <SVOM installation directory>\tomee\conf\server.xml configuration file. After ServerView Operations Manager is installed, you can modify the configuration of cipher suites and protocols by editing the server.xml configuration file. In the <Connector> section for the port 3170, you can define allowed cipher suites under the ciphers attribute and also specific protocols to use (e.g. SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2) under the sslenabledprotocols attribute. You have to restart the ServerViewApplicationService service after modifying the server.xml file. In the server.xml configuration file, allowed cipher suites are specified in IANA nomenclature, whereas the tables of ciphers for specific cipher suites on the Mozilla page provided use OpenSSL cipher designators. However, you will find a cipher names equivalence table in the Mozilla document, showing the corresponding OpenSSL and IANA cipher names (see link above). At upportedciphersuites you will find two tables under Cipher Suites (The SunJSSE Provider), which show you which cipher suite support which Java version. With Java 8 are no restrictions in this regard. 3.3 Web browser A web browser is required to download the starter file for Java Web Start from central management station to any other computer (the management console). The browser must be able to interpret HTML5 and Javascript If you should experience problems when accessing the web server, make one of the following settings in the web browser: Disable the access option for the use of a proxy entirely in the browser. Enter the IP address at an appropriate position to specify that no proxy is to be used for the host on which the web server is running. 3.4 Administrative user "svuser" The password for the special administrative user svuser cannot be changed by the ApacheDS user interface. You can only change it locally in the Operations Manager Installation under Windows 30

31 3.5 Preparations and important steps before you start the installation installation wizard: During a new installation, enter the password in the Administrative User Password window, "Menu-driven installation of Operations Manager software" on page 103. For an existing installation execute a modify installation (see "Modify installation of Operations Manager software" on page 120) and change the password in the ApacheDS Administrative User window, "Menu-driven installation of Operations Manager software" on page Preparations and important steps before you start the installation Make sure that the following tasks have been completed before you start installing the Operations Manager software: Install a Windows operating system (Windows Server 2008, Windows Server 2012, or Windows Server 2016) on the management station. Service Pack Application: Apply Service Pack to all servers and computers in which ServerView components are installed if necessary. It is recommended to apply Service Pack 2 for Windows Server 2008 and Service Pack 1 or later for Windows Server 2008 R2. Make sure to apply the Service Pack. If the Service Pack is not applied, the operation is not guaranteed. If the Service Pack has been already applied, it does not need to reapply. Before applying the Service Pack, make sure that the Microsoft Windows SNMP service is installed. As of version 7.10, ServerView Operations Manager is able to monitor a server via SNMPv3. In order to use SNMPv3 to manage a Windows-based server, two SNMP services are required: the Microsoft Windows SNMP service and the Net-SNMP service. Both these SNMP services must therefore be installed on the management station. For further information, see "Using of SNMPv3 with ServerView Suite products" overview. If you have prepared the managed node and the central management station you can enable SNMPv3 in ServerView Operations Manager. You have two options for enabling SNMPv3 in ServerView Operations Manager: Via the V3 Setting configuration window Via the snmp.conf configuration file For further information, see " ServerView Operations Manager - Server Management" user guide. Installation under Windows 31

32 3.5 Preparations and important steps before you start the installation Set up the SNMP service on the management station. Therefore you must specify which communities and servers (IP addresses) the management station is to receive traps from, see "Installing the Microsoft Windows SNMP service" on page 32. Install Java Runtime Environment on the management station, see "Installing Java Runtime Environment" on page 33. Set up a non-administrative user account for the Tomcat application server which is installed with ServerView Operations Manager. During the installation you have to specify the account in the Tomcat Service Logon Information window. ServerView Operations Manager requires an SQL Server in which to install its SQL database, see "Installation options for SQL Server" on page 33. Operations Manager checks whether a suitable SQL Server instance is installed. If no suitable SQL Server instance is found, you can install SQL Server 2014 Express automatically with Operations Manager Installing the Microsoft Windows SNMP service Windows Server 2008/2012/ Install the SNMP service on the server: 1. Start the Server Manager. 2. On Windows Server 2012/2016 start the Add Roles and Features Wizard. On Windows Server 2008 click in the left window Features and then select Add Features. 3. Select the option SNMP Services. 4. Click Next and then Install. 2. Configure the SNMP service on the server as follows: The default community name is public. This default entry is used by most SNMP services. For security reasons, we recommend that you change this entry. In principle you can define an individual community for each server or server group. Remember to make corresponding changes on the manager. If you want to use the entire range of ServerView functions, you must assign read-write rights to the community. You can restrict access to certain functions by assigning (read-only) access rights to them. 1. Select Administrative Tools Services SNMP Service. 2. Select Properties from the context menu. 3. Click Traps. 4. Enter the community name under Community Name, e. g. public. 5. Click add to list. Installation under Windows 32

33 3.6 Installation options for SQL Server 6. Click Add. 7. Enter the IP address of the management station for the chosen community and then click the Add button. Traps are only sent to the management stations entered here. 8. Click Security and set the Rights for the specified community to e.g. READ WRITE. Confirm your new settings with OK. 9. Specify the computer from which SNMP packets will be accepted by selecting the relevant option. 10. Click OK to finish the configuration Installing Java Runtime Environment You can install JRE via the ServerView Suite DVD 2. Proceed as follows: 1. Place the ServerView Suite DVD 2 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD s root directory. 2. Mark the option Select ServerView Software Products. 3. Click Start. 4. Select the desired language in the displayed window. 5. Select Java. 6. Now click the appropriate *.exe to install. You can also download the latest version of JRE via the Oracle Software Downloads website. If the message Java has discovered application components that could indicate a security concern appears, after starting a Operations Manager component, answer with No. To avoid this, set the following in the Java Control panel: 1. Select Control Panel Java. 2. In the Java Control Panel dialog box change to the Advance tab. 3. Under Mixed code (sandboxed vs. trusted) security verification activate the Enable - hide warning and run with protections option. 3.6 Installation options for SQL Server Operations Manager requires an SQL Server in which to install its SQL database ServerViewDB. During the installation of Operations Manager, an SQL Server can, under certain conditions, be installed automatically. But in some cases, which are described in the Installation under Windows 33

34 3.6 Installation options for SQL Server following sections, you must install SQL Server yourself before installing Operations Manager. Optionally, an SQL Server that is already on the system and is suitable for Operations Manager, can be used and selected during the installation. In any case, a number of important installation requirements and constraints must be observed. Microsoft SQL Server Express edition is suited for monitoring less than 200 servers. To monitor 200 or more servers, we recommend you to install a full edition of Microsoft SQL Server. Parallel (side-by-side) installation of SQL Server SQL Server can be installed up to 16 times in parallel, always under a different instance name, in any edition on the same system. Suitable instances for ServerView Operations Manager must comply with the following restrictions: For SQL Server full editions, any instance name is valid. For SQL Server free (Express) editions, the instance name must be SQLSERVERVIEW. An SQL Server instance can contain several databases. Operations Manager will install its database ServerViewDB in the SQL Server instance selected by you during the Operations Manager installation. The name of the ServerView Operations Manager database is always ServerViewDB.The database name is fixed and cannot be selected during the ServerView Operations Manager setup. As the database name is always unique, it is not possible to install Operations Manager on multiple local management stations and to use the same remotely installed SQL Server instance for each. CAUTION! The name of the ServerView Operations Manager database must never be changed. Otherwise, the Operations Manager applications cannot access the database anymore and installation errors may occur in subsequent upgrade or new installations. Instances of different SQL Server versions may be installed side-by-side on the same system. For general information regarding side-by-side installation of all versions, see also the corresponding chapter in SQL Server Books Online from Microsoft: "Work with multiple instances and versions of SQL Server". Installation under Windows 34

35 3.6 Installation options for SQL Server For SQL Server 2008 and 2008 R2, some additional hints apply, which are documented in the article "Considerations for side-by-side instances of SQL Server 2008 and SQL Server 2008 R2". Both articles mention internal version numbers used by SQL Server which are useful for understanding side-by-side concepts. The following internal version numbers are used by SQL Server versions that are supported by ServerView Operations Manager: SQL Server 2008: SQL Server 2008 R2 : SQL Server 2012: SQL Server 2014: Installations of different language versions of SQL Server instances on the same system are not supported: Example SQL Server 2008 (English) and SQL Server 2008 (German) as side-by-side installations on the same system are not supported. If a non-english SQL Server instance is already installed on the system, Operations Manager cannot automatically install the standard English SQL Server in parallel. In this case a dialog box opens, prompting you to manually install an SQL Server in the appropriate language version. Displaying the existing instances You can display existing instances of SQL Server as follows: 1. Open the input prompt. 2. Enter the following command: sqlcmd -L findstr -i <computer_name> All installed SQL Server instances on the system <computer_name> are displayed. Bear in mind that it can take several minutes for this command to be executed. You can install Operations Manager if there are fewer than 16 instances on the system. The version and language of the instances can be queried via commands, see "Important information in the event of an error" on page 154. General information on SQL Server instance names A single instance is designated as the default instance. This instance does not require a specific instance name. This default instance appears in the selection lists under the name (local) or, for a remote server, under that server s computer name. The other 15 instances require unique instance names. They are referred to as named instances. SQL Server Express is often installed with an instance name that appears in selection lists under the name <server_name>\<instance_name>. Installation under Windows 35

36 3.6 Installation options for SQL Server Language version and operating system language of SQL Server SQL Server is available in various language versions. You must install an SQL Server version whose language is compatible with that of the operating system. The English version of SQL Server can be installed on all supported operating systems. We suggest installing English SQL Server on western European Windows operating systems. Alternatively you can install SQL Server in the same language as your operating system. Verify that the disk where the SQL Server will be installed is uncompressed. Authentication mode Operations Manager uses only Windows authentication mode to connect to SQL Server. If not otherwise needed, it is recommend to install SQL Server with Windows Authentication mode only. This is the default setting in the SQL Server setup and is also recommended by Microsoft. If you choose mixed mode (Windows Authentication and SQL Server authentication), please read the hints from Microsoft regarding authentication mode in SQL Server Locally on the management station SQL Server can be installed locally on the management station or automatically by Operations Manager. Suitable SQL Server instances for Operations Manager are: SQL Server Express editions with instance name SQLSERVERVIEW. SQL Server 2014 Express can be installed as part of the ServerView Operations Manager installation on all Windows Server systems supported by Operations Manager. SQL Server full editions (Enterprise/Standard or Workgroup where available) with any instance name or as an unnamed instance. The Workgroup Edition was discontinued by Microsoft for SQL Server 2012 and higher. Side by Side installations of different SQL Server versions on the system are supported as defined by Microsoft. For general information regarding side-by-side installation of all versions, see also the corresponding chapter in SQL Server Books Online from Microsoft: "Work with multiple instances and versions of SQL Server". Installation under Windows 36

37 3.6 Installation options for SQL Server Recognition of SQL Server instances during Operations Manager installation An SQL server is provided on the ServerView Suite DVD 2. You can automatically install this SQL Server instance during installation of the Operations Manager software. The automatically installed SQL Server is given the SQL Server instance name SQLSERVERVIEW. If a suitable SQL Server instance for Operations Manager is already available, you are offered a choice between installing Operations Manager's default SQL Server instance or using an existing one. In the latter case, you can choose one of the existing SQL Server instances from a selection list and install the ServerView database there. For further information on installing SQL Server 2014 or SQL Server 2014 Express, see "SQL Server 2014" on page 40. For further information on installing SQL Server 2012 or SQL Server 2012 Express, see "SQL Server 2012" on page 49. For further information on installing SQL Server 2008(R2) or SQL Server 2008 (R2)Express, see "SQL Server 2008 (R2)" on page Remotely on a different system You can also use a remotely installed SQL Server instance to install the ServerView database into it. Requirements Operations Manager must not be simultaneously installed locally on the remote server. It is not possible to install Operations Manager on multiple local management stations and use the same remotely installed SQL Server instance for each. The local management station and the remote system must belong to the same domain or to two domains with a two way trust relationship. You need at least one domain user account in the Domain Users group. A suitable SQL Server instance is SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, or SQL Server 2008 in Standard, Workgroup (where available) or Enterprise Edition. It must be installed and configured on the remote server before Operations Manager is installed. For further information on configuring SQL Server for use as a remote SQL Server, see "Configuring a remote SQL Server" on page 68. Installation under Windows 37

38 3.6 Installation options for SQL Server Side by Side installations of different SQL Server versions on the system are supported as defined by Microsoft. For general information regarding side-by-side installation of all versions, see also the corresponding chapter in SQL Server Books Online from Microsoft: "Work with multiple instances and versions of SQL Server". SQL Server Express is not supported. Microsoft SQL Server 2012/2014 Command Line Utilities The use of a remote SQL Server requires the SQL Server command line tools sqlcmd and bcp on the management station. If these commands are not available, the Microsoft SQL Server 2012 Command Line Utilities software is automatically installed. As a prerequisite the Microsoft SQL Server 2012/2014, Native Client is installed beforehand Installing SQL Server on a domain controller For security reasons, whenever possible, do not install SQL Server on a domain controller. SQL Server installation is not supported on a Read Only Domain Controller. Please note the order of installation: 1. First promote the server to a domain controller. 2. Then install SQL Server and ServerView Operations Manager. Proceed as follows: 1. Assign a static IP address to this computer. 2. Log on as a local administrator. 3. Select Start Run. 4. Under Open, type dcpromo and then click OK. Run the Active Directory Installation Wizard. 5. Log on to the server as a domain administrator 6. Install SQL Server, for example Workgroup/Standard/Enterprise Edition. SQL Server service accounts should run as Windows domain user accounts. Run separate SQL Server services under separate Windows accounts. On a domain controller the SQL Server services cannot run as Local Service or Network Service. You can also install SQL Server service accounts to run as Local System. This option is not Installation under Windows 38

39 3.7 Setting SQL Server memory option recommended. 7. Install ServerView Operations Manager. You can still change the service-account assignment after the installation using the SQL Server Configuration Manager, for example for the Express Edition. Do not change the role of the server after you have installed SQL Server. For example, if you install SQL Server on a member server, do not use the Active Directory Installation Wizard (dcpromo.exe) tool to promote the server to a domain controller. Or, if you install SQL Server on a domain controller, do not use the Active Directory Installation Wizard to demote the server to a member server. Changing the role of a server after you install SQL Server can cause loss of functionality and is not supported. 3.7 Setting SQL Server memory option On Windows, ServerView Operations Manager uses Microsoft SQL Server as the database server. Microsoft SQL Server has a server property max server memory which defines the upper limit of memory used by the buffer pool of the Microsoft SQL Server Database Engine. By default, this value is set to MB and Microsoft SQL Server will change its memory requirements dynamically based on available system resources. But you can also set SQL Server memory options manually and restrict the amount of memory that SQL Server can access to a lower limit. This may be desirable when system administrators want to configure an instance of SQL Server in conjunction with the memory requirements of other applications that run on the same computer. For this purpose, therefore, ServerView Operations Manager offers a Windows batch file as a utility tool. The batch file sets the max server memory option in the Microsoft SQL Server instance that Operations Manager uses according to customer input. Open a command prompt window. Find out <DllPath> and switch to the directory: type %windir%\serverviewdb.ini findstr -i DllPath= cd /d <DllPath>\Tools Execute the tool: SVConfigSQLMaxMemSize.bat The max server memory value may be set within a range of 32 to MB. These limits are offered and checked by the tool. The default value if nothing is specified is 128 MB. Installation under Windows 39

40 3.8 SQL Server 2014 Please be aware that the server property max server memory should only be changed with care and with regard to system and application load. From test observations, a setting of 128 MB seems to be enough when there are about ten normally-running servers registered in the server list. Please observe the required permissions in MS SQL Server, especially when ServerView Operations Manager was installed without SQL Server "sysadmin" access: Changing the max_server_memory option requires permissions held by the sysadmin (or serveradmin) fixed server roles. It is therefore required to execute the utility tool from an account which is a member of the "sysadmin" server role in MS SQL Server. 3.8 SQL Server 2014 You can install the ServerView database into an SQL Server 2014 instance on a Windows Server 2008 or later operating system version. On any Windows Server version supported by ServerView Operations Manager, SQL Server 2014 Express can be installed automatically with the ServerView installation. All other editions of SQL Server 2014 must be installed before Operations Manager Hardware and software requirements Hardware requirements For a detailed overview of the hardware requirements for installing SQL Server 2014, see and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2014" Software requirements Operating systems supported for SQL Server 2014: Windows Server 2016 Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 SP1 Windows Server 2008 SP2 Microsoft.NET Framework 3.5 SP 1 and.net Framework 4.0 Installation under Windows 40

41 3.8 SQL Server 2014 For details on how to acquire these packages for the relevant operating system, see and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2014". Windows PowerShell 2.0 is required for installing Database Engine components and SQL Server Management Studio, which is a database administration software. o o For details on how to install and enable SQL Management Studio, see the website mentioned above. On Windows Server 2008 R2 SP1 PowerShell 2.0 comes with the operating system. You find it in All Programs Accessories Windows PowerShell. For Windows Server 2008 SP2 search in Microsoft Download Center for Windows PowerShell 2.0 and download it. Two different packages exist. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. Install the required package. o In case of Windows Server 2012: Windows Power Shell 3.0 is part of the Windows Server 2012 installation. o In case of Windows Server 2012 R2: Windows Power Shell 4.0 is part of the Windows Server 2012 R2 installation. o In case of Windows Server 2016: Windows Power Shell 5.0 is part of the Windows Server 2016 installation Editions You can use the following editions, among others, depending on your performance requirements and budget: Express Edition SQL Server 2014 Express is the successor to SQL Server 2012 Express. SQL Server 2014 Express is free and available from the Microsoft Download Center. The database size limit for SQL Server 2014 Express is 10 GB. The full versions are: Standard Edition Enterprise Edition SQL Server is available in 32-bit and 64-bit editions. Please note limitations and recommendations for using SQL Server Express editions with ServerView Operations Manager (see "Installation options for SQL Server" on page 33). Installation under Windows 41

42 3.8 SQL Server 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 75 and "Setting up a service account" on page 42. For further information of setting up a service account see the section "Setting up a service account" on page 60 under "SQL Server 2008 (R2)" on page Installing SQL Server 2014 Express edition SQL Server 2014 Express is a free edition of SQL Server. You can download these editions from the Microsoft Download Center. More information on installing SQL Server 2014 Express is available from the Microsoft Download Center. It is recommended that you always use the latest service pack. Downloading the files from the Microsoft Download Center 1. Go to the Microsoft Download Center: 2. In the field Search Download Center enter Microsoft SQL Server 2014 Express and press Enter or click the Search button. You can sort the downloads by release date. 3. In the displayed list, click the link Microsoft SQL Server 2014 Express. 4. Under Change language, select the appropriate language version. 5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 6. The required packages are listed under Instructions: Download the packages and install them. 7. Optional: Installation of Microsoft SQL Server 2014 Management Studio Express. In Microsoft Download Center search for Microsoft SQL Server 2014 Management Studio and download it. Eventually check all installation requirements as specified by Microsoft. Installation 1. Log onto the system as administrator. 2. Execute the relevant *.exe file, e.g.: SQLEXPR_x64_ENU.exe SQLEXPR_x86_ENU.exe Installation under Windows 42

43 3.8 SQL Server 2014 The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2014 Express instance under the instance name SQLSERVERVIEW. 1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x Select Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, leave the option Database Engine Service selected, and deselect the options SQL Server replication and SQL Client Connectivity SDK. 5. In the Instance Configuration window, enter the instance name SQLSERVERVIEW under Named instance and Instance ID. 6. Specify the Windows user account under which you want SQL Server to run. Select a suitable account as described in "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service. 8. In the Database Engine Configuration window, click the Add Current User button. This action adds SQL Server administrator rights to the current Windows user account. You can start the Operations Manager installation under this account later. If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. 9. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts: In to execute an "Operations Manager installation without SQL Server "sysadmin" access", skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to step 11 here in this section. 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). 3. The Local system account. Otherwise you will receive the following error message in the SQL Server error logs: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ServerViewDB'. Installation under Windows 43

44 3.8 SQL Server 2014 Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2014 in section "Setting up a service account" on page 60 and for a remote SQL Server 2014 in section "Configuring a remote SQL Server" on page By default, the TCP/IP network protocol is not activated for SQL Server Express editions. This protocol is, however, necessary for the Operations Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the Operations Manager installation. Proceed as follows to activate the TCP/IP network protocol: 1. Start the SQL Server Configuration Manager. 2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance. 3. Set the TCP/IP protocol to enabled. You will need to restart the SQL Server service for this change to become effective Installing SQL Server 2014 Express Management Studio On Windows Server 2012/2016 proceed as follows: 1. Call Server Manager and add feature.net Framework 3.5 SP1. This will require the Windows Server 2012 or Windows Server 2016 installation media (folder \sources\sxs). 2. Start the SQLManagementStudio installation executable. 3. Click Installation on the left side of the wizard. 4. Select New installation or add features to an existing installation and click the OK button 5. Click New installation or add shared features in the Installation Type dialog. 6. Accept the License Term. 7. Let Management Tools Basic selected on the Feature Selection page.the remaining installation dialogs are self-explanatory Installing SQL Server 2014 Enterprise/Standard edition The packages Microsoft.NET Framework and Windows Power Shell will be installed automatically, if the management station is currently connected to the internet. Otherwise, you have to install the Microsoft.NET Framework and - optionally - the Windows PowerShell before installing the SQL Server. Installation under Windows 44

45 3.8 SQL Server 2014 On Windows Server 2012 and Windows Server 2016, PowerShell is already installed in versions 3.0 and 5.0 respectively. To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows: 1. Select Start Server Manager. 2. In the left window pane, select Features. 3. Select Add Features. 4. Select the option Windows PowerShell. 5. Click Next and then Install. Installation 1. Log onto the system as administrator. 2. Insert the installation medium (DVD). 3. Click the setup.exe file in the root directory. The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other. If the Microsoft.NET Framework is not yet installed: In the Welcome to Setup window, accept the license agreement. In the Setup Complete window, click Exit to start the update. After the automatic installation of the required packages, the SQL Server Installation Center starts. 1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x Select the entry Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, select the option Database Engine Service and Management Tools - Basic or Management Tools - Complete. 5. In the Server Configuration window, click the option Use the same account for all SQL Server services. If you are installing the SQL Server 2014 Edition on the same system as Operations Manager, enter a local Windows user account without administrator authorization and a password. In the case of a remote database, enter a domain user account without administrator authorization and a password, see "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser. 7. In the Database Engine Configuration window, click the Add Current User button. This Installation under Windows 45

46 3.8 SQL Server 2014 action adds SQL Server administrator right to the current Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step. Start later the Operations Manager installation under this account. In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. 8. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts: If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to "Installing service packs" on page 46 here in this section. 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon Information window for an upgrade installation. 3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). 4. If you are using a local SQL Server, the Local system account. Otherwise you will receive the following error message in the SQL Server error logs: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ServerViewDB'. Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2014 in section "Setting up a service account" on page 60 and for a remote SQL Server 2014 in section "Configuring a remote SQL Server" on page 68. Installing service packs Microsoft SQL Server 2014 may be used to upgrade any edition of SQL Server If your SQL Server system has Internet access, you can update via the Microsoft Update web page ( Click the Custom button to list the available updates. Installation under Windows 46

47 3.8 SQL Server 2014 Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance ( 1. In the field Search Download Center, enter SQL Server 2014 and press Enter or click the Search button. You can sort the downloads by release date. 2. In the displayed list, click the current Service Pack (SQL Server 2014 Service Pack 1) link. 3. Under Change language select the appropriate language version. 4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 5. Click DOWNLOAD to download the file. 6. In the window that opens, click Save and then select the storage location for the file. Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management Studio and the Add or Remove Programs window must be closed. 1. Start the installation. The installation is interactive and you can accept the default values. 2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window. 3. After the installation, the system is restarted. For setting up high availability you can configure an automatic restart for the ServerView services and SQL Server services. For further information see "ServerView services" on page 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 under Security Server Roles sysadmin and selection of Properties from 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. To view the valid logins, select Security Logins. Installation under Windows 47

48 3.8 SQL Server If the account is not present: 1. Select New Login from the context menu. 2. On the General page, enter the name of the Windows user under Login name or Name. You can keep the other settings. 3. Switch to the Server Roles tab. 4. Select sysadmin or System Administrators as the server role and click OK. 3. If the user account is already present: 1. Select Security Logins <login>. 2. Select Properties from the context menu. 3. Switch to the Server Roles tab and select the sysadmin checkbox. 4. Then click OK. Installation under Windows 48

49 3.9 SQL Server 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 Hardware and software requirements Hardware requirements For a detailed overview of the hardware requirements for installing SQL Server 2012, see and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2012" Software requirements Operating systems supported for SQL Server 2012: Windows Server 2016 Windows Server 2012 Windows Server 2008 R2 SP1 Windows Server 2008 SP2 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, see and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2012". Windows Installer as of version 4.5 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, see the website mentioned above. Installation under Windows 49

50 3.9 SQL Server 2012 Proceed as follows: In case of Windows Server 2008 SP2: Search in the Microsoft Download Center for Windows Power Shell 2.0 and download it. In case of Windows Server 2008 R2: Windows Power Shell 2.0 is part of the Windows Server 2008 R2 installation. (Select All Programs - Accessoires - Windows PowerShell.) In case of Windows Server 2012: Windows Power Shell 3.0 is part of the Windows Server 2012 installation. In case of Windows Server 2016: Windows Power Shell 5.0 is part of the Windows Server 2016 installation Editions You can use the following editions, among others, depending on your performance requirements and budget: 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: Standard Edition Enterprise Edition 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 75 and "SQL Server service accounts" on page Operations Manager service accounts When you install SQL Server 2012, you will see instructions in the Database Engine Configuration window 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 67. Installation under Windows 50

51 3.9 SQL Server 2012 Using a local SQL Server 2012 you must add the following Windows user accounts to SQL Server 2012: Account under which you will be logged on the system during the Operations Manager installation.this account must have Windows administrative rights. Account in the Operations Manager installation window Update Management Logon Information. This account must have Windows administrative rights. Usually you will add the Administrator account. The Local System Account (NT AUTHORITY\SYSTEM). Locally, ServerView Services will be installed to use this account SQL Server service accounts When you install SQL Server 2012, you must specify a service account in the Server Configuration window. It is advisable to set up one or more service accounts before the installation. You require service accounts for the following services: SQL Server Database Service SQL Server Agent (not for SQL Server Express) SQL Server Browser Bear in mind the following if you are installing SQL Server and Operations Manager on the same system: Do not use the Network Service account. The Operations Manager installation will be cancelled if SQL Server runs under the Network Service account. 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 the Password never expires option 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. There are, however, a few exceptions for using a local Windows user account: o 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. In fail cluster installations, local system and local service accounts are not allowed. Installation under Windows 51

52 3.9 SQL Server 2012 If you do not want to set up a local Windows user account, you can use a system account. Proceed as follows: o o Select Local System for the services SQL Server and SQL Server Agent. Select Local Service for the service SQL Server Browser. The local system account (Local System) is an integrated account with very high privileges. You should therefore use the system accounts with appropriate caution. 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 the Password never expires option 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 further information on service accounts, see the SQL Server 2012 Books Online Installing SQL Server 2012 Express edition SQL Server 2012 Express is a free edition of SQL Server. You can download these editions from the Microsoft Download Center. More information on installing SQL Server 2012 Express is available from the Microsoft Download Center. It is recommended that you always use the latest service pack. Downloading the files from the Microsoft Download Center 1. Go to the Microsoft Download Center: 2. In the field Search Download Center enter Microsoft SQL Server 2012 Express and press Enter or click the Search button. You can sort the downloads by release date. 3. In the displayed list, click the link Microsoft SQL Server 2012 Express Edition. 4. Under Change language, select the appropriate language version. 5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 6. The required packages are listed under Instructions: Download the packages and install them. Installation under Windows 52

53 3.9 SQL Server Optional: Installation of Microsoft SQL Server 2012 Management Studio Express: The SQL Management Studio is also available via the SQL Server 2012 Express download page, which contains multiple packages. You will be prompted to select the SQLManagementStudio package from the Details list. Download and install the package you need (x86 or x64). Windows Power Shell is a prerequisite for the Management Studio. On Windows Server 2012 and Windows Server 2016, PowerShell is already installed in versions 3.0 and 5.0 respectively. Installation 1. Log onto the system as administrator. 2. Execute the relevant *.exe file, e.g.: SQLEXPR_x64_ENU.exe SQLEXPR_x86_ENU.exe The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2012 Express instance under the instance name SQLSERVERVIEW. 1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x Select Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, leave the option Database Engine Service selected, and deselect the options SQL Server replication and SQL Client Connectivity SDK. 5. In the Instance Configuration window, enter the instance name SQLSERVERVIEW under Named instance and Instance ID. 6. Specify the Windows user account under which you want SQL Server to run. Select a suitable account as described in "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service. 8. In the Database Engine Configuration window, click the Add Current User button. This action adds SQL Server administrator rights to the current Windows user account. You can start the Operations Manager installation under this account later. If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. Installation under Windows 53

54 3.9 SQL Server In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts: In to execute an "Operations Manager installation without SQL Server "sysadmin" access", skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to step 11 here in this section. 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). 3. The Local system account. Otherwise you will receive the following error message in the SQL Server error logs: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ServerViewDB'. Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2012 in section "Setting up a service account" on page 60 and for a remote SQL Server 2012 in section "Configuring a remote SQL Server" on page By default, the TCP/IP network protocol is not activated for SQL Server Express editions. This protocol is, however, necessary for the Operations Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the Operations Manager installation. Proceed as follows to activate the TCP/IP network protocol: 1. Start the SQL Server Configuration Manager. 2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance. 3. Set the TCP/IP protocol to enabled. You will need to restart the SQL Server service for this change to become effective Installing SQL Server 2012 Express Management Studio On Windows Server 2012/2016 proceed as follows: 1. Call Server Manager and add feature.net Framework 3.5 SP1. This will require the Windows Server 2012 or Windows Server 2016 installation media (folder \sources\sxs). Installation under Windows 54

55 3.9 SQL Server Start the SQLManagementStudio installation executable. 3. Click Installation on the left side of the wizard. 4. Select New installation or add features to an existing installation and click the OK button 5. Click New installation or add shared features in the Installation Type dialog. 6. Accept the License Term. 7. Let Management Tools Basic selected on the Feature Selection page.the remaining installation dialogs are self-explanatory Installing SQL Server 2012 Enterprise/Standard edition If the management station is currently connected to the internet, the packages Microsoft.NET Framework and Windows Power Shell will be installed automatically. Otherwise, you have to install the Microsoft.NET Framework and - optionally - the Windows PowerShell before installing the SQL Server. On Windows Server 2012 and Windows Server 2016, PowerShell is already installed in versions 3.0 and 5.0 respectively. To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows: 1. Select Start Server Manager. 2. In the left window pane, select Features. 3. Select Add Features. 4. Select the option Windows PowerShell. 5. Click Next and then Install. Installation 1. Log onto the system as administrator. 2. Insert the installation medium (DVD). 3. Click the setup.exe file in the root directory. The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other. If the Microsoft.NET Framework is not yet installed: In the Welcome to Setup window, accept the license agreement. In the Setup Complete window, click Exit to start the update. Installation under Windows 55

56 3.9 SQL Server 2012 After the automatic installation of the required packages, the SQL Server Installation Center starts. 1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x Select the entry Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, select the option Database Engine Service and Management Tools - Basic or Management Tools - Complete. 5. In the Server Configuration window, click the option Use the same account for all SQL Server services. If you are installing the SQL Server 2012 Edition on the same system as Operations Manager, enter a local Windows user account without administrator authorization and a password. In the case of a remote database, enter a domain user account without administrator authorization and a password, see "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser. 7. In the Database Engine Configuration window, click the Add Current User button. This action adds SQL Server administrator right to the current Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step. Start later the Operations Manager installation under this account. In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. 8. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts: If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to "Installing service packs" on page 57 here in this section 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon Information window for an upgrade installation. 3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). Installation under Windows 56

57 3.9 SQL Server If you are using a local SQL Server, the Local system account. Otherwise you will receive the following error message in the SQL Server error logs: Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ServerViewDB'. Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2012 in section "Setting up a service account" on page 60 and for a remote SQL Server 2012 in section "Configuring a remote SQL Server" on page 68. Installing service packs Microsoft SQL Server 2012 may be used to upgrade any edition of SQL Server If your SQL Server system has Internet access, you can update via the Microsoft Update web page ( Click the Custom button to list the available updates. Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance ( 1. In the field Search Download Center, enter SQL Server 2012 and press Enter or click the Search button. You can sort the downloads by release date. 2. In the displayed list, click the current Service Pack (SQL Server 2012 Service Pack 1) link. 3. Under Change language select the appropriate language version. 4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 5. Click DOWNLOAD to download the file. 6. In the window that opens, click Save and then select the storage location for the file. Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management Studio and the Add or Remove Programs window must be closed. 1. Start the installation. The installation is interactive and you can accept the default values. 2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window. 3. After the installation, the system is restarted. For setting up high availability you can configure an automatic restart for the ServerView services and SQL Server services. For further information see "ServerView services" on page 125. Installation under Windows 57

58 3.10 SQL Server 2008 (R2) 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 under Security Server Roles sysadmin and selection of Properties from 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. To view the valid logins, select Security Logins. 2. If the account is not present: 1. Select New Login from the context menu. 2. On the General page, enter the name of the Windows user under Login name or Name. You can keep the other settings. 3. Switch to the Server Roles tab. 4. Select sysadmin or System Administrators as the server role and click OK. 3. If the user account is already present: 1. Select Security Logins <login>. 2. Select Properties from the context menu. 3. Switch to the Server Roles tab and select the sysadmin checkbox. 4. Then click OK SQL Server 2008 (R2) As of Operations Manager version 5.10, you can install the ServerView database into an SQL Server 2008 R2 instance. The description for SQL Server 2008 also applies to SQL Server 2008 R2 in this manual. As of Operations Manager version 4.90, you can install the ServerView database into an SQL Server 2008 instance. SQL Server 2008 R2 Express must be installed before Operations Manager. Installation under Windows 58

59 3.10 SQL Server 2008 (R2) Software requirements Operating system for SQL Server 2008 R2: Windows Server 2016 Windows Server 2012 Windows Server 2008 and R2 Operating system for SQL Server 2008: Windows Server 2016 Windows Server 2012 Windows Server 2008 and R2 Microsoft.NET Framework 3.5 SP 1 or.net Framework 4.0 Windows Installer 4.5 or later version Optional: Windows PowerShell 1.0 if you want to install SQL Server 2008 (R2) Management Tools, a program for database administration Editions You can use the following editions, among others, depending on your performance requirements and budget: Express Edition Successor to SQL Server 2005 Express, SQL Server 2008 Express is free and available from the Microsoft Download Center. The database size limit is 10 GB for SQL Server 2008 R2 Express, 4 GB for SQL Server 2008 Express, and 4 GB for SQL Server 2005 Express. The newer edition can store more data than the older one. The full versions are: Workgroup Edition Standard Edition Enterprise Edition Installation under Windows 59

60 3.10 SQL Server 2008 (R2) Setting up a service account Operations Manager service accounts If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", see "Overview of Windows accounts and access rights" on page 75 and "SQL Server service accounts" on page 60. When you install SQL Server 2008, you will see instructions in the Database Engine Configuration window on how to add Windows user accounts which will later be used as the 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 the Operations Manager installation. Follow the instructions in "Adding a user account with SQL Server administrator rights" on page 67. Using a local SQL Server 2008 you must add two Windows user accounts to SQL Server 2008: Account under which you will be logged on the system during the Operations Manager installation. This account must have Windows administrative rights. Account in the Operations Manager installation window Update Management Logon Information. This account must have Windows administrative rights. Usually you will add the Administrator account SQL Server service accounts When you install SQL Server 2008, you must specify a service account in the Server Configuration window. It is advisable to set up one or more service accounts before the installation. You require service accounts for the following services: SQL Server Database Service SQL Server Agent (not for SQL Server Express) SQL Server Browser Bear in mind the following if you are installing SQL Server and Operations Manager on the same system: Do not use the Network Service account. The Operations Manager installation will be canceled if SQL Server runs under the Network Service account. Installation under Windows 60

61 3.10 SQL Server 2008 (R2) 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 the Password never expires option 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. There are, however, a few exceptions for using a local Windows user account: o 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. In fail cluster installations, local system and local service accounts are not allowed. If you do not want to set up a local Windows user account, you can use a system account. Proceed as follows: o o Select Local System for the services SQL Server and SQL Server Agent. Select Local Service for the service SQL Server Browser. The local system account (Local System) is an integrated account with very high privileges. You should therefore use the system accounts with appropriate caution. 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 the Password never expires option 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 2008 installation you can still assign service accounts later with the SQL Server Configuration Manager. For further information on service accounts, see the SQL Server 2008 Books Online Installing SQL Server 2008 (R2) Express edition SQL Server 2008 R2 Express and SQL Server 2008 Express are free versions of SQL Server. You can download these editions from the Microsoft Download Center. More information on installing SQL Server 2008 Express is available from the Microsoft Download Center. It is recommended that you always use the latest service pack. Installation under Windows 61

62 3.10 SQL Server 2008 (R2) Downloading the files from the Microsoft Download Center 1. Go to the Microsoft Download Center: 2. In the field Search Download Center enter Microsoft SQL Server 2008 R2 Express or enter Microsoft SQL Server 2008 Express and press Enter or click the Search button. You can sort the downloads by release date. 3. In the displayed list, click the link Microsoft SQL Server 2008 R2 SP2 - Express Edition or Microsoft SQL Server 2008 SP3 Express Edition. 4. Under Change language, select the appropriate language version. 5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 6. The required packages are listed under Instructions: Download the packages and install them. 7. Optional: In Microsoft Download Center search for Microsoft SQL Server 2008 Management Studio Express and install it if you want to install a program for database administration. Windows Power Shell 1.0 is a prerequisite for the Management Studio. On Windows Server 2012 and 2016, the appropriate PowerShell version is already installed. To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows: 1. Select Start Server Manager. 2. In the left window pane, select Features. 3. Select Add Features. 4. Select the option Windows PowerShell. 5. Click Next and then Install. Installation 1. Log onto the system as administrator. 2. Execute the relevant *.exe file, e.g.: SQLEXPR_x64_ENU.exe SQLEXPR_x86_ENU.exe The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2008 Express instance under the instance name SQLSERVERVIEW. 1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x64. Installation under Windows 62

63 3.10 SQL Server 2008 (R2) 2. Select Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, select the option Database Engine Service and Management Tools - Basic. 5. In the Instance Configuration window, enter the instance name SQLSERVERVIEW under Named instance. 6. In the Server Configuration window, click the option Use the same account for all SQL Server services. 7. Specify the Windows user account under which you want SQL Server to run. Select a suitable account as described in "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service. 9. In the Database Engine Configuration window, click the Add Current User button. This action adds SQL Server administrator rights to the current Windows user account. You can start the Operations Manager installation under this account later. If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. 10. In the Database Engine Configuration window, click the Add button. Add SQL Server administrator right to the following Windows user accounts: If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access", skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to step 11 here in this section. 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon Information window for an upgrade installation. 3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2008 in section "Setting up a service account" on page 60 and for a remote SQL Server 2008 in section "Configuring a remote SQL Server" on page By default, the TCP/IP network protocol is not activated for SQL Server Express editions. Installation under Windows 63

64 3.10 SQL Server 2008 (R2) This protocol is, however, necessary for the Operations Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the Operations Manager installation. Proceed as follows to activate the TCP/IP network protocol: 1. Start the SQL Server Configuration Manager. 2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance. 3. Set the TCP/IP protocol to enabled. You will need to restart the SQL Server service for this change to become effective Installing SQL Server 2008 R2 Express Management Studio On Windows Server 2012/2016 proceed as follows: 1. Call Server Manager and add feature.net Framework 3.5. This will require the Windows Server 2012 or Windows Server 2016 installation media (folder \sources\sxs). 2. Start the SQLManagementStudio installation executable. 3. Click Installation on the left side of the wizard. 4. Select New installation or add features to an existing installation and click the OK button. 5. Click New installation or add shared features in the Installation Type dialog. 6. Accept the License Term. 7. Let Management Tools Basic selected on the Feature Selection page.the remaining installation dialogs are self-explanatory Installing SQL Server 2008 (R2) Enterprise/Standard/Workgroup edition In the manual the description for SQL Server 2008 also applies to SQL Server 2008 R2. The packages Microsoft.NET Framework are automatically installed when you install the SQL Server 2008 Enterprise/Standard/Workgroup Edition. On Windows Server 2012 and 2016, the appropriate PowerShell version is already installed. To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows: Installation under Windows 64

65 3.10 SQL Server 2008 (R2) 1. Select Start Server Manager. 2. In the left window pane, select Features. 3. Select Add Features. 4. Select the option Windows PowerShell. 5. Click Next and then Install. Installation 1. Log onto the system as administrator. 2. Insert the installation medium (DVD). 3. Click the setup.exe file in the root directory. The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other. If the Microsoft.NET Framework is not yet installed: In the Welcome to Setup window, accept the license agreement. In the Setup Complete window, click Exit to start the update. After the automatic installation of the required packages, the SQL Server Installation Center starts. 1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x Select the entry Installation. 3. Select the entry New SQL Server stand-alone installation or add features to an existing installation. 4. In the Feature Selection window, select the option Database Engine Service and Management Tools - Basic or Management Tools - Complete. 5. In the Server Configuration window, click the option Use the same account for all SQL Server services. If you are installing the SQL Server 2008 Edition on the same system as Operations Manager, enter a local Windows user account without administrator authorization and a password. In the case of a remote database, enter a domain user account without administrator authorization and a password, see "Setting up a service account" on page In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser. 7. In the Database Engine Configuration window, click the Add Current User button. This action adds SQL Server administrator right to the current Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step. Start later the Operations Manager installation under this account. Installation under Windows 65

66 3.10 SQL Server 2008 (R2) In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server. 8. In the Database Engine Configuration window, click the Add button. Add SQL Server administrator right to the following Windows user accounts: If you want to execute an "Operations Manager installation without SQL Server "sysadmin" access, skip this step, follow the instructions as described in "Overview of Windows accounts and access rights" on page 75, and then return to "Installing service packs" on page 66 here in this section. 1. The user account in the Operations Manager installation dialog Update Management Logon Information. 2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon Information window for an upgrade installation. 3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set). Do not add the account of dialog Tomcat Service Logon Information. This account will be granted permission during Operations Manager installation automatically. You find the details for the required users for a local SQL Server 2008 in section "Setting up a service account" on page 60 and for a remote SQL Server 2008 in section "Configuring a remote SQL Server" on page 68. Installing service packs Microsoft SQL Server 2008 Service Pack 3 (SP3) respectively Microsoft SQL Server 2008 R2 Service Pack 1 may be used to upgrade any edition of SQL Server If your SQL Server system has Internet access, you can update via the Microsoft Update web page ( Click the Custom button to list the available updates. Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance ( 1. In the field Search Download Center, enter SQL Server 2008 and press Enter or click the Search button. You can sort the downloads by release date. 2. In the displayed list, click the Microsoft SQL Server 2008 Service Pack 3 respectively Microsoft SQL Server 2008 R2 Service Pack 2 link. 3. Under Change language select the appropriate language version. 4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. 5. Click DOWNLOAD to download the file. 6. In the window that opens, click Save and then select the storage location for the file. Installation under Windows 66

67 3.10 SQL Server 2008 (R2) Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management Studio and the Add or Remove Programs window must be closed. 1. Start the installation. The installation is interactive and you can accept the default values. 2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window. 3. After the installation, the system is restarted. For setting up high availability you can configure an automatic restart for the ServerView services and SQL Server services. For further information see "ServerView services" on page 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 under Security Server Roles sysadmin and selection of Properties from 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. To view the valid logins, select Security Logins. 2. If the account is not present: 1. Select New Login from the context menu. 2. On the General page, enter the name of the Windows user under Login name or Name. You can keep the other settings. 3. Switch to the Server Roles tab. 4. Select sysadmin or System Administrators as the server role and click OK. 3. If the user account is already present: 1. Select Security Logins <login>. 2. Select Properties from the context menu. 3. Switch to the Server Roles tab and select the sysadmin checkbox. 4. Then click OK. Installation under Windows 67

68 3.11 Configuring a remote SQL Server 3.11 Configuring a remote SQL Server To configure a remote SQL Server, proceed as follows: 1. Login as the local administrator. 2. The following services for the SQL Server instance must be started on the remote system: SQL Server SQL ServerAgent SQL Server Browser The services SQL Server and SQL Server Agent should run under a domain user account. For security reasons this account should not be a member of Windows group Administrators. Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option 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. This domain user account must belong to the same domain where the remote system is connected to. If both systems are connected to the same domain, the services can also run under the service account Local System. This account has high privileges and is not recommendable for security reasons. The SQL Server Browser service runs under service account Local Service by default. Use a database administration tool to change the startup account for SQL Server. This ensures to automatically assign all the required permissions and Windows user rights to the new startup account for you. Use SQL Server Configuration Manager: 1. Click on SQL Server <version> Services. 2. Stop the services for changing the account. 3. Change via the context menu entry Properties the service account. 4. Start the services. The SQL Server is restarted automatically. 3. Accesses to the remote SQL Server are authenticated via the Windows domain user accounts of the Operations Manager services. Installation under Windows 68

69 3.11 Configuring a remote SQL Server If you want to do an "Operations Manager installation without SQL Server "sysadmin" access" skip the current step. See "Overview of Windows accounts and access rights" on page 75 and then return to the next step 4. Therefore, for the domain user account under which you will be logged on to the system during the Operations Manager installation, in the Operations Manager installation window Remote DB (for a new installation) or ServerView Service Logon Information for an upgrade installation in the Operations Manager installation window Update Management Logon Information, you must bear in mind the following: The domain user accounts must belong to the same domain as the server on which Operations Manager is installed. The domain user accounts must be created in SQL Server as Login using the SQL Server administration tools. These logins must also be assigned a certain server role. This role include the authorization necessary for installing and running the application. To set up a user account, proceed as follows: 1. Log in as the administrator on the remote system. 2. Start the program SQL Server Management Studio for database administration. 3. Select the SQL Server instance or connect to it. 4. Select Security Logins. 5. Select New Login from the context menu. The Login - New window opens. 6. Enter the name for the domain user account under Login name or Name. You can keep the other settings. 7. Switch to the Server Roles tab. 8. Select sysadmin or System Administrators as the server role. 9. Click OK. 4. Remote access (via TCP/IP) to the corresponding SQL Server instance must be activated as follows. 1. Open the SQL Server Configuration Manager by selecting Start All Programs Microsoft SQL Server <version> Configuration Tools SQL Server Configuration Manager. 2. Select SQL Server <version> Network Configuration. 3. Click Protocols for <instance>. A list of protocols and their status is displayed. 4. Check the setting Protocol for <instance>. Installation under Windows 69

70 3.11 Configuring a remote SQL Server 5. The status for the TCP/IP protocol must be Enabled. 6. If not, activate TCP/IP for the instance. 5. For remote access to the SQL Server instance, a static port is required. Either use an unnamed SQL Server instance or configure a static port for a named instance. To check the port configuration of a named instance, proceed as follows: 1. Open the Registration Editor. 2. Search for the following entries: For an SQL Server 2014 instance: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.<Instance Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll For an SQL Server 2012 instance: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.<Instance Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll For an SQL Server 2008 R2 instance: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_ 50.<Instance Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll For an SQL Server 2008 instance: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll As of SQL Server 2008, the internal version number (10, 10_50, 11) suffixed with the instance name is used: MYSQL<internal version number>.<instance Name>. 3. Check the values for TCPDynamicPorts and TCPPort. If the value for TCPDynamicPorts is not set, SQL Server always uses a static port. You will see the port number under TCPPort. If a static port was configured previously, the SQL Server instance must be restarted for the changes to the port configuration to take effect. The static port for a named instance can be assigned via SQL Server Configuration Manager. The procedure is described in SQL Server Books Online "Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)". 6. Make sure that the port is not blocked by any firewall settings. If necessary, allow via firewall administration program the following port for the SQL Server instance: Add for program SQL Server and protocol TCP either the default port number 1433 or the port number given under TCPPort in the Registration Editor. Installation under Windows 70

71 3.11 Configuring a remote SQL Server Add for program SQL Server and protocol UDP port number When installing SQL Server in another, but trusted domain, the SQL Server must be accessible via netbios name. You can do this by expanding the DNS Suffix Search List. 1. Log on to the SQL Server machine. 2. Look at the current DNS Suffix Search List. Open a command prompt window and type ipconfig /all. 3. In the Windows IP Configuration entry you will find the DNS Suffix search list. The suffix of the domain to which the central management station is connected must be listed. 4. If not, you can change it e.g. by configuring Append these DNS suffixes: 1. Select Control Panel Network and Sharing Center. 2. Click Properties and click Internet Protocol Version. 3. Click Properties and click Advanced for the DNS server address. 4. In the DNS tab, select the option Append these DNS suffixes (in order) and click Add. 5. Insert the TCP/IP Domain Suffix of the domain to which the central management station is connected to. Further procedure on the management station If you followed all instructions in "Operations Manager installation without SQL Server "sysadmin" access" skip the following steps 1 to 3 and go on with step Log on as local administrator. 2. Add the domain user account under which you want to perform the Operations Manager installation and all further domain user accounts which you specify for services during the installation, as for example in the Remote DB window, ServerView Service Logon window and in the Update Management Logon Information window to the Administrators group. 3. Log on under this domain user account. 4. Start the ServerView Operations Manager installation and select in the Select SQL Server window the Use existing remote SQL Server option, "Menu-driven installation of Operations Manager software" on page On a new installation enter in the Remote DB window the corresponding values, "Remote DB window" on page 106. The local service ServerView Services will run under this account and will have access to the remote SQL Server via the SQL Server Login you created above. 6. In the other Logon Information windows enter the same domain user account or a further domain user account for which you have created a SQL Server Login. Installation under Windows 71

72 3.11 Configuring a remote SQL Server 7. In the other windows fill in as described in section "Menu-driven installation of Operations Manager software" on page 103. If you want to change the service account of SQL Server and SQL Server Agent after the ServerView Operations Manager installation you must additionally give on remote system write admission to the SQL Server backup folder DbBackupPath from %windir%\serverviewdb.ini file and to the files below. Upgrade installation When you installed ServerView Operations Manager, you specified a user name and password for the ServerView services in the Remote DB window. In an upgrade installation you must enter the password in the ServerView Service Logon information dialog again because it is not saved Troubleshooting for Remote SQL Server This section describes examples of error messages which appear if the remote SQL Server was not configured correctly. Under Troubleshooting you will find a short description of the cause of the error. For the configuration details please search for the underlined terms in "Configuring a remote SQL Server" on page 68 if no other section is specified Messages after clicking Next in the Remote DB dialog Message "Error: Unable to connect to SQL Server. Connection attempt rejected [ ] SQL Server does not exist or access denied." Troubleshooting 1. Enter the correct SQL Server name in the Remote DB dialog. You can display existing SQL Server instances and see the correct SQL Server names by entering at the command prompt: sqlcmd -L 2. Make sure that the port is not blocked by any firewall settings. You can test the connection by entering at the command prompt: sqlcmd -S <SQL Server instance> -E The message "Unable to complete login process due to delay in opening server connection" indicates blocking by a firewall. Installation under Windows 72

73 3.11 Configuring a remote SQL Server Message "Error: Unable to connect to SQL Server. Connection attempt rejected [ ] Login failed for user ' '. Reason: Not associated with a trusted SQL Server connection" Troubleshooting Please check for a two-way trust relationship via Administrative Tools Active Directory Domain and Trusts. Message "Error: Given user name does not exist in SQL Server. Check user name and SQL Server logins. Troubleshooting Create the domain user account in the SQL Server as Login. Message "The specified remote database could not be validated. Please check the server name and user account parameters. Error: New installation, but ServerViewDB already exists in SQL Server database." Troubleshooting See "Remotely on a different system" on page Messages after the Ready to Install the Application dialog during execution of SQL Script ExecDefRecBcp.sql Message 1. "String or binary data would be truncated." 2. "Conversion failed when converting the value ' ' to data type " Troubleshooting 1. Start the SQL Server services SQL Server and SQL Server Agent under a domain user account that should not be a member of the Windows group Administrators. 2. Make sure that the domain user account under which you are performing the Operations Manager installation still exists. 3. Check if the central management station and remote SQL Server computer are in different domains, see Control Panel System entry Domain. If they are in different domains, please check for a two-way trust relationship via Installation under Windows 73

74 3.12 Operations Manager installation without SQL Server "sysadmin" access Administrative Tools Active Directory Domain and Trusts. 4. The SQL Server must be accessible via netbios name Messages after the Click Install to begin installation dialog during execution of SQL Script ServerConfig.sql or SVSQLDbCreation.sql Message " permission denied in database " " permission denied on object " Troubleshooting Assign the SQL Server administrator right sysadmin or System Administrators to the domain user accounts under which you want to perform the Operations Manager installation and which you are specifying for services Messages after the Click Install to begin installation dialog during execution of GrantLoginJBoss.sql Message [ ] Windows NT user or group ' not found. Check the name again." Troubleshooting You must insert a domain user in the Tomcat Service Logon Information window, see "Menu-driven installation of Operations Manager software" on page Operations Manager installation without SQL Server "sysadmin" access The default installation of Operations Manager requires system administrator permission in the SQL Server (the sysadmin server role) for the installing account and the accounts used for ServerView Services and ServerView Download Services. The SQL Server sysadmin permission is considered critical by customers in security-sensitive environments, especially when using remote SQL Servers and SQL Server Clusters. An alternative since ServerView Operations Manager V6.20 is to configure the SQL Server without SQL Server administration rights for the accounts - so-called enhanced security. When you then start the Operations Manager installation the enhanced security settings in SQL Server are detected. You will need to configure the SQL Server before you execute a new or upgrade installation of Operations Manager. Installation under Windows 74

75 3.12 Operations Manager installation without SQL Server "sysadmin" access IMPORTANT: The configuration for enhanced security settings (without sysadmin ) requires good knowledge and experience of SQL Server administration. It is therefore only recommended for customers with enhanced security requirements especially using a remote SQL Server. The default installation method with sysadmin user access uses default settings and is easier to handle for users without SQL Server administration knowledge. It therefore remains the normal installation method. This section explains the configuration of accounts for SQL Server with enhanced security. For the default installation with sysadmin access, see the corresponding chapters in this installation guide Overview of Windows accounts and access rights 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: 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. 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 o For a local SQL Server: Always the Local System account. For a remote SQL Server: During setup, specified in the window Remote DB (for a new installation) or ServerView Service Logon Information (for an upgrade installation). The account cannot be changed in upgrade or modify installations. Installation under Windows 75

76 3.12 Operations Manager installation without SQL Server "sysadmin" access 3. ServerView Application Server account. Windows account used to start the ServerView Application Server service. During setup, specified in the window Tomcat Service Logon Information. 4. ServerView Download Service account. The account used to start the ServerView Download Service. During setup, specified in the window Update 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 Tomcat 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 Tomcat 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 60. 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) as Installation under Windows 76

77 3.12 Operations Manager installation without SQL Server "sysadmin" access SQL Server Login for Windows authentication before 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 1 dbcreator optional: diskadmin Database Role Recommended in database msdb for full versions of SQL Server: db_backupoperator (or db_owner) SQLAgentReaderRole SQLAgentUserRole Optional in database master for all SQL Server editions: db_ backupoperator (or db_owner) The dbcreator server 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 two SQLAgent roles 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. The diskadmin server 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 Installation under Windows 77

78 3.12 Operations Manager installation without SQL Server "sysadmin" access 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. The db_backupoperator database role for the system database msdb is highly recommended for the full versions of SQL Server. The db_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. The db_owner role comprises the permission to back up, but is the role with the highest privilege. It has permission to perform any task on the database Configuration steps Note down in the following table the accounts you want to use in the Operations Manager setup: No. Account Window (title) Account 1 Installation Account - 2 ServerView Services For remote SQL Server: Remote DB or ServerView Service Logon Information 3 ServerView Application Server 4 ServerView Download Service For local SQL Server: no window Tomcat Service Logon Information Update Management Logon Information Tasks to be performed by the Windows Administrator on the CMS 1. Log on as a user with administrator rights on the central management station. 2. Add the accounts to the Windows Administrator group: For a local SQL Server: Add the accounts (1) and (4) to the Windows Administrator group. For a remote SQL Server: Add the domain accounts used for the accounts (1), (2) and (4) to the Windows Administrator group. Installation under Windows 78

79 3.12 Operations Manager installation without SQL Server "sysadmin" access Select the SQL Server Decide whether to use a remote or local SQL Server. o o IMPORTANT: A remote SQL Server is recommended. Valid editions for a remote SQL Server: SQL Server Standard, Enterprise and Workgroup (where available). Valid editions for a local SQL Server: SQL Server Express, SQL Server Standard, Enterprise, Workgroup (where available), see "Installation options for SQL Server" on page 33. If you do not have an SQL Server already installed, install it as described in one of the previous SQL Server 20xx sections. Install a full version of SQL Server with the Management Tools feature. For an SQL Server Express edition install the SQL Server Management Studio. In the case of a remote SQL Server, now follow: o Section "Remotely on a different system" on page 37 o Section "Configuring a remote SQL Server" on page 68, steps 1 and 2. Instead of step 3, follow the next sections below Tasks to be performed by the SQL Server Administrator Add the accounts (1) to (4) with SQL Server Management Studio as follows: 1. Start the SQL Server Management Studio by selecting Run as Administrator from the context menu. 2. Connect to the server instance as SQL Server Administrator under an account which holds the sysadmin server role in SQL Server. IMPORTANT: The sysadmin server role is always required for the SQL Server Administrator account to administer the SQL Server. DO NOT revoke the sysadmin right from all logins in SQL Server. At least one account must hold the sysadmin server role in the SQL Server. Installation under Windows 79

80 3.12 Operations Manager installation without SQL Server "sysadmin" access Check if the account to be added is already present in the list of valid SQL Server logins and add if necessary: 1. To view the valid logins, select Security Logins. 2. If the account is not present, create a new login: 1. Select New Login from the context menu. 2. On the General page, select Windows Authentication. Enter the name of the Windows user under Login name or Name. You can keep the other settings. 3. Then click OK. Do the steps 1. to 3. for the accounts (1) to (4). IMPORTANT: If the account is already present, revoke the sysadmin right for accounts (1) to (4): 1. Start SQL Server Management Studio as described above. 2. Select Security Logins. 3. Select the entry for the accounts (1) to (4). 4. Select Properties from the context menu. 5. Switch to the Server Roles page. 6. Uncheck the sysadmin option. Add the installation account to the server role dbcreator : 1. Start SQL Server Management Studio as described above. 2. Select Security Logins. 3. Select the entry for the installation account (1). 4. Select Properties from the context menu. 5. Switch to the Server Roles page. 6. Select the dbcreator checkbox and optionally diskadmin. 7. Click OK. Add the installation account to the database roles in the msdb database for full versions of SQL Server: 1. Start SQL Server Management Studio as described above. 2. Select Security Logins. 3. Select the entry for the installation account (1). 4. Select Properties from the context menu. 5. Switch to the User Mapping page. 6. Select the Map checkbox for the msdb database. Installation under Windows 80

81 3.12 Operations Manager installation without SQL Server "sysadmin" access 7. Select the row for the msdb database. 8. Select the following checkboxes for Database role membership: for msdb: o o o db_backupoperator (or db_owner) (not for Express editions) SQLAgentUserRole (not for Express editions) SQLAgentReaderRole (not for Express editions) Optionally add the installation account to the database roles in the master database: 1. Start SQL Server Management Studio as described above. 2. Select Security Logins. 3. Select the entry for the installation account (1). 4. Select Properties from the context menu. 5. Switch to the User Mapping page. 6. Select the Map checkbox for the master database. 7. Select the row for the master database. 8. Select the following checkboxes for Database role membership: for master. o Additional task db_backupoperator (or db_owner) For a local SQL Server, ServerView Operations Manager always uses the Local System account for ServerView Services operation. Check whether this account has a valid SQL Server Login for Windows authentication in SQL Server: 1. Log in to SQL Server Management Studio under an account holding the sysadmin role in SQL Server. 2. Select Security Logins. 3. Can you see the following? NT AUTHORITY\SYSTEM on a English operating system NT AUTORITÄT\SYSTEM on a German operating system AUTORITE NT\SYSTEM on a French operating system If the login is not present, add it with New Login from the context menu Further configuration steps for a remote SQL Server IMPORTANT: Now return to section "Configuring a remote SQL Server" on page 68 and continue with step 4 Remote access (via TCP/IP) to the corresponding SQL Server instance must be activated. Complete the rest of the remote SQL Server configuration. Installation under Windows 81

82 3.13 Upgrade installations of SQL Server Further procedure on the management station 1. Log on to the central management station as the installation account (1). 2. Proceed with the installation as described in section "Menu-driven installation of Operations Manager software" on page 103 and add the accounts in the corresponding installation windows as specified in the previous section Configuration steps. 3. After the installation you will see the following entries in the file %windir%\serverviewdb.ini: [Accounts] InstallationAccount=Domain\User SqlServerViewServicesAccount=Domain\User SqlServerViewDownloadServiceAccount=Domain\User SqlServerWithEnhancedSecurity=yes The entry SqlServerWithEnhancedSecurity must be set to yes Upgrade installations of SQL Server Upgrading to later SQL Server versions An installed ServerView database from an existing instance of SQL Server can be upgraded to a later version of SQL Server. Operations Manager as of version 4.90 supports an upgrade from SQL Server 2005/SQL Server 2005 Express to SQL Server 2008 edition. Operations Manager as of version 5.10 supports an upgrade from SQL Server 2005/SQL Server 2005 Express to SQL Server 2008/2008 R2 edition. The description for SQL Server 2008 is also valid for SQL Server 2008 R2 in this manual. Operations Manager as of version 6.30 supports an upgrade to SQL Server 2012 version from the following SQL Server versions: o o o SQL Server 2005/SQL Server 2005 Express SQL Server 2008/SQL Server 2008 Express SQL Server 2008 R2 /SQL Server 2008 R2 Express Installation under Windows 82

83 3.13 Upgrade installations of SQL Server Operations Manager as of version 7.10 supports an upgrade to SQL Server 2014 version from the following SQL Server versions: o o o o SQL Server 2005/SQL Server 2005 Express SQL Server 2008/SQL Server 2008 Express SQL Server 2008 R2 /SQL Server 2008 R2 Express SQL Server 2012/SQL Server 2012 Express You have two upgrade options: 1. Upgrade the complete SQL Server instance to a later version of SQL Server, see "Upgrading the SQL Server instance" on page Move only the ServerView database from the existing SQL Server instance into an SQL Server instance of a later version, see "Moving the ServerView database" on page 88. Once you have upgraded the SQL Server instance or moved the ServerView database, further migration steps are necessary in order to update or set up internal backup and administration jobs for Operations Manager. For this purpose, the installation provides a batch file, which you must execute after upgrading the instance or moving the database. Please observe the permissions in Microsoft SQL Server needed for upgrades. Several upgrade steps require membership of the "sysadmin" server role of MS SQL Server. It is therefore recommended to perform the process as a member of the "sysadmin" server role. If the SQL server is not installed on the central management station but remotely on another server (see "Remotely on a different system" on page 37), you must check or ensure the following: Installation of SQL Server client tools To access the remote SQL Server 2005/2008/2012, you will need the relevant SQL Server client tools (Microsoft SQL Server Native Client) on the local management station. Check whether these tools are installed: For SQL Server 2005: Microsoft SQL Server Native Client For SQL Server 2008: Microsoft SQL Server 2008 Native Client For SQL Server 2008 R2: Microsoft SQL Server 2008 R2 Native Client For SQL Server 2012: Microsoft SQL Server 2012 Native Client For SQL Server 2014: Microsoft SQL Server 2012 Native Client If the tool is not installed, you must install it on the local management station after completing the SQL Server upgrade and before executing the provided batch files. SQL Server client tools are available from the Microsoft Download Center. Installation under Windows 83

84 3.13 Upgrade installations of SQL Server Upgrading the SQL Server instance This upgrade method is also called an in-place upgrade and is offered as an installation option by the SQL Server setup. The upgrade is performed when you execute the SQL Server setup and select the appropriate option offered there. During the SQL Server upgrade, all databases installed in this instance - i.e. also the ServerView database - are automatically upgraded. Operations Manager remains installed on the system. Only while the upgrade is being performed must accesses to Operations Manager be temporarily stopped. An in-place upgrade requires the following: An installed instance of SQL Server in a particular edition can only be upgraded to a corresponding compatible edition of SQL Server. An SQL Server 2005 Express instance can, for example, be upgraded to an SQL Server 2008 Express instance, but not directly to an SQL Server 2008 Standard or Enterprise Edition. You cannot perform an in-place upgrade from an installed 32-bit edition of SQL Server to a 64-bit edition of SQL Server. Language dependencies must also be taken into account: During an in-place upgrade it is not possible to upgrade a localized version of SQL Server (for example, the German version) to a different-language version of SQL Server. For an in-place upgrade, therefore, you must install the new SQL Server instance in the same language version as the old instance. Only an English version of SQL Server can be upgraded to a localized version in a different language. The installation requirements are also checked by the SQL Server setup process itself, with messages or warnings being output if necessary. If the existing SQL Server instance was installed by Operations Manager, the installation language is English or Japanese. You can also check the product version, installation language and edition of the installed SQL Server instance beforehand as follows: 1. Find out the contents of the Server_Instance parameter in the configuration file ServerViewDB.ini. The configuration file is located in the <windir> directory. 2. Open the input prompt. 3. Enter the following commands: osql -S <server_instance> -E xp_msver GO GO Installation under Windows 84

85 3.13 Upgrade installations of SQL Server You will find the necessary information on the version and language in the command output under 2 ProductVersion and 3 gives you the edition. You quit osql with the quit command. Preparing for installation While the SQL Server instance is being upgraded, the setup checks the necessary hardware and software requirements. You can find out these requirements in advance from the web pages of the Microsoft Download Center for the SQL Server version required or from the SQL Server online documentation available on the Internet. To install an SQL Server Express Edition, you may have to download the required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components and install them when you start the setup. You should also find out from the relevant SQL Server online documentation which version and edition upgrades from SQL Server to later SQL Server editions Microsoft supports in the setup. Find out the type (default instance or named instance) and name of the installed SQL Server instance. You have to specify the instance name and type while executing the SQL Server installation, so that the SQL Server setup upgrades the correct SQL Server instance. You will find this information in the configuration file ServerViewDB.ini (in the <windir> directory) in the Server_Instance and Instance parameters: o o If there is no Instance parameter, the instance is a default one. Under Server_ Instance, only the server name (usually (local)) is given. For a named instance, the instance name is given under Instance. The Server_ Instance parameter contains the information <server_name>\ <instance_name>. Necessary actions before the upgrade Back up the databases of the relevant instance. Close all applications which have access to the relevant SQL Server instance. Stop all dependent services, in particular ServerView Services and ServerView Download Service. Install the required software for the installation of the new SQL Server version and edition. Performing the upgrade You upgrade the instance by executing the SQL Server setup. The installation can be performed interactively for all editions of SQL Server. It is recommended that you always use the latest service pack. If possible you should also perform a Microsoft update after the setup, so that you receive any current security updates for the upgraded SQL Server version from Microsoft. Installation under Windows 85

86 3.13 Upgrade installations of SQL Server Upgrading from older SQL Server editions Bear in mind the following during the upgrade to a newer SQL Server version: During the procedure, the SQL Server setup program detects all installed SQL Server instances on the server and displays them for selection and configuration in various interactive steps. First of all, in the Select Instance window you must select the instance name from the displayed list. If there are several instances installed, the setup preselects a standard instance of SQL Server, if there is one. An SQL Server Express instance used by ServerView is normally installed as a named instance (instance name SQLSERVERVIEW). You can find out the name and type of the instance used by ServerView from the configuration file ServerViewDB.ini (in the <windir> directory) as described above. In the later Instance Configuration window, you must then check the instance name again and specify whether you want to install a standard instance or a named instance. For the remaining configuration options, apart from the instance name, you can accept the default options. Upgrading from an older SQL Server Express version The Microsoft documentation contains a detailed upgrade support matrix for any version and edition of SQL Server. Please check the supported path for your version of SQL Server Express in advance. For example, additional tools allow you to perform the following upgrades: An installed SQL Server 2005 Express, you can upgrade to SQL Server 2008 Express or its extended versions with additional tools (SQL Server 2008 Express with Tools). If you want to install the extended editions, however, you must execute the installation program again after the upgrade in order to add the additional components. An installed SQL Server 2005 Express, you can upgrade to SQL Server 2012 Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools). An installed SQL Server 2008 Express, you can upgrade to SQL Server 2012 Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools). You can get the editions of SQL Server 2008/2012/2014 Express you require from the Microsoft Download Center. After starting the setup, select the option Upgrade from SQL Server 2005 / Upgrade from SQL Server 2008 / Upgrade from SQL Server 2008 R2 / Upgrade from SQL Server During the installation you must then specify in a later follow-up dialog the SQL Server instance to be upgraded. Installation under Windows 86

87 3.13 Upgrade installations of SQL Server Upgrading from all other SQL Server editions All SQL Server editions can usually be upgraded to a corresponding edition of a higher SQL Server version, provided the upgrade path is supported by Microsoft version and edition restrictions. Please check the supported upgrade path for your version and edition in the Microsoft documentation in advance. Full editions of SQL Server are not available free of charge from the Download Center but must be licensed and installed from your SQL Server installation medium. Necessary actions after the upgrade After the in-place upgrade of the instance, you must perform the following steps for all versions of SQL Server: 1. Check whether the SQL Server (<instance_name>) service was started. 2. For editions other than SQL Server Express: Check whether the SQL Server Agent (<instance_name>) service was started. If you are using a remote SQL Server for Operations Manager, you must perform the additional steps on the management station. To do this, log on to the management station under the user account specified in the %windir%\serverviewdb.ini file under the entries Domain and Username. 3. For SQL Server Express: Check whether the Windows service Task Scheduler has started. 4. Internal backup jobs of Operations Manager must now be set up again before you can restart Operations Manager. The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: SQL Server Client tools must be installed and accessible via the PATH environment variable in their default location on the CMS: <Program Files>\Microsoft SQL Server\<version>\Tools\Binn\ (with <version> in 90\100\110). The calling account must be a member of the sysadmin server role in SQL Server. The Windows command prompt used to call the tool must be opened with full administrator rights. Proceed as follows: 1. Open the input prompt. 2. Switch to the directory: <installation_path>\serverview Services \scripts\serverview\tools Installation under Windows 87

88 3.13 Upgrade installations of SQL Server 3. Execute the following batch file, which you will find in this directory after upgrading to an SQL Server 2008, SQL Server 2012 edition, or SQL Server 2014 edition: SVCreateJobs_Upgrade2008 SVCreateJobs_Upgrade2012 SVCreateJobs_Upgrade During the execution, answer Renamed SQL Server Instance [Y/N]? with N. 5. All necessary upgrade steps for Operations Manager will be executed from this batch file. The individual steps will also be logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2008.log or <DbApplicationFolder>\SVCreateJobs_Upgrade2012.log(for SQL Server 2012/2014). You can find out the contents of the DbApplicationFolder parameter from the configuration file ServerViewDB.ini (in the <windir> directory). 6. After successful execution, start the services ServerView Services and ServerView Download Service. 7. Then check whether the backup jobs for the ServerView database have been set up and can be executed. For SQL Server Express editions the jobs were set up via the Windows Task Scheduler and therefore can only be monitored via this tool: To do this, open Control Panel Scheduled Tasks and you will see a list of jobs and their schedules. For all other editions of SQL Server, the service SQL Server Agent is used to set up the jobs. In this case, check the jobs and schedules via SQL Server Management Studio. Start SQL Server Management Studio. Click the SQL Server instance and select the entry SQL Server Agent. Under Jobs you will see the jobs that have been set up. You can view the current schedule for each job with View History Moving the ServerView database If you do not want to or cannot perform an in-place upgrade of the entire SQL Server instance, you can instead move the ServerView database from an installed SQL Server instance into a new SQL Server instance, thus migrating it. This procedure is also referred to in the Microsoft online documentation for SQL Server as a "side-by-side" upgrade. You must choose this variant if an in-place upgrade for your SQL Server edition is not supported by Microsoft. This is the case, for example, if you want to upgrade from a 32-bit SQL Server edition to a 64-bit SQL Server edition. Installation under Windows 88

89 3.13 Upgrade installations of SQL Server In the Microsoft online documentation for the SQL Server version required, you can find out which version and edition upgrades from SQL Server/SQL ServerExpress to later SQL Server editions are supported by Microsoft. With this upgrade method, a new SQL Server instance is installed side-by-side with the existing one. The ServerView database is first detached from the installed instance and then attached to the new instance. Operations Manager also remains installed on your system with this method. You must install the new SQL Server instance on the same system as the old one, so that the client configuration for Operations Manager is retained. So that, the old and new instances of SQL Server cannot be installed side-by-side under the same instance name. You must either Uninstall the SQL Server instance after the database is detached and before the new instance is installed, or Install the new SQL Server instance under a different instance name. Note the following: Switching the instance type is not supported for the upgrade of the ServerView database. For the upgrade you can install a named instance under a different name, but not switch from a named instance to a default instance (or vice versa). Preparing for installation During the installation of the newer instance, the necessary hardware and software requirements are checked. For information on this, see, for example, the product pages for the new SQL Server version in the Microsoft Download Center. To install an SQL Server Express Edition, you may have to download the required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components. Find out the type (default instance or named instance) and name of the installed SQL Server instance. You will find this information in the configuration file ServerViewDB.ini (in the <windir> directory) in the Server_Instance and Instance parameters: o o If there is no Instance parameter, the instance is a default one. Under Server_ Instance, only the server name (usually (local)) is given. For a named instance, the instance name is given under Instance. The Server_ Instance parameter contains the information <server_name>\ <instance_name>. Find out the current path names of the ServerView database files. The path names are needed for attaching the database to the newer SQL Server instance. Installation under Windows 89

90 3.13 Upgrade installations of SQL Server You can find out the path names as follows using the SQL Server Management Studio: 1. Start the tool and connect to the installed SQL Server instance. 2. Select the database ServerViewDB. 3. Select Properties from the context menu. After selecting files, you will find the path name. You can find out the path names using osql (or sqlcmd) as follows: 1. Open the input prompt and enter the following commands: osql -S <Server_Instance> -E EXEC sp_helpfile GO The filename column contains the path details.you quit osql with the quit command. Necessary actions before the upgrade In the existing SQL Server instance, back up the ServerViewDB database so that you have an up-to-date backup. Close all applications which have access to the relevant SQL Server instance. Stop all dependent services, in particular ServerView Services and ServerView Download Service. Install the required software for the installation of the new SQL Server version. Performing the upgrade Detach the ServerView database from the existing SQL Server instance. You can either do this with SQL Server Management Studio, or directly by calling an SQL Server procedure from an input prompt with osql. If you want to use a management tool, you can find out from the online help for the tool you are using how to detach the database. If you are using an input prompt, proceed as follows: 1. Open the input prompt and enter the following commands: osql -S <server_instance> -E EXEC GO You quit osql with the quit command. Detach does not delete the database files from SQL Server; instead they remain in the relevant storage location. You can either leave the files there or copy them to a different directory. In any case you must specify the current path name in the new instance when you attach the database later. Installation under Windows 90

91 3.13 Upgrade installations of SQL Server If the name of the SQL Server instance is not to be changed, you must now uninstall the existing SQL Server instance. Install the new SQL Server instance: o o For an SQL Server Express Edition, start the installation from the files downloaded from the Download Center. For all other editions of SQL Server you can start the installation directly from your installation medium (DVD or iso image). If the instance name is not to be changed and a previous SQL Server instance was uninstalled, then perform the installation with the same type (default instance or named instance) and name (for a named instance), e.g. SQLSERVERVIEW for SQL Server Express edition. Note the following when installing SQL Server Express: Deactivate the option Hide advanced configuration options in the Registration Information window, otherwise you will not be able to assign an instance name other than the default name SQLEXPRESS during the installation. Then attach the database as follows: 1. Open SQL Server Management Studio and connect to the new instance. 2. Select New Query and enter the following command in the Query window, where <data_path> is the path name of the ServerView database files on your system. CREATE DATABASE ServerViewDB ON PRIMARY (FILENAME='<data_path>\ServerViewDB.mdf') LOG ON (FILENAME='<data_path>\ServerViewDB_log.LDF') FOR ATTACH Following the attachment, execute the following command to check the consistency and to update: DBCC UPDATEUSAGE('ServerViewDB') If you are using the SQL server as a remote SQL server for Operations Manager, set up the user account as described in section "Configuring a remote SQL Server" on page 68. On the management station you will find the user account in the %windir%\serverviewdb.ini file under Domain and Username. Set up the user account under which the ServerView Services and ServerView Download Service are registered in SQL Server as of 2008 as an authorized SQL administrator, see "Adding a user account with SQL Server administrator rights" on page 67. If you are using SQL Server as of 2012 as a local SQL Server, also add the LOCAL SYSTEM account as an authorized administrator. Installation under Windows 91

92 3.13 Upgrade installations of SQL Server Necessary actions after the upgrade After the side-by-side upgrade of the instance, you must perform the following steps for all versions of SQL Server: If you are using the SQL server as a remote SQL server for Operations Manager, you must perform the additional actions on the management station, logging on as the user who is entered on there in the %windir%\serverviewdb.ini file under Domain and Username. 1. For an Express Edition, check whether the service Windows Task Scheduler is started before you continue with the upgrade. 2. For all other editions of SQL Server: Check whether the service SQL Server Agent <instance_name> is started. 3. Internal backup jobs of Operations Manager must now be set up again before you can restart Operations Manager. The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: SQL Server Client tools must be installed and accessible via the PATH environment variable in their default location on the CMS: <Program Files>\Microsoft SQL Server\<version>\Tools\Binn\ with <version> in 90\100\110. The calling account must be a member of the sysadmin server role in SQL Server. The Windows command prompt used to call the tool must be opened with full administrator rights. Proceed as follows: 1. Open the input prompt. 2. Switch to the directory <installation_path>\serverview Services \scripts\serverview\tools. 3. Execute the following file, which is located in this directory: o For SQL Server 2012 / SQL Server 2014: SVCreateJobs_Upgrade2012 o For SQL Server 2008: o SVCreateJobs_Upgrade Answer the question Renamed SQL Server Instance [Y/N]? o o With N if the new SQL Server instance was installed under the same name. With Y if the new instance was installed under a different name. Then enter the Installation under Windows 92

93 3.13 Upgrade installations of SQL Server new name at the following prompt: Please enter new SQL Server Instance Name 4. The necessary upgrade steps for setting up the Operations Manager jobs are executed while this application is running and are logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2012.log or<dbapplicationfolder>\svcreatejobs_upgrade2008.log. You can find out the contents of the DbApplicationFolder parameter from the configuration file ServerViewDB.ini (in the <windir> directory). 5. After successful completion, start the services ServerView Services and ServerView Download Service. 6. Then check in all cases whether the backup jobs for the ServerView database have been set up correctly and can be executed on your system: o o For SQL Server Express editions the jobs were set up via the Windows Task Scheduler. You can check the jobs and the schedule via the relevant Windows user interface: 1. Open Control Panel Scheduled Tasks. You will see a list of jobs and their schedules. For all other editions of SQL Server you can use the SQL Server Agent service to set up the jobs. You can check the jobs and the schedule via SQL Server Management Studio: 1. Start SQL Server Management Studio. 2. Click the SQL Server instance and select the entry SQL Server Agent. 3. Under Jobs you will see the jobs that have been set up. You can view the current schedule for each job with View History Upgrading SQL Server 2012/2014 Express to SQL Server 2012/2014 You can perform the following upgrade installations: SQL Server 2012 Express instance to an SQL Server 2012 full version. SQL Server 2014 Express instance to an SQL Server 2014 full version. Because the upgrade installation is the same for both SQL Server 2012 and SQL Server 2014, it is described for both in this section. Below, the full edition is always referred to as SQL Server 2012/2014 and the express edition as SQL Server 2012/2014 Express. An upgrade could be necessary if the maximum size of the ServerView database (10 GB) is reached or if you want to use additional features or components of SQL Server 2012/2014 full versions in your environment, which are not included in SQL Server 2012/2014 Express. Installation under Windows 93

94 3.13 Upgrade installations of SQL Server Preparing for installation Before you perform an upgrade installation, you must make the following preparations: During the upgrade installation of SQL Server 2012/2014, the necessary hardware and software requirements are checked. For information on this, see the Microsoft website. Find out which edition updates of SQL Server 2012/2014 (Express) are supported by Microsoft by checking the online documentation for SQL Server 2012/2014 (Express). If you require a particular feature or component in your environment, find out the functional scope of the edition to which you want to upgrade. Note the following for the upgrade: Localized versions of SQL Server 2012/2014 Express can only be upgraded to localized versions of the same language or to the English version of SQL Server 2012/2014. It is recommended that you always install the latest service pack. After the upgrade you should always check whether any current updates are missing and install them if so. An existing installation of SQL Server Management Studio (Basic) may have to be uninstalled and reinstalled for the new edition, as different editions of SQL Server Management Studio cannot be installed side-by-side. Necessary actions before the upgrade 1. Back up the databases of the installed instances. 2. Close all applications which have access to the relevant SQL Server 2012/2014 Express instance. 3. Stop all dependent services, in particular ServerView Services and ServerView Download Service. Performing the upgrade The upgrade is performed by executing the SQL Server 2012/2014 Setup from the installation DVD. 1. Start the Setup for the target edition you require. 2. In the left window pane, select Maintenance and then select the option Edition Upgrade. 3. The Installation Wizard for upgrading the edition opens. 4. When a number of preconditions have been verified, you must select in the Select Instance window the instance you want to upgrade to the target edition. The instance name for a named SQL Server 2012/2014 used by Operations Manager is SQLSERVERVIEW. 5. The program then checks whether an edition upgrade is possible, asks you to reconfirm in the Ready to upgrade edition window, and then performs the upgrade. The successful upgrade is displayed in the following Complete window. Installation under Windows 94

95 3.13 Upgrade installations of SQL Server Necessary actions after the upgrade 1. Install any outstanding service packs, service-pack updates or hotfix updates for the new edition status. 2. Check whether the SQL Server (<instance_name>) service is started. 3. Check whether the SQL Agent (<instance_name>) service is started. Before you can restart the ServerView services and Operations Manager, you must recreate internal backup and maintenance jobs for the ServerView database. The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: SQL Server Client tools must be installed and accessible via the PATH environment variable in their default location on the CMS: <Program Files>\Microsoft SQL Server\<version>\Tools\Binn\ (with <version> in 90\100\110). The calling account must be a member of the sysadmin server role in SQL Server. The Windows command prompt used to call the tool must be opened with full administrator rights. Proceed as follows: 1. Open the input prompt. 2. Switch to the directory <installation_path>\serverview Services\scripts\ServerView\Tools. 3. Execute the file SVCreateJobs_Upgrade2012, which is located in this directory. During the execution, answer the question Renamed SQL Server Instance [Y/N]? with N. All necessary upgrade steps are performed by this batch file and are logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2012.log. You can find out the path for <DbApplicationFolder> from the configuration file ServerViewDB.ini (in the <windir> directory). 4. When the file has successfully executed, start the services ServerView Services and ServerView Download Service. 5. Then always check whether the backup jobs for the ServerView database are set up on your system and can be executed. The jobs are set up using the SQL Server Agent service. You can view the jobs via SQL Server Management Studio: 1. Start SQL Server Management Studio. 2. Click the SQL Server instance and select SQL Server Agent. 3. The jobs that have been set up are listed under Jobs. You can view the current schedule for each job with View History. Installation under Windows 95

96 3.13 Upgrade installations of SQL Server Upgrading SQL Server 2008 Express to SQL Server 2008 The description for SQL Server 2008 is also valid for SQL Server 2008 R2. You can perform an upgrade installation of an SQL Server 2008 Express instance to an SQL Server 2008 full version. An upgrade could be necessary if the maximum size of the ServerView database (for SQL Server 2008 R2 Express: 10 GB, for SQL Server 2008 Express: 4 GB) is reached or if you want to use additional features or components of SQL Server 2008 full versions in your environment, which are not included in SQL Server 2008 Express. Preparing for installation Before you perform an upgrade installation, you must make the following preparations: During the upgrade installation of SQL Server 2008, the necessary hardware and software requirements are checked. For information on this, see the Microsoft website. Find out which edition updates of SQL Server 2008 (Express) are supported by Microsoft by checking the online documentation for SQL Server 2008 (Express). If you require a particular feature or component in your environment, find out the functional scope of the edition to which you want to upgrade. Note the following for the upgrade: Localized versions of SQL Server 2008 Express can only be upgraded to localized versions of the same language or to the English version of SQL Server It is recommended that you always install the latest service pack. After the upgrade you should always check whether any current updates are missing and install them if so. An existing installation of SQL Server Management Studio (Basic) may have to be uninstalled and reinstalled for the new edition, as different editions of SQL Server Management Studio cannot be installed side-by-side. Necessary actions before the upgrade 1. Back up the databases of the installed instances. 2. Close all applications which have access to the relevant SQL Server 2008 Express instance. 3. Stop all dependent services, in particular ServerView Services and ServerView Download Service. Performing the upgrade The upgrade is performed by executing the SQL Server 2008 Setup from the installation DVD. Installation under Windows 96

97 3.13 Upgrade installations of SQL Server 1. Start the Setup for the target edition you require. 2. In the left window pane, select Maintenance and then select the option Edition Upgrade. 3. The Installation Wizard for upgrading the edition opens. 4. When a number of preconditions have been verified, you must select in the Select Instance window the instance you want to upgrade to the target edition. The instance name for a named SQL Server Express 2008 instance used by Operations Manager is SQLSERVERVIEW. 5. The program then checks whether an edition upgrade is possible, asks you to reconfirm in the Ready to upgrade edition window, and then performs the upgrade. The successful upgrade is displayed in the following Complete window. Necessary actions after the upgrade 1. Install any outstanding service packs, service-pack updates or hotfix updates for the new edition status. 2. Check whether the SQL Server (<instance_name>) service is started. 3. Check whether the SQL Agent (<instance_name>) service is started. Before you can restart the ServerView services and Operations Manager, you must recreate internal backup and maintenance jobs for the ServerView database. The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: SQL Server Client tools must be installed and accessible via the PATH environment variable in their default location on the CMS: <Program Files>\Microsoft SQL Server\<version>\Tools\Binn\ (with <version> in 90\100\110). The calling account must be a member of the sysadmin server role in SQL Server. The Windows command prompt used to call the tool must be opened with full administrator rights. Proceed as follows: 1. Open the input prompt. 2. Switch to the directory <installation_path>\serverview Services\scripts\ServerView\Tools. 3. Execute the file SVCreateJobs_Upgrade2008, which is located in this directory. During the execution, answer the question Renamed SQL Server Instance [Y/N]? with N. All necessary upgrade steps are performed by this batch file and are logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2008.log. Installation under Windows 97

98 3.14 Installing Operations Manager on Windows Terminal Server/Remote Desktop Services You can find out the path for <DbApplicationFolder> from the configuration file ServerViewDB.ini (in the <windir> directory). 4. When the file has successfully executed, start the services ServerView Services and ServerView Download Service. 5. Then always check whether the backup jobs for the ServerView database are set up on your system and can be executed. The jobs are set up using the SQL Server Agent service. You can view the jobs via SQL Server Management Studio: 1. Start SQL Server Management Studio. 2. Click the SQL Server instance and select SQL Server Agent. 3. The jobs that have been set up are listed under Jobs. You can view the current schedule for each job with View History Installing Operations Manager on Windows Terminal Server/Remote Desktop Services If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager. Remote Desktop Services is known as Terminal Services in Windows Server 2008 and earlier. Installation on Windows Terminal Server/Remote Desktop Services 1. Click Server-Manager Roles. If you see terminal services/remote Desktop Services, the Terminal Server/Remote Desktop Services role is installed. 2. Find out the path for the Operations Manager installation program: 1. Insert the ServerView Suite DVD Search for the file serverview.exe. 3. Note the path to file serverview.exe. 3. Install Operations Manager via the command prompt window: 1. Open a command prompt window and type: Change user /install 2. Type the path name to the serverview.exe file in the same command prompt window and install Operations Manager. 3. After the installation, type in the command prompt window: Change user /execute Installation under Windows 98

99 3.15 Installation check list General procedure with Operations Manager and Terminal Server/Remote Desktop Services It is recommended that you install Terminal Server/Remote Desktop Services before installing Operations Manager. Then install Operations Manager as described above. If Terminal Server/Remote Desktop Services has been installed after Operations Manager, please check whether Operations Manager is working well. If error messages appear, uninstall Operations Manager and execute the steps described above. Installation of Operations Manager on Terminal Server/Remote Desktop Services with remote SQL Server is not supported The installation mode described above does not apply when a remote SQL Server is used Installation check list Web browser No. Check point 1 Supported version Configuration Supported web browser for Windows is the following: Internet Explorer 10 / 11 2 Trusted sites Mozilla Firefox 16 / 17 or higher. Supported web browser for Linux is the following: Default web browser released with distribution. If you use Internet Explorer, add the URL of ServerView Operations Manager into Trusted sites. 1. Open Internet Explorer. 2. Select Tools Internet Options. 3. Click the Security tab and select Local intranet or Trusted sites. 4. Click Sites and enter the URL of the server on which ServerView Operations Manager is installed. 3 Proxy It cannot access to ServerView Operations Manager via proxy. Disable to use proxy on web browser configuration. Installation under Windows 99

100 3.15 Installation check list No. Check point 4 32-bit/64- bit Configuration Table 7: Check list web browser On 64-bit operating systems the 64-bit JRE can be used. But this can only be done together with the 64-bit Web browser. Otherwise a 32-bit JRE is necessary. Exception: 32-bit JRE is needed on Windows Java Runtime Environment (JRE) No. Check point 1 Supported version 2 32-bit/64- bit ServerView Operations Manager detects the installed Java-version (32-/ 64-bit) during installation. Therefore the Java-version (32-/ 64-bit) should not be changed after installation of ServerView Operations Manager. ServerView Operations Manager needs the prior xx bit version to work well. Configuration V 1.8.0_131 or higher JRE must be installed on both server side (system where ServerView Operations Manager is installed) and client side. You can use the same architecture of JRE as the operating system, i.e. 32- bit version of JRE on 32-bit Windows, and 64-bit version of JRE on 64-bit Windows. 3 Security Configure security settings as follows: Table 8: Check list JRE 1. Open Java Control Panel. 2. Select Advanced tab. 3. Open Settings Security Mixed code (sandboxed vs. trusted security verification). 4. Check Enable - hide warning and run with protections. Installation under Windows 100

101 3.15 Installation check list Operating system settings No. Check point 1 host name resolve Configuration Host name of the CMS must be available to resolve from both CMS itself (system where ServerView Operations Manager is installed) and client side. Make sure that the name resolve is available by the following commands: Windows: > tracert <host name>.<dns suffix> 2 Network ports 3 host name 4 SQL instance 5 Active Directory 6 Network drive 7 Terminal Server Linux: # traceroute <host name>.<dns suffix> ServerView Operations Manager uses some network ports. Which ports ServerView Operations Manager requires is described in "Calling and ports used" on page 26. Host name and DNS suffix of CMS must not contain underscore ('_'). If you want to use your own SQL Server instead of a bundled SQL Server, you must set up a suitable SQL Server instance before installing ServerView Operations Manager, see "Installation options for SQL Server" on page 33. Important: Please consider the notes in section "Setting up a service account" on page 60" for a local SQL Server and in section "Configuring a remote SQL Server" on page 68 for a remote SQL Server. If you want to use Active Directory for directory service of ServerView Operations Manager, Active Directory must be installed and configured for ServerView Operations Manager before ServerView Operations Manager installation. When you install ServerView Operations Manager, the connection to Active Directory must be available. Details of configuration of Active Directory are described in the "User Management in ServerView" user guide. It is not possible to install ServerView Operations Manager to network drives. If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager. Details of how to install ServerView Operations Manager is described in "Installing Operations Manager on Windows Terminal Server/Remote Desktop Services" on page 98. Table 9: Check list operating system settings Installation under Windows 101

102 3.16 Installation process Update Installation No. Check point Configuration 1 Base version Update installation is only possible from version or newer. Table 10: Check list update installation 3.16 Installation process The installation process consists of three steps: Installation of SQL Server Installation of the web server used by ServerView Operations Manager Installation of ServerView Operations Manager Installing SQL Server The first step of the ServerView Operations Manager setup is the installation of SQL Server. The start program serverview.exe opens the Select SQL Server window. For further information, see section "Installation options for SQL Server" on page 33 and section "SQL Server settings in case of a new installation" on page 105. Installing the web server used by ServerView Operations Manager The second step of the ServerView Operations Manager setup is the installation of the web server used by ServerView Operations Manager (see "Installing Tomcat via Fujitsu Software ServerView Application Server Setup wizard" on page 107). The start program serverview.exe calls the wizard Fujitsu Software ServerView Application Server Setup to install the web server used by ServerView Operations Manager. If you start an upgrade installation of ServerView Operations Manager, the old web server version will be removed. An upgrade installation is only possible as of Operations Manager version or ServerView Installation Manager version This wizard contains the web-server-relevant queries: Destination Folder window (see page 107). This window is only displayed during a new installation. Application Service Logon Information window ("Application Service Logon Information window" on page 108) Security Configuration window ("Security Configuration window" on page 109) Select Directory Server window ("Select Directory Server window" on page 110) Administrative User Password window (see page 110). Installation under Windows 102

103 3.17 Menu-driven installation of Operations Manager software This window is only displayed if you use ServerView Operations Manager s own preconfigured directory service ApacheDS. Directory Service Settings window (see page 111). This window is only displayed if you use an already existing directory service (e.g. Active Directory). Computer Details window ("Computer Details window" on page 114) Tomcat is configured as the standalone service ServerView ApplicationService, which is automatically started after the installation. The entry Fujitsu Software ServerViewApplication Service is created under Control Panel - Programs and Features to modify or uninstall Tomcat. The folder structure in the installation directory has been changed for Tomcat. For example, log files are located in the directory <installation_path>\tomee\logs and the configuration file is located in the directory <installation_path>\tomee\svconf. Installing ServerView Operations Manager The third step of the ServerView Operations Manager setup is the installation of ServerView Operations Manager itself (see "Installing ServerView Operations Manager" on page 115). After installation of the web server used by ServerView Operations Manager, the installation wizard Fujitsu ServerView Operations Manager Setup is started automatically. This wizard contains the relevant windows for installing the ServerView Operations Manager software Menu-driven installation of Operations Manager software The Operations Manager software (Operations Manager, Update Manager, and Event Manager) can be installed under Windows under menu control. On the ServerView Suite DVD 2, under SVSSoftware Software ServerView Windows ServerView S2, you will find the serverview.exe file, which you use to start installation. If the Microsoft Installer is not yet installed on the computer, it will be installed now. Installation and application language of Operations Manager on a Japanese operating system is Japanese by default. For all other operating system languages it is English. On installation via command line the language can be determined by the user, see "Installing Operations Manager software via the command line" on page 161. If you copy the installation files and folders to your local disk and install from there, do not delete these setup files. Sometimes when executing a Modify installation you are prompted for the original media. In this case reuse the setup files or DVD. Installation under Windows 103

104 3.17 Menu-driven installation of Operations Manager software Starting the installation procedure 1. Log on as a user with Windows administrator rights or, if using a remote SQL Server instance, as a domain user with Windows administrator rights. 2. Place the ServerView Suite DVD 2 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD s root directory. 3. Select ServerView Software Products. 4. Select the desired language in the displayed window. 5. Select ServerView Operations Manager. 6. Under ServerView Operations Manager Application (incl. ServerView Event Manager and ServerView Operations Manager) start the serverview.exe program. 7. Unpack the software to a directory of your choice. 8. Open Windows Explorer and switch to this directory. 9. Start the program serverview.exe by double-clicking it. The installation can also be done unattended ( silent ). For further information on silent installation, see "Installing Operations Manager software via the command line" on page 161. Installation under Windows 104

105 3.17 Menu-driven installation of Operations Manager software SQL Server settings in case of a new installation 1. Once the program has started, the following window is displayed in case of a new installation: Figure 2: Select SQL Server window The program then checks whether an SQL Server Express with the instance name SQLSERVERVIEW or a full edition with any instance name in a version supported by ServerView Operations Manager are already installed on your system. If no suitable SQL Server instance is found, you can select the option Install free edition of SQL Server to install automatically SQL Server 2014 Express. Then click Next. The ServerView database will be installed locally on the management station into the SQL Server 2014 Express instance with instance name SQLSERVERVIEW. Following this, the Operations Manager installation wizard is automatically started. If a suitable SQL Server instance is found on the local management station, you can use this local SQL Server instance. Select the option Use existing local SQL Server and then click Next. Following this, the Operations Manager installation wizard is automatically started. You can also use a remotely installed SQL Server instance. For further information, see "Remotely on a different system" on page 37. Select the option Use existing remote SQL Server... and then click Next. Installation under Windows 105

106 3.17 Menu-driven installation of Operations Manager software The Remote DB window opens: Figure 3: Remote DB window SQL Server Name Name of the SQL Server instance. (With an unnamed default instance of SQL Server this is the name of the system.) The SQL Server Name can be seen when opening the SQL Server Management Studio: You will find SQL Server Name (e.g. MYCOMPUTER\SQLSERVER1) under Server name in the first dialog box. User Name For this user name you must have set up a domain user account on the SQL Server, see "Configuring a remote SQL Server" on page 68. Domain Name Name of the domain. Password Password for accessing the user name. Now click Next. 2. Click OK. The Fujitsu Software ServerView Application Server Setup wizard starts. Installation under Windows 106

107 3.17 Menu-driven installation of Operations Manager software Installing Tomcat via Fujitsu Software ServerView Application Server Setup wizard 1. The wizard also checks the installed product version of Installation Manager. If this version is incompatible a message is displayed and the installation is aborted. 2. In the case of a new installation, an upgrade installation, or after the removal the Fujitsu Software ServerView Application Server Setup wizard opens. Figure 4: Fujitsu Software ServerView Application Server Setup window 3. With Next you initially go through general windows of the wizard which contain, for example, the license conditions and information on installation. 4. In the Destination Folder window, define the installation directory for the web server used by ServerView Operations Manager. This window is only displayed in the case of a new installation. ServerView Operations Manager and the web server used by ServerView Operations Manager are always installed in the same installation directory. So if you are doing an upgrade installation, the installation directory already exists. By default the software is installed in the following directory: (32-bit operating system): C:\Program Files\Fujitsu\ServerView Suite\ (64-bit operating system): C:\Program Files(x86)\Fujitsu\ServerView Suite\ 5. Click Next. Installation under Windows 107

108 3.17 Menu-driven installation of Operations Manager software 6. Enter the user account for the Tomcat service. Figure 5: Application Service Logon Information window Use LocalService? This option is only available if you use a local SQL database. Select Yes if you want to use the built-in account LocalService for the ServerView Application Server service. Otherwise click No. Please be aware that the LocalService account has full access to the ServerView Operations Manager files. If another service is also running under this account, it can access the ServerView Operations Manager files as well. It is recommended that you use a separate user account for the service. User Name For this user name you should have set up a standard user account with no special rights. Enter this user name. If you use a remote SQL Server instance, the field is preset to the domain name, which you have specified in the Remote DB window under Domain Name. You can use a domain user account with no special rights. Password Password for accessing the user name. Installation under Windows 108

109 3.17 Menu-driven installation of Operations Manager software 7. Configure the cipher suites and SSL protocols used by the ServerView Application Server. Figure 6: Security Configuration window Modern The Modern configuration set is the most secure configuration. Only the latest SSL protocol version TLSv1.2 is allowed. So it will pass vulnerability scanning without errors. But it can happen that older Java versions will not work. Intermediate By default Intermediate is selected. The Intermediate configuration set allows TLSv1.2, TLSv1.1 and TLSv1.0 Old If a client which can be connected to ServerView Operations Manager allows only the SSL protocol version SSLv3, the Old configuration set should be selected. Otherwise a connection cannot be established. Old should work with the oldest Web browsers and Java versions. Installation under Windows 109

110 3.17 Menu-driven installation of Operations Manager software 8. Select the directory server. Figure 7: Select Directory Server window Local directory server installed with ServerView Enable this option if you want to use the directory server ApacheDS. If you enable this option, the directory server ApacheDS is automatically installed when you install ServerView Operations Manager. The Administrative User Password window opens, where you can specify the password for the administrative user svuser. The password for svuser must not be an empty string. External existing directory server (you have to specify the properties later) Enable this option if you want to use an already existing Active Directory server. Choose where the authorization is to be done. with authorization on remote directory server (requires LDIF import there) The authorization is done on the remote directory server. So user authentication and user authorization are managed within the same "external" directory service (e.g. Active Directory). For further information, see the "User Management in ServerView" user guide. with authorization on local directory server (no LDIF import necessary) The authorization is done on the local ApacheDS. The "internal" directory service of ServerView Operations Manager (ApacheDS) is used for managing the role assignments, whereas the "external" directory Installation under Windows 110

111 3.17 Menu-driven installation of Operations Manager software service (e.g. Active Directory) is only accessed for managing user authentication (unified RBAC management). If you enable this option, the directory server ApacheDS is automatically installed when you install ServerView Operations Manager. In case of unified RBAC with authorization done on the local ApacheDS, a second directory service can be configured. For further information about unified RBAC, see the "User Management in ServerView" user guide. 9. If you use an already existing Active Directory server (option External existing directory server (you have to specifiy the properties later) enabled), you have to make some more settings for the directory service in the Directory Service Settings window. In case of authorization done on the local ApacheDS (option with authorization on local directory server (no LDIF import necessary) selected), it is also possible to configure a second Active Directory server, if required, in the Directory Service Settings window. Host(FQN) Fully-qualified name of the server on which the directory service is running. The fully-qualified name is an unambiguous name which specifies the system in the network. It is important that this name can always be properly resolved! This can be done via a DNS or NIS server, or through appropriate entries in the hosts file of the central management station. If you are not sure whether you can ensure for a proper name resolution, you can issue the system's IP address here. Backup Host(FQN) Fully-qualified name for a backup directory server, which is configurable in the Tomcat setup. The fully-qualified name is an unambiguous name which specifies the system in the network. It is important that this name can always be properly resolved! This can be done via a DNS or NIS server, or through appropriate entries in the hosts file of the central management station. If you are not sure whether you can ensure a proper name resolution, you can issue the system's IP address here. Port Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL). SSL Yes is enabled by default to protect the data transfer with SSL encryption. The TLS v1.1, TLS v1.2, and SSLv2Hello protocols are supported. Installation under Windows 111

112 3.17 Menu-driven installation of Operations Manager software It is recommended that you always protect the connection to the directory service, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose. For further information, see section "Managing SSL Certificates on the CMS and managed nodes" and "Integrating ServerView user management into Microsoft Active Directory" in the "User Management in ServerView" user guide. Domain Name Only if the option with authorization on local directory server (no LDIF import necessary) is selected (unified RBAC management is configured). Domain name of the Active Directory server. For further information, see section "Integrating ServerView user management into Microsoft Active Directory" in the "User Management in ServerView" user guide. You must enter this domain name in the login window of the Central Authentication Service where you are asked to specify the authentication domain of your user account (see "ServerView Operations Manager" user guide). SVS Base DN Base directory for the ServerView authorization data, e.g.: OU=application,DC=fujitsu,DC=com You can specify any directory in the Active Directory here. The Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further information, see section "Integrating ServerView user management into Microsoft Active Directory" in the "User Management in ServerView" user guide. Group Search Base Starting point for the group search in the directory server e.g.: CN=Users,DC=fujitsu,DC=com User Search Base Starting point for the user search in the directory server e.g.: CN=Users,DC=fujitsu,DC=com User Search Filter Filter for user search. User (read only account) User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, Installation under Windows 112

113 3.17 Menu-driven installation of Operations Manager software as displayed in the Active Directory in the user s account settings under User logon name. Password / Confirm Password for read access. The password which is written into the sv-sec-config.xml file is stored encrypted. In case of an upgrade or modify installation: If the previous directory service also was Active Directory, the Password / Confirm fields can be left empty. In this case, the previous password remains in effect. Password Expiry Warning No is enabled by default. In this case, expiry of user passwords will not be indicated when a user authenticates to CAS. Select Yes and then click Next if you want configure that a user signing on to CAS is informed on an imminent password expiry. In this case, the Password Expiration Settings dialog box opens, which allows you to configure the required parameters. Selecting Yes and configuring the first three options in the Password Expiration Settings dialog box enables the LDAP Password Policy Enforcement (LPPE), which is disabled by default. LPPE handles a variety of login exceptions which would otherwise prevent user authentication. For further information, see the "User Management in ServerView" user guide. Domain DN Distinguished Name of the Active Directory domain, e.g.: DC=fujitsu,DC=com Valid Days Number of days a password is valid (e.g. 90). This value is used as default if no maxpwdage attribute is found in Active Directory. A maxpwdage value configured in Active Directory always overrides the value specified in the Valid Days field. Warning Days Number of days a user is warned before the password expires (e.g. 60). There is no corresponding attribute in Active Directory. Therefore, the Warning Days field is the only option for configuring the password expiry warning time. Password URL (optional) URL to which the user will be redirected in order to change the password. Installation under Windows 113

114 3.17 Menu-driven installation of Operations Manager software Configure additional Directory Server No is enabled by default. Select Yes and click Next if you want configure an additional Active Directory server. In this case, the Additional Directory Service settings dialog box opens, which allows you to configure the required parameters for the additional Active Directory server. The dialog box is the same as for the first Active Directory server (see above). Via the Test button you can test the settings by calling up the ldapsearch command. You can see the result in the displayed DOS window. 10. The Computer Details window displays information about the computer. Figure 8: Computer Details window Computer Name of the central management station. DNS Suffix DNS suffix used for Tomcat configuration. IP Address IP address of the management station. If any of these details change, you must perform a Modify installation to update the information, see "Modify installation of Operations Manager software" on page Click Next. In the Ready to Install the Application window click Next to start the installation. Installation under Windows 114

115 3.17 Menu-driven installation of Operations Manager software 12. Click Finish to complete the installation. After installation of the web server used by ServerView Operations Manager, the service ServerView ApplicationService is started automatically. Installing ServerView Operations Manager 1. After the installation of the web server used by ServerView Operations Manager the Fujitsu ServerView Operations Manager Setup wizard opens. 2. With Next you initially go through general windows of the wizard which contain, for example, the license conditions and information on installation. 3. In case of an upgrade installation, an additional window is displayed providing you with important hints on the upgrade installation. Important notes: There is server and configuration data from a previous ServerView installation. Please save the old data before performing this upgrade installation so that you can restore the data in case of a failure. Information about the old version can be found in C:\Windows\OldSVVersion.ini. Please read the release notes for further information. Please clean the cache of the java plug-in on all systems on which you used a web browser to install the old ServerView version. Additionally, the window allows you to specify whether to change the default settings for the internal trap that indicates changes of connectivity settings. As of Operations Manager V6.30, these default settings are preset to "enabled" (with one poll interval and no startup check). Prior to this, "disabled" was the default. To change the value to "enabled" for all servers in the server list which have the old default value, select Yes. Otherwise select No. The configured value is stored in the ServerView database and can be changed via the Base Configuration Wizard. Installation under Windows 115

116 3.17 Menu-driven installation of Operations Manager software 4. In the next window, select the SQL Server instance ("Recognition of SQL Server instances during Operations Manager installation" on page 37) into which the ServerView database is to be installed. Figure 9: SQL Server connection window 5. Select the setting(s) for the SQL Server database backup, see also "Backing up the ServerView database" on page 134. Figure 10: SQL Server Backup window typical Leave the backup mode typical selected if the management station is not always running. typical is equivalent to the SQL Server recovery model "simple". Installation under Windows 116

117 3.17 Menu-driven installation of Operations Manager software advanced Select advanced if you perform a lot of important monitoring functions with Operations Manager and the management station is nearly always running. advanced is equivalent to the SQL Server recovery model "full". Browse button During a new installation, you can additionally specify under SQL Server Backup Path a path under which the backup files of SQL Server are created. You can use the backup files if you have to restore the ServerView database, as described in "Restoring the ServerView database" on page 142. In case your are using a locally installed SQL Server instance you see: In case you are using a remotely installed SQL Server instance you see: 6. Define the installation type. Figure 11: Select Installation Type window Installation under Windows 117

118 3.17 Menu-driven installation of Operations Manager software Custom enables you to select individual Operations Manager products for installation as the Operations Manager installation wizard run progresses. 7. The Select Features window below is displayed if you selected the installation type Custom. Select the management products you wish to install. With Complete you select them all. For an overview of which ServerView components are installed, see "ServerView Operations Manager components" on page 24. Figure 12: Select Features window 8. Enter a password for the user name for the ServerView Download Service. Figure 13: Update Management Logon Information window Refer to the "ServerView Update Management" user guide ("Prerequisites section) to get more information about the logon. Installation under Windows 118

119 3.17 Menu-driven installation of Operations Manager software 9. The Computer Details window displays information about the computer. Figure 14: Computer Details window SNMP Community Management station s community. This is important for receiving traps. If any of these details change, you must perform a Modify installation to update the information, see "Modify installation of Operations Manager software" on page Select the required integration into another Enterprise Management System. Figure 15: Select Enterprise Management Integrations window Installation under Windows 119

120 3.18 Modify installation of Operations Manager software This window is only displayed if Enterprise Management software was found on the management station. The corresponding management system must already be installed on the management station so that the integration can be selected. Further information on integrations is provided in the corresponding ServerView Integration guides. 11. Start the installation. Figure 16: Ready to Install the Application window You start installation with Install >. < Back enables you to correct the details for installation if required. With Cancel you terminate the Operations Manager installation wizard without any change being made. In the last window of the Operations Manager installation wizard you are shown concluding information. Click Finish to complete the installation. Editing/addition/deletion of ServerView-related files may give influences on operations. Make sure not to do any other operations than the ones explained in this documentation Modify installation of Operations Manager software You choose a Modify installation if you want to install or uninstall a feature of Operations Manager or if the computer name, the membership of a domain/workgroup, the IP address of the system, the directory service or the service account has been changed after the installation of ServerView Operations Manager. Installation under Windows 120

121 3.18 Modify installation of Operations Manager software If you change the computer name, you must remove the managed server from the server list and add it again. Otherwise, the old computer name will be retained in the server list. If you only want to change the passwords of the accounts for the services ServerView ApplicationService, ServerView Services and ServerView Download Service you should NOT execute a modify installation. Change the passwords for these services in Administrative Tools Services. Wait at least 5 minutes after the restart of the Tomcat service. Please note that the installation account and the user names you add into the installation dialogs need access rights in the SQL Server instance. Either reuse the preset user names. Or refer to the "Setting up a service account" section corresponding to your SQL Server (in chapter "Installing ServerView Operations Manager" on page 23) if you use a local SQL Server or see "Configuring a remote SQL Server" on page 68, step 3 if you use a remote SQL Server or see "Operations Manager installation without SQL Server "sysadmin" access" on page 74 if you have configured the SQL Server for enhanced security. You see the used accounts in file %windir%\serverviewdb.ini (see also section "Further procedure on the management station" on page 82). Proceed as follows: 1. Log on as a user with administrator rights or, if using a remote SQL Server instance, as a domain user with administrator rights. 2. Close every open window of Operations Manager, Event Manager and Update Manager. 3. Select Control Panel Programs and Features. 4. Select Fujitsu ServerView Operations Manager or Fujitsu ServerView ApplicationService. 5. Click Change. 6. Enable the Modify option and click Next. Modifying ServerView Operations Manager 1. The Select Feature window opens. Select the features you would like to install or uninstall. 2. In the Update Management Logon Information window, you can change the service account of the ServerView Download Service. This window is only displayed if in the Select Features window the feature ServerView Update Manager was not set to Entire feature will be unavailable. 3. If you have removed the system from the domain, please clear the field DNS Suffix in the Computer Details window. Installation under Windows 121

122 3.19 Upgrade installation of Operations Manager 4. Click Install. 5. Click Finish. After a successful run of setup, you have to do the following action: If you have ServerView Agents running on the system, you will need to restart the SNMP service, so that the agents work with the new IP address. Modifying Tomcat 1. In the Tomcat Service Account window, you can choose whether you want to change the account of the ServerView Tomcat service. 2. In the Select Directory Server window, you can select your directory server. 3. In the ApacheDS Administrative User window, you can select whether you want to change the password of the administrative user svuser in your ApacheDS directory service. The password for svuser must not be an empty string. 4. In the Computer Details window, you can change the computer details Upgrade installation of Operations Manager If an older version of Operations Manager is already installed, you can perform an upgrade installation of Operations Manager. To execute an upgrade installation, proceed as described in section "Menu-driven installation of Operations Manager software" on page 103. An upgrade installation to the current is only supported as of Operations Manager version Operations Manager requires Java Runtime Environment (JRE) V1.7.0_55 or higher. Please ensure that these requirements are met before upgrading. To avoid a reboot, stop ServerView Services and the Tomcat service first. If an newer version of Operations Manager is already installed, you cannot perform an downgrade installation. To downgrade, you must uninstall the existing Operations Manager first. Installation under Windows 122

123 3.20 Uninstalling the Operations Manager software Please note that the installation account and the user names you add into the installation dialogs need access rights in the SQL Server instance. Either reuse the preset user names or refer to the corresponding sections. If you use a local SQL Server, refer to the "Setting up a service account" section corresponding to your SQL Server (in chapter "Installing ServerView Operations Manager" on page 23). If you have configured the SQL Server for enhanced security, see "Operations Manager installation without SQL Server "sysadmin" access" on page 74. You see the used accounts in file %windir%\serverviewdb.ini (see also section "Further procedure on the management station" on page 82). Some windows are omitted during an upgrade installation, for example: The Select SQL Server, Remote DB and SQL Server Connection windows do not open. The SQL Server must be the same as in the new installation. You cannot switch between the local and remote SQL Servers. The Destination Folder window does not open. You cannot change the destination folder Uninstalling the Operations Manager software If you want to uninstall a web component and then install an older version of the same component, you must first flush all caches. Installation under Windows 123

124 3.20 Uninstalling the Operations Manager software Before you uninstall Operations Manager, you should make a note of the name of the SQL Server instance and the SQL Server edition from the configuration file ServerViewDB.ini (in the <windir> directory). The name of the instance is shown under Server_Instance, and the edition under DbServerEdition. Before you uninstall Operations Manager, it is recommended that you remove all report configurations of the Performance Manager according to the description in the "Performance Manager" user guide. If you do not remove them, there will be a discrepancy between Operations Manager and agents after Operations Manager is installed again. Please check before removal whether there are any other Operations Manager installations which use these reports too. If Virtual-IO Manager or Installation Manager are still installed on the system, you will be asked to uninstall them first. Do not stop the uninstallation while it is running. Please wait until the process is completed. It is recommended to log in at the central management station with the account you used during installation. If not, it may occur that database ServerViewDB cannot be deleted. In this case you can delete it with SQL Server Management Studio by your own. You see the Installation Account in file %windir%\serverviewdb.ini (see also section "Further procedure on the management station" on page 82). You uninstall the Operations Manager software via the Windows start menu: 1. Select Control Panel Programs and Features. 2. To display the product versions on Windows Server 2008, select Choose Details from the View menu. 3. Select the Version option and click OK. First you must uninstall ServerView Operations Manager and then Tomcat. Uninstalling ServerView Operations Manager 1. Select Fujitsu ServerView Operations Manager. 2. Click Remove to remove the complete package. Uninstalling Tomcat 1. Select Fujitsu Software ServerView Application Server. 2. Click Remove to remove the complete package. Installation under Windows 124

125 3.21 ServerView services Uninstalling the SQL Server instance If you are using the SQL Server instance SQLSERVERVIEW, you can then uninstall this instance. If in the configuration file ServerViewDB.ini (in the <windir> directory) the entry for the edition (DBServerEdition) was Express Edition, proceed as follows: 1. Select the entry Microsoft SQL Server <version>. 2. Click Remove. 3. Select the instance SQLSERVERVIEW: Database Engine. 4. Uninstall the software. If SQLSERVERVIEW is the only SQL Server instance, you can also uninstall the Workstation Components/Shared Components. If you have installed SQL Server Management Studio Express, you can uninstall this software. With an SQL Server instance of an Enterprise/Standard/Workgroup Edition, you must first make sure that the SQL Server instance is not being used by another application. If it is not, you can uninstall it in the same way as for the SQLSERVERVIEW instance. Depending on your version of SQL Server, you can then uninstall Microsoft SQL Server Native Client/SQL Server 2008 Native Client/SQL Server 2008 R2 Native Client/SQL Server 2012 Native Client. If you uninstalled the SQL Server accidentally you can install the same SQL Server edition with the same instance name (see in configuration file ServerViewDB.ini the entry DBServerEdition and Server_Instance) and restore the ServerView database from backups as described in "Restoring the ServerView database" on page 142 (restore additionally master database in case of a remote SQL Server and msdb database in case of a SQL Server full edition) ServerView services The following services are available for operating Operations Manager: ServerView Download Service ServerView ApplicationService ServerView Services MSSQL$SQLSERVERVIEW or SQL Server (SQLSERVERVIEW) or SQL Server (MSSQLSERVER) ServerView Apache Directory Server Installation under Windows 125

126 3.21 ServerView services Stopping/starting/restarting services You can stop, start and restart the services: 1. Select Administrative Tools Services. 2. Select the appropriate service and then select Stop, Start or Restart from the context menu. Watchdog for ServerView Services On Windows, the main service program AlarmService.exe watches the started subservices and, if one of them disappears, it is restarted. Auto-restart of services As of Operations Manager version 5.30, for the SQL Server Express instance with the name SQLSERVERVIEW, an automatic restart of the SQL Server service SQL Server (SQLSERVERVIEW) or MSSQL$SQLSERVERVIEW is automatically configured for the event of failure. You can check these settings: 1. Select Administrative Tools Services. 2. Select the SQL Server service and select Properties from the context menu. 3. Select the Recovery tab. You will find the restart properties in the fields First/Second/Subsequent failure. For the Workgroup/Standard/Enterprise edition, you can manually configure the SQL Server and SQL Server Agent services to restart automatically. On failover cluster instances, auto-restart should not be enabled for these services. You can choose one of three options for setting up auto-restart of the SQL Server and SQL Server Agent services. 1. Via the Windows Services Microsoft Management Console: 1. Select Administrative Tools Services. 2. Select the services SQL Server (MSSQLSERVER) and SQL Server Agent (MSSQLSERVER) and then select Properties from the context menu. 3. Select the Recovery tab. You will find the restart properties in the fields First/Second/Subsequent failure. Set these fields to Restart the Service and in the Reset fail count after:... days field set e.g. to You can use the service controller command sc for a detailed setting of the delay time: 1. In the configuration file ServerViewDB.ini (in the <windir> directory) you will find the name of the SQL Server service under the entry DbService and the name of the SQL Server Agent service under the entry DbAgent. 2. Open a command prompt window. Installation under Windows 126

127 3.22 Collecting diagnostics data 3. Check the current recovery settings via the following command: sc qfailure <Service> <Service> Value of the DbService and DbAgent parameters. 4. To get help, type: sc failure 5. To configure the recovery action to automatic restart, type: sc failure <Service> reset= <failureresetperiod> actions= restart/<delay_time>/restart/<delay_time>/restart/<delay_ time> You must include a space after the equal sign (=). 3. You can activate a two-way control of the SQL Server and SQL Server Agent services. If both services are started and one of them fails, this service will be restarted by the other one. Configuration in SQL Server Management Studio: 1. In Object Explorer, connect to Database Engine and Server name, and then expand that instance. 2. Right-click SQL Server Agent, and then select Properties from the context menu. 3. On the General page, check Auto restart SQL Server if it stops unexpectedly and Auto restart SQL Server Agent if it stops unexpectedly and then click OK Collecting diagnostics data After Operations Manager is installed on the central management station, the CmsCollect.bat script is available in the directory Programs - Fujitsu - ServerView Suite. This script allows you to collect various diagnostics data (e.g. information about the web server used by ServerView Operations Manager, ServerView Services, log files). For diagnostic purposes you can send this file to your Fujitsu Customer Service Desk. To collect the data, proceed as follows: 1. Switch to the directory Programs - Fujitsu - ServerView Suite. 2. To start the collection double-click the file CmsCollect.bat. The result of the collection is stored in the zip file cmscollect.zip in the directory...\serverview Suite\svom\data. Installation under Windows 127

128 3.23 ServerView Status gadget for Windows ServerView Status gadget for Windows 7 If Windows 7 is installed on a standard PC, a ServerView status gadget is offered. This gadget allows you to display the number of servers in the different status situations. Via a link you can start ServerView Operations Manager. Installation You can install the gadget in one of the following ways: Double-click the StatusGadget.gadget file. This file is located on the ServerView Suite DVD 2 in the following directory: SVSSoftware\Software\ServerView\Windows\ServerView_S2\StatusGadget Via the ServerView Suite DVD 2. Execute the file StatusGadget.gadget. This file is located under ServerView Suite Operations Manager. If the status gadget is already installed, you will be asked whether you want to replace the current version. Configuration After installation the following dialog is displayed: Figure 17: ServerView status gadget - start dialog For connecting to a ServerView Operations Manager installation (on a central management station) you need to enter the corresponding URL. By clicking the tool icon (see figure above) you start the SV Status Gadget dialog to enter the URL. Installation under Windows 128

129 3.23 ServerView Status gadget for Windows 7 Figure 18: SV Status Gadget dialog After this, the name of the central management station is displayed as a link in the status gadget (see figure below). Via this link you can start ServerView Operations Manager which is located on this central management station. Figure 19: ServerView status gadget The icons identifies the status of the servers. The meaning of the icons is explained in the "ServerView Operations Manager" user guide. Opening the status gadget If you have closed the gadget, you can reopen it as follows: 1. Right-click anywhere on the desktop. 2. Select Gadget. 3. On the displayed gadget overview, select the ServerView status gadget. 4. Select Add from the context menu. Installation under Windows 129

130 3.23 ServerView Status gadget for Windows 7 After reopening the gadget, you will need to configure it again, see "Configuration" on page 128. Opening multiple status gadgets You can open more than one status gadget. This allows you to display the number of servers in the different status situations from different central management stations. Uninstalling the status gadget To uninstall the gadget proceed as follows: 1. Right-click anywhere on the desktop. 2. Select Gadget. 3. On the displayed gadget overview, select the ServerView status gadget. 4. Select Uninstall from the context menu. Installation under Windows 130

131 4.1 Configuration file ServerViewDB.ini 4 ServerView database Operations Manager requires an SQL database in an SQL Server. You can use SQL Server versions 2008 / 2008 R2 / 2012 and Both Express edition and full editions are supported, depending on your system and installation requirements (see"installation options for SQL Server" on page 33). It is recommended that you always use the current service pack. SQL Server 2014 Express is supplied with the Operations Manager software. 4.1 Configuration file ServerViewDB.ini The configuration file ServerViewDB.ini contains, among other things, information about the SQL Server instance, installation paths and the path names of the log files. The configuration file is located in the directory %windir%. You must not modify the ServerViewDB.ini file. Sometimes you may need information from this file to execute some actions. 1. Press the Windows Logo key + [R]. 2. Enter the text %windir% in the Open field. 3. Click OK. A Windows Explorer window opens. 4. Scroll to the ServerViewDB.ini file and open it. Installation under Windows 131

132 4.1 Configuration file ServerViewDB.ini Figure 20: Example of an *.ini file Important entries in the ServerViewDB.ini configuration file You will find the following important entries in the ServerViewDB.ini configuration file: Instance name of the database server: entry Server_Instance This entry must be specified for <SQL Server_Instance> Path for the database backup files: entry DbBackupPath Backup mode for the database: entry DbBackupMode SQL Server version: entry DbServerVersion SQL Server edition: entry DbServerEdition Accounts: entries InstallationAccount, SqlServerViewServicesAccount, SqlServerViewDownloadServiceAccount Whether Operations Manager was installed on an SQL Server configured with enhanced security: entry SqlServerWithEnhancedSecurity Installation under Windows 132

133 4.2 Connection to the ServerView database is interrupted 4.2 Connection to the ServerView database is interrupted If the connection to the ServerView database is interrupted, e.g. in the case of LAN problems, the following occurs: The ServerView Services service and, if present, the ServerView Download Service service are stopped. A message (see figure below) is written to the Windows event log. If Operations Manager is running, the following screen is displayed: Figure 21: Error message Once the connection to the ServerView database has been restored, the services ServerView Services and ServerView Download Service must be restarted manually: 1. Select Administrative Tools Services. 2. Select the relevant service. 3. Select Start from the context menu. 4.3 Managing the ServerView database The following programs are available for managing the ServerView database on SQL 2014/2012/2008. The description for SQL Server 2008 also applies to SQL Server 2008 R2 in this manual. SQL Server Management Studio (Basic) for SQL Server 2014/SQL Server 2012/SQL Server Management Studio (Basic) for SQL Server 2008 Graphical program. With the Enterprise/Standard/Workgroup Edition, this is a component of SQL Server and can be found on the Microsoft SQL Server installation DVD. For SQL Server 2014 Express/SQL Server 2012 Express and SQL Server 2008 Express, there are edition variants that already contain a basic version of SQL Server Management Studio (SQL Server 2014/2012/2008 Express with Tools, SQL Server 2014/2012/2008 Express with Advanced Services). The basic versions of the Management Studio can also be downloaded from the Internet separately as Installation under Windows 133

134 4.4 Backing up the ServerView database installation packages and installed additionally or later. With a later installation, make sure you use the current service pack. sqlcmd The command line program sqlcmd is available after installation of SQL Server full edition. For management of the ServerView database, the SQL Server instance must be registered in the programs. In the configuration file ServerViewDB.ini (in the <windir> directory) you will find the entry for the SQL Server instance under Server_Instance=<SQL Server instance>. SQL Server Management Studio (Basic/Express) To enter the SQL Server instance, proceed as follows: 1. Start Microsoft SQLServer <version> SQL Server Management Studio (Express). 2. In the Connect to Server dialog, select the server type Database Engine. For the server name, select the instance name of the SQL Server. 3. Click Connect. sqlcmd To connect the SQL Server instance, proceed as follows: 1. Open the input prompt. 2. Enter the following command: sqlcmd -S <SQL Server instance> -E 4.4 Backing up the ServerView database The ServerView database ServerViewDB is automatically backed up at regular intervals by backup jobs entered during the installation. Please note: Adjust the backup jobs for automatic backup of the ServerView database to the times when your system is running. The backup jobs will only be performed if the system is running. In the backup mode advanced the backup jobs JobServerViewHourly and JobServerViewLongInterval not only take care of the backup but also ensure that the ServerView database does not grow too big. In the backup mode advanced this backup jobs must be performed automatically from time to time. The backups are performed online. The database services MSSQL$SQLSERVERVIEW or MSSQLSERVER (for SQL Server 2014 /2012/2008: SQL Server (SQLSERVERVIEW) or SQL Installation under Windows 134

135 4.4 Backing up the ServerView database Server (MSSQLSERVER)) continue to run and the ServerView database remains accessible during the backup Backup jobs for the ServerView database During the installation of Operations Manager you could select the SQL server backup mode typical or advanced. In the ServerViewDB.ini configuration file (in the <windir> directory) you will find the selected backup mode under the entry DbBackupMode. If you selected the backup mode typical during installation, you will have the backup job JobServerViewDaily. This job backs up the ServerView database every day, overwriting the previous day s backup. If you select the backup mode advanced, the following backup jobs will be available: JobServerViewDaily Backs up the database every day, appending each backup to the previous day s. JobServerViewHourly Backs up the transaction log every hour. JobServerViewLongInterval Backs up the database once a week, overwriting all previous backups. Overview of the differences between backup modes: Backup mode typical SQL Server recovery model simple full Maximum data loss The data entered during one day Frequency of backups Once a day Hourly Overhead for monitoring the backup jobs (see "Editing and tracking the progress of the backup jobs" on page 137) Low Backup mode advanced The data entered during one hour Higher Disk space usage Lower Higher Define a suitable execution time for the backup jobs when the system is normally running. If you selected advanced backup mode, you should check from time to time whether the backup jobs JobServerViewHourly and JobServerViewLongInterval are being executed, to prevent the log file ServerViewDB_log.LDF from getting too big. If the file is growing rapidly, reduce its size, see "Growth of the ServerViewDB_log.LDF file" on page 155 and Installation under Windows 135

136 4.4 Backing up the ServerView database follow the steps in the following paragraphs ("Requirements for executing jobs" on page 136 to "Checking the contents of the backup files" on page 141). The log file ServerViewDB_log.LDF is also generated in typical backup mode. It is automatically reduced in this mode, but not backed up. As well as backing up the ServerView database onto hard disk, you should also save it to external media at regular intervals. Under Windows, use the backup program Administrative Tools - Windows Server Backup on Windows Server 2012/2016 and Start All Programs Accessories System Tools Backup on Windows Server Requirements for executing jobs For jobs to be executed, the following services must be running and the start type must be set to Automatic in Administrative Tools Services: For SQL Server Express Task Scheduler. For SQL Server Enterprise/Standard/Workgroup Edition the SQL Server agent SQL Server Agent (MSSQLSERVER) for unnamed instances. For SQL Server Enterprise/Standard/Workgroup Edition the SQL Server agent SQL Server Agent (<INSTANCE NAME>) for named instances. For the full versions of SQL Server you can list and manage the SQL Server Agent Services via Program Files Microsoft SQL Server <SQL Server version> Configuration Tools SQL Server Configuration Manager: In the ServerViewDB.ini configuration file (in the <windir> directory) you will find the name of the SQL Server agent under the entry DbAgent. For the Express editions of SQL Server there is no SQL Server agent. Job management is described in "Editing and tracking the progress of the backup jobs" on page 137. Installation under Windows 136

137 4.4 Backing up the ServerView database Editing and tracking the progress of the backup jobs Editing and tracking via a database management tool for full versions of SQL Server (not SQL Server Express) To view the schedule for the backup jobs, proceed as follows: 1. Start the SQL Server Management Studio. 2. Click the SQL Server instance and then select the entry SQL Server Agent. 3. Then click Jobs. 4. Select the appropriate backup job and then select Properties from the context menu. In SQL Server Management Studio you can display the progress details for each job: 1. Under SQL Server Agent Jobs, select all jobs or a specific one. 2. Select View History from the context menu. 3. Select Properties from the context menu. 4. In the properties window select the Schedules link to adjust the schedule of a job if necessary. 5. Then click Edit. Adjust the schedule in the displayed window, by selecting an execution time for the job when the system is normally running. Editing and tracking via Windows Explorer or task scheduler for SQL Server Express editions With SQL Server Express, the backup and maintenance jobs cannot be managed via SQL Server agent. This component does not exist for SQL Server Express. The jobs are set up via the Windows Task Scheduler and therefore can only be monitored via this component. Windows Server 2016/2012/ In Administrative Tools select the entry Task Scheduler. 2. In the middle window, scroll down to the entry Task Status. Installation under Windows 137

138 4.4 Backing up the ServerView database 3. Double-click one of the JobServerView jobs. All ServerView jobs are shown in the middle window. 4. Click the History tab to view the progress of the job. 5. In the top part of the window, select a JobServerView job. 6. Select Properties from the context menu, followed by the Trigger tab. 7. Click Edit and adjust the schedule, by selecting an execution time for the job when the system is normally running. Tracking via Event Viewer on all editions of SQL Server To view the scheduled execution of the database backup jobs, Windows Event Viewer can be applied as follows: 1. Select Administrative Tools Event Viewer. 2. Select Windows Log. 3. Select Application. The following table shows the entries in the Windows Application Event Log written during the regular execution of the backup jobs dependent on the used SQL Server. For SQL Server Express: Column Source Column Event ID MSSQL$SQLSERVERVIEW MSSQL$SQLSERVERVIEW Description Database backed up. Database: ServerViewDB, pages dumped:, MEDIANAME='ServerViewDB': {'ServerViewDBData'}). This is an informational message only. No user action is required. Windows Task Scheduler Job 'JobServerView ' invoked. For SQL Server Enterprise/Standard/Workgroup Edition (in case of remote SQL Server track on the remote SQL Server machine): Column Source Column Event ID Description SQLSERVERAGENT or 208 SQL Server Scheduled Job 'JobServerView ' - Status: SQLAgent$Instancename Succeeded -. MSSQLSERVER or MSSQL$Instancename You can create a filter for selective tracking. Database backed up. Database: ServerViewDB,, pages dumped:, MEDIANAME='ServerViewDB': {'ServerViewDBData'}). This is an informational message only. No user action is required. Installation under Windows 138

139 4.4 Backing up the ServerView database Checking the existence of backup files The ServerView database is backed up at regular intervals. This creates two files with the suffix.bak: ServerViewDBData.bak Backup file of the ServerView database. ServerViewDBLog.bak Backup file of the transaction logs of the ServerView database. This is only created in advanced backup mode. In the ServerViewDB.ini configuration file (in the <windir> directory) you will find the path of the files at the time of installation under the entry DbBackupPath, and the setting for the backup mode under DbBackupMode. Installation under Windows 139

140 4.4 Backing up the ServerView database The following applies only for installation with a remotely installed SQL Server instance: During installation of the Operations Manager software, you can specify the path for the backup files on the remote SQL Server in the SQL Server Backup Path window. If you do not specify a path or if you executed an "Operations Manager installation without SQL Server "sysadmin" access" and the installation account does not have the server role "diskadmin", the backup files will be created in the SQL Server default path. In this case the configuration file ServerViewDB.ini (in the <windir> directory) contains the entry default for DbBackupPath. Default path for SQL Server 2008 (named instance): \Program Files\Microsoft SQL Server\MSSQL10.<Instancename>\MSSQL\Backup Default path for SQL Server 2008 (unnamed instance): \Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup\ Default path for SQL Server 2008 R2 (named instance): \Program Files\Microsoft SQL Server\MSSQL10_ 50.<Instancename>.MSSQLSERVER\MSSQL\Backup\ Default path for SQL Server 2008 R2 (unnamed instance): \Program Files\Microsoft SQL Server\MSSQL10_ 50.MSSQLSERVER\MSSQL\Backup\ Path if the instance was upgraded from SQL Server or MSDE 2000: \Program Files\Microsoft SQL Server\MSSQL$SQLSERVERVIEW\BACKUP\ Default path for SQL Server 2012 (named instance): \Program Files\Microsoft SQL Server\MSSQL11.<Instancename>\MSSQL\Backup\ Default path for SQL Server 2012 (unnamed instance): \Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\ Default path for SQL Server 2014 (named instance): \Program Files\Microsoft SQL Server\MSSQL12.<Instancename>\MSSQL\Backup\ Default path for SQL Server 2014 (unnamed instance): \Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Backup\ The path name is also displayed in SQL Server Management Studio. Installation under Windows 140

141 4.4 Backing up the ServerView database SQL Server Management Studio 1. Start SQL Server Management Studio. 2. In the Connect to Server dialog, select the server type Database Engine and the server name <SQL Server_Instance>. 3. Click Connect. 4. Then in the Object Explorer select the entry Server Objects. 5. Click Backup Devices. 6. Select ServerViewDBData and then select Properties from the context menu. 7. The path name for the ServerView database backup file is displayed below the Destination field. 8. If you are using advanced backup mode, you can find out the path name for the transaction logs via Backup Devices ServerViewDBLog Properties. The path name for the backup file of the transaction logs is displayed below the Destination field. If you are using a remote SQL Server instance and nothing was specified for SQL Server Backup Path during the installation, you can set up the following: 1. Click Backup Devices. 2. Select New Backup Device... from the context menu. 3. Under Device name enter ServerViewDBData. 4. Click OK. If you are using advanced backup mode, repeat these steps for the backup file ServerViewDBLog Checking the contents of the backup files You can check what the backup jobs have written to the backup files. You can also view the number of data records etc. in the backup files. If you are using a remote SQL Server instance, you can do the check if the backup media ServerViewDBData and ServerViewDBLog are displayed in the Management Studio. Otherwise you can set them up as described above and then proceed with the contents check. You have the following options for the check: 1. Start SQL Server Management Studio (Express): 2. Click the SQL Server instance. 3. Click Server Objects. 4. Click Backup Devices. 5. Select a backup device. Installation under Windows 141

142 4.5 Restoring the ServerView database 6. Select Properties from the context menu. 7. Select the Media Contents tab. By advanced backup mode please check from time to time that the device ServerViewDBLog only contains one week s worth of records. When a week has passed, ServerViewDBLog must be overwritten from the beginning. If this is not done, the backup job JobServerViewLongInterval did not run. In this case, start the backup job JobServerViewLongInterval. This causes the *.bak files to be reduced. If the log file ServerViewDB_log.LDF has grown very big, reduce its size as described in "Growth of the ServerViewDB_log.LDF file" on page 155. For permanent, automatic execution of backups and reduction of file size, follow the steps described in "Requirements for executing jobs" on page 136 and the subsequent sections. 4.5 Restoring the ServerView database In the event of an error, you can restore the ServerView database from the backups. If you detect any errors during the process, you can restart the restoration from the beginning. For the restoration, you must first read in the database backup and then, if available, one or more transaction log backups. Backups of transaction logs are available if, in the ServerViewDB.ini file (in the <windir> directory), the entry DbBackupMode is set to advanced. For information on the directory for the database backup, see "Checking the existence of backup files" on page Restoration via SQL Server Management Studio You should only restore the ServerView database from backup files to the same Operations Manager version. The SQL Server version must either be the same or higher on the server where the backup is restored. If you restore to the wrong version, Operations Manager will not work, either immediately or after the next upgrade installation. Please note: Restoring the database requires membership in the "sysadmin" server role of SQL Server. Find out the version of the installed Operations Manager: 1. Select Control Panel Programs and Features. 2. Select Fujitsu ServerView Operations Manager. Installation under Windows 142

143 4.5 Restoring the ServerView database Find out the Operations Manager version in the backup files: 3. Restore the backup files into a test database, see "Checking the database backup " on page 146. Please make sure there is enough disk space, as the files RECOVERYTEST.mdf and RECOVERYTEST.LDF will be created. 4. Start SQL Server Management Studio. 5. Connect to the SQL Server instance. 6. Select Databases RECOVERYTEST. 7. Select Tables dbo._property. 8. Select Open Table or Select Top 1000 rows from the context menu. 9. See row ParentVersion. Is the value in column Value the same as the installed Operations Manager version determined before? If this is true, the first prerequisite for restoring is achieved. Find out the installed SQL Server version: 10. Select the New Query button and type: GO Find out the SQL Server version in the backup files: 11. Select Databases RECOVERYTEST. 12. Select Properties from the context menu. 13. Select Options. In field Compatibility level you see the SQL Server used during backup. 14. If the value is the same or higher than the value in the field Compatibility level the second prerequisite is achieved and restoration can be executed. To restore the ServerView database and, if available, the transaction logs, proceed as follows: 1. Restrict the access to the ServerView database. 1. Start SQL Server Management Studio. 2. Connect with the SQL Server instance and select Databases ServerViewDB. 3. Select Properties from the context menu. 4. Select the Options page and, under Restrict Access, select the entry RESTRICTED_ USER. Click OK followed by YES. 2. The services ServerView Services, ServerView ApplicationService and ServerView Download Service must be stopped: 1. Select Administrative Tools Services. 2. Select the appropriate service and then select Stop from the context. Installation under Windows 143

144 4.5 Restoring the ServerView database 3. Restore from the database backup: 1. Click Databases and then select Restore Databases from the context menu. 2. The Restore Databases window opens: 1. On the General page, enter the name ServerViewDB or msdb in the To database field or select the name from the list. 2. Select the option From device. 3. Click the... button. 4. Add the database backup ServerViewDBData.bak from the appropriate storage location and then click OK. 3. Select the database backup to be restored: In Select the backup sets to restore, click the box in the Restore column. 4. Switch to the Options page. 5. Select the options Overwrite the existing database. 6. If no transaction log backup ServerViewDBLog.bak is available, click OK. Otherwise, select the option Overwrite the existing database and Leave database nonoperational and do not roll back uncommitted transactions. Additional transaction logs can be restored. 7. Click OK and then OK again. Restoration of the database begins. In the Object Explorer you will see the message ServerViewDB (Restoring ). Installation under Windows 144