Preparing for installation of App Visibility agent for .NET
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
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:\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
- Reinstall the Operations Manager agent without .NET Application Performance Monitoring, as
. Ensure that you use the
SCOM APM is not installed and will not interfere with agent for .NET.
To configure the required Terminal Server options
On Windows, 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.
You must configure the Terminal Server options only once on a host computer. You do not have to configure the options if you reinstall a TrueSight product on the same host computer.
Do the following:
- On the host computer, open the Local Group Policy Editor by selecting Start > Run, and type gpedit.msc.
- Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
- Double-click the following options to set them to Enabled:
- Do not delete temp folder upon exit
- Do not use temporary folders per session
- On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
- Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
- Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
- Restart the computer.
You can revert these changes after you complete the installation process. You might need to restart the computer.
Where to go from here
If you are installing the product, perform the other preinstallation tasks listed in the Preparing to install the TrueSight Operations Management solution page.