What's New in Environment Manager?

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

Entra ID support for personalization

Environment Manager personalization now allows you to manager Microsoft Entra ID users. This enables personalisation administrators to browse and select Entra ID user and device objects to use as conditions. This enhances the ability to use Entra ID users and groups in rules for Environment Manager policy and other solutions in the User Workspace Manager suite.

Support for Group Managed Service Accounts (gMSAs_)

Environment Manager personalization now supports the use of gMSAs to access the SQL database. This enhancement avoids storing SQL credentials to enhance security and reduce administrative overhead.

Set an Access Control List (ACL) when creating a folder

Environment Manager now allows you to create ACLs and apply them when you create a folder or a file. Refer to Using the Access Control List.

Check file metadata using policy file conditions

You can apply conditions based on file metadata to evaluate for revisions. Refer to Setting Conditions Based on File Metadata.

Create unique folder locations for temporary script execution

Environment Manager allows you to create a custom working directory from which to execute custom condition scripts. Refer to Custom Conditions.

Endpoint analysis changes to folders and log files

Environment Manager now allows you to specify the maximum number of log folders to save before deleting the oldest folders and to specify retention times for log folders. Refer to Endpoint Analysis Tool - Settings.

Endpoint analysis ETL logs process start/stop conditions

A new option under endpoint analysis advanced settings allows you to capture process started and process stopped conditions. Refer to Endpoint Analysis Tool - Settings.

Updated Microsoft branding

Environment Manager has been updated to reflect Microsoft's branding change from Azure Active Directory (AAD) to Microsoft Entra ID.

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

Outlook Search Index Roaming

Environment Manager now supports per-user Outlook Search Index persistence through cache roaming.

Ability to deploy through Ivanti Neurons

Customers with both Ivanti Neurons and Environment Manager now can use Ivanti Neurons to deploy the Environment Manager engine and deploy policies via the Ivanti Neurons agent management feature. Learn more about Integrating Environment Manager with Ivanti Neurons

Personalization: Change Tracking

Enable the new Change Tracking feature for Personalization to track configuration changes including the original and new values, the login ID, and the timestamp of the change. This feature applies to both Application groups and Windows Settings groups.

Updates to Agent Installer

The agent installer now installs the following signed binary files in the agent folder:

• RefreshNow.exe

• SetBrowserForUser.exe

• SetPdfViewer.exe, and

• SetMailClient.exe.

We have introduced a new predefined session variable called $(ClientPath) for your convenience. This variable provides the full path to the agent binary folder. This addition means that it's now easy to reference these programs from within a custom action.

Increased IIS Sync Limits

The default limits for the MaxHTTPCollectionKeys and MaxAllowedContentLength keys have been increased to better support IIS Syncs. They have been set to 10,000 and 100,000,000 (95.37MB), respectively.

Existing values will be overwritten for upgrading customers.

Improved default settings for GeoSyncAgent

Following feedback from implementers, we have updated the default values for the Geo Sync Agent keys to better align with customer requirements. The new settings are outlined below. They will not be applied to configurations of existing customers who upgrade to this version.

<add key=”GeoSyncAgentRetryCount” value=”4" />

<add key=”GeoSyncAgentRetryWaitMs” value=”600” />

<add key=”GeoSyncAgentNonDeadlockRetryWaitMs” value=”10000” />

<add key=”GeoSyncAgentDefaultCommandTimeoutSecs” value=”180” />

<add key=”GeoSyncAgentReconnectTries” value=”6” />

<add key=”GeoSyncAgentReconnectDelayMs” value=”10000” />

<add key=”GeoSyncMaxConsecutiveErrors” value=”100” />

Encrypted SQL Communication

The Management/Personalization Server now supports encrypted (with certificate validation) communication with SQL.

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).

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.

Azure Virtual Desktop Enhancements

Improved security in 2022.1 includes the addition of Operating System conditional checks. These conditional checks validate whether the queried client is an Azure Virtual Desktop offering clarity on the client. Conditions configured across both Environment Manager Policy and Personalization are supported.

Extended Windows 11 Capability

Environment Manager is fully supported as of the 2021.3 release when running on Windows 11. In 2022.1 we have enhanced our value offering on this OS by introducing Windows 11 as an option within our Custom Windows Settings conditions list.

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

Environment Manager Endpoint Analysis Tool

Gain environment wide insights into the applied EM Policy Configuration on every device.

The Environment Manager Endpoint Analysis Tool enables analysis of policy configurations on endpoints using endpoint logging data. The tool detects and highlights configuration issues that may exist so that administrators can quickly investigate, diagnose causes, and make the changes required accordingly. In addition to its value in troubleshooting or debugging configuration issues, the tool enables risk assessment of planned upgrade or system changes.

Refer to Endpoint Analysis Tool for further information.

Non-Virtualized Application Group Personalization

The behavior and performance of certain applications can be adversely affected when their user settings reside within a virtual cache. Where critical functions rely upon interaction with 3rd party or OS resources it has been previously necessary to shift management of them from Application Groups to Windows settings groups (WSGs).

With the 2021.3 release, Environment Manager offers real flexibility where this scenario occurs. Configured on a per-Application Group basis, the ‘Non-Virtualized’ Application Group (or NVAG) option enables captured settings to remain in the real file and registry locations - as opposed to the default virtual cache. Synchronization continues to occur at start and end of the application groups processes. The result is optimal performance with no hindrance to users at on Logon or Logoff.

Refer to Applications Groups and About PVC virtualization for further information.

Windows 11 and Windows Server 2022 – OS Conditions

OS conditions within Environment Manager Policy and Personalization (Windows settings groups (WSGs) have been updated to support Windows 11 and Windows Server 2022.

OS conditions enable Administrators to create actions or make selections based upon the operating system (OS) of the endpoint.

Refer to Computer Conditions and Windows Personalization help topics for information.

Delete Archives and Settings

The ‘Delete Archives and Settings’ option within Personalization Analysis > Delete Settings is now Disabled by default.

Refer to Delete Archives for information.

Office 365 – creation of an Outlook profile action

The ability to configure a Create Office 365 Profile for Outlook is no longer supported in Environment Manager 2021.3 for Microsoft Office 2016 and later.

Refer to Outlook Actions for further information.

Telemetry

Telemetry data can help us measure the quality, scalability, reliability, and capabilities of our products. It can provide us with a wide view of deployment and adoption data and so enable us to make the best-informed decisions on future developments of our products.

Environment Manager 2021.3 introduces telemetry for license data. Information supplied by the agent is in-line with our existing EULA agreement and does not include any sensitive or personally-identifiable data.

Refer to Telemetry for further information.

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

VHD(X) Support

Support for cache roaming for virtual sessions is now extended to include VHDX and VHD. VHDX offers the benefits of higher virtual disk storage capacity, and is optimized for use with modern hardware and operating systems.

Refer to Cache roaming for virtual sessions for further information.

VHD max size

Default values for the maximum storage capacity has been increased for VHD to 150 MB and 2 TB. For VHDX the maximum capacity is between150 MB and 64 TB. Refer to Cache roaming for virtual sessions for further information.

Start menu

The Windows 10 Start Menu Builder now allows you to create personalized Start menu actions without a tile layout.

Refer to Windows 10 Start Menu Builder for further information.

Personalization Operations changes

Full Profile Deletion in PersOps

A Delete Current Settings for All Groups option has been added to the Personalization Operations user interface.

See Personalization Operations Help (Current Settings for Single Users) for further information.

Allow Membership of Multiple Groups

As of 2021.1 Personalization server provides aggregated authorization, where multiple roles assigned to a user are combined. Previously when duplicate groups were matched a ‘Conflicting Groups’ message was displayed.
See Personalization Operations Help (User Management) for further information.

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

File Type Association for UWP apps

The Environment Manager2020.3 release extends support for file type association to now include both Win32 apps and UWP (Universal Windows Platform) apps. The File Type Association action dialog requires administrators to select the application type radio button and then select or specify the app required. The list of UWP apps available for selection is generated automatically by Environment Manager but can be manually edited if required.

Watch a short video overview

See File Type Association for further information.

Configure action delay

Environment Manager 2020.3 introduces new options for the configuration of delays to actions. It is now possible to simply specify the action delay required using the Delay tab which forms part of the Actions dialog. Previously, action delays were configured using Custom Actions and the use of a scripting language.

See Configuring Actions for further information.

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

Windows 10 Start Menu Builder

This release introduces the Environment Manager Windows 10 Start Menu Builder - a great new feature that provides a matchless solution to deployed Start menu customization.

• It provides the ability to quickly create user-centric menus for different users

• As an administrator, you can customize the UWP and Win32 apps listed, and create a tile layout from just one simple-to-use interface

• You can easily maintain and manage the customized menus as your user needs evolve or when Windows updates result in unwanted changes.

Watch a related video

The customized menu is created as an action on a logon trigger and saved as part of the configuration. You can create as many different Start menus as required and deploy them to whichever user groups you specify. The default list of Windows applications available in the Start Menu Builder wizard is supplied by an XML file which can easily be replaced or modified from within the wizard itself.

For more information see Windows 10 Start Menu Builder.

File type exclusions for Windows settings groups

Custom Windows settings enable you to personalize registry keys, particular folders, and files by specifying which of these are to be included (or excluded) from the personalization database. Environment Manager 2020.2 provides an improved user workflow and allows you to exclude specific file types without having to specify their folder path.

Custom Windows settings can be applied to your Windows settings groups and the exclusions honored. The enhancement provides greater flexibility when specifying exclusions, and more targeted results.

See Custom Windows settings for more information.

Sync of Windows Settings over VPN

At logon, a sync of the user’s Personalized Windows Settings preferences is attempted. The result of this sync is dependent upon a stable connection having already been established with the Personalization Server.

As of Environment Manager 2020.2 an Engineering Key is now available which can ensure the timings of the sync and the VPN connection are aligned. This supports delivery of a familiar, personalized user desktop regardless of location and connection type.

Please refer to Enable VPN Sync for WSGs.

Easier Access to Further Information

In addition to this online help system, Ivanti provides a wealth of supporting information in the form of online documents, help videos and curated community articles. In the 2020.2 release we have collated these resources into a summary table and made this available via the Release Notes and from the online Help landing page.

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

Localization

Environment Manager 2020.1 release has been localized and now supports following 5 languages:

• English

• German

• Japanese

• Chinese (Simplified)

• Chinese (Traditional)

Selection of the language setting required is described in the Language Settings help topic within User Workspace Manager.

Windows Server 2019 support

Environment Manager 2020.1 Personalization Server, Console and Agent Components are now all compatible with Windows Server 2019. For example, additional conditions are available in Policy that check for Windows Server 2019.

For more information on supported software see the Maintained Platforms Matrix.

See Computer Conditions for information on operating system conditions.

Environment Manager 2019.1 SP2 release contains bug fixes and code enhancements. There are no new features.

Toggle the auto copy of VHDs for multiple sessions ON/OFF

In Environment Manager 2018.3, Ivanti introduced the ability to use VHD Cache Roaming to provide users with access to their cache when working across multiple virtual sessions. This enables users within a non-persistent Windows environment to have multiple sessions running at the same time.

However, to provide this multi-session support, a VHD is created for each device logon, with a maximum of 5 VHDs retained per user.

Feedback from certain customers was that this capability was not required by default and so it is now possible to toggle multi-session support ON or OFF, to help reduce disk usage on back-end storage.

For further details see Cache Roaming.

Context sensitive help improvements

The Environment Manager context-sensitive help system has been extended to provide improved access to relevant help topics directly from the console. In addition, anonymous telemetry within the Ivanti help system can provide us with insights into how the system is being used.

Examples of the data gathered include:

• The most visited help pages

• The most searched-for terms

• The navigation paths from specific pages

This data enables us to focus development effort and resource on key areas of the product to help improve features and simplify the user experience.

Group Policy Import Wizard

An intuitive Wizard has been introduced to import Active Directory Group Policy Objects and Group Policy Preferences. The objects are imported and then can be applied as Environment Manager actions. This simplifies the adoption of policy objects and can improve user logon times on the endpoint.

For more information see Group Policy Import.

Override Ivanti Automation Parameters

Environment Manager's integration with Ivanti Automation has been extended. Parameters from individual Tasks and Modules created with Ivanti Automation are now passed to Environment Manager automation actions. Intelligence is built-in to identify and correct out-of-sync parameters between Environment Manager and Ivanti Automation. Where a correction is not possible, the user is alerted.

For more information, see Ivanti Automation.

VHD Cache Roaming - Windows and Outlook Search

The cache roaming feature has been extended to include support for roaming both the Windows and Outlook search indexes. This is achieved using two new built-in templates:

• Outlook Search Template
  

  The Outlook search index is roamed between sessions in both VDI and RDSH on a per-user profile.

• Windows and Outlook Search Template
  

  A system-wide Windows search database can be roamed on a single-user desktop (VDI, kiosk/hotdesk PC)

For more information, see Windows and Outlook Search .

Personalization Database - Azure SQL Compatibility

With this release it is now possible to deploy the Personalisation database as an Azure SQL database. This means you no longer need to use virtual machines to manage your SQL database in Azure.

Configuration and management of the database continues to be done via the Server Configuration Portal (SCP) and support remains for on-premises and Azure virtual machine SQL server installations.

For more information, see Azure SQL as a Service Compatibility

Personalization Template - Roam File Type Associations (Windows 10)

Roam File Type Association Windows 10 using the new built-in Windows Settings Group Template. Persist user default application preferences across sessions ensuring a consistent and familiar User experience regardless of the device.
For more information, see File Type Association.

GeoSync AlwaysOn Support

AlwaysOn support has been added to GeoSync. Previously with SQL Merge Replication, you have needed to disable Replication on the primary and all subscribers prior to upgrading to a newer version of Environment Manager. This is not the case with GeoSync, upgrades can be performed with GeoSync in place.
For more information, see GeoSync AlwaysOn Support

OneDrive Cache Roaming

The cache roaming feature has been extended and now includes a built-in template to enable a user's OneDrive cache to be roamed between non-persistent sessions. This benefits organizations using Office 365.

For more information, see OneDrive Cache Roaming.

Concurrent User Access for Office 365 Virtual Containers

It is now possible to use the cache roaming feature to provide users with access to their cache when working across multiple virtual sessions. A typical scenario is where a user is accessing Outlook from multiple virtual sessions.

For more information, see Concurrent users.

Run As or Connect As features - Improved Security

The Run As or Connect As features allow drive mapping and policy actions to be performed using a profile selected from the Run As User Library. The method used to encrypt and decrypt credentials for such user profiles has been improved in 2018.3 to provide far greater security.

A public key and private key pair is now used to encrypt and decrypt Run As credentials:

• The public key is used on the Environment Manager console to encrypt the password
• The private key is required by the agent to decrypt the password. The private key must be installed in the Certificates - Local Computer\Personal\Certificatesfolder on every endpoint being managed

For more information about this feature, see Run As User Library

Integration with Ivanti Automation

This release introduces integration with Ivanti Automation to enable the automated management of tasks. Routine and complex tasks can now be run from within Environment Manager Policy Action. This integration brings together the power of Ivanti Automation and the Environment Manager Policy engine, allowing IT the time to focus on higher priorities.

For more information about this feature, see Automation integration into Environment Manager Policy.

Documentation for this release has been removed. The What's New section is for information purposes only.

Cache Roaming for Virtual Sessions

Cache Roaming attaches a container to the user’s virtual desktop or session during logon that persists application caches between sessions.

This feature introduces 2 new EM Policy actions:

• VHD Management – to create, attach and detach a container(s) during a user session.
  (Note, the ability to detach VHDs on session locked and session disconnected triggers, has subsequently been deprecated in Environment Manager.)
• Cache Roaming – configure locations within the user profile for redirection, either to a container managed with the above action or an alternate folder location

One of the key drivers behind this feature is to support the increasing adoption of Office 365 within the enterprise. Customers can now easily configure roaming between virtual sessions for scenarios, such as Outlook Cached Exchange Mode, using either the “out of box” profile cache options, or alternatively by setting up custom redirections.

GeoSync Set-up for existing Subscribers – Improved Workflow

GeoSync enables organizations to synchronize their personalization configuration and/or user settings across multiple locations, all without the requirement for any 3rd party technologies (such as SQL Merge Replication).

10.1 FR4 introduces capabilities to help existing customers who currently maintain multiple ‘stand-alone’ Personalization Databases but wish to move to GeoSync. To enable a smooth transition to a synchronized model, 10.1 FR4 provides customers with a script that can be used to ensure the subscriber database(s) are compatible with their publisher prior to set-up.

Windows 10 Enhancements

As part of our continued focus on Windows 10 adoption, 10.1 FR4 extends existing features in two key areas:

• The File Type Association (FTA) policy action now fully manages default application settings for file types
• User resizing of the Start Menu is now personalized across sessions on Windows 10 1703 (and above)

Documentation for this release has been removed. The What's New section is for information purposes only.

Microsoft Edge Browser Personalization

As customers continue to progress in their adoption of Windows 10, having the ability to personalize the Edge Browser is something that is key to user experience. Environment Manager now ensures that common browser items such as Favorites, Reading Lists and Browser Settings are persisted for the user between their sessions.

Administrators import our Microsoft Edge Personalization template using the existing console workflow before then assigning to the required Personalization Groups. Although Edge utilises the Universal Web Platform (UWP) associated with Windows Store applications, we ensure that customers can personalize in a similar approach to a standard Win32 application, and provide support for profile archiving and rollback.

Watch a related video

Documentation for this release has been removed. The What's New section is for information purposes only.

GeoSync

Users may roam from city to city, or from physical to virtual desktop, but they expect the same personalized experience to follow them. With the release of Environment Manager 10.1 FR2, the new Geo Sync feature provides users with their personalized desktop experience regardless of their corporate location.

Administrators simply configure which users require their settings to be synchronized to which sites and configure a scheduled time for synchronization to occur. For customers who only want to centrally manage EM Personalization configurations and not user data, this can also be easily configured.

Supported by accompanying PowerShell cmdlets and APIs, the setup, configuration and monitoring of the Geo Sync feature can be fully automated to comply with enterprise deployment models.

Until now customers with multiple, geographically-distributed sites have relied on SQL Server Merge Replication for synchronization of Personalization data and configurations, which comes with a range of limitations and complexities. With the Geo Sync feature this functionality is built-in, and only requires SQL Standard Edition.

Watch a related video

Endpoint Self Service Tool (ESST) Localization

ESST is a System Tray utility that can be configured per Personalization group to allow End Users to manage their User Personalization data. With the release of FR2, the ESST will now localise French, German and Dutch Languages automatically for the user based on the configured Endpoint locale.

Documentation for this release has been removed. The What's New section is for information purposes only.

Console Rebrand and Renaming

The Environment Manager Console has been updated to reflect the new company name of Ivanti - see here for more details.

You may still see the ‘AppSense Environment Manager’ name used in certain areas, such as the registry or services. This is to make the transition as least disruptive as possible for existing.

Icon Refresh

Having made significant changes to the design of the User Workspace Manager consoles in version 10, we have listened to feedback and added a splash of color back into the consoles by refreshing and updating some of the icons used in the Environment Manager console.

Scheduling of Policy Nodes

It is now possible to configure Environment Manager Policy Nodes to additionally also run at a given schedule. This provides Administrators with the flexibility to re-apply or evaluate specific actions or conditions within their configuration at a determined interval without the trigger having to be re-executed.

For example, if an Administrator chose to schedule a Node within the User Pre-Desktop Trigger. It could run both during logon and at the determined schedule irrespective of whether the User had logged off and on again.

By using a similar workflow to the Windows Task Scheduler, we have made it simple for customers to leverage this new functionality as an alternative to complex scripting.

This feature is available for both the User and Computer Policy Triggers.

Video: Node Scheduling

Watch a related video

Configuration Notes and Comments

Within Environment Manager Policy, Administrators can now annotate their Node Actions and Conditions.

This feature introduces 3 new options:

• Comments within the Policy Node Action pane
• The default Node description is now editable
• A Notes tab has been added to the Policy Node Action view

These are especially useful in environments were multiple administrators will be accessing Policy configurations, allowing for visual tracking of key additional details and updates within the configuration.

Video: Node Descriptions

Watch a related video

SQL Mirroring Support

Support for SQL Mirroring has been re-instated for 10.1 FR1 release - it was not available in 10.0/10.1. Our best practice for this use case is to utilize SQL Always On. This allows adequate time to make the transition to our best practice.

Documentation for this release has been removed. The What's New section is for information purposes only.

Support for Windows Server 2016

Environment Manager 10.1 Personalization Server, Console, and Agent Components are all compatible with Windows Server 2016 (Server with Desktop Experience installation). For example, additional conditions are available in Policy that check for Windows Server 2016.

Group Policy Action enhancements

The Set Policy dialog has been redesigned for a simpler workflow. The dialog displays more detailed settings, such as the policy category, name, file name, and whether it is enabled. These detailed settings are also available in the report produced by Configuration Profiler. In addition, you can now set a default location that the console will use to store all Group Policy templates. This is useful, for example, if you store Group Policy Objects on a network share and do not want to copy them to the local Policy Definitions folder.

Lockdown for Microsoft Office 2016

Create Environment Manager Lockdown actions on applications in the Office 2016 suite using the updated Microsoft Office Lockdown Wizard.

New "Is Older Than" condition for file and folder deletes

A new condition is available for File and Folder Delete actions. Use it specify that files or folders get deleted if an attribute - Created, Last Modified Time, or Last Accessed Time- is older than a certain number of days.

Simplified Triggers for Citrix XenDesktop sessions

XenDesktop sessions now correctly execute the appropriate triggers during Session Lock/Unlock and Disconnect/Connect changes. Previously this required additional configuration.

Build number option for the operating system condition

The Microsoft update model now uses build numbers to identify feature releases and service packs. When creating a computer operating system rule, you can specify a target build number to be matched or used as the maximum or minimum build release. For example, you can target specific Windows 10 and Windows Server 2016 builds.

View/Edit functionality is now available in Find and Replace

You can now quickly navigate to specific actions and conditions in a policy that are returned by the Find and Replace search results. Selecting a result and clicking View/Edit immediately opens the item in the appropriate dialog for viewing and editing.

Support for Windows Server 2016

Environment Manager 10.1 Personalization Server, Console, and Agent Components are all compatible with Windows Server 2016 (Server with Desktop Experience installation). You can install Personalization Server 10.1 on a Windows Server 2016 machine and require no additional configuration than for a Server 2012 install, and out-of-the-box Windows Setting Groups are available for Windows Server 2016. For example, the Windows 10 personalization settings on a user's laptop will be available to that user on a Server 2016 RDP session.

Enhanced shortcut management

When users are roaming between different environments, Personalization now manages and prevents any personalized shortcut links that are not resolvable from appearing in the user’s session.

Personalization Operations Console localization

The Personalization Console is now available in three new UI languages - French, Dutch, and German.