What's New in Environment Manager?

Version 2023.1

In addition to code enhancements and bug fixes the following features are included:

Ability to Clone Personalization and Application Groups

This feature is one of our highest-voted enhancement requests and supports the need to duplicate personalization and application groups for testing purposes.

See also Personalization Groups and Application Groups.

Addition of a New Condition – AAD Joined

Following on from the 2022.3 release of Environment Manager where we introduced support for AAD users and groups, in this version, we’ve added a new condition “AAD Joined” for use when creating and editing rules.

See also Connect to Azure AD Tenant.

Office 365 Credential Persistence for Modern Authentication

The Microsoft Teams WSG Personalization Template, available from the Ivanti Marketplace, now supports modern authentication. See the Ivanti Marketplace.

Azure SQL Managed Instance Support for Personalization Server

Creation of the Personalization database now available for Azure SQL Managed Instance by supporting server logins.

Start Menu Builder Logging Improvements

Logging has been improved to show the actual function names, derived from AXE_LOG_INFO_EX and [CallerMemberName].

File Menu Alteration

The ‘Unlock without saving’ option has moved to the top level of the file menu to remove the confusion of it being in the ‘Save’ menu.

Tree File Group View Enhancement

Under certain circumstances, the files in application groups that share a parent directory could get shown in the wrong location in the Tree File Group view yet show as expected in the Flat view. This issue has now been resolved so the file always shows in the correct location, regardless of the view.

EMPSSubscribers Cmdlet No Longer Has Defunct Parameters

The -ExportScript and -ScriptFolder parameters are now no longer available on the EMPSSubscribers cmdlet because they were non-functional and therefore added confusion.

The list of parameters are found on GeoSync-cmdlets.

Process Start/Stop Node Optimization

Prior to this release, when any trigger runs, the engine creates a thread for every node below it. This can be inefficient when the trigger is process start or process stop. We have addressed this by checking when a thread - created by process start/stop – to see if any existing nodes match the process. If so, only then is the thread created. The result is the exact same functionality but performance improvements in configurations that have many process start/stop nodes.

This new functionality is reflected in EmMon – process conditions that have been checked will be marked ‘[Precheck]’ in the node column. Full information is found at Node Management.

‘Parent Process Only’ Option

Process conditions now have the flag ‘Parent Process Only’ added. If this is set, the condition only succeeds if its parent process does not have the same executable name. This is to handle applications such as Microsoft Edge and Google Chrome, where the executable spawns child copies of itself to handle separate operations (e.g. separate browser tabs). If this flag is not set, actions below the condition may run multiple times (legacy behavior).


Previous Versions