Installing and Configuring SPI for Terminal Server for OVO/Windows (version 01.00)

1. Installing and ConfiguringSPI for Terminal Serverfor OVO/Windows(version 01.00) HERMES SoftLab d.d. v1.0 September, 2006

2. Contents • Software Requirements • Installation on the Mgmt Server • Verifying Mgmt Server Installation • Configuring Mgmt Server • Deploying Instrumentation • Licensing Managed Nodes • Verifying Requirements andConfiguration • Installing Reports • Verifying Reports Installation on OVO/W / Reporter • Configuring Reports on OVO/W / Reporter • Installing Graphs • Verifying Graphs Installation on OVO/W / OVPM

3. Software Requirements • Microsoft Terminal Server: • Windows 2000 Server family • Windows Server 2003 (+R2) family • Windows Server 2003 x64 (+R2) family NOTE: Microsoft Terminal Server component is a part of Microsoft Windows Server family of operating systems • HP OpenView: • HP OpenView Operations/Unix 7.17/8.1x/8.2x • HP OpenView Reporter 3.50/3.60/3.70 • HP OpenView Performance Manager 5.0/6.0

4. Installation on the Mgmt Server • Login to the Mgmt Server as user administrator • Insert the SPI for Terminal Server installation CD • Install the SPI • If autorun is enabled, a Web page is launched -> click on: SPI for Terminal Server for OVO Windows -> Product packages -> Installation package 01.00 (The package is not signed; thus, IE may issue a warning – just ignore it and allow installation to execute) • If autorun is disabled, start TSSPI_01.00.exe on the CD

5. Verifying Mgmt Server Installation • Node groups under “SPI for Terminal Server” • 4 node subgroups • Tools under group “SPI for Terminal Server” • 54 tools in 21 tool subgroups • Policies under group “SPI for Terminal Server” • 57 policies in 22 policy subgroups • Instrumentation • One new subfolder in folders<InstrumentationDir>\Windows 2000\5.0 and <InstrumentationDir>\Windows Server 2003\5.2: • SPI for Terminal Server

6. Configuration: Deploying Instrumentation • Put nodes under management. Terminal Server SPI is able to manage two node types: • Terminal Server nodes • Terminal Server License Server nodes • Deploy instrumentation • Deploy “SPI Data Collector” and “SPI for Terminal Server” instrumentation to the nodes that you want to manage • Go to “SPI for Terminal Server/TSSPI-Maintenance/TSSPI-Configure” tool group, and execute tool “TSSPI-Register Subagent” against every node that you want to manage.

7. Configuration: Licensing Managed Nodes • IMPORTANT: Instrumentation needs to be deployed to the managed nodes as specified on the previous slide! 1. Deploy the policy group “SPI for Terminal Server/TSSPI-SPI Licensing” to all Terminal Server and Terminal Server License Server nodes. It contains the following policy: • TSSPI-Licensing

8. Configuration: Licensing Managed Nodes • Go to tool group “SPI for Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Licensing” • Run the tool “TSSPI-1. Clear License Request File on Mgmt Server” to clear the tsspi_license_requests.dat license request file on the management server. • Run the tool “2. Generate License Request for Node” on the managed nodes for which you need licenses. In the Edit Parameters dialog box, replace the string “your company name” with the name of your company. Press [OK] to generate the license request.After the tool is executed on all nodes, license requests of all nodes are located on the management server in file<SPI-Share>\tsspi\tsspi_license_requests.dat(e.g.: C:\Program Files\HP OpenView\Data\shared\SPI-Share\tsspi\tsspi_license_requests.dat)

9. Configuration: Licensing Managed Nodes 4. Obtain the tsspi_licact_new.dat license activation file You can obtain the license activation file: • Using the Licensing portal:Go to http://spi.hermes-softlab.com/licensing/, register, and upload the license request file. When registering, have your PO information ready. The system will automatically process your request and send you the license activation file by e-mail.or • Via e-mail: Send the generated license request file by e-mail to the HERMES SoftLab Licensing Department at spi-licensing@hermes.si. You will receive the license activation file usually within 24 hours. If you need immediate response, contact HERMES SoftLab by telephone and e-mail (see contact information on License Entitlement Certificate).

10. Configuration: Licensing Managed Nodes 5. Merge and Deploy the License File • Copy the license activation file tsspi_licact_new.dat to the following directory:<SPI-Share>\tsspi(e.g.: C:\Program Files\HP OpenView\Data\shared\SPI-Share\tsspi) • Run the “3. Merge License Activation Codes on Mgmt Server” tool to merge tsspi_licact_new.dat with the SPI license file. • Deploy the “SPI for Terminal Server” instrumentation to all managed nodes for which you have requested the licenses. • To list license activations on the management server, run the “TSSPI-List License Activation Codes” tool

11. Verifying Requirements and Configuration • From the tool group “SPI for Terminal Server/TSSPI-SPI Maintenance”, run the tool “TSSPI-Check Requirements/Configuration” on all newly configured managed nodes. The tool should report OK status for several items checked. • IMPORTANT: Do not deploy any SPI for Terminal Server monitoring policies to managed node until the above tool reports that the node has been correctly configured!

12. Installing Reports • Reports can be installed on the system with OVO/Windows management server or Reporter product installed • Login to one of the above systems as user administrator • Insert the SPI for Terminal Server installation CD • Install the SPI • If autorun is enabled, a Web page is launched -> click on: SPI for Terminal Server for OVO Windows -> Product packages -> Installation package - Reporter 01.00 (The package is not signed; thus, IE may issue a warning – just ignore it and allow installation to execute) • If autorun is disabled, start TSSPI_01.00-Reporter.exe on the CD

13. Verifying Reports Installationon OVO/W • If installed on OVO/W: • Wait for a day or two for reports to appear underReports & Graphs / Reports / SPI for Terminal Server

14. Verifying Reports Installationon Reporter • The following metric lists should be installed: • TSSPI_LIC • TSSPI_SESS • TSSPI_SESSINFO • TSSPI_SRV • TSSPI_PSLD • TSSPI_PROFILE • TSSPI_PROFILES • 40 reports should be installed under “SPI for Terminal Server” report group

15. Configuring Reports on OVO/W • Nothing needs to be configured in OVO/W – reports will be automatically generated • Reports will be generated only for the following managed nodes: • Terminal Server 5.0 (Windows 2000) managed nodes that have the “TSSPI-TS50 Data Collection” policy group deployed • Terminal Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TS52 Data Collection” policy group deployed • Terminal Server License Server 5.0 (Windows 2000) managed nodes that have the “TSSPI-TLS50 Data Collection” policy group deployed • Terminal Server License Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TLS52 Data Collection” policy group deployed

16. Configuring Reports on Reporter 1/2 • SPI for Terminal Server reports will only be generated for those nodes that are put into the “SPI for Terminal Server” Reporter node group. • The SPI configures a “SPI for Terminal Server” auto-group (File -> Configure -> Auto Groups) to help with that task. • If “SPI for Terminal Server” node group is not generated automatically, you need to create it manually. • Every node when it is first discovered by Reporter, and Reporter detects that node has SPI-related data, automatically inserts the node in this group. • If by any chance this does not happen for some nodes, place them into the “SPI for Terminal Server” Reporter group manually.

17. Configuring Reports on Reporter 2/2 • Reports will be generated only for the following managed nodes: • Terminal Server 5.0 (Windows 2000) managed nodes that have the “TSSPI-TS50 Data Collection” policy group deployed • Terminal Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TS52 Data Collection” policy group deployed • Terminal Server License Server 5.0 (Windows 2000) managed nodes that have the “TSSPI-TLS50 Data Collection” policy group deployed • Terminal Server License Server 5.2 (Windows 2003) managed nodes that have the “TSSPI-TLS52 Data Collection” policy group deployed

18. Installing Graphs • Graphs can be installed on the system with OVO/Windows management server or Performance Manager product installed • On OVO/W, graphs are automatically installed as part of the base SPI for Terminal Server product installation • On Performance Manager, copy the file VPI_GraphsSPI for Terminal Server.txt from the installation CD to the following location: • OVPM on Windows: • <HP OpenView Home>\newconfig\OVPM • OVPM on HP-UX and Solaris: • /opt/OV/newconfig/OVPM/

19. Verifying Graphs Installation • On OVO/W, SPI for Terminal Server graphs should be located under Reports & Graphs / Graphs / SPI for Terminal Server graph family. • On Performance Manager, click the Display tab. In the right pane you will see the main SPI for Terminal Server graph family. • In order for graphs to show data, the corresponding data collection policies need to be deployed to Terminal Server and Terminal Server License Server systems (see Reports section for details).