Introduction VITAL SIGNS FROM SAVISION / FAQS Savision B.V. savision.com All rights reserved.

Transcription

1 Rev 2.6.0

2 Introduction 2 VITAL SIGNS FROM SAVISION / FAQS 2014 Savision B.V. savision.com All rights reserved. This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Savision B.V. Savision B.V. assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without prior written permission of Savision B.V. Any references to company names, organizations, persons, or places are for demonstration purposes only and are not intended to refer to any actual company, organization, person or place. Copyrighted and/or trademarked materials remain the property of their respective owners. REVISION NUMBER: 2.6.0

3 Introduction 3 Contents 1 Introduction Related Documentation Document Conventions Contacting Savision Requirements What are the System Requirements for the Client? What are the System Requirements for the Server? Permissions What Permissions are Required for the Windows Server Dashboard? Granting the DCOM Permission Granting the WMI Permission Granting Registry Read Access Granting Event Log Read Access What Permissions are Required for the SQL Server Dashboard? What Permissions are Required for the Hyper-V Server Dashboard? What Permissions are Required for the Exchange Server Dashboard? Firewall What Ports Must Be Open Between the Vital Signs Client and the Vital Signs Server? What Ports Must Be Open for the Windows Server Dashboard? What Ports Must Be Open for the SQL Server Dashboard? What Ports Must Be Open for the Hyper-V Server Dashboard? What Ports Must Be Open for the Exchange Server Dashboard? Required Services... 16

4 Introduction 4 1 INTRODUCTION This guide answers Frequently Asked Questions (FAQs) regarding Vital Signs, release from Savision. The content herein is intended for system administrators responsible for the implementation, configuration and upkeep of enterprise-class IT systems. The document is organized as follows: Chapter 1, Introduction, provides the scope and purpose of the document. Chapter 2, Requirements, provides information about the software necessary to use Vital Signs. Chapter 3, Permissions, covers access rights required to use Vital Signs. Chapter 4, Firewall, discusses firewall and networking considerations. Chapter 5, Required Services covers the services that must be running on target systems. 1.1 RELATED DOCUMENTATION Other documents available in regard to Vital Signs include the following: Vital Signs Installation Guide provides the procedures to install the Vital Signs product. Vital Signs Quick Start Guide provides essential instructions to get Vital Signs up and running quickly. 1.2 DOCUMENT CONVENTIONS The following conventions are used throughout the document: Application Elements Window names, field labels, links, and other user interface (UI) elements are italicized. Code Samples Scripts, program source code, configuration files and the like are handled in this fashion: AddObjectProperty attributemap {element: value, element: value} End-user Entry Things you type including user names, passwords, responses and commands are shown in bold. Notes Notes and observations are emphasized as follows: Note: you can also use CTRL-Q to quit.

5 Introduction 5 Warnings Warnings convey limits, ramifications, negative impacts or other important information as follows: Warning: do not close the window before the process ends. 1.3 CONTACTING SAVISION For additional information, go to or support@savision.com.

6 Requirements 6 2 REQUIREMENTS 2.1 WHAT ARE THE SYSTEM REQUIREMENTS FOR THE CLIENT? The Vital Signs client can run in any browser that supports Silverlight 4. Download Silverlight 4 from: WHAT ARE THE SYSTEM REQUIREMENTS FOR THE SERVER? The Vital Signs server runs on the Windows Operating System running Internet Information Services (IIS) 7.0 or greater. The Microsoft.NET Framework 4.0 and the Visual C Runtime Libraries are also required. Download the Microsoft.NET Framework 4.0 from: Download the Visual C Runtime Libraries from one of these locations: x86 x D5867

7 Permissions 7 3 PERMISSIONS 3.1 WHAT PERMISSIONS ARE REQUIRED FOR THE WINDOWS SERVER DASHBOARD? By default, accounts with Administrator rights already have the permissions necessary to collect data needed by the Windows Server dashboard. For other users, the following permissions are required: DCOM Launch and Activation Permissions WMI root/cimv2 Namespace Access Registry Read Access Event Log Read Access Follow the steps below to grant these rights GRANTING THE DCOM PERMISSION This section shows how to grant the DCOM Launch and Activation right to non-administrative user accounts. The steps in this section should be performed on the target system(s) to be monitored. (1) Run dcomcnfg.exe. Expand Component Services. Expand Computers. Right-click My Computer, then click Properties.

8 Permissions 8 (2) Click the COM Security tab. Click Edit Default in the Launch and Activation Permissions section. (3) Grant the target user the Launch and Activation permissions. Click OK.

9 Permissions GRANTING THE WMI PERMISSION This section shows how to grant the WMI Namespace access right to non-administrative user accounts. The steps in this section should be performed on the target system(s) to be monitored. (1) Run wmimgmt.msc. Right-click WMI Control, then click Connect to another computer. (2) Type the target system s name, then click OK. (3) Right-click WMI Control, then click Properties. Click the Security tab.

10 Permissions 10 (4) Navigate to the Root/CIMV2 namespace. Click the Security command button. (5) Grant the target user the Enable Account and Remote Enable permissions. Click OK GRANTING REGISTRY READ ACCESS This section shows how to grant Registry Read access to non-administrative user accounts. The steps in this section should be performed on the target system(s) to be monitored.

11 Permissions 11 (1) Run regedit.exe. Click File on the main menu. Click Connect Network Registry. (2) Type the target system s name, and then click OK. Click HKEY_LOCAL_MACHINE. Click Edit on the main menu. Click Permissions. (5) Grant the target user Read permissions. Click OK GRANTING EVENT LOG READ ACCESS This section provides information regarding granting Event Log Read access to non-administrative user accounts. The steps in this section should be performed on the target system(s) to be monitored.

12 Permissions 12 A user can be granted Event Log Read Access locally or by using Group Policy. The following Microsoft Support article outlines how to set these permissions on Windows Server 2003: WHAT PERMISSIONS ARE REQUIRED FOR THE SQL SERVER DASHBOARD? In addition to the permissions required for the Windows Server dashboard, the following specific permissions are required for the SQL Server dashboard: db_datareader SQL Security Role Grant a user account this SQL security role by executing the following SQL query: EXEC sp_addrolemember db_datareader, <username> where <username> is the user account to receive the role. 3.3 WHAT PERMISSIONS ARE REQUIRED FOR THE HYPER-V SERVER DASHBOARD? In addition to the permissions required for the Windows Server dashboard, the following specific permissions are required for the Hyper-V Server dashboard: PowerShell Remoting is enabled PowerShell Remoting can be enabled during the connection registration process within Vital Signs. Refer to the Vital Signs Quickstart Guide for more detailed information. 3.4 WHAT PERMISSIONS ARE REQUIRED FOR THE EXCHANGE SERVER DASHBOARD? In addition to the permissions required for the Windows Server dashboard, the following specific permissions are required for the Exchange Server dashboard: PowerShell Remoting is enabled PowerShell Remoting can be enabled during the connection registration process within Vital Signs. Refer to the Vital Signs Quickstart Guide for more detailed information.

13 Firewall 13 4 FIREWALL 4.1 WHAT PORTS MUST BE OPEN BETWEEN THE VITAL SIGNS CLIENT AND THE VITAL SIGNS SERVER? The port used for communication between the Vital Signs Client and Server is specified during the installation. By default, this port is 443. This section shows how to check which port is being used by Vital Signs. (1) Run inetmgr.exe. In the left-side tree view, expand the top level server. Expand Sites. (2) Find the web site hosting Vital Signs.

14 Firewall 14 (3) Right-click the web site hosting Vital Signs. Click Edit Bindings. The Edit Bindings window shows the ports used by the web site. Document the ports for use in configuring the firewall. 4.2 WHAT PORTS MUST BE OPEN FOR THE WINDOWS SERVER DASHBOARD? The Windows Server dashboard requires remote WMI access to the target system. The requirements are: port 315 (for remote WMI) A port between 1024 and 5000, assigned by the machine running the Vital Signs server component, used to connect to WMI on the target system. port 445 (for Registry and Event Log data collection) 4.3 WHAT PORTS MUST BE OPEN FOR THE SQL SERVER DASHBOARD? In addition to the ports required for the Windows Server dashboard, ports specific to SQL Server must also be opened. By default, SQL Server uses port However, a different port may be used. Refer to the following knowledgebase article for more information: WHAT PORTS MUST BE OPEN FOR THE HYPER-V SERVER DASHBOARD? In addition to the ports required for the Windows Server dashboard, ports specific to Hyper-V Server must also be opened. PowerShell Remoting is used and by default, port 5985 is used for this communication.

15 Firewall WHAT PORTS MUST BE OPEN FOR THE EXCHANGE SERVER DASHBOARD? In addition to the ports required for the Windows Server dashboard, ports specific to Exchange Server must also be opened. PowerShell Remoting is used and by default, port 5985 is used for this communication.

16 Required Services 16 5 REQUIRED SERVICES The following services must be running on a target system for Vital Signs to successfully connect and collect data from that system: Netlogon Remote Registry RPC Endpoint Mapper Windows Management Instrumentation Windows Remote Management (required for Hyper-V Server and Exchange Server)