The latest local client (available in early 2025) for eADM key administrative functions within the main user interface. The need for a local configuration file is eliminated, and the entire eADM is moved to the cloud. This update simplifies system management and troubleshooting for both customers and our support team by resolving previous limitations related 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 perform a full synchronization outside of scheduled times, administrators had to access the local client directly within Active Directory. This process, which retrieves 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 such as 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 such as missing AD accounts.
How do I know if I already have the new client?
Check the status page in eADM. If you see buttons for both running delta synchronization and running full synchronization, then you’re already using cloud config.
Improvements resulting from the switch to the new client with cloud configuration
These issues have now been resolved. The new client includes the following improvements:
-
Centralized configuration: All settings have been moved from the local configuration file to the eADM interface.
-
Remote synchronization: You can now run a full synchronization directly from the eADM , eliminating the need for local server access.
-
Accessible logs: Logs from the local Active Directory are now available directly within the eADM interface, streamlining the troubleshooting process.