Pre-requisites for Using the eG Enterprise Logon Simulator for Exchange

 

Category Pre-requisites
Logon Simulator Agent / Simulation Endpoint
  • The Logon Simulator Agent should be installed on a dedicated endpoint. The dedicated endpoint should only run 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.

Environment
  • The simulator will only work with Exchange 2013 / Exchange 2016 / Exchange 2019 / Office 365 environments.
  • One/more valid and dedicated email IDs on the Exchange server is required for the purpose of the simulation.
  • The simulation can use either Outlook Web Access (OWA) interface or the Office 365 portal to access the configured mailbox. If Office 365 is used, then make sure that the default start page of the Office 365 portal is set to Mail for every email ID that has been configured for the purpose of the simulation. To know how to achieve this, refer to Configuring the Default Start Page for Office 365. Once this is done, make sure you clear the browser history.

  • 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.

Browser

The eG Logon Simulator for Exchange mandates the presence of the Chrome browser v122 (and above). No other browser supports this simulation.

Note:

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