Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I run Synthetic Private Agent jobs using the domain Admin User?

Is there a way to configure the Synthetic Private Agent to use the domain Admin User instead of the agent_user?

 

If you want to run the Synthetic Private Agent jobs using the chosen domain admin user account instead of the installer created agent_user, try this workaround. 

 

Note: This solution is not officially documented or supported at this time
and therefore may not work in every environment.

 

 

Table of Contents

 

Configuring Synthetic Private Agent to use the domain Admin User

This configuration workaround to using the default agent_user to run the Synthetic Private Agent jobs is to modify the Synthetic Private Agent's configurations so they use chosen domain admin user account user (ex: DOMAIN\appdadmin) instead. 

 

To achieve this you will need to do the following:

  1. Login to the Synthetic Private Agent host as DOMAIN\appdadmin. Validate that all Private agent processes are fully stopped, and kill any java.exe processes even if they don't belong to the agent_user.

  2. Clear out the logs directory into a temp folder so that the current logs directory is empty. Also, take a backup of the synthetic-driver.yml file before making any changes.

    C:\appdynamics\synthetic-agent\synthetic-driver\conf\synthetic-driver.yml

  3. Edit the synthetic-driver.yml to remove any lines that reference the agent_user. Specifically, update the following two sets of commands.

    1. Remove  agent_user Appdynamics123​ from the line starting with -Command​

Change this:

webdriverServerCommand:
  name: WebDriver Server
  exe: powershell.exe
  args: >
    -ExecutionPolicy ByPass
    -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123
    .\synthetic-driver\scripts\windows\start-webdriver-server.bat

 

To this:

webdriverServerCommand:
  name: WebDriver Server
  exe: powershell.exe
  args: >
    -ExecutionPolicy ByPass
    -Command .\synthetic-driver\scripts\windows\start-webdriver-server.bat

 

  1. Remove > -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123 powershell.exe​ from the line starting with args:

 

Change this:

- name: Reset IE cache
    exe: powershell.exe
    args: >
      -ExecutionPolicy ByPass
      -Command .\synthetic-driver\scripts\windows\sudo.ps1 agent_user Appdynamics123
      powershell.exe -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\reset-ie-cache.ps1
    browsers: IE10, IE11

 

To this:

 - name: Reset IE cache
    exe: powershell.exe
    args: -ExecutionPolicy ByPass -Command .\synthetic-driver\scripts\windows\reset-ie-cache.ps1
    browsers: IE10, IE11

 

After you've made these changes, save the .yml file.

  1. Finally, backup the start_agent.bat file first and then edit the original start_agent.bat file located at C:\appdynamics\synthetic-agent​ by modifying the following line:

Change this: 

if exist "C:\appdynamics\installers" (powershell.exe -ExecutionPolicy Unrestricted C:\appdynamics\cookbooks\run_chef_as_unprivileged_user.ps1 )

 

To this:

rem if exist "C:\appdynamics\installers" (powershell.exe -ExecutionPolicy Unrestricted C:\appdynamics\cookbooks\run_chef_as_unprivileged_user.ps1 )

 

 

Does your scheduled task use the correct Admin user?

If you’re running the scheduled task to start the agent, make sure to update the scheduled task to use the DOMAIN\appdadmin user instead of the agent_user for running said task.

Version history
Revision #:
7 of 7
Last update:
‎04-07-2020 02:03 PM
Updated by:
 
Labels (1)


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.