Page tree
Skip to end of metadata
Go to start of metadata

This topic provides information about preparing your environment before installing the App Visibility agent for .NET.

This topic presents the following sections:

Install the App Visibility server

Before you install the App Visibility agents, which require the IP address or host name of the App Visibility portal and its port number, install the App Visibility server components.

Install IIS Management Scripts and Tools

If you are monitoring applications hosted on an IIS server, ensure that IIS Management Scripts and Tools are installed. The App Visibility agent for .NET employs the memory usage events feature to access application pool settings. On the computer where you are installing the agent, ensure that IIS Management Scripts and Tools is selected:

  • Microsoft Windows 2008 R2

  • Microsoft Windows 2012

Download installation files

Download the agent for .NET installation files from the Electronic Product Distribution site.

Confirm access and permissions

When you perform an installation or upgrade, you must use an IIS Application Pool Identity that has read and execute access to the installation directory, subdirectories, and files for App Visibility agent for .NET. Specifically, you must have Traverse folder access to the agent installation directories. For example, if %ProgramFiles(x86)% is C:\Program Files (x86), you need Traverse folder access to the following directories:

  • C:\
  • C:\Program Files (x86)\
  • C:\Program Files (x86)\BMC Software\
  • C:\Program Files (x86)\BMC Software\App Visibility\

Remove SCOM APM

To use agent for .NET in a Microsoft System Center Operations Manager (SCOM) version 2012 environment, you must disable application performance monitoring for SCOM, because only one application can use the .NET CLR Profiler at a time. For more information, see the SCOM product documentation.

To remove SCOM APM

  1. Uninstall the Operations Manager agent.
  2. Reinstall the Operations Manager agent without .NET Application Performance Monitoring, as described in the SCOM product documentation . Ensure that you use the NOAPM=1 switch.

SCOM APM is not installed and will not interfere with agent for .NET.

To configure the required Terminal Server options

On a Windows operating system, to run the installation utility through a Terminal Services connection or a remote desktop session, configure the Terminal Server options that pertain to temporary folders.

  1. On the host computer, open the Local Group Policy Editor by selecting Start > Run and typing gpedit.msc.
  2. Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
  3. Double-click the following options to set each to Enabled:
    • Do not delete temp folder upon exit
    • Do not use temporary folders per session
  4. Restart the computer.

Troubleshooting tip

If you receive a notification about Terminal Server configuration when you run the installation, perform the following steps to back up the registry and adjust the registry key values as follows:

  1. On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
  2. Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
  3. Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
  4. Restart the computer.

Note

You can revert these changes after you complete the installation process. You might need to restart the computer.

Where to go from here

Select an installation method for agent for .NET:

Related topics

System requirements for App Visibility Manager

Known and corrected issues