Showing results for 
Show  only  | Search instead for 
Did you mean: 

Active gate synthetic engine not running as a user only as a local service

Dynatrace Participant
Dynatrace Participant

The new activegate synthetic engine for windows behaves differently than the PLM agent it replaces, and does not function in a corporate environment.

In the old PLM setup - when the PLM agent is installed you can override the local service account and configure a specific user to run the service as via the installation gui.
The PLM synthetic engine then runs as that user and most importantly the synthetic browser session honours windows user credentials for any single signon application.

In the new private activegate synthetic engine it runs as a local service account with no install option to use another account.
The the synthetic browser does not honour the windows credentials for single signon applications as the PLM browser did, as i am unaware of any corporate environment that has single signon for "local service"

This means the any synthetic tests do not function that use single signon. eg proxy services etc..
It also means that screenshots are not able to be published back up to AWS s3.


Dynatrace Participant
Dynatrace Participant

We have been able to successfully get the activegate synthetic engine to replicate the behaviour of the Private Last Mile technology.
ie. run on windows as a windows user
use the windows user active directory crendentials for synthetic testing ( replicating a synthetic user session)
use the windows network automatic proxy configuration for synthetic testing

the detail of the steps we followed are attached in a word doc.
A summary is below

Step 1 Remove existing acitvegate installation
Run "services "as admin
Stop dynatrace Synthetic
Stop dynatrace gateway
Stop dynatrace autoupdater

Run control panel | programs and features
Uninstall dynatrace synthetic
Uninstall dynatrace gateway

Delete folders
c:\Program Files\dynatrace

Step 2 Install Activegate software

  • Browse to our tenant install page page;gf=all
    check synthetic and download
    Put it in \program_files\BCC
    Copy the installer command line from page above and run it
    Enable proxy setting <proxy domain>:<proxy port>
    Install directory default
    Installation successful message is important here !!

Step 3 - Dynatrace SaaS check
Wait for the engine to come up in our tenant - all components must be up
check your machine name synthetic engine
Synthetic Engine status Running
Synthetic Engine health check Ok
HTTP monitors Enabled
Browser monitors Enabled

Step 4 - Stop Activegate
Run "services "as admin
Stop dynatrace Synthetic
Stop dynatrace gateway
Stop dynatrace autoupdater

Step 5 - Change Folder Permissions
Change folder permissions -
allow full control for bcc\ictdashnn on the following folders
c:\Program Files\dynatrace

Do this by clicking security tab - then edit and add bcc\ictdashnn full control and save

Step 6 - Fix folder permissions
As the ictdashnn user browse to C:\ProgramData\dynatrace\synthetic and allow permanent access (For some reason the synthetic directory still requests access override)

Step 7 - Modify Activegate Chromium
In file C:\ProgramData\dynatrace\synthetic\config\

  1. Disables AppContainer on Windows 8 and newer
  2. Disables AppContainer on Windows 8 and newer
  3. BCC - auto detect Proxy

Step 8 - Run Activegate as the user ictdashnn
Change the logon as user for the 2 following services to ( password in the password portal)
Dynatrace Gateway
Dynatrace Synthetic

Step 9 - Delay start the synthetic engine
Change Dynatrace Synthetic service to be "Automatic (Delayed Start)"

Step 10 - Reboot

Step 11 - Fix Location in Dynatrace SaaS
Browse to;gf=all
You will need to reconfigure the activegate into locations

  • Step 12 - Reboot*

NOTE: Changing is not supported. Upgrade will overwrite those settings at this moment.

Dynatrace Participant
Dynatrace Participant

To summarize what we have done here and what the discussion is currently about.

1. The gateway and synthetic engines need different proxy configurations as one is Java and one is Chrome, Currently Dynatrace only supports one config shared by both, ( your java engine does not honor user or AD credentials sets - Chrome however can be configure to do so)

2. the gateway process and synthetic process on windows is now running as a domain use - as per PLM.

So we have found a way to make both those things happen but.....
for 1. how do we make the proxy configurations different and have it stick during upgrades? or how do we make Java behave like chrome.
for 2, how to we stop the upgrade process changing the services back to "local system"?

Remembering that auto updates is not far away for activegate on windows 🙂