Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: removed extra return


  1. In the Windows menu, click AppDynamics > .NET Agent > AppDynamics Agent Configuration.
    If the "Warning: 3rd Party Profiler installed" message displays, click Yes to exit and uninstall any pre-existing profiler.


    Check the registry to make sure that the uninstall process cleaned up the registry entries. Use the warning message to identify any undeleted profiler environment variables.

  2. If the configuration utility detects legacy agent configurations from the .NET Agent version 3.7.7 or earlier, it displays the Upgrade Configuration window.
    • Answer Yes to remove legacy configurations. See "Clean up legacy configurations" on Upgrade the .NET Agent.

    Removing legacy configurations modifies web.config files causing IIS to restart affected applications.

    • Answer No to leave legacy configurations in place.
    When the utility discovers no further profiler conflicts or after any configuration clean up it displays the welcome window.
  3. On the Log directory permissions window you can optionally change the location of the log directory, click Change and select a new location.
  4. If needed, type in an account to grant log directory permissions. Click Add. If you see a warning message, make sure that the account is valid on the system.
    The wizard confirms the list of accounts.
  5. On the Controller Configuration window, enter the Controller access information and credentials.
    • The AppDynamics Agent Configuration utility only supports configuration of one Controller and business application per server.
    • Enter the Controller server name or IP and port number.
    • For single-tenant accounts, enter your Account Access KeyFind your credentials under Settings > License in the Controller.
    • For multi-tenant accounts, click Multi-Tenant Controller. Enter the Account Name and Account Access Key as provided to you by AppDynamics.
    • For a secure connection, click  Enable SSL.
      • Make sure you have secured the Controller with a trusted certificate. See Enable SSL for .NET.
      • When you enable SSL, the agent secures communication to the Controller using the protocols set for ServicePointManager.SecurityProtocol in your application.
      • By default, the configuration utility enables TLS 1.2, making it the first option in the list of secure protocols. This affects all secure communications from your application, not just requests to the AppDynamics Controller. If you want to disable TLS 1.2, click to deselect this option.
    • If needed, fill in the HTTP proxy information. Proxies that use authentication require additional configuration. 
  6. Click Test Controller Connection to verify the connection.
  7. On the Application Configuration window, AppDynamics displays existing business application information from the Controller and displays it in the left column. Controller connection status displays on the right.
  8. Configure the business application for the Controller as follows:
    • If you already have a business application on the Contorller, click Existing Applications from the Controller and click the appropriate business application. If you haven't defined business applications in the Controller, the utility displays an empty list.
    • Click New Application to define a new business application. Be careful about spellings and capitalization and note down the exact name. Ampersands are not supported in application names.
    • If you want to use Config Management in the Controller, click Register Machine with No Application.
  9. Click Next to advance to Assign IIS applications to tiers where you can use one of the options below.

Watch the Video:


<style type="text/css">.vidyard_player{width: 600px; }.vidyard_player > span{max-width: 600px !important; max-height: 360px!important;margin-left:0!important;}.innerContainer{position: relative; display: block; width: 100% !important; height: 0; }</style><script type="text/javascript" id="vidyard_embed_code_AXLDUFcgGskDm6kDowNFnj" src="//play.vidyard.com/AXLDUFcgGskDm6kDowNFnj.js?v=3.1.1&type=inline&second=90"></script> 



For full-screen viewing, click Modeling .NET Applications in AppDynamics.



Automatically name IIS tiers