Traditional Manual Process
Manual WebDriver update burden
1 Create a Local Program
Run driver sync on engine
Result
Driver stays in sync
Operational Recommendations
Best practices for scheduled runs
Overview
Synthetic monitoring environments commonly use browser-automation frameworks such as Selenium and Microsoft Edge WebDriver. When Microsoft Edge updates automatically, the installed browser and WebDriver versions may become incompatible, causing synthetic scenarios to fail even though the monitored application remains healthy. GermainUX can automatically detect and resolve these version mismatches, keeping synthetic monitoring operational without manual intervention. Microsoft requires the first three components of the four-part Microsoft Edge and Edge WebDriver version numbers to match. See Microsoft Edge WebDriver documentation.Traditional Manual Process
Without automation, operations teams must:
This manual process can cause:
- Synthetic monitoring downtime
- Operational overhead
- Overnight alert noise
- False-positive incidents
- Unnecessary escalations
Automated Resolution
GermainUX provides a self-healing workflow that:- Detects the installed Microsoft Edge version.
- Detects the installed Edge WebDriver version.
- Compares the first three version components.
- Downloads the matching WebDriver when a mismatch is detected.
- Replaces the existing driver.
- Validates the updated version.
- Allows synthetic monitoring to continue without manual intervention.
Configuration
This example uses a PowerShell script executed by a GermainUX Engine on Windows Server.1 Create a Local Program
Go to GermainUX Workspace > Automation > Local Program, and then click Add New Configuration. Configure:
Enabling Execute via Engine ensures that the script runs on the server where Microsoft Edge and Edge WebDriver are installed.

2 Add the PowerShell Script
Click Add New Script, and then add the following PowerShell script.
$driverFolder to match the Edge WebDriver location used by your synthetic monitoring environment.
- Locates the installed Microsoft Edge executable.
- Reads the browser and WebDriver versions.
- Compares their first three version components.
- Stops active
msedgedriverprocesses when an update is required. - Downloads and extracts the matching 64-bit Windows driver.
- Replaces the existing executable.
- Validates compatibility after installation.
- Returns exit code
0for success and1for failure.
3 Configure the Command
Configure the Local Program to execute the PowerShell script.
Use only the PowerShell execution policy permitted by your organization’s security requirements.
4. Configure the Schedule
Choose a schedule based on browser-update frequency and synthetic monitoring requirements.
5. Configure an SLA Trigger
The action can also run when an SLA condition indicates a possible driver mismatch. Possible triggers include:- Synthetic scenario execution failures
- A sudden increase in failed synthetic transactions
- WebDriver startup failures
- A detected browser and driver mismatch
Result
Once configured, the GermainUX Engine automatically synchronizes Microsoft Edge WebDriver with the installed Edge browser. The workflow can run on a schedule or in response to an SLA condition. This reduces false-positive failures, monitoring interruptions, manual maintenance, and unnecessary incident escalations.Additional Automation Use Cases
The same GermainUX automation pattern can support:- Infrastructure maintenance
- Service recovery
- Dependency synchronization
- Environment consistency enforcement
- Automated remediation
- Configuration validation
Operational Recommendations
- Test the script in a non-production environment.
- Run the GermainUX Engine with only the permissions required to update the driver.
- Restrict outbound downloads to trusted Microsoft endpoints.
- Schedule updates when no synthetic scenario is using the driver.
- Enable execution logging and failure notifications.
- Validate your organization’s code-signing and software-download requirements before deployment.
- Maintain a recoverable copy of the previous driver when required by your change-management policy.
Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE LLC.

