Skip to main content

Release notes - March 3, 2025

— Nik Pot

Unified script deployment

Big exciting update for us! We have now unified the deployment for Windows agents (macOS will be added soon). You can now use one installation script and pass it the desired customer name with the -customerName attribute. The agent will automatically associate with the appropriate customer tenant, and if the customer does not exist in idemeum, it will be automatically created.

Installation is now migrated from EXE to MSI in order to improve reliability of integrations with deployment tools. We automatically handle required prerequisites when installing with command-line script.

Unified deployment with a command line script is documented below.

Command-line installation
Install idemeum agent with a command-line script.
idemeum docsNik Pot

Updated integrations

As we now have the simpler way to deploy idemeum agent and automatically create customer tenants, we tested and verified the following integrations with RMMs. Most of these integrations are using the built-in customer name variables that get automatically passed to idemeum script for installation.

Proxy configuration from command-line script

We have added the option to configure proxy for idemeum agent when Windows agent is installed with PowerShell script. You can simply pass the -proxyHost and -proxyPort attributes to the PowerShell installation command. The documentation for proxy configuration is below.

Command-line installation
Install idemeum agent with a command-line script.
idemeum docsNik Pot

Version selection from command line script

Starting from this current version (Windows 1.8.0) you will be able to install the desired version of idemeum desktop agent by passing it the -version attribute.

Duo integration - auto registry changes

Previously when idemeum agent was installed on the workstations with Duo, manual registry modifications were necessary to make both products work together. What is more, Duo would often update the registry keys and idemeum credential provider would not be display.

We have now simplified the integration and there is nothing you need to do when idemeum is installed on machines with Duo. We manage registry keys automatically.

Duo Security - idemeum agent integration
JIT computer access When Duo Security agent is installed on a Windows workstation, it disables all credential providers except the native Windows password credential provider. However, there is a way to enable excluded credential providers via the registry. When idemeum agent is installed, it automatically makes the necessary changes to
idemeum docsNik Pot

Account discovery enhancements

  • We now support removing manually added domain user accounts from local administrator group on domain-joined workstations. When these accounts are added manually, idemeum discovers them and can downgrade from the cloud.
  • We updated the UI for account discovery page and we now show the workstation type for convenience (local, domain-joined, domain-controller)

Spanish locale support

We have started the support for various languages to make sure JIT and elevation work correctly on machines with different languages. We have now added support for Spanish language. For this feature to work properly the workstation needs to have Spanish set up as locale.

Additional enhancements

  • Improved the Groups page to show group types (local, built-in, external) and consolidated actions under .... Now it is very easy to view group members by choosing one of the actions from ....
  • Improved the Customers page to show the separate column for groups that are delegated to each customer tenant. By clicking on the counter you can access the delegation window.
  • QR-code expiry in Technician mode made independent of client time i.e., when client time is not in sync.