New and upgraded local client for eADM
The latest local client (available early 2025) for eADM centralizes key administrative functions into the main user interface. This update simplifies system management and troubleshooting for both customers and our support team by resolving previous limitations tied to local server access.
Previous limitations of the local client
Previously, managing the local client involved several impractical and time-consuming processes:
Manual synchronization: To run a full synchronization outside of scheduled times, administrators had to access the local client directly within Active Directory. This process, which pulls updated data from the source system, was often inconvenient.
Local log files: Communication logs between the local client and Active Directory were stored on the local server. This required administrators and our support team to request local access to retrieve log files during troubleshooting, which could be a cumbersome process.
Local configuration: The client was configured using a local file that also contained encrypted API keys for HRM systems like Simployer and Visma Enterprise. This setup made the keys difficult to manage, exposed them to unnecessary risk, and made it challenging for support to get a complete overview when troubleshooting issues like missing AD accounts.
Improvements with the new client
These challenges are now resolved. The new client introduces the following improvements:
Centralized configuration: All settings have been moved from the local configuration file into the eADM user interface.
Remote synchronization: You can now run a full synchronization directly from the eADM interface, eliminating the need for local server access.
Accessible logs: Logs from the local Active Directory are now available directly within the eADM user interface, streamlining the troubleshooting process.