What’s New in VMware User Environment Manager (UEM) 9.1.0

VMware Environment Manager (UEM) 9.1.0. has recently been released.  Lets take a look at some of the new features.

No AD Mode

First off you no longer have to deploy UEM using a GPO it can be deployed using an xml file which could be ideal for getting a Proof of Concept up and running really quickly.

For Active Directory deployment refer to:

Deploying VMware User Environment Manager (UEM) 9.0

  1. Create .xml config file

Once you have downloaded the media and unzipped the file, navigate to \\VMware-UEM-9.1.0\NoAD Mode and you will see the NoAD Sample.xml file.  Modify this file for your deployment.  Example:

All settings you can configure in AD can be deployed using the xml file.  More Examples:

BackupPath=”\\Filesrv\UemUsers$\%username%\Backups”

BackupCount=”3″

BackupDaily=”1″

Once you have completed the .xml file save it the following location: \\FileServer\UEMconfigShare$\General\FlexRepository\NoA

      2. Install the UEM agent with the switch:NOADCONFIGFILEPATH

Use the command line to install the UEM agent on your gold image, physical machine etc.

Example:

msiexec.exe /i “VMware User Environment Manager 9.1 x64.msi” /qn LICENSEFILE=”\\FileServer\share\VMware UEM.lic”  NOADCONFIGFILEPATH=\\FileServer\UEMconfigShare$\General

A nice quick and easy alternative to using AD and login scripts i’m sure you’ll agree.

*Note – you cannot use the SyncTool with the No AD deployment.

Horizon Smart Policies

These policies have been improved.  There are new conditions for Endpoint Platform so you can apply policies based on whether the endpoint is a Android, Linux, MAC, Windows device.

Horizon Client Property now has improved Client location settings to define whether a device is internal or external.

The bandwidth profile also now supports Blast protocol

For more information on Horizon Smart Policies refer to:

VMware User Environment Manager using Horizon Smart Policies

Application Blocking – ‘hash-based’ blocking.

This feature has been improved to allow blocking of applications using the applications unique hash.

Application Blocking first needs to be enabled globally, in User Environment Manager tab >>> Global Configuration.

Now when creating an ‘Application Blocking’ setting.

You can block or allow application by Path or by Hash.  You can combine path and hash based blocking.

When clicking  ‘Add’ an explorer window will open for you to browse to the application .exe file. The hash is then populated automatically.

‘Path-specific’ checkbox enables you to only allow specific versions of an application and block everything else.

Other things to note:

Windows Vista and Server 2008 is no longer supported in v9.1.0

For release notes and official VMware documentation refer to:

https://www.vmware.com/support/pubs/uem-pubs.html

 

 

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *