On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
19 rates
The instructions below show you how to fetch and install a Synthetic Private Agent on a Windows Server 2012 machine. 

The installation of the Synthetic Private Agent will make the following changes to your system:

  • Install the Synthetic Private Agent.
  • Install browsers.
  • Configure many aspects of Windows to make it amenable for collecting performance data from browsers, including changing several Windows registry settings.
  • Turn on the Windows firewall and prevent any inbound network connections to the server.

Prerequisites

Before beginning the installation, confirm that you have completed the following:

Installation Steps

Follow the steps below to install the Synthetic Private Agent:

Fetch the Synthetic Private Agent

Navigate to the AppDynamics Downloads and download the Synthetic Private Agent.

Log in as the Administrator

Before you can copy and run the Synthetic Private Agent installer, you are required to log in as the administrator to the dedicated Windows machine for the Synthetic Private Agent.

Copy/Move the Synthetic Private Agent to Your Dedicated Machine

  1. Move or copy the compressed archive file SyntheticAgentInstaller.zip containing the Synthetic Private Agent to this machine. 

  2. Unzip and decompress the archive file.
  3. Confirm that the directory SyntheticAgentInstaller contains the installer script install.ps1

Set Up an HTTP Proxy (Optional)

To use a proxy to connect the Synthetic Private Agent to the EUM Cloud, you need to set the system variable SYNTHETIC_DRIVER_OPTS to the value shown below, replacing <url> and <port> with the URL and port to your proxy. See Configuring System and User Environment Variables to learn how to set system variables.

Key: SYNTHETIC_DRIVER_OPTS
Value: -Dhttps.proxyHost=<url> -Dhttps.proxyPort=<port>

This method does not work for proxies requiring authentication.

Prepare Account and Location Information

Before you install the Synthetic Private Agent, you will need the following information:

  • EUM Account Name / EUM License Key:
    1. Go to your SaaS Controller.
    2. Navigate to License > Peak Usage.
    3. Scroll down to the User Experience section.
    4. Copy the values for the Account Name and License Key fields.
  • Location name: A user-friendly string for the location. You can use the same location information on multiple computers to add capacity to that location. For example, if the private location is for multiple machines running from the company office in SF, you might use "SF Office".
  • Location ID: A unique alphanumeric string from 4-10 characters identifying a location where one or more agents may be running. You should create this ID based on the location name. 
  • Latitude and longitude of the location: Navigate to the GPS Coordinates with Google Maps tool at 
    https://www.gps-coordinates.net to get the latitude and longitude of your location.

Run the Installer

After you unzip and decompress the archive file:

  1. Open a PowerShell console.
  2. Change to the directory SyntheticAgentInstaller.

  3. Set the PowerShell execution policy to Unrestricted

    > Set-ExecutionPolicy Unrestricted
  4. Execute the PowerShell script install.ps1 to install the Synthetic Private Agent, Internet browsers, and make changes to the Windows configuration:

    > .\install.ps1
  5. At the command prompts, enter the information that you prepared in the last step.

Connect the Agent to the Synthetic Server (Optional)

By default, the Synthetic Private Agent will report measurement results to the SaaS Synthetic Server located in the Americas business region. Thus, if your Synthetic Private Agent is located in the Americas business region and reporting to our SaaS Synthetic Server, continue to Start the Synthetic Private Agent.

If your Synthetic Private Agent is reporting measurement results to an on-prem Synthetic Server, see Connect Synthetic Agents to the Synthetic Server for configuration instructions.

To configure your Synthetic Private Agent to report to a SaaS Synthetic Server in the EMAC or APAC business regions, follow these instructions:

  1. Select the EMAC or APAC tab in the following table to find the URL to the SaaS Synthetic Server in your region.

    SaaS Domains and IP Ranges

    AppD Data Center

    In the AppD Data Center, the Controllers are tagged and labeled as being for APAC, EMEA, and the Americas; maintenance is carried out at times appropriate for these regions.

    Platform ComponentsDomainsIP BlockEquivalent Range
    Controllerhttps://<your-controller>.saas.appdynamics.com45.64.64.0/2245.64.64.0 – 45.64.67.255
    69.27.41.0/2469.27.41.1 – 69.27.41.254
    69.27.42.0/2469.27.42.1 – 69.27.42.254
    69.27.44.0/2469.27.44.1 – 69.27.44.254
    103.28.248.0/2203.28.248.1 – 103.28.251.254
    107.154.126.0/24107.154.126.0 – 107.154.126.255
    149.126.72.0/21149.126.72.1 – 149.126.79.254
    162.210.94.0/23162.210.94.1 – 162.210.95.254
    185.11.124.0/22185.11.124.1 – 185.11.127.254
    192.230.64.0/18192.230.64.1 – 192.230.127.254
    198.143.32.0/19198.143.32.1 – 198.143.63.254
    198.169.194.0/23198.169.194.1 – 198.169.195.255
    199.83.128.0/21199.83.128.1 – 199.83.135.254
    2a02:e980::/29 (optional)2a02:e980:0:0:0:0:0:0 – 2a02:e987:ffff:ffff:ffff:ffff:ffff:ffff
    EUM Cloud, IoT REST API, Synthetic Server, Analytics

    For these platform components, see the table given in the Americas tab for the domains, AWS regions, and IP ranges.

    Notes:

    • 69.27.44.20–24 is the SNAT pool range of IP addresses used for sourced (or originated) traffic from the data center for both 69.27.44.0/24 and 198.169.195.0/24 traffic.
      That range is used for ALL outbound traffic.

    • 69.27.44.226 is the IP address of the SMTP service (both in and out).

    Americas

    Platform ComponentsDomainsAWS RegionIP Ranges
    Controller

    https://<your-controller>.saas.appdynamics.com

    us-west-2

    The IP range will be from an assigned set from Amazon.
    For a smaller and restricted set, contact customer support.

    EUM Cloud

    https://col.eum-appdynamics.com (EUM Collector)

    https://api.eum-appdynamics.com (EUM API)

    us-east-1

    us-west-2

    eu-west-1

    IoT REST APIhttps://iot-col.eum-appdynamics.comus-west-2
    Analyticshttps://analytics.api.appdynamics.comus-west-2
    Synthetic Serverhttps://synthetic.api.appdynamics.comus-west-2

    Static IP Addresses

    • 52.40.35.5 (Boardman, Oregon)
    • 52.201.103.47 (Ashburn, Virginia)

    EMEA

    Platform Components
    Domains
    AWS Region
    IP Range
    Controllerhttps://<your-controller>.saas.appdynamics.com

    eu-central-1

     

     

     
    The IP range will be from an assigned set from Amazon.
    For a smaller and restricted set, contact customer support.
    EUM Cloud

    https://fra-col.eum-appdynamics.com (EUM Collector)

    https://fra-api.eum-appdynamics.com (EUM API)

    IoT REST APIhttps://fra-iot-col.eum-appdynamics.com
    Analyticshttps://fra-ana-api.saas.appdynamics.com
    Synthetic Serverhttps://fra-synthetic.eum-appdynamics.com

    Static IP Address:

    52.48.243.82 (Dublin, Ireland)

    APAC

    Platform ComponentsDomainsAWS RegionIP Range
    Controllerhttps://<your-controller>.saas.appdynamics.comap-southeast-2

     

     

     

    The IP range will be from an assigned set from Amazon.
    For a smaller and restricted set, contact customer support.

     

     
    EUM Cloud

    https://syd-col.eum-appdynamics.com (EUM Collector)

    https://syd-api.eum-appdynamics.com (EUM API)

    IoT REST APIhttps://syd-iot-col.eum-appdynamics.com
    Analyticshttps://syd-ana-api.saas.appdynamics.com
    Synthetic Server

    https://syd-synthetic.eum-appdynamics.com

  2. Change to the directory C:\appdynamics\synthetic-agent\synthetic-driver\conf.
  3. Edit the file synthetic-driver.yml.
  4. Set the URL to SaaS Synthetic Shepherd in your region to the shepherdUrl as shown below:

    ## Use the SaaS Synthetic Server URL from the table above for EMAC or APAC.
    shepherdUrl: http://<saas_synthetic-server_url>
  5. Save your changes and close the synthetic-driver.yml file.

Start the Synthetic Private Agent

After installation is complete (the installer may restart your computer), start the Synthetic Private Agent by double-clicking the desktop shortcut Start Agent.

Confirm the Installation Was Successful

  1. Go to your SaaS Controller and to the Synthetic Job List.
  2. Click Create a Job.
  3. From Choose Locations, select Private from the dropdown to view all the Synthetic Private Agents associated with your account.
  4. Verify that your private location shows up as one of the available locations. 

Configure Autologon 

You should configure autologon so that the machine after booting up will automatically log on to the Administrator account. You are recommended to use the free Microsoft Sysinternals utility Autologon.exe for configuring autologon. Autologon.exe is easy to use, and more importantly, encrypts the account credentials stored in the Windows Registry.

To configure autologon:

  1. Review User Account for the Synthetic Private Agent to ensure that the user account has been set up properly.
  2. Download Autologon.exe from https://docs.microsoft.com/en-us/sysinternals/downloads/autologon.
  3. Double-click the executable Autologon.exe.
  4. Enter the requested information (username, domain, password, etc.).
  5. Click Enable.

You can also run Autologon.exe from the command line, but be sure to escape any special characters in your password.

To manually configure autologon by editing the registry, see How to turn on automatic logon in Windows. Note that the given instructions can change slightly depending on the version of Windows being used. 

Schedule the Synthetic Private Agent to Start on Logon

After you have set up autologon, you still need to schedule the Synthetic Private Agent to automatically start after the machine logs on to the Administrator account.

  1. Open a PowerShell console.
  2. Download and save the file startagent.xml to your $HOME directory.

  3. Change to your $HOME directory.
  4. If you are logged on as a different user than "Administrator", edit the startagent.xml file and replace the value "Administrator" for the following XML elements with your user name. (Remember, your user account still must have Administrator permissions.)
    • <Author>
    • <UserId>
  5. Schedule the task of starting the Synthetic Private Agent:

    > schtasks /create /f /tn "Start the Synthetic Private Agent"/xml .\startagent.xml
  6. Restart your machine.

  7. After the machine boots up, you should see the Windows console open titled "Administrator: Windows PowerShell" that displays the log message "Synthetic-agent is running".

Advanced Options

Install Multiple Agents 

After installing one Synthetic Private Agent, you should consider whether you need to install more Synthetic Private Agents.

Installing multiple agents is recommended for the following use cases:

  • You want to test multiple locations. You need to install the Synthetic Private Agent on multiple machines and provide different location information during the installation. Each location will appear separately in the Job Editor.
  • You need more throughput to run more tests. If you run a lot of synthetic jobs from a location, you may see errors like “Location is overloaded”. This means the machine is at capacity and you need to add another machine. You can simply install the agent on another machine and provide the same location information. 
  • You want support for multiple versions of Internet Explorer. See Software Requirements for more information.