What's New in Environment Manager?

Version 2022.3

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

Support for Azure Active Directory

Four new conditions can be used on endpoints that are joined to AAD domains. The join can be a full join or a hybrid join (where the endpoint is a member of an on-prem AD domain synchronized to the AAD domain by AAD Connect). These conditions are:

  • AAD Computer Group Membership

  • AAD User Group Membership

  • AAD User Name

  • AAD Client Computer Group Membership

These rules apply on the agents of both AAD-joined and hybrid-AAD-joined machines. If a device is not connected to the network at logon then the last known Groups apply. User group assignment changes can only apply at logon. Device group assignment changes can only apply at restart.

Further, when creating custom rules in the console, they can be created with conditions for AAD User Name, AAD User Group, AAD Computer Group and AAD Client Computer Group.

Configuration for AAD is via the global settings.

References:

Azure AD Tenant Access

 

Change to default value for ‘Stop sub-nodes on fail’

The ‘Stop sub nodes on fail’ setting has previously been set to True by default when creating a new configuration. The change made with this release is that it will now default to false as that is the desired setting in most situations. The value can still be altered when required.

Enhancements to Most Recently Used list

The Most recently used (MRU) list in the common tasks of the Environment Manager Monitor has had some improvements. It no longer lists files that have been deleted or moved and it now provides a tool tip showing the full path to the file.

Custom actions and conditions new timeout

Custom actions and conditions have, by default, been created with an infinite timeout, which, if the custom action doesn’t execute properly can cause problems on the end point devices such as hangs or issues with logon. The change has been to have these actions and conditions have a 30 second timeout by default (this is configurable) so that it is less likely their non-success status will have a detrimental effect.

Previous Versions