User Environment Manager 9.7 has been released

[DEMdev]

We're happy to announce that User Environment Manager 9.7 has been released. Just a single new feature this time, but a very important one if you're using the UEM SyncTool: application blocking and privilege elevation are now also supported in SyncTool scenarios.

Other changes:

• We fixed a bug that prevented [ExcludeFiles] and [ExcludeIndividualRegistryValues] entries from being processed correctly in rare situations. So rare, that it took until last month for someone to report the problem, which was caused by a bit of code that had been unchanged for nearly nine years 🙂
• Too specific to warrant inclusion in the release notes, but if you happen to have hundreds and hundreds of DirectFlex executables configured in a single Flex config file, you no longer need to wait a few (or more than a few...) seconds for the Executables list to be populated when you switch to the DirectFlex tab for that config file 🙂
• Mapping drives with explicit credentials was already deprecated in UEM 9.0, but until now we still supported config files created with older versions.
  No longer: as of UEM 9.7, you'll see a [WARN]  Mapping a drive with explicit credentials is no longer supported message in the log if such a config file is encountered by the UEM agent. The agent will still try to map the drive, but it will do so without those credentials.
  Editing such a config file in the Management Console will silently remove the credentials.

[system32AUT]

Hi UEMdev and thanks for the update!

1 question: What do you mean with "Drive Mapping with Explicit Credentials"

Do you mean AD Group Memberships or Conditions like this one:

Or do you mean maybe net use for explicit users over logon tasks ? Other things ?

Thank you!

[sjesse]

In older versions you used to be able to map drives to users using a set user name and password, this would be used instead of the currently logged in user. They removed the option from the management interface, but older configuration files still have the settings in them.  I've been dreading this since that use case is going to make me do something different now.

[DEMdev]

Hi system32AUT​,

As sjesse already mentioned, previous versions of UEM allowed specifying a user name and password for a drive mapping.

As the password could not be securely encrypted, we decided to deprecate this feature in UEM 9.0. Since then it has not been possible to create such mappings with explicit credentials, but both the UEM Management Console and the UEM agent still processed existing settings.

At some point, deprecated features go away completely, so as of UEM 9.7 this support is gone.

sjesse,

If you don't mind me asking: any particular reason why you can't manage this with group-based access control on the shares?

[sjesse]

UEMdev​ honestly I can't remember, but they wanted everyone to connect as that user for some reason.