#Res one workspace update

This has a lot of benefits, especially in the amount of management that needs to be done. Devices run from one Golden Image and user data is saved in roaming, streamed or hybrid profiles. As always, a special thanks to all the team members who helped building, testing, documenting and delivering this release.These days we live in a non-persistent (RDS,VDI) workspace world. Ivanti Workspace Control 10.2 is available in the Ivanti Community portal. This concludes the Headline News, but there are other minor updates as described in the product documentation.

Support of macOS 10.8, for macOS, support start from 10.10.

We removed support for the following third-party platforms:

Support of Red Hat Enterprise Linux 6.9.

Support of Citrix XenApp/XenDesktop 7.15 LTSR.

The Workspace Control v10.2 release delivers support for the following third-party platform versions:

#Res one workspace update

Where the File Hash Monitor eliminates the need to manually configure file hashes, as it allows you to automatically import and update these in your Workspace Control environment, the Application Whitelist Monitor is also capable of identifying and importing file certificates. The Application Whitelist Monitor is the new version of the File Hash Monitor (FHM). It simplifies security whitelisting if you deploy new applications via a third-party tool such as Microsoft System Center or IBM BigFix, or if you deploy them manually by storing them on a file share. The Workspace Control Application Whitelist Monitor (AWM) is a companion tool to Workspace Control. In this example a rule is created which whitelists all the applications with the publisher ‘Microsoft Corporation’ and product name ‘Microsoft Office 2016’:

With application whitelisting based on file certificates you can easily create a whitelist rule based on the digital signature of the Microsoft Office applications. Of course, while application whitelisting based on file hashes is very secure, it does require quite some maintenance because if an update of Microsoft Office is installed, the file hashes will change. If you want to whitelist applications like Word, Excel, Outlook and PowerPoint you need a whitelist rule per application and per application version when using application whitelisting based on executables or file hashes. Let’s take the Microsoft Office 2016 suite as an example.

This Workspace Control v10.2 release contains the final version of this simplified and powerful application whitelisting feature.Īpplication whitelisting based on file certificates allow IT to create rules to whitelist applications from a specific vendor or product name using the certificates of signed executables-providing the same level of security as file hashes, but with fewer rules and a lot less maintenance. More information can be read in this blog. Basically, this version focused on a redesign of existing application whitelisting feature including a technical preview of whitelist management using file certificate. In the v10.1 release, in July 2017, we introduced improved security management in the Management Portal.

File Certificate-based Application Whitelisting We are working in the background to rebrand the other components of Workspace Control too.