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

The following topics provide information about preparing your environment before you install the App Visibility server:

Preinstallation tasks for the App Visibility server components

To prepare for the App Visibility proxy component

As the system administrator, configure your network to ensure that the App Visibility proxy can collect end-user browser data, and pass it on to the App Visibility collector and portal.

Before you install the App Visibility proxy, configure the following items:

  1. Define a host name that resolves to the App Visibility proxy’s IP address, or to a Virtual IP on a load balancing server.
  2. Create a certificate in which the Common Name matches the defined host name.
  3. Configure the load balancing server to do the following actions:
    • Negotiate HTTPS using the certificate created in Step 2.
    • Redirect end-user HTTP/HTTPS requests from this host name to the host:port of the App Visibility proxy.


To use the App Visibility portal or collector in a Microsoft System Center Operations Manager (SCOM) version 2012 environment, you must disable application performance monitoring for SCOM. For more information, see the SCOM product documentation.

To remove SCOM APM

  1. Uninstall the Operations Manager agent , also know as Microsoft Monitoring 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 App Visibility portal or collector.

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.


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 the App Visibility server:

Related topics

System requirements for App Visibility Manager

Sizing App Visibility Manager and Synthetic TEA Agent components

App Visibility Manager high-availability deployment

Upgrading the App Visibility server



  1. The above states the following under the "Preinstallation tasks for the App Visibility server components" section:

    • User defined in the sudo file with root privilege

    Per Omer David in App Visibility Engineering team, this statement is incorrect and needs to be corrected.  The correct information is that only a user with id 0 can run the App Visibility Server installation, which is the 'root' user (or a renamed root). Any other users with sudo root privileges will fail on validation.

    Please make the necessary corrections on this documentation page.





    1. Thanks, Winsor! I confirmed the correction and updated the documentation.