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
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
- Uninstall the Operations Manager agent.
- 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 Terminal Server options on Windows
If you are planning to install Remedy SSO on a host computer with Windows, configure the following Terminal Server options that pertain to temporary folders. Doing this enables you to run the installation utility through a Terminal Services connection or a remote desktop session.
Note
- You need to configure the Terminal Server options only once on a host computer running on Windows.
- You do not have to configure the options if you are planning to install Remedy SSO on running on Linux or you are reinstalling a TrueSight product on the same host computer running on Windows.
- On the host computer, from Start, type Run and press Enter, and type
gpedit.msc
and press Enter.
The Local Group Policy Editor is opened. - From the Local Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folder.
- Double-click the following options and set each to Enabled:
- Do not delete temp folder upon exit.
Do not use temporary folders per session.
Back up the Windows registry and avoid receiving notification about Terminal Server configuration at the time of product installation:
- On the host computer, from Start, type Run and press Enter, and type
regedit
and press Enter.
The Registry Editor is opened. - From the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
Set the value for PerSessionTempDir and DeleteDeleteTempDirsOnExit to 0.
Note
You can revert these changes after you complete the installation process.
- On the host computer, from Start, type Run and press Enter, and type
Restart the host computer.
Where to go from here
Select an installation method for agent for .NET:
- Performing the installation of the App Visibility agent for .NET
- Performing the silent installation of the App Visibility agent for .NET
Comments
Log in or register to comment.