Pre-requisites for Using eG Enterprise Logon Simulator for Amazon WorkSpaces

Before attempting to use the simulator, make sure that the following pre-requisites are fulfilled:

Category Pre-requisites
Logon Simulator Agent / Simulation Endpoint
  • Client Session Simulation capability should be enabled on the eG license.
  • The logon simulator agent/external agent should be installed on a dedicated virtual machine or a physical server running Windows 2012/2016/2019/2022 or Windows 8/10/11 operating system.
  • The logon simulator agent/external agent should only run on an English version of Windows operating system.

  • No other eG agent should exist on the same host on which the logon simulator agent has been installed.

  • .Net 4.5 (or above) should pre- exist on the system hosting the logon simulator agent.

  • The simulator requires a user account with local administrator rights on the simulation endpoint - i.e., on the system hosting the Logon Simulator Agent. This user should be logged in at all times for the simulator to run continuously.


    • The logon simulation will not work if the session is closed.
  • One/more valid and dedicated email IDs on the Amazon WorkSpaces infrastructure is required for the purpose of the simulation.
  • To perform the simulation, the simulator needs to be configured with the URL of the Amazon WorkSpaces that it needs to access. Ensure that the Web Access check box is enabled for that URL for which the simulation is to be performed. To know more on how to enable the Web Access, click here.
  • If a firewall separates the simulation endpoint from the web interface, then make sure you configure the firewall to allow two- way communication between the endpoint and the web interface.

  • Chrome browser v122 and above should be available on the dedicated endpoint.


    In some environments where browsers are automatically updated to their latest versions, incompatibility is cited between the browser version and the Chrome drivers. This may sometimes hamper the start of the simulation. Therefore, ensure that the Chrome drivers are also updated whenever the browser is updated to the latest version.

    Chrome is capable of automatically applying updates and upgrading itself to higher versions. Sometimes, when Chrome auto- upgrades, some drivers that the eG Logon Simulator Agent uses may suddenly be rendered incompatible with Chrome. This can cause problems in simulation. To avoid this, the eG Enterprise Logon Simulator for Exchange, by default, prevents Chrome upgrades/updates (both automatic and manual) from being applied at the simulation endpoint. However, whenever a new version of the eG agent with updated drivers is released, you will have to manually upgrade Chrome to ensure continued compatibility. In this case therefore, you will have to make sure that the simulation endpoint allows Chrome upgrades. To achieve this, before manually upgrading Chrome, follow the steps below:

    • Login to the eG agent host.
    • Open the Windows command prompt as Administrator.
    • Switch to the <EG_AGENT_INSTALL_DIR>\lib directory, and issue the following command:

      ChromeUpgradeHandler.exe enable


To ensure that all the pre-requisites of the Amazon WorkSpaces Logon Simulator is fulfilled, you can execute the LogonSimulatorChecks.exe which is available in the <eG_INSTALL_DIR>\lib folder. This executable should be executed by a user with administrator privileges from the command prompt of the target agent host. If any pre-requisite has not been fulfilled, failure will be highlighted in Red (as shown by Figure 1).

Figure 1 : Setup script where a pre-requisite has failed

Use the pointers provided in Figure 1, just below the failed pre-requisite, to know how to fulfill that requirement. Then, rerun the LogonSimulatorChecks.exe to make sure that all pre-requisites are fulfilled, and then proceed.

If all pre-requisites are fulfilled, then Figure 2 will appear.

Figure 2 : All pre-requisites are fulfilled