Dynatrace Network Analyzer

Dynatrace Network Analyzer Installation Guide Release 12.3.0

Please direct questions about Dynatrace Network Analyzer or comments on this document to: Customer Support https://community.compuwareapm.com/community/display/support Copyright 2014 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at https://community.compuwareapm.com/community/display/apmdoc. Adobe Reader is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners. Local Build: December 8, 2014, 16:08

Contents Contents Chapter 1 Dynatrace Network Analyzer System Requirements.............. DNA System Requirements........................................... DNA Console Hardware Requirements................................. DNA Console Operating System Compatibility........................... DNA Console Other Software Requirements............................. Additional DNA System Recommendations.............................. Agent System Requirements........................................... Windows DNA Agent System Requirements............................. Unix Dynatrace Network Analyzer Agent System Requirements............... Database Requirements.............................................. Configuring an Existing SQL Server Installation.......................... Enabling TCP/IP............................................... Enabling SQL Server Browser...................................... Enabling Server Authentication..................................... Changing Service Account to Local System............................ Migrating Existing Databases........................................ Restricting SQL Service............................................ Chapter 2 Installation.............................................. Console Installation................................................. Task Duration Estimates............................................ Upgrading Existing Console Installations................................ Installing SQL Server Management Studio Express........................ Migrating Existing Databases........................................ Installing Dynatrace Network Analyzer Console.......................... Disabling Network Task Offload...................................... Enabling Add-on for Internet Explorer.................................. Adding a Windows Firewall Exception for Mongoose...................... User Accounts and Administrative Rights............................... Running Dynatrace Network Analyzer for the First Time.................. Managing User Access Rights with AVUsers Group Membership............ DNA and VMware................................................ Installing Missing Certificates for DNA Installation........................ 7 7 7 8 8 9 9 10 11 15 15 16 16 16 17 17 18 19 19 20 20 20 21 21 24 25 25 25 26 27 27 29 3

Contents Trace Trimmer Configuration from Windows Control Panel.................. Agent Installation................................................... Administrator Installation Options..................................... Creating an Encrypted User Credentials File for Silent Agent Installations........ Agent Installation on Windows Machines............................... Installing a Windows Dynatrace Network Analyzer Agent................. Remote Installation of Dynatrace Network Analyzer Agent on Windows....... Sample Dynatrace Network Analyzer Agent Installation Scripts............. Agent Installation on UNIX Machines.................................. Installing a Unix or Linux Dynatrace Network Analyzer Agent.............. Listing the Unix Dynatrace Network Analyzer Agent Files................. Configuring a Solaris Zone to Run an Agent........................... DNA Agent Technical Notes......................................... Installing a Compuware Certificate.................................. Enabling Add-on for Internet Explorer................................ Configuring a Solaris Zone to Run an Agent........................... DNA Simple Capture Installation....................................... Installing and Running Simple Capture................................. Configuring Simple Capture......................................... Chapter 3 Licensing Dynatrace Network Analyzer........................ Understanding Dynatrace Network Analyzer Licensing....................... Distributed License Management (DLM)................................ Compuware License Service......................................... Node-locked Licensing............................................. Concurrent Licensing.............................................. Setting Up and Using Node-Locked Licensing.............................. Obtaining a Node-locked License..................................... Installing a Node-locked License...................................... Setting Up and Using Standard Concurrent Licensing......................... Determining Need for Compuware License Service........................ Setting Up Compuware License Service................................ Obtaining a Concurrent License...................................... Using Dynatrace Network Analyzer with Concurrent Licensing............... Freeing Licenses for Other Users...................................... Borrowing a License............................................... Returning a Borrowed License....................................... Chapter 4 DNA Silent Installations................................... DNA Console Installation Command Syntax............................... Dynatrace Network Analyzer Console Upgrade Command Syntax............... Dynatrace Network Analyzer Agent Installation Command Syntax............... Creating an Encrypted User Credentials File for Silent Agent Installations.......... Installing a Compuware Certificate...................................... Performing a Silent Agent Installation.................................... Dynatrace Network Analyzer Agent Upgrade Command Syntax................. 29 30 30 31 32 32 34 34 35 35 36 37 38 39 40 40 41 41 42 47 47 47 48 48 48 48 49 49 50 50 51 51 51 52 52 53 55 56 59 60 62 63 63 64 4

Contents Chapter 5 Uninstallation........................................... Console Uninstallation - Interactive...................................... Console Uninstallation - Silent......................................... Windows Agent Uninstallation......................................... Windows Agent Uninstallation - Silent................................... Unix Agent Uninstallation............................................ Chapter 6 Troubleshooting Installation Problems........................ Index........................................................... 65 65 66 66 67 67 69 73 5

Contents 6

CHAPTER 1 Dynatrace Network Analyzer System Requirements Be sure to review the following requirements and recommendations before installing Dynatrace Network Analyzer (DNA) console or agent software. NOTE The term console refers to the main DNA software that is installed on a Windows machine, probably on your own desktop. You use the DNA console software to analyze application traffic data you have gathered from the network. The term agent refers to the Dynatrace Network Analyzer Agent software that you install on various Windows or Unix machines carrying the network traffic you want to analyze. You use DNA agents to gather data from various points in your network and use the DNA console software to correlate and analyze this data. DNA System Requirements The following are the minimum system requirements for the Dynatrace Network Analyzer console and agent. DNA Console Hardware Requirements The following are minimum hardware requirements for the DNA console. Pentium III processor, 1.4 GHz 2 GB RAM We recommend the following basic system: Intel Core 2 duo, 2.13 GHz 3 GB RAM Additional hardware minimum requirements: 2 GB hard disk space; 4 GB hard disk space for LAN Gigabit 7

Chapter 1 Dynatrace Network Analyzer System Requirements Video card and monitor (at least 16-bit color and 1024x768 bit or higher screen resolution) Ethernet (10 Mbps, 100 Mbps, or 1 Gbps), use enhanced-mode 32-bit NDIS 3.0 or higher-compatible promiscuous mode network cards. DNA Console Operating System Compatibility The Dynatrace Network Analyzer console software can run on any of the following Microsoft Windows versions. Windows Server 2008 (32-bit and 64-bit versions) with Service Pack 2 Windows Server 2008 R2 (64-bit version) with Service Pack 1 Windows 7 (32-bit and 64-bit versions) with Service Pack 1 Windows 8 (32-bit and 64-bit versions) Windows 8.1 (32-bit and 64-bit versions) Windows Server 2012 Windows Server 2012 R2 NOTE All platforms should have version 3.1 of the Windows Installer. If you are not running automatic Windows updates, you can find the Windows 3.1 Installer at http://update.microsoft.com/ and on the Dynatrace Setup browser Utilities tab. DNA Console Other Software Requirements The following are other software requirements for the DNA console. Microsoft Internet Explorer 9.0 or later is required for full DNA functionality. Compatibility Mode is not supported. No tablet or smart phone browsers are supported. You can use the latest stable release of Mozilla Firefox or Google Chrome for most DNA functionality, but be aware that the Browser Data Collection (BDC) add-in works only with Microsoft Internet Explorer. To use BDC, Internet Explorer must permit third-party browser extensions to operate. By default, Windows 2008 Server does not do so. To change this setting: 1. Open Internet Explorer. 2. Select Tools Internet Options. 3. Click the Advanced tab. 4. Under Browsing, select Enable third-party browser extensions and click OK. 5. Restart Internet Explorer. To use the Transaction Expert tool, one of the following versions of Microsoft Word must be installed: Microsoft Word 2007 8

Chapter 1 Dynatrace Network Analyzer System Requirements Microsoft Word 2010 Microsoft Word 2013 One of the SQL Server versions listed below must be installed and running prior to running Dynatrace Network Analyzer. SQL Server 2005 Express SQL Server 2005 SQL Server 2008 Express SQL Server 2008 SQL Server 2008 R2 SQL Server 2012 Express SQL Server 2012 If none of these are detected on your machine during installation, the Dynatrace Network Analyzer installer offers to install SQL Server Express. Migration tools are provided with Dynatrace Network Analyzer to migrate your existing databases. Dynatrace Network Analyzer currently is designed to support a dedicated per-user database and requires exclusive-use locks at the database level. Additional DNA System Recommendations The following are recommendations (not requirements) for improving processing on the Windows machine on which you have installed the DNA console software. Increase the amount of RAM in your system. Install a faster processor. Install the Dynatrace Network Analyzer database on an SSD disc. Install your Dynatrace Network Analyzer database locally; performance may significantly degrade when using a remote database. Do not run other applications on your system when you are capturing traffic on the Dynatrace Network Analyzer console. Do not use a PCMCIA network adapter card in a 100 Mbps environment. Recommendations When Using Unattended Capture Mode A dedicated computer is recommended when using Unattended Capture Mode. Network traffic volume varies greatly depending on the network. The amount of this traffic affects the size of the hard disk you need. If you plan to use disk caching, your agents require a large amount of RAM and a large amount of free hard disk space. Agent System Requirements The Dynatrace Network Analyzer Agent can be installed on a variety of Windows and Unix/Linux platforms. 9

Chapter 1 Dynatrace Network Analyzer System Requirements Windows DNA Agent System Requirements The following are system requirements for a Windows machine running this release of DNA Agent software. IMPORTANT The Windows version of the DNA Agent software is designed to run on Windows systems as described below. The agent will not function on an Itanium system. Operating System Requirements A Windows system must have one of the following operating system versions to run the DNA Agent software: Windows Server 2008 (32-bit and 64-bit versions) with Service Pack 2 Windows Server 2008 R2 (64-bit version) with Service Pack 1 Windows Server 2008 R2 Server Core Windows 7 (32-bit and 64-bit versions) with Service Pack 1 Windows 8 (32-bit and 64-bit versions) Windows 8.1 (32-bit and 64-bit versions) Windows Server 2012 Windows Server 2012 R2 Windows Server 2012 Server Core Windows Server 2012 R2 Server Core Minimum Hardware Requirements Following are the minimum system requirements for the DNA Agent. IBM or compatible PC with Pentium III 1.2 GHz or faster processor 1 GB RAM Hard disk space: A minimum of 35 MB of available hard disk space is required for temporary storage. For Unattended Capture Mode, you may need more disk space. We recommend 2 GB. NIC Ethernet (10 Mbps, 100 Mbps or 1 Gbps), use enhanced-mode 32-bit NDIS 3.0 or higher-compatible promiscuous mode network cards. 10

Chapter 1 Dynatrace Network Analyzer System Requirements Additional Software Required Windows 3.1 Installer All platforms should have the Windows 3.1 Installer. If you are not running automatic Windows updates, you can find the Windows 3.1 Installer at www.microsoft.com and on the Dynatrace Setup browser Utilities tab. Additional System Recommendations When Using Unattended Capture Mode A dedicated computer is recommended when using Unattended Capture Mode. Network traffic volume varies greatly depending on the network. The amount of this traffic affects the size of the hard disk you will need. If you plan to use disk caching, your agent will require a large amount of RAM and a large amount of free hard disk space. Unix Dynatrace Network Analyzer Agent System Requirements The following are requirements for a Unix system running this release of the DNA agent software. This release of the DNA Unix agent supports the following systems: IMPORTANT Be sure to inspect the library requirements listed in this document for each of your platforms. Some libraries that were not required for earlier versions of the DNA Unix agent are now required starting with agent version 11.0. Solaris The following Solaris systems are supported: Solaris 8 32-bit and 64-bit (SPARC platform only) NOTE Older versions of Solaris 8 SPARC may not have the libsendfile.so.1 library and older versions of DNA did not require it, but libsendfile.so.1 is required by DNA agent 11.0 and later, so be sure that it is included on any Solaris 8 SPARC platform. Solaris 9 32-bit and 64-bit (SPARC platform only) Solaris 10 32-bit and 64-bit (SPARC & Intel/AMD x86 platforms) NOTE Solaris 10 (Intel/AMD x86 platforms) may have an older version of the older libc.so.1 library. This was sufficient for DNA agent 10.2, but a newer version of this library is required by DNA agent 11.0 and later, so be sure to update the libc.so.1 library on any Solaris 10 (Intel/AMD x86 platform) platform. In all cases, be sure that your Solaris system meets these requirements: Solaris SPARC dynamic library requirements: libpthread.so.1 (SUNW_1.2) 11

Chapter 1 Dynatrace Network Analyzer System Requirements libnsl.so.1 (SUNW_0.7, SUNWprivate_1.1) libsocket.so.1 (SUNW_1.4) libcrun.so.1 (SUNW_1.1) libm.so.1 (SUNW_1.1) libw.so.1 (SUNW_0.8) libc.so.1 (SUNW_1.18, SUNWprivate_1.1) librt.so.1 (SUNW_0.7): Required by DNA agent 11.0 and later. libsendfile.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later. libthread.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later. Solaris i386 dynamic library requirements: libpthread.so.1 (SUNW_1.2) libnsl.so.1 (SUNW_1.7, SUNWprivate_1.1) libsocket.so.1 (SUNW_1.4) libcstd.so.1 (SUNW_1.1.1, SUNW_1.4) libcrun.so.1 (SUNW_1.4) libm.so.2 (SUNW_1.2) libc.so.1 (SUNW_1.22.1, SUNWprivate_1.1) librt.so.1 (SUNW_0.7): Required by DNA agent 11.0 and later. libsendfile.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later. libthread.so.1 (SUNW_1.1): Required by DNA agent 11.0 and later. Solaris hardware requirements: 5 MB plus capture buffer RAM (128 MB minimum system RAM recommended) 30 MB disk space plus sufficient space for capture temp files 1 or more NICs running TCP/IP protocol IBM AIX The following IBM AIX systems are supported: IBM AIX 5.3 32-bit and 64-bit IBM AIX 6.1 IBM AIX 7.1 In all cases, be sure that your IBM AIX system meets these requirements: 5 MB plus capture buffer RAM (128 MB minimum system RAM recommended) 30 MB disk space plus sufficient space for capture temp files 1 or more NICs running TCP/IP protocol The bos.net.tcp.server fileset must be applied on AIX systems. 12

Libraries required for AIX: /usr/lib/libpthreads.a(shr_comm.o) /usr/lib/libpthreads.a(shr_xpg5.o) /usr/lib/libc.a(shr3.o) /usr/lib/libc.a(shr2.o) /usr/lib/libc.a(shr.o) /usr/lib/libcrypt.a(shr.o) /usr/lib/libc.a(shr.o) /usr/lib/libc.a(ansi_32.o) Chapter 1 Dynatrace Network Analyzer System Requirements /usr/lib/libiconv.a(shr4.o): Required by DNA agent 11.0 and later. HP-UX The following HP-UX systems are supported: HP-UX 11.11 32-bit and 64-bit If you are installing the agent in an HP-UX 11.11 environment, you must apply patch PHSS_22898 for the C++ runtime library. HP-UX 11.23 32-bit and 64-bit HP-UX 11.31 64-bit In all cases, be sure that your HP-UX system meets these requirements: 5 MB plus capture buffer RAM (128 MB minimum system RAM recommended) 30 MB disk space plus sufficient space for capture temp files 1 or more NICs running TCP/IP protocol NOTE The installer configures the agent without the capability to set network interfaces to promiscuous mode on HP-UX 11.00 and HP-UX 11.11 due to HP issue number JAGae83251 against HP-UX 11.00 and HP-UX 11.11. If promiscuous mode capture is required on these HP-UX releases, see the note regarding promiscuous mode capture in the troubleshooting section below. Libraries required for HP: /usr/lib/libdld.2 /usr/lib/libc.2 /usr/lib/libcl.2 /usr/lib/libisamstub.1 /usr/lib/libm.2 /usr/lib/libcsup_v2.2 /usr/lib/librt.2 13

Chapter 1 Dynatrace Network Analyzer System Requirements /usr/lib/libpthread.1 /usr/lib/libstd_v2.2 Linux The following Linux kernel versions are supported: Linux 2.4 32-bit Intel (libraries required; see below) Linux 2.6 32-bit Intel (libraries required; see below) Linux 2.6 64-bit Intel EM64T/AMD64 (libraries required; see below) This is not the same as the Linux distribution version. For example, Red Hat Enterprise Linux 3 is a Linux distribution based on the Linux 2.6 kernel, which is one of the kernel versions listed above. DNA agent 12.3 therefore supports Red Hat Enterprise Linux 3. NOTE To check your Linux kernel version, issue the command: % uname -r and verify that the first two digits of the displayed kernel number are listed above. In all cases, be sure that your Linux system meets these requirements: 5 MB plus capture buffer RAM (128 MB minimum system RAM recommended) 30 MB disk space plus sufficient space for capture temp files 1 or more NICs running TCP/IP protocol If you are installing the agent on a Linux machine, you must ensure your machine has the base C and C++ runtime libraries, sockets library, and threading libraries: libpthread.so.0 libstdc++.so.6 or libstdc++.so.5 libc.so.6 libm.so.6 libgcc_s.so.1 libexpat.so.0 In Red Hat Linux distributions prior to release 6, these libraries were installed by default. In Red Hat Enterprise Linux 6, these libraries must be installed manually and may be available under different names. The installation script checks the installed gcc version. Libraries required for Linux systems with gcc 3.4.0 or higher: /usr/lib/libpthreads.a(shr_comm.o) /usr/lib/libpthreads.a(shr_xpg5.o) /usr/lib/libc.a(shr3.o) 14

Chapter 1 Dynatrace Network Analyzer System Requirements /usr/lib/libc.a(shr2.o) /usr/lib/libc.a(shr.o) /usr/lib/libcrypt.a(shr.o) /usr/lib/libc.a(shr.o) /usr/lib/libc.a(ansi_32.o) /usr/lib/libiconv.a(shr4.o): Required by DNA agent 11.0 and later. Libraries required for Linux systems with gcc version below 3.4.0: libstdc++.so.5 (libstdc++.so.5.0.7): Required by DNA agent 11.0 and later. libpthread.so.0 (libpthread-2.3.4.so): Required by DNA agent 11.0 and later. libm.so.6 (libm-2.3.4.so): Required by DNA agent 11.0 and later. libgcc_s.so.1 (libgcc_s-3.4.3-20050228.so.1): Required by DNA agent 11.0 and later. libc.so.6 (libc-2.3.4.so): Required by DNA agent 11.0 and later. /lib/ld-linux.so.2 (ld-2.3.4.so): Required by DNA agent 11.0 and later. libexpat.so.0 (libexpat.so.0.5.0): Required by DNA agent 11.0 and later. NOTE The 32-bit shared libraries are required for 64-bit Linux on amd64 and ia64 systems. These libraries are typically distributed as package ia32-libs. Database Requirements DNA uses a SQL database to store captured and imported data. This is done to ensure data integrity and the easy scaling of large numbers of traces. IMPORTANT We highly recommend a locally installed database for use with DNA. Performance may significantly degrade when using a remote database. DNA currently is designed to support a dedicated per-user database and requires exclusive use locks at the database level. By default, Microsoft SQL Server Express is installed when you install DNA if a suitable SQL Server is not already installed. The engine loads when you start your computer so that it is available to support DNA. Configuring an Existing SQL Server Installation If you install Microsoft SQL Server Express during the DNA installation, it is automatically configured to work with DNA; skip to Installing Dynatrace Network Analyzer in the Dynatrace Network Analyzer User Guide. 15

Chapter 1 Dynatrace Network Analyzer System Requirements If SQL Server is already installed at the time DNA is installed, however, you must verify some SQL server settings manually before installing DNA: Enabling TCP/IP If SQL Server is already installed at the time DNA is installed, verify that TCP/IP is enabled. 1. Open the SQL Server Configuration Manager. NOTE The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select Programs Microsoft SQL Server [version] Configuration Tools SQL Server Configuration Manager. 2. In the SQL Server Configuration Manager navigation tree, open the Network Configuration branch and select Protocols for MSSQLSERVER. 3. The TCP/IP setting displayed in the right pane must have a status of Enabled for DNA to work. If it is not enabled, right-click TCP/IP and select Enable. 4. In the SQL Server Configuration Manager navigation tree, click the SQL Server Services branch. 5. In the right pane, right-click SQL Server and select Restart (or select Stop and then select Start). Enabling SQL Server Browser If SQL Server is already installed at the time DNA is installed, verify that SQL Server Browser is enabled. 1. Open the SQL Server Configuration Manager. NOTE The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select Programs Microsoft SQL Server [version] Configuration Tools SQL Server Configuration Manager. 2. Click SQL Server Services. 3. Right-click SQL Server Browser and select Properties. The SQL Server Browser Properties dialog box opens. 4. Click the Service tab. 5. Set Start Mode to Automatic and then click OK. 6. If SQL Server Browser is not already running, right-click SQL Server Browser and select Start. Enabling Server Authentication If SQL Server is already installed at the time DNA is installed, verify that server authentication is enabled. 16

Chapter 1 Dynatrace Network Analyzer System Requirements 1. From the Windows Start button, select Programs Microsoft SQL Server [version] SQL Server Management Studio Express. 2. In the Registered Servers window, select the local server. 3. In the Object Explorer window, right-click the server and select Properties. The Server Properties dialog box opens. 4. On the Security page, select SQL Server and Windows Authentication mode and then click OK. 5. In the Object Explorer window, right-click the server and select Restart. Confirm the restart and wait for the server to restart. 6. In the Object Explorer window, open Security Logins, right-click the sa login, and select Properties. The Login Properties dialog box opens. 7. On the General page, enter the sa password twice (Password and Confirm password). 8. On the Status page, set Login to Enabled and then click OK. Changing Service Account to Local System If SQL Server is already installed at the time DNA is installed, verify that Local System Account is selected. 1. From the Windows Start button, select Settings Control Panel Administrative Tools Services. 2. Right-click SQL Server in the Services (Local) list and select Properties. The SQL Server Properties dialog box opens. 3. Click the Log On tab. 4. Select Local System Account and then click OK. Migrating Existing Databases DNA can migrate some older DNA database versions to the current version. If you are upgrading from a previous version of DNA, the InstallShield will detect the earlier version of the software and database and will ask whether you want to migrate your database. Provide your database login information and click Next to migrate your database while the latest version of DNA is installed. This is the easiest and fastest way to migrate your database to the latest format. If you choose to skip database migration during installation, however, you can still easily migrate your database later when you start DNA. 17

Chapter 1 Dynatrace Network Analyzer System Requirements CAUTION Do not interrupt installation or migration processes. Migration is a one-way process. If you migrate an existing DNA database to DNA current format, the new database can be opened only by the current version of DNA, not by previous versions of DNA, and you cannot migrate it back to the older version. If you also want to continue working in the old version of DNA (on a different machine), you must keep a copy of the database in the old format. In such a case, back up the existing database before performing the migration. To avoid the possibility of data loss or corruption during software upgrade or database migration, you should always keep a recent backup of your database in a safe place. Restricting SQL Service When you enable TCP/IP for SQL service, it is automatically enabled for all IP addresses. To tighten security, you can restrict SQL Server to just the local address (127.0.0.1). 1. Open the SQL Server Configuration Manager. The location of SQL Server Configuration Manager depends on your SQL Server version. For SQL Server Express, click the Windows Start button and select: Programs Microsoft SQL Server [version] Configuration Tools SQL Server Configuration Manager. 2. In the SQL Server Configuration Manager navigation tree, open the Network Configuration branch and select Protocols for MSSQLSERVER. 3. In the right pane, right-click TCP/IP and select Properties. 4. Change Listen All to No. 5. Click the IP Addresses tab. 6. Change the Active and Enabled settings to No for all entries except address 127.0.0.1, which must be set to Yes. 7. Click OK. 8. In the SQL Server Configuration Manager navigation tree, click the SQL Server Services branch. 9. In the right pane, right-click SQL Server and select Restart (or select Stop and then select Start). 18

CHAPTER 2 Installation This chapter describes how to install Dynatrace Network Analyzer software on approved systems. Console Installation This section describes how to install the Dynatrace Network Analyzer console. If you are a previous user of Dynatrace Network Analyzer, you may be able to upgrade your existing installation and migrate your previous database to the new installation. Assuming the DNA database is installed with SQL Server Express, provided with the DNA installation, and database size is less than 4 GB. Task/Factor How many DNA consoles are installed? How many agents to upgrade automatically? How many agents to upgrade manually? Validate DNA is fully operational. Estimating Criteria Each console must be upgraded by logging into the machine and manually upgrading it. Estimate up to 1 hour for each console installed (including database backup and upgrade), though you may be able to work on them in parallel. Plan 0.5 hours for upgrade to complete on agents. Plan on 0.25 hour for each agent to be upgraded. Perform a smoke test. Estimate 2 hours for console and agents. My time How many releases back is the console version you have installed? When you upgrade to release 12.3 from release 12.1 or 12.2, upgrade is automatic through the installer. When you upgrade to release 12.3 from an earlier version of DNA, however, you need to upgrade that earlier release to release 12.1 or 12.2 first, and then upgrade that installation to release 12.3. This will effectively double your console update time. 19

Chapter 2 Installation Task Duration Estimates Assuming the DNA database is installed with SQL Server Express, provided with the DNA installation, and database size is less than 4 GB. Task/Factor How many DNA consoles are installed? How many agents to upgrade automatically? How many agents to upgrade manually? Validate DNA is fully operational. Estimating Criteria Each console must be upgraded by logging into the machine and manually upgrading it. Estimate up to 1 hour for each console installed (including database backup and upgrade), though you may be able to work on them in parallel. Plan 0.5 hours for upgrade to complete on agents. Plan on 0.25 hour for each agent to be upgraded. Perform a smoke test. Estimate 2 hours for console and agents. My time How many releases back is the console version you have installed? When you upgrade to release 12.3 from release 12.1 or 12.2, upgrade is automatic through the installer. When you upgrade to release 12.3 from an earlier version of DNA, however, you need to upgrade that earlier release to release 12.1 or 12.2 first, and then upgrade that installation to release 12.3. This will effectively double your console update time. Upgrading Existing Console Installations The Dynatrace Network Analyzer Release 12.3 console can be upgraded from Dynatrace Network Analyzer 12.1 or 12.2. Older Dynatrace Network Analyzer releases must be uninstalled before you can install the new version. During the installation of Dynatrace Network Analyzer, you are prompted whether it is possible to upgrade your older version of Dynatrace Network Analyzer. If it is not possible, uninstall your older version before installing the new version. For more information, see Console Uninstallation - Interactive [p. 65]. Only one Dynatrace Network Analyzer release can be open at a time. Installing SQL Server Management Studio Express Some of the database management procedures in the DNA documentation are written with the assumption that you have installed SQL Server Management Studio Express, a tool that comes with Microsoft SQL Server Express. If you have not installed it already, we strongly recommend that you download and install Microsoft SQL Server Express. 1. Open web page http://www.microsoft.com/en-us/download/details.aspx?id=29062. 2. Download the appropriate installer for your system (32-bit or 64-bit). 20

Chapter 2 Installation 3. Run the installer. Additional installation instructions are included on the download page and in the software's readme file. Migrating Existing Databases DNA can migrate some older DNA database versions to the current version. If you are upgrading from a previous version of DNA, the InstallShield will detect the earlier version of the software and database and will ask whether you want to migrate your database. Provide your database login information and click Next to migrate your database while the latest version of DNA is installed. This is the easiest and fastest way to migrate your database to the latest format. If you choose to skip database migration during installation, however, you can still easily migrate your database later when you start DNA. CAUTION Do not interrupt installation or migration processes. Migration is a one-way process. If you migrate an existing DNA database to DNA current format, the new database can be opened only by the current version of DNA, not by previous versions of DNA, and you cannot migrate it back to the older version. If you also want to continue working in the old version of DNA (on a different machine), you must keep a copy of the database in the old format. In such a case, back up the existing database before performing the migration. To avoid the possibility of data loss or corruption during software upgrade or database migration, you should always keep a recent backup of your database in a safe place. Installing Dynatrace Network Analyzer Console To perform this console installation procedure, you must be logged in as a user with administrative privileges. Installations on computers that already have an older version of Dynatrace Network Analyzer or any Dynatrace product installed have a shorter installation procedure than computers that have never had a Dynatrace product installed. A full installation consists of installing: Dynatrace Operating System Updates Dynatrace Network Analyzer SQL Server Express Database The installer automatically checks your computer for each of the above items. When an item is found, the installation step for that item is skipped. 1. Temporarily disable antivirus software on the target machine. This is not necessary in all cases, but some antivirus software prevents DNA from installing. 21

Chapter 2 Installation 2. Download the installation package from the Downloads section of the Dynatrace Community. 3. Extract the installation package into a temporary directory. 4. Double-click setup.exe in the installation package to open the installation browser. 5. On the Additional Products tab, click the Dynatrace Network Analyzer Console link. The DNA installer starts. NOTE To install DNA, you must have administrator privileges for the target machine. If you receive a Windows security message concerning the installer, click Install or Run to continue with the installation. If you receive an OS Update Error, the target machine may need new certificates. For more information, see Installing Missing Certificates for DNA Installation [p. 29]. 6. The Dynatrace operating system software is checked. If updates are required, the necessary updates are listed. Review them and, if you are satisfied with the listed updates, click Next to make those updates and continue. 7. The installer program extracts the necessary files for DNA installation. 8. On the Welcome page, click Next. 9. On the License Agreement page, review the text of the license, select I accept the terms in the license agreement, and then click Next to accept the terms of the license and begin installing DNA. 10. Your computer is checked to see whether you have access to an appropriate SQL Server instance. If you do not, select Yes when prompted and click Next to install SQL Server Express. If you select No, you must otherwise arrange for this DNA installation to have access to an appropriate SQL Server instance. The Utilities tab of the media browser has a link that you can use at a later time to install it. 11. If you installed SQL Server Express in the previous step, you are now prompted to create a password for the sa database administration account. Type the new password twice, click Next, and wait while SQL Server is installed. 12. If you are upgrading DNA and you are asked to migrate the database, click Skip if you don't want to migrate the database, or provide the SQL Server Instance, Database Name, User Name, and Password and then click Next to migrate to the database. 13. On the Destination Folder page, review the default settings, change them if needed, and then click Next. 14. On the Custom Setup page, select the Browser Data Collection, Documentation, Help, and Trace Trimmer features you want to install and then click Next. By default, all features are installed. Your computer is checked and you are warned if any system requirements are not met, but you are allowed to continue the installation. Click Back to discontinue the installation. Otherwise, click Next and continue responding to the requested information. 22

Chapter 2 Installation 15. On the Promiscuous Mode page, you are asked to choose the capture type: either promiscuous mode or non-promiscuous mode. Leave the default selection (Yes) to have DNA capture all traffic the NIC card can see. Click No to have DNA capture only traffic to or from the NIC card itself. Click Next. 16. On the TCP Port Number page, provide the TCP port number for the DNA agent. Click Next if your network does not have strict firewall policies and the default port of 2408 is suitable for your use. If the 2408 default port is not suitable for your use, click Yes and type the port information requested. 17. If this is a new installation, the Database Creation page appears; complete the database information and click Next. First select the database authorization method you want to use: Windows Authentication: If you select this method, access to DNA database will be controlled by Windows user ID and password. The User name and Password fields on this page of the wizard will be hidden. SQL Authentication: If you select this method, access to DNA database will be controlled by SQL user ID and password. Type the User name and Password information on this page of the wizard. You can install the database on a remote server by selecting a server from the SQL Server instance list, which displays all SQL server instances on your network. You can create the database on any of these instances if you have the valid user ID and password for them. (You created a password for the user name sa in Step 11 [p. 22].) You can also enter the name or IP address of any other SQL Server. If the database you want to create already exists on the machine you select, you receive a message indicating that the database already exists on the server. You do not need to have DNA installed on the remote server to have the database installed on the server. If you choose a remote SQL Server, a database will be created but sample data will not be installed. If you want to have sample data, you will have to do it after installation using the database backup and restore tools. Click Advanced if you want to change the install path, the database size, or the log size. DNA performance is adversely affected by use of a remote database. Each database can only be used by a single user at a time. NOTE If this is an upgrade from an acceptable prior release, this dialog box does not appear. The default settings install the default database on your Microsoft SQL Server unless you make changes. Accept the defaults by clicking Next, unless you have a reason to customize the settings. If you skip this step, you will later have to create a DNA database (unless you have one from an earlier installation) and a Trace Trimmer database (required to use the Trace Trimmer trace filtering tool). 18. If you created a local database in Step 17 [p. 23], the Sample Data page asks whether you want to install sample data. 23

Chapter 2 Installation If you are new to DNA, you should select Yes to install the sample data. You can use the sample data to explore DNA without corrupting live data. Also, explanations in this documentation sometimes refer to examples from the sample database. 19. On the Ready to Install the Program page, review your selections, and then click Install if they are correct. You can use the Back button to go back and change settings, and then use Next to return to this point. 20. When the installation is finished, a Start Programs Compuware Dynatrace Network Analyzer menu is created on the target machine. The Dynatrace Network Analyzer menu includes: Dynatrace Network Analyzer Agent Manager Dynatrace Network Analyzer User Guide Dynatrace Network Analyzer Get Support File Trace Trimmer Before you use DNA: If you have disabled antivirus software on the target machine for DNA installation, be sure to enable it again. Reboot the machine. Install a license. Disable network task offload. (Before capturing data, you must disable network task offload on your DNA machine. ) Enable the Internet Explorer add-on from Dynatrace (Internet Explorer 9.0 and later, and only if you intend to use BDC). For more information, see Enabling Add-on for Internet Explorer [p. 25]. Disabling Network Task Offload Network task offload is a Microsoft Windows feature for improving TCP/IP processing speed. However, it hides network traffic from DNA and thus may invalidate your network analysis. Before capturing data, you must disable network task offload on your DNA machine. NOTE Disabling network task offload may degrade TCP/IP processing speed on that machine. To disable network task offload: 1. Click Start Search, right-click cmd, and choose Run as Administrator. 2. In the command shell, issue the following command: netsh int ip set global taskoffload=disabled 24

Chapter 2 Installation You can copy the command from here, paste to the machine's command line, and press [Enter]. There are no machine-specific parameters to change. 3. Reboot the machine before continuing to work with DNA. Enabling Add-on for Internet Explorer Starting with Microsoft Internet Explorer (IE) 9.0, all new IE add-ons are disabled by default. If you are going to use Browser Data Collection (BDC), you must enable the Dynatrace add-on called InterceptorEventHandler. 1. On the IE menu bar, select Tools Manage Add-ons. 2. In the Compuware Corporation section, select InterceptorEventHandler and click Enable. 3. Restart IE. Adding a Windows Firewall Exception for Mongoose Mongoose is a third-party open-source component (web server) used by RTP 2.0. If a Windows Security Alert states that Windows Firewall has blocked some features of a program called Mongoose when you first open Response Time Predictor 2.0, you should allow Mongoose to run and add an exception for Mongoose to your Windows Firewall. User Accounts and Administrative Rights The availability of some DNA features depends on user account privileges and how account privileges are managed by the machine's operating system. Accounts with administrative rights If the intended user's Windows account has administrative rights to the machine on which DNA is installed, all DNA features will be available to the user. DNA by default runs with limited permissions even if the user account belongs to the administrative group. To run DNA with administrative rights, you need to right-click the DNA icon or menu entry and specify that DNA should be run as an administrator. Accounts without administrative rights but with AVUsers membership If the intended user's Windows account does not have administrative rights to the machine on which DNA is installed, the system administrator should ensure that the intended user's Windows account is added to the Windows users group called AVUsers. The first time you run DNA on the intended user's account, you may see a message such as: The current user does not have privileges to use full functionality of Dynatrace Network Analyzer. Do you want to elevate the current user's privileges? (You will need to provide administrator credentials to make this change.) 25

Chapter 2 Installation If you answer yes and provide administrator credentials, the user will be added automatically to AVUsers. If you prefer to do so manually, see the Managing User Access Rights with AVUsers Group Membership [p. 27] procedure for more information. Adding a non-administrator user account to AVUsers will ensure that the user account has access to almost all DNA features. However, a small set of DNA features will remain unavailable to the user. The user will not be able to create a new database for Trace Trimmer. Most users never need to create a new database for the Trace Trimmer trace filtering utility. The user will be able to run the Get Support File utility for gathering system information to report to customer support however, generated log will remain at info level only. Accounts without administrative rights and without AVUsers membership If you do not add a non-administrator user account to AVUsers, the following additional items will be unavailable to that user: The user will not be able to change promiscuous mode for a local capture point. This is generally an important restriction. The user will not be able to access DNA databases using Windows authentication. To work around this, use the SQL Authentication or have the SQL administrator add the account manually to the DNA database using SQL Management Studio. In addition, restrictions described in Accounts without administrative rights but with AVUsers membership [p. 25] apply to the restrictions explained in this section. To avoid these last two restrictions and minimize the need for administrator intervention, make the user's account a member of the AVUsers Windows users group where possible. Running Dynatrace Network Analyzer for the First Time After installing Dynatrace Network Analyzer, the system administrator should run Dynatrace Network Analyzer from the user's account to make sure the intended user has the appropriate access rights. 1. Log in to the intended user's account. 2. On the Windows desktop, double-click the Dynatrace Network Analyzer icon. 3. If you are prompted to do so, specify whether to elevate the current user's privileges. For more information, see User Accounts and Administrative Rights [p. 25] and Managing User Access Rights with AVUsers Group Membership [p. 27]. Click Yes to add the current Windows login to the list of users who can carry out administrative-level actions through Dynatrace Network Analyzer. In this case, someone with Windows administrator privileges (presumably you if you are installing Dynatrace Network Analyzer) will have to enter admin-level login credentials to approve the selection. After approval, the original user can log back in to Windows and restart Dynatrace Network Analyzer. Click No if you do not want to elevate the current user's privileges. Also select Do not ask me this again if you do not want the current user to see this message again. 26

Chapter 2 Installation Managing User Access Rights with AVUsers Group Membership Dynatrace Network Analyzer user rights are managed through a Windows user group named AVUsers. To grant or deny a user access to Dynatrace Network Analyzer on the console machine, manage the AVUsers Windows users group to add or delete that user's Windows user name. 1. In Windows, right-click My Computer and select Manage. The Computer Management dialog box is displayed. 2. In the navigation tree, select System Tools Local Users and Groups Groups. 3. In the list of user groups, double-click the AVUsers group. The AVUsers Properties dialog box is displayed. This group normally is created automatically during Dynatrace Network Analyzer. If it does not exist, you should reinstall Dynatrace Network Analyzer or create the group manually (right-click the list of user groups and select New Group). 4. Click Add to add a user to the AVUsers group. 5. Type the Windows login name of the user you are adding to the AVUsers group, and then click OK. That user now has administrative rights in Dynatrace Network Analyzer DNA and VMware DNA supports VMware environments with certain limitations. Follow Dynatrace guidelines to minimize the effects of running DNA in a VMware virtual environment. Use hardware-based timing when possible Virtual machine operations do not necessarily run in real time. For example, if a virtual machine is competing with other virtual machines for resources on a single piece of real hardware, an operation that would run in 1.0 seconds on a real (physical) machine might take 1.3 seconds of real time (time on the wall clock) to execute. The virtual machine might then attempt to make up for such a delay by executing another operation in less time than it would take to execute in real time. In most cases, such minor adjustments go unnoticed, but they could make a difference in an application such as DNA in a virtual environment with a virtual clock. For example, a packet captured in the 11th real second since the (real) computer was turned on might be recorded as if it had arrived in the 8th second if the packet capture driver (running on a virtual machine) was not kept consistent with the underlying real time. Views that are affected to a degree dependent on the severity of the virtual timer are those that measure or allocate delay. These include CNS Breakdown, Performance Overview, Node Processing and Node Sending tables, Transaction Expert reports, and auto-adjustment (heuristic). For more information, see http://www.vmware.com/files/pdf/timekeeping-in-virtualmachines.pdf. With DNA (console, agent, and Simple Capture) running on VMware ESX(i) 3.5 (or later) or VMware Workstation 6.5 (or later), you can now configure the driver to read the current time from the underlying host machine instead of depending on the (virtualized) operating system's time, which may be unsynchronized with real time. 27

Chapter 2 Installation For more information, see Enabling Hardware-Based Timekeeping in VMware Virtual Machines in the Dynatrace Network Analyzer - Help. Use a separate VMware guest machine when possible The preferred method for capturing network traffic in a VMware environment is to use a separate VMware guest machine dedicated to the Dynatrace Network Analyzer Agent. Make sure that this guest machine runs with high priority. Use the port spanning functionality available through the VMware vnetwork Standard Switch (vss) or VMware vnetwork Distributed Switch (vds). This configuration will allow the network traffic between VMware guest machines to be visible to the Agent machine. To learn more about vss and vds, see (external link) http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf Alternatively, you can install the Dynatrace Network Analyzer Agent directly on a guest machine. However, the additional processing performed by the machine may cause the virtual timing problem to be more pronounced. NOTE Some of the possible timing problems described below may be mitigated or negated if you can use the hardware-based timing method. For more information, see Use hardware-based timing when possible [p. 27]. VMware virtualization timing considerations affect some of DNA's performance analysis. Specifically, VMware's timer virtualization technique (called apparent time ) allows a virtual timer to fall behind real time and then to catch up as needed. This time lag between the virtual machine and real time may reach a level greater than a millisecond. Such delays will be recorded in the time stamps in DNA traces. These timing problems affect only the network trace capture phase. For trace analysis performed in the DNA console, it does not matter whether DNA runs in a VMware environment. It is accuracy of time stamps in the traces that matters. For analyzing single trace files within DNA without merging or adjusting to examine network delays the following holds true: The inaccuracies resulting from using virtual time stamps will usually not be noticeable, and should have a negligible effect on most analyses. In these cases, views and functionality that offer byte/packet statistics, as well as protocol decodes, will not be affected beyond the loss of time stamp precision. These include the Packet Trace, Conversation Map, Thread Analysis, Error Analysis, and Payload vs. Overhead views. Views that are affected to a degree dependent on the severity of the virtual timer are those that measure or allocate delay. These include CNS Breakdown, Performance Overview, Node Processing and Node Sending tables, Transaction Expert reports, and auto-adjustment (heuristic). If the analysis will require merging or adjusting traces within DNA, extra caution may be required, especially if the network separating the capture points is low-latency. (High-latency WAN links easily mask most virtual time stamp inaccuracies.) For this reason, we do not 28

Chapter 2 Installation recommend merging trace files across low-latency links (< 20 milliseconds round-trip) where one of the trace files must come from a virtual machine. However, you may be able to use hardware-based timing on your virtual machine to mitigate this problem. For more information, see Use hardware-based timing when possible [p. 27]. Installing Missing Certificates for DNA Installation If you receive an OS Update Error 1330 during Dynatrace Network Analyzer (DNA) installation, it indicates that the target machine requires a Windows update that includes certain required certificate updates, and that the machine does not have an Internet connection through which these updates could be made automatically. If it is possible to give the target machine an Internet connection during DNA installation, you should do this and restart the installation process. If you cannot give the target machine an Internet connection during DNA installation, or if the error occurs again after giving the machine an Internet connection, install the missing certificates manually before running the DNA installation: 1. On a machine that has an Internet connection, go to page: https://search.thawte.com/support/ssl-digital-certificates/index?page=content&id=ar1406 2. Follow the instructions on that page for installing the Code Signing Intermediate CA and Thawte Primary Intermediate Root CA certificates on the intended DNA machine. This will require you to create two certificate files manually, copy them to the intended DNA machine, and then use the Certificate Import Wizard in Microsoft Windows to install those certificates on the intended DNA machine. 3. After the certificates are installed, install DNA. Trace Trimmer Configuration from Windows Control Panel You can change some Trace Trimmer settings through the Windows Control Panel. 1. In Windows, select Start Control Panel. 2. Click Uninstall a program. 3. Select Dynatrace Network Analyzer Trace Trimmer. 4. Click Uninstall/Change. 5. Select the option you need to change and click Next. Options include: HTTP and SSL Server settings Database user password 6. Change the configuration parameters. 7. Click Change. 8. Click Finish. 29

Chapter 2 Installation Agent Installation Follow this procedure to install Dynatrace Network Analyzer Agent. Remote capture using DNA can be performed on a variety of Windows and Unix/Linux machines on which you have installed the Dynatrace Network Analyzer Agent. (For a list of system requirements, see the Dynatrace Network Analyzer Agent release notes.) Before anyone can perform remote captures on a machine using the Dynatrace Network Analyzer Agent, the agent must first be installed on that machine. The Dynatrace Network Analyzer Agent and the DNA console should not be installed on the same machine. Importing of external third-party wireless LAN captures is not supported. All platforms should have the Windows 3.1 Installer. If you are not running automatic Windows updates, you can download the Windows 3.1 Installer. For more information, see http://update.microsoft.com. Proper operation of wireless capture is dependent on the specific 802.11 adapter and Windows version in use. For many 802.11 adapters, you need to set the capture mode to non-promiscuous, with the consequence that the captured transaction traffic must be directed to/from the machine performing the capture. In other words, in non-promiscuous mode, the transaction needs to run from the machine performing the wireless DNA capture. Capturing on wireless agent NICs is hardware dependent. DNA captures on most wireless NICs. For some wireless NICs you must reboot after installation or after changing the promiscuous mode setting. To confirm proper operation of wireless capture, try capturing access to a Web page (HTTP traffic). Check to make sure the byte count is advancing during the capture. After completing the capture, go to the Payload View to verify that the packet content is correct. During the installation of DNA on Windows machines, a Microsoft Installer file called Transaction Trace Agent.msi is installed in Transaction Trace\Transaction Trace Agent. This file is also available from the Dynatrace distribution. For Unix agent installations, first read the readme located under the *Unix_Agents folder. The appropriate tar file and install script are inside each platform s folder, such as AIX, HP-UX, Linux, and Solaris. The All folder contains another tar file that has all the platforms together. For Unix installations, run the script install from the Dynatrace distribution. Administrator Installation Options Depending on your target machines, you have various options for installing Dynatrace Network Analyzer Agent. Windows Your options for installing Dynatrace Network Analyzer Agent on a remote Windows machine are: Place the installer file on a network drive that is available to the remote machine. Install it on the remote machine from your own machine if you have remote control of that machine. 30

Chapter 2 Installation Provide the installer file to the user of the remote machine and let that user install it on the remote machine. Put the file on a Web page for users to download and install. Include Dynatrace Network Analyzer Agent as part of your basic system configuration program. Use the Remote Installer to install Dynatrace Network Analyzer Agent software to a Windows machine on your network from a central location. This process is referred to as remote (unattended) installation. See the release notes for Windows version compatibility information. Conduct a silent installation. For more information, see DNA Silent Installations [p. 55]. Unix or Linux Your options for installing Dynatrace Network Analyzer Agent on a remote Unix or Linux machine are: Copy the files, as appropriate for your platform, from the Dynatrace Unix or Linux distribution *_Unix_Agents folder to a temporary directory on your target Unix or Linux machine (/tmp) and run the install script. Download these files from the Dynatrace. In either case, untar the files and run the install script. Creating an Encrypted User Credentials File for Silent Agent Installations To use an encrypted user credentials file with the AVAUTHFILE parameter during a silent agent installation, you have to run a small standalone utility included on your software distribution media. 1. On your software distribution media, locate the AVpasswd.zip file. 2. Unzip the file to a local directory. 3. Double-click the AVpasswd file to run the utility. 4. Type a user name and password in the edit boxes. 5. Change the destination folder if necessary. 6. Click the Generate now button. What to Do Next The output file can now be referred to by an AVAUTHFILE parameter in an agent installation command. For more information, see Dynatrace Network Analyzer Agent Installation Command Syntax [p. 60]. To run the AVpasswd utility in batch mode: 1. Open the Windows command prompt. 2. Change the current directory to the folder in which AVpasswd was extracted. 31

Chapter 2 Installation 3. Type bin\avpasswd.exe u<username> -p<password> -o"<outputfolder>" For example: bin\avpasswd.exe ualice pwhit3r4bbit -o"c:\myttaagentpasswords\agent007" 4. Wait until a new file ttagentauth.ppp is created at the path provided Agent Installation on Windows Machines Installing a Windows Dynatrace Network Analyzer Agent Follow this procedure to install the DNA agent on a Windows machine. DNA agent installation procedures vary depending on a company s particular network administration policies and procedures. Consult your Network Administrator for specific details for your location before installing the agent. After agent installation, be sure to review the firewall notes that follow this procedure. For more information, see Verify firewall exceptions [p. 33]. 1. To install an agent on a remote machine, copy the Transaction Trace Agent Installer folder to the remote machine. During installation of the DNA console, a self-extracting executable file called Transaction Trace Agent.msi is installed in the Transaction Trace\Transaction Trace Agent Installer folder. 2. On either the remote machine or the machine that contains DNA, double-click the Transaction Trace Agent.msi file to begin installation. You must run it with elevated privileges. To do so, click Start Search cmd, right-click on cmd, and choose Run as administrator. Then execute msiexec /I <properpath>\transaction Trace Agent Follow the instructions as they appear on the screen. 3. On the Welcome page, click Next. 4. Optional: If you do not have.net 4.0 or later installed, you will be asked whether you want to install it. The agent software itself does not require.net, but you should install.net to make agent troubleshooting easier. The Get Support File troubleshooting tool that is installed with the agent software requires that.net 4.0 or later be installed on the target machine. If you prefer, you can install.net if and when you need to run GetSupportFile for troubleshooting. 5. On the Destination Folder page, review the default settings, change them if needed, and then click Next. 6. On the Please Choose Data Location (Local Drive) page, specify a local directory in which to save captured data. If there are multiple NICs, each has its own sub-directory. 7. On the Browser Data Collection Agent page, specify whether you want to install the Browser Data Collection (BDC) agent. 8. On the Promiscuous Mode page, specify whether to use promiscuous mode. 32

Chapter 2 Installation Unattended captures normally have Promiscuous Mode selected. You can change this setting later. 9. On the User Name and Password page, type an administrator User Name and Password (twice). This is a unique identifier for this agent on this machine; it does not need to be related to any other Windows user names or passwords. It is used to activate, administer, and use the agent. 10. On the TCP Port Number page, specify a TCP port for accessing remote agents through firewalls. If your site has strict firewall policies, you can type a specific port number here so that DNA can exchange data through the firewall with remote agents. Your IT administrator can then make certain that traffic for that port is allowed through the firewall. To ensure communication with the remote agents when there is a firewall, always install an agent on the DNA console system and then use the same port number that you used on the remote machines where the agents are installed. 11. On the Ready to Install the Program page, click Install to apply your settings and install the DNA agent. 12. When the installation is complete, the InstallShield Wizard Completed page will open. It is not necessary to reboot the computer before using the agent. What to Do Next Verify firewall exceptions On a Windows Server 2008 R2 Server Core machine, the agent installer automatically sets a firewall exception for the DNA agent, but this exception is sometimes created incorrectly. To ensure that the firewall exception is correct, run the following command: netsh advfirewall firewall add rule name="transaction Trace Agent" protocol=tcp dir=in localport=2408 action=allow profile=private On all other supported Windows releases, the agent installer does not automatically set a firewall exception for the DNA agent if your NIC s network location type is set to something other than private (public, domain). To view or change this setting, open the Network and Sharing Center control panel and click Customize. To view or change the list of firewall exceptions, open the Windows Firewall control panel, click the Change Settings, and then click the Exceptions tab. If the DNA agent is not on the list, click Add port and type the exception name and the agent s TCP port number (by default, this is set during agent installation to 2408). Enable Internet Explorer add-on for BDC If you are using Internet Explorer and if you intend to use BDC, you must enable the Internet Explorer add-on from Dynatrace. For more information, see Enabling Add-on for Internet Explorer [p. 25]. 33

Chapter 2 Installation Remote Installation of Dynatrace Network Analyzer Agent on Windows The easiest and most general way to install the agent on a remote Windows system may be to use the PSExec utility from Microsoft. 1. Download PSExec from Microsoft. http://technet.microsoft.com/en-us/sysinternals/bb897553 2. Determine the full path and file name to the installer msi. 3. Run the following command: PsExec.exe \\<computer> -u <username> -p <password> cmd /c msiexec.exe /i <path_to_agent_msi_package> [options] /qn where: <computer> is remote machine name or address. <[domain\]username> and <password> are a user with administrative privileges. <path_to_agent_msi_package> is the Dynatrace Network Analyzer Agent installer msi. If your path includes spaces, be sure to enclose the entire path and file name in quotation marks. [options] are agent silent install options. The agent is installed on the remote Windows machine. For administrators of Windows Server systems, you may instead be able to use Group Policy to install the agent remotely. For instructions, see How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003 on the Microsoft website (http://support.microsoft.com/kb/816102). Sample Dynatrace Network Analyzer Agent Installation Scripts Use these samples to help you write commands for installing or upgrading Dynatrace Network Analyzer Agent on Windows machines. Silent Installation Script Example with Mandatory Properties The command for a silent installation of a Dynatrace Network Analyzer Agent using the mandatory properties and the default settings is: msiexec.exe /I "Drive>\<Path>\Transaction Trace Agent.msi" /qn AVUSERNAME=<username> AVPASSWORD=<password> TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\" New Installation Script Example with Optional Properties Here is an example of a script for a new installation with the optional properties included: msiexec.exe /I "C:\Transaction Trace Analysis Agent Installer\Transaction Trace Agent.msi" /qn INSTALLDIR="C:\Program Files\Compuware\Transaction Trace Agent\" TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\" AVUSERNAME=admin AVPASSWORD=admin PROMISCUOUS=1 DATADIR=C:\AgentData PORT=2409 34

Chapter 2 Installation Upgrade Script Here is an example of a script for an upgrade: msiexec.exe /I "C:\Transaction Trace Analysis Agent Installer\Transaction Trace Agent.msi" /qn REINSTALLMODE=vomus REINSTALL=ALL Agent Installation on UNIX Machines Installing a Unix or Linux Dynatrace Network Analyzer Agent Follow this procedure to install Dynatrace Network Analyzer Agent on a Unix or Linux machine. You must be logged in as the root user to run the install script. 1. Copy the following files to a temp folder on your target Linux/Unix/AIX machine. av12.3.0.0<platform>.tar Choose the one with the platform matching your target Linux/Unix machine install The script to do the install Instructions Instructions 2. Change directory to the temp folder with those installation files. 3. Modify the file permission of the install file by typing the following command: chmod 0550 install 4. Start the installation by typing the following command to run the script install../install 5. Follow the directions as they appear on your screen to install the Dynatrace Network Analyzer Agent. The default values are displayed in brackets. To accept the default value, press [Enter]. a. Review the copyright notice and press [Enter] to continue. b. Select the destination folder for the agent. To accept the default name /opt/avagt, press [Enter] To specify a different name, enter it at the prompt. NOTE If the last sub-directory in the directory path is not /avagt, the install script appends /avagt to the name. If the directory already exists, you are notified and given the chance to specify another one. c. Select the Dynatrace Network Analyzer Agent port number (for communication between the agent and the DNA console). d. Select the destination folder for unattended capture temporary data files. 35

Chapter 2 Installation Choose a writable file system with sufficient capacity to hold your capture data. e. Type the administrator User Name and Password. You are prompted to confirm these. They are not the same as the Unix administrator account name and password. This password is needed to administer and use the agent. f. Select to automatically restart the Dynatrace Network Analyzer Agent at boot time using the system startup file. The default is to not automatically restart. NOTE On Linux machines, you must manually add the agent to your boot time startup files. For more information, see Troubleshooting Unix Dynatrace Network Analyzer Agent Installation in the Dynatrace Network Analyzer Agent. g. Select to start the Dynatrace Network Analyzer Agent immediately. h. A message will indicate when the installation has finished successfully. To verify that the agent is installed and running, start the agent and then use the ps and netstat commands. Issue the command: ps -ef grep avagt to see a message of the form: root 17141 17110 0 18:09:45 pts/4 0:00 grep avagt root 16968 1 0 18:08:29? 0:05 /opt/avagt/avagt Issue the command: netstat -an grep 2408 to see a message confirming that the agent is listening on that port: 2408 *.* 0 000 LISTEN Listing the Unix Dynatrace Network Analyzer Agent Files The /etc/appvantageagentinstall.cfg file is always created upon installation, indicating the version of the installed Dynatrace Network Analyzer Agent and the agent installation directory installdir. The following files are installed into the installation directory (../opt/avagt by default): AgentUnix.log.properties Logger property file. AppVantage.cfg Text file of the configuration of the Dynatrace Network Analyzer Agent. av_snapshot Script file for gathering info about the agent. avagt.log Text file of the Dynatrace Network Analyzer Agent working log. 36

Chapter 2 Installation avagt Executable file for the Dynatrace Network Analyzer Agent. You must have root access to run it. avdrivertest.log.properties Logger properties file. avinstall.log Text file of the Dynatrace Network Analyzer Agent installation log. avpasswd Executable file for resetting the Dynatrace Network Analyzer Agent administrator User Name and Password. AvSmartSplash.dat Binary configuration file used by agent. avsupport Executable file of DNA Get Support File function. ttagentauth.ppp Binary file that stores the Dynatrace Network Analyzer Agent administrator User Name and Password. release.d Text file containing release and build information. start_avagt Script file for starting the agent process. stop_avagt Script file for stopping the agent process. uninstall Script file for the Dynatrace Network Analyzer Agent un-installation. You must have the root access to run it. Configuring a Solaris Zone to Run an Agent NOTE The local Solaris Zone where an agent is to be installed needs to have access not only to the network device agent is going to listen on (/dev/e1000g0), but also to its parent device (/dev/e1000g), or the agent won't be able to detect the selected NIC (/dev/e1000g0). Configure the zone It must be an Exclusive-IP zone. Assuming you choose zone name exip, do the following: 1. Run zonecfg for that zone. zonecfg -z exip 2. Verify the configuration. In our sample exip zone, we want the agent to be able to capture traffic on interface /dev/e1000g0. Make sure it is configured as in the example below:... ip-type: exclusive 37

Chapter 2 Installation... net: device device address not specified physical: e1000g0 defrouter not specified match: /dev/e1000g0 match: /dev/e1000g NOTE The local Solaris Zone where an agent is to be installed needs to have access not only to the network device agent is going to listen on (/dev/e1000g0), but also to its parent device (/dev/e1000g), or the agent won't be able to detect the selected NIC (/dev/e1000g0). Start the zone, enable the interface, and install the agent inside the zone 3. Start the zone. zoneadm -z exip boot 4. Log in to the zone. zlogin -C exip 5. Enable interface e1000g0 inside the zone. ifconfig e1000g0 plumb ifconfig e1000g0 dhcp start 6. Install the agent inside the zone. DNA Agent Technical Notes The following are important technical notes applying to this release of DNA Agent software. This section includes technical information that may affect how you use the product. Installation procedures The installation procedures for the Windows agents are listed below. The operating instructions for the Dynatrace Network Analyzer Agent Manager are contained in the Dynatrace Network Analyzer User Guide. The DNA Agent can be upgraded if the agent currently installed is Release 12.1 or 12.2. Other agent versions should be un-installed before installing the current agent. Close all open windows and exit all other applications before installing the DNA Agent. Non-promiscuous mode Always install a remote wireless agent using the Non-Promiscuous mode option. Multiple NIC support For concurrent capture on multiple interfaces, select the All NICs/Ports simultaneously option during remote capture setup. When All NICs/Ports simultaneously is selected, the NICs/Ports must be of the same media type, such as Ethernet. DNA does not support multiple 38

Chapter 2 Installation NICs/ports in the same machine of different media types. Active Latency Detection is disabled when All NICs/Ports simultaneously is selected. Active Latency Detection (ALD) Active Latency Detection will not provide latency information about a node if that node also hosts a DNA Agent using the default agent port (2408). If you have a DNA Agent on a node involved in your transaction, use one of the following techniques to obtain latency information: 1. Perform a multi-point capture, and include the agent on that node (and keep ALD enabled, if necessary). 2. Change the default ALD port using the REG_SZ key. To override the default setting on the console, change the REG_SZ key in: HKEY_LOCAL_MACHINE\SOFTWARE\Compuware\CWPingerDLL\PING_PORT_OVERRIDE 3. Temporarily stop the DNA Agent service on the node. The precise breakdown for Client-Network-Server Breakdown views using Active Latency Detection depends upon proper Active Latency Detection operation. To verify proper ALD operation, you should go to the Single Trace Adjustment view to make sure interrogated nodes are included in the Active Segments and to view plots of latency measurements. Without the latency measurements, the CNS breakdown cannot distinguish Network and Server time. Installing a Compuware Certificate To install the agent remotely or silently, you should first install a Compuware certificate in the Trusted Publishers certificate store. NOTE You can distribute the certificate to multiple remote machines using Microsoft Group Policy. The certificate needs to be added to the store Trusted Publishers\Local Computer as follows: 1. In your Windows Explorer, right-click the Compuware.cer file and select Install certificate from the menu. The certificate file Compuware.cer is located in the Transaction Trace Analysis Agent Installer folder in the Dynatrace Network Analyzer distribution. The Certificate Import Wizard will open. 2. On the Certificate Import Wizard screen, click Next. The Certificate Store screen will be displayed. 3. Select Place all certificates in the following store and click Browse. 4. In the Select Certificate Store window, select the Show physical stores check box, expand the Trusted Publishers node, select Local Computer, and click OK. The Certificate Store screen will be displayed again but with Place all certificates in the following store selected and Trusted Publishers\Local Computer specified in the Certificate store field. 39

Chapter 2 Installation 5. Click Next. The Completing the Certificate Import Wizard screen will display a summary of the intended import. 6. If the summary is correct, click Finish. The certificate will be added to Trusted Publishers\Local Computer and a window will display The import was successful. Enabling Add-on for Internet Explorer Starting with Microsoft Internet Explorer (IE) 9.0, all new IE add-ons are disabled by default. If you are going to use Browser Data Collection (BDC), you must enable the Dynatrace add-on called InterceptorEventHandler. 1. On the IE menu bar, select Tools Manage Add-ons. 2. In the Compuware Corporation section, select InterceptorEventHandler and click Enable. 3. Restart IE. Configuring a Solaris Zone to Run an Agent NOTE The local Solaris Zone where an agent is to be installed needs to have access not only to the network device agent is going to listen on (/dev/e1000g0), but also to its parent device (/dev/e1000g), or the agent won't be able to detect the selected NIC (/dev/e1000g0). Configure the zone It must be an Exclusive-IP zone. Assuming you choose zone name exip, do the following: 1. Run zonecfg for that zone. zonecfg -z exip 2. Verify the configuration. In our sample exip zone, we want the agent to be able to capture traffic on interface /dev/e1000g0. Make sure it is configured as in the example below:... ip-type: exclusive... net: address not specified physical: e1000g0 defrouter not specified device match: /dev/e1000g0 device match: /dev/e1000g NOTE The local Solaris Zone where an agent is to be installed needs to have access not only to the network device agent is going to listen on (/dev/e1000g0), but also to its parent device (/dev/e1000g), or the agent won't be able to detect the selected NIC (/dev/e1000g0). 40

Chapter 2 Installation Start the zone, enable the interface, and install the agent inside the zone 3. Start the zone. zoneadm -z exip boot 4. Log in to the zone. zlogin -C exip 5. Enable interface e1000g0 inside the zone. ifconfig e1000g0 plumb ifconfig e1000g0 dhcp start 6. Install the agent inside the zone. DNA Simple Capture Installation The DNA Simple Capture application is a standalone Windows utility provided with Dynatrace Network Analyzer. Use it to capture traces on Windows computers that do not have the Dynatrace Network Analyzer console or its remote agents installed. DNA Simple Capture is easy to use: unzip it, start it, wait while it captures the data you want, stop it, and transfer the output file to your Dynatrace Network Analyzer console machine for analysis. Installing and Running Simple Capture Simple Capture runs on various Microsoft Windows platforms with minimal installation and configuration required. Compatible platforms include: Windows Server 2008 (32-bit and 64-bit versions) with Service Pack 2 Windows Server 2008 R2 (64-bit version) with Service Pack 1 Windows 7 (32-bit and 64-bit versions) with Service Pack 1 Windows 8 (32-bit and 64-bit versions) Windows 8.1 (32-bit and 64-bit versions) Windows Server 2012 Windows Server 2012 R2 Simple Capture generates *.ope trace files that can be imported to Dynatrace Network Analyzer. By default, the Simple Capture utility is always on top and the capture buffer size is 16384 K (16 MB ). To change these and other default settings, edit the configuration files. For more information, see Configuring Simple Capture [p. 42]. Simple Capture generates no on-screen error messages; any messages for the user are written to log file AVSimpleCapture.log in the Simple Capture directory. For instructions on changing the log level, see Configuring Simple Capture [p. 42]. 1. Unzip and extract the AVCaptureUtility.zip file into a new directory. 2. Double-click the AVSimpleCapture.exe file to open the Simple Capture utility. 41

Chapter 2 Installation A large red Start button is presented. 3. Click the red circular start button to start a capture. A large blue square Stop button is presented. This indicates that a capture is in progress and that the only action you can take is to stop the capture. NOTE Messages concerning routine file maintenance may be displayed while the application is running. These are logged in snetcfg.txt. Messages such as Cleaning OEM driver failed. do not indicate a problem and may be safely ignored. 4. After you have captured sufficient traffic, click the blue Stop button to stop the capture. When the red circle reappears, you will know that the capture has stopped. There may be a short delay. 5. By default, captured traces are saved to the folder in which you unzipped the AVSimpleCapture.exe file. Trace file names are of the form: yyyy-mm-dd_hh.mm.ss.ope 6. Transfer the output file to the machine on which you have installed Dynatrace Network Analyzer and import it to Dynatrace Network Analyzer (File Import Trace from the Dynatrace Network Analyzer menu bar) for analysis. What to Do Next Enable the Internet Explorer add-on from Dynatrace (Internet Explorer 9.0 and later, and only if you intend to use BDC). For more information, see Enabling Add-on for Internet Explorer [p. 25]. Configuring Simple Capture Follow this procedure to configure the Simple Capture utility before running it. 1. Review the logging level and change it if needed. a. Use a text editor to open the config\avsimplecapture.log.properties file that was included in the AVCaptureUtility.zip file. b. Find a line that starts with log4j.rootlogger=. 42

Chapter 2 Installation Example: log4j.rootlogger=info, A1 c. Change the string that immediately follows the equal sign to one of the following: TRACE Provides the most detail. Simple Capture logs all possible messages. DEBUG Simple Capture logs debug information and informational messages, warnings, errors, and fatal errors. INFO Simple Capture logs informational messages, warnings, errors, and fatal errors. This is the default setting. WARN Simple Capture logs warnings, errors, and fatal errors. ERROR Simple Capture logs only errors and fatal errors. FATAL Provides the least detail: Simple Capture logs only fatal errors. Leave the rest of that line (", A1") as it is. d. Save your changes and close the file. 2. Use a text editor to open the captureconfig.ini file that was included in the AVCaptureUtility.zip file. 3. Review the [Run Mode] section. Set Interactive to true (for interactive mode) or false (for silent mode). Default: Interactive=true When Simple Capture is run in interactive mode, the value of WindowAlwaysOnTop determines whether the Simple Capture window will always be displayed on top of all other windows. Change WindowAlwaysOnTop to false if you want the windows of other applications to be displayed on top of the Simple Capture window. Default: WindowAlwaysOnTop=true Set Timer to the number of seconds to run Simple Capture when run in silent mode. This parameter is ignored for interactive mode. If Timer = 0, Simple Capture runs in interactive mode regardless of the Interactive setting. Default: Timer=20 4. Review the [Available NICS] section. When Simple Capture is installed on a computer that has only one NIC, it binds to that NIC. If no physical NIC exists on the computer, the utility cannot capture traces. Review but do not change the NicDesc settings. This setting is empty by default but, when you run Simple Capture, it is updated automatically according to the NICs detected on your system. Each NIC description is preceded by an integer. Set NicIndex 43

Chapter 2 Installation (see below) to one of these integer values to specify the NIC on which to capture traffic. The first entry is always All NICs/Ports Simultaneously. Default: NicDesc= Set NicIndex to the number of the NIC on which you want to capture traffic. The number is the integer that precedes the NIC description in the NicDesc field. Set NicIndex to 1 to capture on all NICs and ports simultaneously. Default: NicIndex=1 Set Promiscuous to 1 (promiscuous mode) or 0 (non-promiscuous mode). Default: Promiscuous=0 5. Review the [Filter Expression] settings. Set Filter to a BPF-format packet filter statement. For more information on BPF, see the DNA user guide. If you leave it blank (the default setting), no filter will be applied. Default: Filter= 6. Review the [Capture Buffer] section. Set Size to the size of the capture buffer in kilobytes. The default is 16384 K (16 MB). The maximum supported capture size is 204800 K (200 MB). Default: Size=16384 Set Overwrite to 1 (to overwrite older data if the buffer is full) or 0 (to not overwrite data). Default: Overwrite=0 7. Review the [ALD] section. Set Enable to 1 (to turn ALD on) or 0 (to turn ALD off). If ALD is enabled, ALD latency information is saved in the trace file. Default: 0 Set Port to the ALD port number. Default: 2408 Set Filter to 1 (to filter ALD ping packets out of the captured trace) or 0 (to not filter them out). Default: 0 Set Resolver to 1 (resolve ALD nodes to DNS or NETBIOS names) or 0 (do not resolve). Default: 0 8. Review the [Output File] section. Set Name to the desired path of the output file. If you do not specify a path and name, a file name of the form yyyy-mm-dd_hh.mm.ss.ope will be saved in the Simple Capture directory. 44

Chapter 2 Installation Default: Name= 9. Review the [Interceptors] section. Set EnableBrowser to 1 to enable Browser Data Collection (BDC) or 0 to disable it. Default: EnableBrowser=1 10. Save the captureconfig.ini file if you have made any changes. The sample captureconfig.ini file below uses the default settings. The NicDesc= line will be automatically generated from your own system's settings; do not change it. Capture Utility Config File Version 1.0 [Run Mode] Interactive=true WindowAlwaysOnTop=true Timer=20 [Available NICS] NicDesc=;1 Intel(R) 82567LM-3 Gigabit Network Connection - McAfee NDIS Intermediate Filter Miniport (1) NicIndex=1 Promiscuous=0 [Filter Expression] Filter= [Capture Buffer] Size=16384 Overwrite=0 [ALD] Enable=1 Port=2408 Filter=1 Resolver=0 [Output File] Name= [Interceptors] EnableBrowser=1 45

Chapter 2 Installation 46

CHAPTER 3 Licensing Dynatrace Network Analyzer Dynatrace Network Analyzer is no longer sold as a separate product. Instead, it is included as a feature of DC RUM. One concurrent-user license for Dynatrace Network Analyzer is bundled with a new DC RUM purchase. There is a limit of one bundled license per customer location. Additional DC RUM purchases for the same site will not qualify for the bundled license. Only one bundled license with a DC RUM purchase is allowed per customer location. The bundled Dynatrace Network Analyzer license is considered a feature of DC RUM, so there is no separate maintenance fee for the bundled Dynatrace Network Analyzer components. Additional licenses include normal maintenance. An existing Dynatrace Network Analyzer customer who owns DC RUM cannot get free Dynatrace Network Analyzer maintenance because Dynatrace Network Analyzer was purchased under a different program. For licensing details, please contact your Compuware representative. Understanding Dynatrace Network Analyzer Licensing Dynatrace Network Analyzer (and certain components of it) can be installed with either a node-locked license or a concurrent license. In either case, you must use the Distributed License Management system to manage your licenses. If you are using concurrent licensing, you also need to set up Compuware License Service on a server. Distributed License Management (DLM) Compuware's software products are protected from unauthorized usage via a standard licensing mechanism, Distributed License Management (DLM). DLM software components validate that an appropriate license is available to users and facilitate the license management and administration needs for your Compuware products. Licenses are provided in files that can be installed on individual end-user desktops (for node-locked licenses) or installed on a central license server (for centralized administration of licenses). 47

Chapter 3 Licensing Dynatrace Network Analyzer If you have installed Dynatrace Network Analyzer, DLM is located in Programs Compuware Distributed License Management If you have not installed Dynatrace Network Analyzer, DLM can be run from the Dynatrace product installation program s main menu. Compuware License Service Compuware License Service (cpwr.exe) is a software application that manages the allocation of the purchased concurrent licenses. Compuware License Service can be installed on a Windows server accessible by all users and accessed with the DLM utility. Node-locked Licensing A node-locked license ties your Dynatrace Network Analyzer installation to a particular machine via a unique hardware identifier (generally the NIC MAC Address, but optionally a hard disk signature). Two types of node-locked license are available for Dynatrace Network Analyzer: A trial node-locked license has a fixed expiration date from the time that it is installed on your system. A permanent node-locked license has no expiration date. Such a license is available to existing customers only. Concurrent Licensing To use concurrent (or floating) licensing, you purchase x licenses without assigning them to particular workstations. Instead, the centralized Compuware License Service makes sure that only x licenses are ever in use at any time. When all x licenses are checked out from the server, no additional user can run Dynatrace Network Analyzer (or a specific component Dynatrace Network Analyzer that you have licensed separately) until one of the current users checks his or her license back in. There are two types of concurrent license available for Dynatrace Network Analyzer: Server-based concurrent licensing requires that you be connected to the license server. When you are not connected over the network to the license server, you are unable to use Dynatrace Network Analyzer. Borrow-enabled concurrent licensing does not require a continuous connection to the license server. Instead, you can check out concurrent licenses from Compuware License Service and then use the product while you offline from the license server. When you reconnect to the license server, you can check the license back in, making it available for other users. Setting Up and Using Node-Locked Licensing A node-locked license ties your Dynatrace Network Analyzer installation to a particular machine via a unique hardware identifier (generally the NIC MAC Address, but optionally a hard disk signature). 48

Chapter 3 Licensing Dynatrace Network Analyzer NOTE Dynatrace licenses recognize only the first NIC address identified during system startup. If you have a multi-homed system, you need to obtain a license based on your disk serial number. Such a license is identified by the HOSTID keyword in the license file and must always be run on the machine on which it was originally installed. If you change workstations or NIC cards, you must contact Compuware to obtain a new license. A node-locked license must be requested from Compuware; it is not shipped with the product. There are two types of node-locked license: trial (demo) and permanent. A trial node-locked license has a fixed expiration date from the time that it is installed on your system. A permanent node-locked license has no expiration date. Such a license is available to existing customers only. For node-locked licenses, the use of the Compuware License Service is not required, but can be used if you want a central place to store all of your licenses. Obtaining a Node-locked License To obtain a node-locked license, you must give Compuware the host information for the machine on which the license is to be installed and then receive a machine-specific license file from Compuware. NOTE If you have already received a node-locked license from Compuware, skip to Installing a Node-locked License [p. 49]. 1. Run Distributed License Management (DLM). If you have installed Dynatrace Network Analyzer, DLM is located in Programs Compuware Distributed License Management. If you have not installed Dynatrace Network Analyzer, DLM can be run from the Dynatrace product installation program s main menu. 2. Click the Show System Information hyperlink to view the host information. 3. Click Save To File to open the Save As dialog box. 4. In the Save in list, select a directory and type the name of the text file hostinfo.txt in the File name field. 5. Click Save. 6. Send the file via email to your Dynatrace representative. Installing a Node-locked License After you receive a node-locked license from Compuware, you must open the license file with DLM. 1. Copy the license file provided by Compuware onto your machine. A permanent license will replace any temporary license you had previously installed. 49

Chapter 3 Licensing Dynatrace Network Analyzer 2. Run DLM. 3. Select the Local Environment tab. 4. Click Add and browse to the license file you saved to your machine. 5. Select the license file and click Open to add it to the configuration. 6. Click OK to install the license. What to Do Next NOTE When using multiple Dynatrace products, you can add multiple license files. Refer to the DLM help for more information. The remainder of this chapter is pertinent only to concurrent licensing. If these do not apply to your installation, you can skip to the next chapter. Setting Up and Using Standard Concurrent Licensing Concurrent licensing permits you to use Dynatrace Network Analyzer when you are connected to a license server on a network. When you are not connected over the network to the license server you are not able to use Dynatrace Network Analyzer. NOTE A concurrent license allows multiple users to work at the same time, each using their own dedicated database, not to work on the same database. Dynatrace Network Analyzer allows only a single user to access a given database at one time. When using multiple Dynatrace products, you can add multiple license files. Refer to the DLM help for more information. Determining Need for Compuware License Service Before you set up Compuware License Service, make sure that you need it. If you are using a node-locked license, you do not need Compuware License Service. If you are already using Compuware License Service for another Dynatrace product, you can use the same Compuware License Service for Dynatrace Network Analyzer. You do not need to set up a separate server. Compuware License Service allows you to manage your Dynatrace product licenses and licenses from multiple vendors as long as you are using the same version of the Compuware License Service included with the Dynatrace distribution. You do need to set up a license server if you are going to use concurrent licensing and you do not already have a license server set up for another Compuware product. If you intend to have a large number of concurrent license users, it is a good idea to set up more than one server to offer an alternative if your users have a server access problem. Refer to the DLM help for more information. 50

Chapter 3 Licensing Dynatrace Network Analyzer Setting Up Compuware License Service If you have determined that you need to install Compuware License Service, the license administrator must execute this procedure once to set up Compuware License Service for all users. 1. Select a server location that is available to all intended users when they need to use Dynatrace Network Analyzer. If this is not possible to arrange, you need to use borrow-enabled concurrent licensing, which allows users to connect to Compuware License Service, check licenses out, and then disconnect from Compuware License Service until they need to check the licenses back in. To use borrow-enabled concurrent licensing, continue with the procedures in this section and then follow the procedures on borrowing and returning licenses. For more information, see Borrowing a License [p. 52] and Returning a Borrowed License [p. 53]. 2. Start DLM. 3. Select the Local Environment tab. 4. Click Add to open the Add License Source dialog box. 5. Type the fully qualified path to a license, or click Browse to open the Open dialog box and find the license file, or type the port@host definition. For example: 7188@mylicenseserver; 7188=port and mylicenseserver=host 6. Click OK. You can now use Dynatrace Network Analyzer and the components for which you have obtained licenses. Obtaining a Concurrent License The license administrator must execute this procedure once to make a concurrent license available to all users. 1. Run DLM. If you have installed Dynatrace Network Analyzer, you can run DLM from Programs Compuware Distributed License Management. If you have not installed Dynatrace Network Analyzer, you can run DLM from the Dynatrace product installation program s main menu. 2. Click the Show System Information hyperlink to view the host information. 3. Click Save To File to open the Save As dialog box. 4. In the Save in list, select a directory and type the name of the text file hostinfo.txt in the File name field. 5. Click Save. 6. Send the file via email to your Dynatrace representative. Using Dynatrace Network Analyzer with Concurrent Licensing Each user of a concurrent license must execute this procedure to use the licensed software. 51

Chapter 3 Licensing Dynatrace Network Analyzer To use concurrent licenses on your machine: 1. Start Dynatrace Network Analyzer. Double-click the Dynatrace Network Analyzer program icon that was placed on your Windows desktop during installation, or select Dynatrace Network Analyzer from the Start menu. 2. When you start Dynatrace Network Analyzer as a concurrent user, Dynatrace Network Analyzer opens with the following optional features available (unless there are no licenses available or they have been suppressed): Extended Merge Expert Analysis If licenses are currently unavailable, you are informed as to which licenses are not available and, if possible, the number of licenses stored in Compuware License Service for those options. Once the licenses are acquired, Dynatrace Network Analyzer keeps the licenses until the product is exited. The licenses are then available for other users. Freeing Licenses for Other Users A user of Dynatrace Network Analyzer can suppress (disable) certain licensed features on their own machines if they do not need them. This frees the licenses for those features, making them available to other concurrent users. To suppress licenses on your machine: 1. Start Dynatrace Network Analyzer. Double-click the Dynatrace Network Analyzer program icon that was placed on your Windows desktop during installation, or select Dynatrace Network Analyzer from the Start menu. 2. Select Help About Dynatrace Network Analyzer 3. Click Advanced to open the Product Information dialog box. 4. On the Product Add-In Options tab, click Manage Features to open the Manage Features dialog box. 5. Select Suppress for each listed feature you do not need to use. 6. When you restart Dynatrace Network Analyzer, the suppressed features will be unavailable to you and will be available to other users of the concurrent license for those features. Borrowing a License License borrowing, an extension of concurrent licensing, enables you to check out licenses from Compuware License Service and use the product even while you are disconnected from the network. When you reconnect to the network, the license can be checked back in to make it available to other users. To borrow a Dynatrace Network Analyzer license: 1. Set up standard concurrent licensing. For more information, see Concurrent Licensing [p. 48]. 2. Start the DLM. 52

Chapter 3 Licensing Dynatrace Network Analyzer 3. Click the Local Environment tab. 4. Click the Borrow License Client tab. 5. In the Available Features field, click the feature (license) you want to borrow. This activates the Borrow button (unless the feature has expired). If the feature is part of an association, the button reads Borrow Association. 6. Click Borrow to open the Borrow dialog box. 7. Select either Days or Hours as the interval for this borrow transaction. 8. In the text box, type the number of hours or days you need the license. The time requested cannot exceed 365 days or the equivalent number of hours (and your administrator may have configured a lower maximum). 9. Click Apply to borrow the license. Returning a Borrowed License Follow this procedure to return a license before it has expired. 1. Start DLM. 2. Click the Local Environment tab. 3. Click the Borrow License Client tab. 4. In the Borrowed Features field, click the feature you want to return. 5. Click Return to return the selected license to the server. 53

Chapter 3 Licensing Dynatrace Network Analyzer 54

CHAPTER 4 DNA Silent Installations This is an administrator guide to writing scripts for silently installing or upgrading the DNA console or agent. After you set up a silent installation for each of your users' machines, when your users log in to or start up their machines the products are installed automatically. This makes it easy on the user because there are no prompts for them to answer. Additionally, because the installation is automatic and is identical on all machines, maintenance on those machines is much easier. The InstallShield uses the silent installation option to install DNA console and agents. Silent installations use the Microsoft msiexec command line prompt to silently install agents and probes. This command is run from a command line or the Run box against the Dynatrace-provided *.msi file. Before installing the main application for the agent or the console, it may be necessary to update environmental prerequisites. For example, for a local database, the Microsoft SQL Server database needs to be installed prior to the DNA console. In general, you should execute the following procedures to prepare the system and install the application: 1. For a console installation, update your Microsoft SQL Server database. For the exact instructions, refer to the Microsoft documentation. 2. For a console installation, issue the following command to install the operating system updates: \OS Update\setup.exe -s -f1 C:\OSU_inst.iss 3. If you intend to use the Get Support File function on the agent, issue the following command to install Microsoft.NET: \Transaction Trace Analysis\dotNetFx40_Full_x86_x64.exe /q:a /c: install /q The agent software itself does not require.net, but we recommend that you install.net to make agent troubleshooting easier. The Get Support File troubleshooting tool that is installed with the agent software requires that.net 4.0 or later be installed on the target machine. If you prefer, you can install.net if and when you need to run GetSupportFile for troubleshooting. 55

Chapter 4 DNA Silent Installations 4. For a console installation, issue the following command to install Microsoft Primary Interoperability Assemblies: \Transaction Trace Analysis\vs_piaredist.exe 5. Issue the following command to install the console or agent: msiexec /I <productinstaller> <switch> where <productinstaller> is the file path and file name of the product you are installing: For the console: \Transaction Trace Analysis\Transaction Trace.msi For the agent: \Transaction Trace Analysis\Transaction Trace Analysis Agent Installer\Transaction Trace Agent.msi <switch> is one of these switches: /I /qn /qb Installs or configures a product. Run in quiet mode with no user interface displayed. Quiet and basic user interface, which displays a small window that shows the progress of the installation. DNA Console Installation Command Syntax This section describes the properties you can use when writing scripts for silent installations of the DNA console. Sample scripts are included at the end. Properties for New Console Installation Scripts This section describes the supported properties for new installations of the DNA console. NOTE All of these properties are always optional except DBPASSWORD, which is required when DBSKIP=False INSTALLDIR The main product installation directory for an installation. The default is: [PROGRAMFILES]Compuware\Transaction Trace\ This typically resolves to: C:\Program Files\Compuware\Transaction Trace\ Important: The trailing backslash (as shown above) is required. DBSKIP Instructs the installation whether to skip or omit creating the DNA database. Possible values: False (default) or True 56

Chapter 4 DNA Silent Installations NOTE When DBSKIP=False, the property DBPASSWORD (see below) is mandatory. DBSERVER Identifies the SQL server Instance where the DNA database is to be created. This server can be either local or remote. IMPORTANT If you use DBSERVER=(local) with a silent installation, the database instance name must be MSSQLSERVER. If you use another name, installation won't create a database. Default: (local) DBNAME Identifies the DNA SQL server database name to be created. DBUSER Identifies the user ID to be used to log on to the SQL Server where the DNA database is to be created. For SQL authentication, set DBUSER to an administrator's ID For Windows authentication, set DBUSER to Trusted DBPASSWORD Identifies the password for the SQL server user ID with system administrator (sa) privileges to create, drop, or modify the DNA database. This property is mandatory when DBSKIP=False IMPORTANT When the console is installed silently, it requires a correct DBPASSWORD parameter (database administrator password, user 'sa') to install a sample database and then install Trace Trimmer. If this DBPASSWORD is incorrect, the sample database is not installed and, consequently, Trace Trimmer setup fails. For SQL authentication, set DBPASSWORD to the password of the administrator specified by DBUSER For Windows authentication, set DBPASSWORD to Trusted DBPATH Identifies the path on the SQL server where the DNA database files are to be created. Default: [Microsoft SQL Server Data Directory] DBSIZE Identifies the initial creation size (in megabytes) of the DNA database file. Default: 30 DBLGSIZE Identifies the initial creation size (in megabytes) of the DNA database Log file. Default: 12 57

Chapter 4 DNA Silent Installations BROWSERDATA Indicates whether you want to install the Browser Data Collector agent or not. IMPORTANT To silently install the console or agent with BDC, it is necessary to set BROWSERDATA=1 and ADDLOCAL=ALL Possible values: 1 to turn on the Browser Data Collector agent; 0 to leave the Browser Data Collector agent turned off. Default: 0 ADDLOCAL Lists the features that are to be installed. When BROWSERDATA=1 or ALL, all the features are to be installed. When BROWSERDATA=0, the default installs all features except the Browser Data Collection Agent. IMPORTANT To silently install the console or agent with BDC, it is necessary to set BROWSERDATA=1 and ADDLOCAL=ALL PROMISCUOUS With promiscuous mode on, all traffic seen on that NIC is captured, regardless of whether the traffic was intended for that NIC. With promiscuous mode off, only the traffic that the NIC is intended to receive is captured. Possible values: 1 (on) or 0 (off). Default: 1 (on) PORT Port number Default: 2408 DBSAMPLES Install sample database. Possible Values: True or False Default: True INSTALLTRACETRIMMER Indicates whether you want to install Trace Trimmer. Possible values: Y or N Default: Trace Trimmer is installed by default (if this parameter is omitted, Trace Trimmer is installed). Samples Here is an example of a script to install DNA installation silently using the mandatory properties and the default settings: 58

Chapter 4 DNA Silent Installations msiexec.exe /i "<Drive>\<Path>\Transaction Trace.msi" /qn /lv [path]\silentinstall.log DBPASSWORD=<password> DBSERVER=(local) Where <Drive>\<Path> would be replaced with the actual drive and path of the msi file. <password> would be replaced with the actual password of the database administrator Here is a similar example with the optional properties added: msiexec.exe /i "<Drive>\<Path>\Transaction Trace.msi" /qn INSTALLDIR="C:\Program Files\Compuware\Transaction Trace\" INSTALLTRACETRIMMER=N DBUSER=sa DBPASSWORD=<sapassword> PROMISCUOUS=1 PORT=2409 The example below is identical to the previous example except that this one uses Windows authentication: msiexec.exe /i "<Drive>\<Path>\Transaction Trace.msi" /qn INSTALLDIR="C:\Program Files\Compuware\Transaction Trace\" INSTALLTRACETRIMMER=N DBUSER=Trusted DBPASSWORD=Trusted PROMISCUOUS=1 PORT=2409 Dynatrace Network Analyzer Console Upgrade Command Syntax This section shows how to write a script to silently upgrade the Dynatrace Network Analyzer console. Properties for Console Upgrade Scripts This section describes the supported properties for upgrading the Dynatrace Network Analyzer console. These are the only properties that are required for an upgrade. Do not use any of the properties for new installations when performing an upgrade. REINSTALLMODE vomus REINSTALL ALL Sample This example script upgrades Dynatrace Network Analyzer silently: msiexec.exe /i "<Drive>\<Path>\Transaction Trace.msi" /qn DBPASSWORD=<password> REINSTALLMODE=vomus REINSTALL=ALL Where: Only the two mandatory properties listed above (REINSTALLMODE and REINSTALL) are used. <Drive>\<Path> would be replaced with the actual drive and path of the msi file. 59

Chapter 4 DNA Silent Installations <password> would be replaced with the actual password of the database administrator if you are using SQL authentication, or would be replaced with the string Trusted if you are using Windows authentication. IMPORTANT When the console is installed silently, it requires a correct DBPASSWORD parameter (database administrator password, user 'sa') to install a sample database and then install Trace Trimmer. If this DBPASSWORD is incorrect, the sample database is not installed and, consequently, Trace Trimmer setup fails. Dynatrace Network Analyzer Agent Installation Command Syntax This section describes the properties you can use when writing scripts for silent installations of the Dynatrace Network Analyzer Agent (Windows only). Sample scripts are included. Properties for New Agent Installation Scripts Use the properties described for fresh installations of agents. AVUSERNAME, AVPASSWORD These two parameters specify the login and password used to connect to and operate an agent (initiate/terminate capture, change settings, collect cached packet capture data, etc.). Compare with AVAUTHFILE. AVAUTHFILE This parameter is mandatory if you do not specify AVUSERNAME and AVPASSWORD. Instead of specifying AVUSERNAME and AVPASSWORD in the command, you can use AVAUTHFILE to specify the path to a pre-generated file containing an encrypted agent username and an encrypted agent password. The syntax is AVAUTHFILE=filepath. To create the file, you have to use a small standalone application that takes a typed user name and password and writes an encrypted file. For more information, see Creating an Encrypted User Credentials File for Silent Agent Installations [p. 31]. Compare with AVUSERNAME and AVPASSWORD. TARGETDIR Mandatory. The destination of an administrative installation. Default: <Program Files Directory>\Compuware\Transaction Trace Agent NOTE TARGETDIR instructs the installation where to write the PortCfg.txt and ttagentauth.ppp files. If you want to specify an alternate INSTALLDIR, you must specify both the INSTALLDIR and TARGETDIR Properties with the same value. INSTALLDIR Optional. The main product installation directory for an installation. 60

Chapter 4 DNA Silent Installations NOTE If the installation directory (INSTALLDIR) is changed, the TARGETDIR must be changed to match this value. The INSTALLDIR Property can be left off to use the default, but TARGETDIR cannot. If you want to specify an alternate INSTALLDIR, you must specify both the INSTALLDIR and TARGETDIR Properties with the same value. PROMISCUOUS With promiscuous mode on, all traffic seen on that NIC is captured, regardless of whether the traffic was intended for that NIC. With promiscuous mode off, only the traffic that the NIC is intended to receive is captured. Possible values: 1 (on) or 0 (off). Default: 1 (on) DATADIR Optional. Location of the directory where cached unattended capture data is stored. Default: C:\Documents and Settings\All Users\Application Data\Compuware\Transaction Trace Agent\ PORT Optional. Port number Default: 2408 BROWSERDATA Optional. Indicates whether you want to install the Browser Data Collector Agent or not. Possible values: 1 to turn on the Browser Data Collector Agent; 0 to leave the Browser Data Collector Agent turned off. IMPORTANT To silently install the console or agent with BDC, it is necessary to set BROWSERDATA=1 and ADDLOCAL=ALL Default: 0 ADDLOCAL Lists the features that are to be installed. When BROWSERDATA=1 or ALL, all the features are to be installed. When BROWSERDATA=0, the default installs all features except the Browser Data Collection Agent and ADDLOCAL is not needed. IMPORTANT To silently install the console or agent with BDC, it is necessary to set BROWSERDATA=1 and ADDLOCAL=ALL AVPASSWORD2 Optional. If used, must match AVPASSWORD. Only needed without the silent /qn switch. Otherwise, this password confirmation property should not be included with the script. For Dynatrace Network Analyzer, when running in silent mode (using /qn) you do not need to specify the AVPASSWORD2 property. This property is only used during user 61

Chapter 4 DNA Silent Installations interface processing to confirm that the user entered the same password in both fields of the window. Samples Here is an example of a script to install Dynatrace Network Analyzer Agent silently using the mandatory properties and the default settings described above. msiexec.exe /i "<Drive>\<Path>\Transaction Trace Agent.msi" /qn AVUSERNAME=<username> AVPASSWORD=<password> TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\" Below is a similar example with the optional properties added. Be sure to provide your own meaningful username and password for AVUSERNAME and AVPASSWORD. msiexec.exe /i "C:\Transaction Trace Analysis Agent\Transaction Trace Agent.msi" /qn INSTALLDIR="C:\Program Files\Compuware\Transaction Trace Agent\" TARGETDIR="C:\Program Files\Compuware\Transaction Trace Agent\" AVUSERNAME=adminusername AVPASSWORD=adminpassword PROMISCUOUS=1 DATADIR=C:\AgentData PORT=2409 Creating an Encrypted User Credentials File for Silent Agent Installations To use an encrypted user credentials file with the AVAUTHFILE parameter during a silent agent installation, you have to run a small standalone utility included on your software distribution media. 1. On your software distribution media, locate the AVpasswd.zip file. 2. Unzip the file to a local directory. 3. Double-click the AVpasswd file to run the utility. 4. Type a user name and password in the edit boxes. 5. Change the destination folder if necessary. 6. Click the Generate now button. What to Do Next The output file can now be referred to by an AVAUTHFILE parameter in an agent installation command. For more information, see Dynatrace Network Analyzer Agent Installation Command Syntax [p. 60]. To run the AVpasswd utility in batch mode: 1. Open the Windows command prompt. 2. Change the current directory to the folder in which AVpasswd was extracted. 3. Type bin\avpasswd.exe u<username> -p<password> -o"<outputfolder>" For example: bin\avpasswd.exe ualice pwhit3r4bbit -o"c:\myttaagentpasswords\agent007" 4. Wait until a new file ttagentauth.ppp is created at the path provided 62

Chapter 4 DNA Silent Installations Installing a Compuware Certificate To install the agent remotely or silently, you should first install a Compuware certificate in the Trusted Publishers certificate store. NOTE You can distribute the certificate to multiple remote machines using Microsoft Group Policy. The certificate needs to be added to the store Trusted Publishers\Local Computer as follows: 1. In your Windows Explorer, right-click the Compuware.cer file and select Install certificate from the menu. The certificate file Compuware.cer is located in the Transaction Trace Analysis Agent Installer folder in the Dynatrace Network Analyzer distribution. The Certificate Import Wizard will open. 2. On the Certificate Import Wizard screen, click Next. The Certificate Store screen will be displayed. 3. Select Place all certificates in the following store and click Browse. 4. In the Select Certificate Store window, select the Show physical stores check box, expand the Trusted Publishers node, select Local Computer, and click OK. The Certificate Store screen will be displayed again but with Place all certificates in the following store selected and Trusted Publishers\Local Computer specified in the Certificate store field. 5. Click Next. The Completing the Certificate Import Wizard screen will display a summary of the intended import. 6. If the summary is correct, click Finish. The certificate will be added to Trusted Publishers\Local Computer and a window will display The import was successful. Performing a Silent Agent Installation You can use the silent (or quiet) installation options for installing the Enterprise Synthetic agent, Dynatrace Network Analyzer Agent, and Server Monitoring agent. IMPORTANT To install the agent remotely or silently, you should first install a Compuware certificate in the Trusted Publishers certificate store. For more information, see Installing a Compuware Certificate [p. 39]. To silently install a product, type: msiexec /i <product>.msi /qn PROPERTY1="<VALUE>" PROPERTY2="<VALUE>" where <product> is the name of the product you are installing and /i and /qn are switches. 63

Chapter 4 DNA Silent Installations The MSI file Transaction Trace Agent.msi is in the distribution in the \Transaction Trace Analysis\Transaction Trace Analysis Agent Installer directory. The supported switches are: /i /qn /qb The i switch (install) installs installs or configures a product. The /qn switch (quiet mode, no interface) runs the installation in quiet mode with no user interface displayed. The qb switch (quiet mode, basic interface) runs the installation in quiet mode with a basic user interface, which displays a small window showing the progress of the installation. Use qb-! if you want to reboot the machine silently (no user confirmation) after installation. For more information, see Dynatrace Network Analyzer Agent Installation Command Syntax [p. 60]. If you are performing an upgrade, do not use any of the properties for new installations when performing the upgrade. For more information, see Dynatrace Network Analyzer Agent Upgrade Command Syntax [p. 64]. Dynatrace Network Analyzer Agent Upgrade Command Syntax This section describes the only properties required for performing an agent upgrade. Do not use any of the properties for new agent installations when performing an upgrade. Properties for Agent Upgrades If you are performing an agent upgrade, the following properties are the only properties that are required. REINSTALLMODE vomus REINSTALL ALL Sample The script below is an example for upgrading an agent. Note that it uses only the two properties listed above. msiexec.exe /i "C:\Transaction Trace\Transaction Trace Agent Installer\Transaction Trace Agent.msi" /qn REINSTALLMODE=vomus REINSTALL=ALL 64

CHAPTER 5 Uninstallation Uninstallation removes DNA software from your machines. Console Uninstallation - Interactive Follow this procedure to interactively uninstall the Dynatrace Network Analyzer console software. Before You Begin Be sure to save any open work in other applications before uninstalling Dynatrace Network Analyzer console. 1. From the Start button, select Settings Control Panel Add/Remove Programs to open the Add or Remove Programs utility. 2. Select Dynatrace Network Analyzer and click Change/Remove. 3. When the InstallShield Welcome dialog box opens, click Remove and then Next. 4. When the Database Uninstall dialog box appears, you are given the opportunity to remove the databases, click Skip to leave the databases on your computer, or type the identifying database information and click Next to remove the databases. 5. When a dialog box asks you to confirm that you want to completely remove Dynatrace Network Analyzer and all of its features, click OK. CAUTION If a Files in Use dialog box indicates that Windows Explorer needs to be updated by this setup, do not indicate that you want to Windows Explorer until you save any open work in other applications on this machine. 6. When maintenance is complete, click Finish. 65

Chapter 5 Uninstallation Console Uninstallation - Silent Follow this procedure to uninstall the Dynatrace Network Analyzer console software silently (minimal user input required). Before You Begin Be sure to save any open work in other applications before uninstalling Dynatrace Network Analyzer console. To uninstall the Dynatrace Network Analyzer console software silently. 1. On the machine from which you are removing Dynatrace Network Analyzer, open a command window. a. In Windows, click Start Run. b. In the Run window, type cmd and click OK. 2. In the cmd.exe window, issue the command: msiexec.exe /qn /x [path1]\transaction Trace.msi /lv [path2]\uninstall.log path1 is the path to the Transaction Trace.msi file used to install Dynatrace Network Analyzer on this machine. path2 is the path to where you want to write a log file of the uninstallation process. q = quiet n = no interface Example 1. msiexec.exe /qn /x [path1]\transaction Trace.msi /lv [path2]\uninstall.log 3. Do not interrupt the process. Wait for Dynatrace Network Analyzer to be uninstalled completely before rebooting the machine. Windows Agent Uninstallation Follow this procedure to remove Dynatrace Network Analyzer Agent software from a Windows machine. 1. From the Start button, select Settings Control Panel Add/Remove Programs to open the Add or Remove Programs utility. 2. Select the Compuware Dynatrace Network Analyzer Agent line and click Remove. 3. When the InstallShield dialog box opens, follow the on-screen instructions. 66

Windows Agent Uninstallation - Silent You can uninstall Dynatrace Network Analyzer Agent silently via the command prompt. To remove Dynatrace Network Analyzer Agent, you must determine the agent's GUID and then use that GUID in an MsiExec call. NOTE A globally unique identifier (GUID) is a unique key generated during installation and used as an internal reference by the operating system. To obtain the agent GUID key and silently remove the agent: 1. In Windows, open the Add/Remove Programs control panel and note the Dynatrace Network Analyzer Agent application title. Typically, the agent title includes the Dynatrace Network Analyzer Agent string that should be used as a search criteria during next steps. 2. Open regedit. From the Windows Start button, select Run and then issue the command regedit. 3. Search the registry for the application title obtained in Step 1 [p. 67]. The agent's globally unique identifier (GUID) should be located in HLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, but some operating systems may store it otherwise. The GUID will be a key such as: B8C9D638-29A3-4D73-A0D6-57BFA6D55BBC with { and } brackets on either end. 4. From the command prompt, execute the following command: MsiExec.exe /X {GUID} /qn Where GUID is the key you found in Step 3 [p. 67]. Example 2. MsiExec.exe /X{ADFC76B7-3718-4569-943D-EE00EE637D38} /qn 5. To verify that the agent has been removed, open the Add/Remove Programs control panel again. Unix Agent Uninstallation Follow this procedure to remove Dynatrace Network Analyzer Agent software from a Unix machine. Stop the agent before un-installing. NOTE Chapter 5 Uninstallation The following steps assume the Dynatrace Network Analyzer Agent is installed in the /opt/avagt folder and that you have root access. 67

Chapter 5 Uninstallation 1. Type the following commands: cd /opt/avagt./uninstall 2. To confirm your decision to un-install the agent, the un-install script forces you to type uninstall again. (Prompt: Verify your desire to uninstall Dynatrace Network Analyzer Agent by typing uninstall now =>) You must type the command uninstall to continue with the un-installation process. Any other response cancels the uninstall. 3. The uninstall script identifies the agent home directory where the executables are stored and asks for your confirmation. (Prompt: Is "/opt/avagt" the correct Home Directory to uninstall the agent from (y/n) [y] =>) 4. Type y to confirm the directory name. Any other response aborts the un-installation process. 5. If there are un-retrieved capture data files in the installation directory, the uninstall script asks you to confirm deletion of these files (Prompt: Would you like to remove the.opx data files from "/opt/avagt directory? (y/n) [y] =>). Answering n keeps those data files unremoved in the installation directory. Answering y results in the whole installation directory being removed. All files for the agent are removed, regardless the answer to the above question, including: Files in the agent home directory Unattended capture data file directory Boot time automatic restart files (if specified during install) The agent configuration file, /etc/appvantageagentinstall.cfg 68

CHAPTER 6 Troubleshooting Installation Problems Check this section for help on troubleshooting installation problems. Capture After modifying an existing DNA installation through the Control Panel, the installation becomes unusable. If you modify an existing DNA installation by choosing Uninstall/Change from the Control Panel\Programs\Programs and Features list: the DNA console and Trace Trimmer fail to load and initialize properly. A capture driver is erroneously removed during this installation modification. Workaround: 1. Locate AVSimpleCaptureUtility.zip in the APM distribution. This file can be found in folder Transaction Trace Analysis\Capture Utility 2. Unzip the files appropriate to your system: For a 32-bit machine, unzip: cwenprobe.cat cwenprobe.sys enprobe.inf For a 64-bit machine, unzip: cwenprobe64.cat cwenprobe64.inf cwenprobe64.sys 3. Open the Network Connections dialog from the Control Panel ( Control Panel\Network and Internet\Network Connections ). 4. Right-click on an active connection and select Properties from the pop-up menu. 5. Click Install in the Network Connection Properties dialog. 6. Select Protocol from Select Network Feature Type and click Add. 7. Click Have Disk in the Select Network Protocol dialog box. 69

Chapter 6 Troubleshooting Installation Problems 8. Click Browse in Install From Disk dialog and point to previously unzipped INF file. 9. After installing the capture driver, reboot the computer. The list of local adapters available for capturing data is empty This may occur on Windows 8 (32-bit and 64-bit) and Windows 2012 machines. The Local Adapters list should be similar to the one pictured here, with a selection for All NICs/Ports Simultaneously and an additional selection for each available adapter on the machine. If this list is instead empty, restart the capture driver to repopulate it: 1. Open the Transaction Trace target folder, which typically is: C:\Program Files (x86)\compuware\transaction Trace 2. Right-click the RestartDriver.cmd and select Run as administrator. If the problem occurs frequently, it can be resolved permanently by creating a task in Windows Scheduler to restart the driver at any user logon. To do so: 1. Open the Transaction Trace target folder, which typically is: C:\Program Files (x86)\compuware\transaction Trace 2. Right-click CreateTask.cmd and select Run as administrator. Trace Trimmer Trace Trimmer cannot be configured through the Windows Control Panel after DNA upgrade. You can change some Trace Trimmer settings through the Windows Control Panel. 70

Chapter 6 Troubleshooting Installation Problems Sometimes, however, it is not possible to open the Trace Trimmer control panel after upgrading Dynatrace Network Analyzer. Workaround: open the configuration application from the command line. 1. Navigate to the Trace Trimmer uninstall folder (usually C:\Program Files\Compuware\Transaction Trace\TraceTrimmer\_uninst). 2. Run the following command:..\_jvm\bin\java.exe -jar uninstall.jar 71

Chapter 6 Troubleshooting Installation Problems 72

Index Index A access rights 25 27 Active Directory Group Policy 34 administrator rights 25 27 agent 9, 30 32, 34 36, 38, 55, 60, 62 64, 66 67 installation scripts 34 installing 31, 60, 62 scripts 31, 60, 62 Linux 35 installing 35 removing 67 silent installation 30, 63 silent uninstall 55, 67 system requirements 9 uninstalling 66 67 Unix 67 Windows 66 Unix 35 36 installing 35 listing files 36 upgrading 64 command syntax 64 Windows 32, 34, 38 technical notes 38 AVpasswd 31, 62 AVUsers 25 27 B Browser Data Collection (BDC) 21, 25, 32, 40, 56, 63 console installation 56 Browser Data Collection (BDC) (continued) console installation (continued) silent 56 enabling add-on in Internet Explorer 25, 40 installing during console installation 21 installing during silent agent 63 installing with Windows agent 32 C certificate 39, 63 installing in Trusted Publishers certificate store 39, 63 command syntax 31, 60, 62, 64 installing Dynatrace Network Analyzer Agent 31, 60, 62 upgrade agent 64 Compuware License Service 48 console 65 66 uninstalling 65 66 silent 66 D database management 15, 17, 21 database requirements 15 migrating 17, 21 deleting 66 67 uninstalling Unix agent 67 uninstalling Windows agent 66 Distributed License Management (DLM) 47 DLM 47 DNA Simple Capture 41 installing 41 73

Index E elevating user privileges 25 27 H hardware requirements and recommendations 7, 9 11 Dynatrace Network Analyzer Agent 10 11 Unix 11 Windows 10 Dynatrace Network Analyzer console 7, 9 I installing 19 21, 30 32, 34 35, 41, 55 56, 59 60, 62 64 DNA Simple Capture 41 Dynatrace Network Analyzer Agent 30 32, 34 35, 55, 60, 62 64 administrator options 30 Linux 35 scripts 34 silent 30, 55, 63 64 Unix 35 Windows 32, 34 Dynatrace Network Analyzer console 19 21, 55 56, 59 silent 55 56, 59 L licensing 47 53 Compuware License Service 48, 50 51 determining need for 50 setting up 51 concurrent 48, 50 53 borrowing a license 52 freeing a license for others 52 obtaining 51 returning a borrowed license 53 setting up and using 50 using with Dynatrace Network Analyzer 51 DLM 47 node-locked 48 49 installing 49 obtaining 49 setting up and using 48 understanding Dynatrace Network Analyzer licensing 47 Linux agent 35 installing 35 local system account on SQL server 17 M migrating databases 17, 21 Mongoose 25 N network task offload 24 disabling 24 node-locked license 48 49 installing 49 obtaining 49 setting up and using 48 O operating system requirements 8, 10 11 Dynatrace Network Analyzer Agent 10 11 Unix 11 Windows 10 Dynatrace Network Analyzer console 8 P PSExec 34 R remote installation of 34 Dynatrace Network Analyzer Agent 34 removing 67 Dynatrace Network Analyzer Agent 67 requirements 7 11, 30 Dynatrace Network Analyzer Agent 10 11, 30 Unix 11, 30 Windows 10, 30 Dynatrace Network Analyzer console 7 9 Response Time Predictor 25 Mongoose and 25 S script 34 install agent 34 upgrade agent 34 server 16 authentication on SQL server 16 silent installation 21, 30 31, 55 56, 60, 62 63 74

Index silent installation (continued) Dynatrace Network Analyzer Agent 31, 60, 62 Dynatrace Network Analyzer console 56 silent removal 67 Dynatrace Network Analyzer Agent 67 Simple Capture 41 42 configuring 42 installing 41 software requirements 8 Dynatrace Network Analyzer console 8 software requirements and recommendations 7, 10 11 Dynatrace Network Analyzer Agent 10 11 Unix 11 Windows 10 Dynatrace Network Analyzer console 7 Solaris zone 37, 40 SQL server 15 17 changing service to local system 17 configuring an existing installation 15 enabling server authentication on 16 enabling SQL server browser 16 enabling TCP/IP on 16 SQL server browser 16 enabling 16 SQL Server Management Studio 20 installing 20 SQL service 18 restricting 18 system requirements 7 11 agent 9 Dynatrace Network Analyzer Agent 10 11 Unix 11 Windows 10 Dynatrace Network Analyzer console 7 9 T task offload 24 disabling 24 TCP/IP 16 TCP/IP (continued) enabling on SQL server 16 Trace Trimmer 29 configuration 29 troubleshooting 69 Trusted Publishers certificate store 39, 63 installing certificate in 39, 63 U unattended capture mode 9 system recommendations 9 uninstalling 65 67 Dynatrace Network Analyzer Agent 67 Dynatrace Network Analyzer console 65 66 silent 66 Unix agent 67 Windows agent 66 Unix agent 35 36, 67 installing 35 listing files 36 uninstalling 67 upgrading 20, 55, 59, 64 Dynatrace Network Analyzer Agent 55, 64 silent 55, 64 Dynatrace Network Analyzer console 20, 55, 59 silent 55, 59 user 25 27 console 25 27 adding 25 27 deleting 25, 27 user privileges 25 27 V VMware 27 W Windows agent 32, 34, 66 uninstalling 66 75

Index 76