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:
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.
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
Edit the synthetic-driver.yml to remove any lines that reference the agent_user. Specifically, update the following two sets of commands.
Remove agent_user Appdynamics123 from the line starting with -Command