VMware App Volumes

VMware App Volumes (before Cloud Volumes) - a product is focused on distribution of the VMware ThinApp applications, ready to use, by means of the connected virtual disks to machines.

2020

Updating of VMware ThinApp to version 4.1

On July 14, 2020 it became known that VMware updated the solution for distribution of the VMware ThinApp applications, ready to use, by means of the connected virtual disks to machines. Now App Volumes 4.1 (it is officially version 2006) can work also in cloud the environment Horizon Cloud on Azure.

In upgraded version of a product appeared:

• At change of appointments (assignments) there is a dialog box with the overview of changes which will be made. If they are updated, then now it is not required to delete last appointments, they are just updated.
• Administrators can limit delivery of application packages to computers with a certain prefix in a machine name.
• App Volumes Manager allows to use uniform workflow for third-party packets now and to start them in parallel with native. Packets MSIX with attached by VHD can be used means of the App Volumes Packaging Utility utility.
• Support of LDAP Channel Binding and LDAP Signing.
• Change of a versioning - is now not version number 4.1, and year and month, i.e. the current version - 2006. For the agent and App Volumes Manager version 4.1 will remain.
• Performance improvements at the user login.
• The rolling upgrade functions returned again - now it is possible to update one of App Volumes Manager when the others continue to work.
• Support Microsoft Office 2019, Microsoft SQL Server 2019 and Microsoft Windows 10, is added by version 2004.
• Updates of documentation.

Updating of the VMware App Volumes Entitlement Sync utility to version 4.0

On the website of the VMware Labs project the useful VMware App Volumes Entitlement Sync utility to version 4.0 was updated. It became known on June 18, 2020. It allows to read, compare and synchronize access rights to objects between App Volumes copies on geographically separated platforms. After authentication on both platforms it is possible to select access rights which should be compared or synchronized.

Possibilities of the updated App Volumes Entitlement Sync 4:

• Support of App Volumes 4.x - as for Application Packages, and old Legacy 2.x AppStacks is added
• App Volumes Managers of version 2.x are still supported
• Error corrections in a linking of Application/Package at replication
• Preserving of the address of the server, user name and the domain in the register
• The improved mechanism of logging and error handling
• Opportunity with to inkhronizirovat objects of Application Package Markers
• It is possible to delete empty applications
• Determination and displays of the selected type of appointment (assignment type)
• Display of the version of the current marker (or is shown that it is absent)
• Display of the version of App Volumes Manager on the homepage
  • 1 XLIFFService: Sequence contains no elements

Final release of App Volumes 4

On January 16, 2020 the VMware company released final release of the solution App Volumes 4.

According to the developer, in the provided version additional opportunities of the simplified management of applications appeared. Instead of AppStacks objects as it was in App Volumes 2.x, users work with the following objects:

1. Applications – at first the user creates the application. It comprises one or several versions of the packed software product. Purposes of the rights to users, groups, computers or organization units it is made at the level of the application. Appointments can be also made in certain packets.
2. Packages – after application creation the user uses packaging VM for collecting of changes which the application makes on a disk to prepare it for distribution for users and computers. It is the same process, as was during AppStacks creation. Packets are appointed to creation stages then they can go on lifecycle stages.
3. Programs – after creation of a packet occurs autogeneration of the program. The name of the program is appointed automatically. One program may contain several installers of applications.

Such architecture gives big flexibility and granularity at management of applications:

For example, at an exit of upgraded version of the application, the user can add the necessary Package to already existing object of Application and to bring him to the necessary users.

On the other hand, such model allows to operate applications on a hierarchy level of the organization. For example, it is possible to create Application for marketing departments where there will be separate packets for each department. And already at the level of department to make assemblies (Program) for each of cases (for example, a role of the user at the level of department):

Function of coexistence of applications of old versions. The applications of version 2.x created as App Stacks can coexist with applications of version 4.x (Applications/Packages) within the administrative App Volumes 4 console. For this purpose in the console the special tab for 2.x applications which the user can gradually drag on upgraded version of the platform is made.

Additional functions. In this category the following improvements appeared:

• Application Owners – the user can appoint Active Directory entities for designation of the owner of the specific application.
• Application History – the user can look at the list of the administrative operations performed with the application and who executed them.
• Intent-based Assignments with a Current Marker – can designate one of application packets as current to designate that this version will be delivered to users.
• Single-app Package Format – applications can be extended within one packet which can be combined somehow and within a configuration with several VMDK disks in the course of delivery to users.
• Package Lifecycle Stages – for a packet can see stages of its lifecycle (New, Tested, Published or Retired).
• Package Notes – can trace packet parts, by adding of notes about required specifics or a configuration of the application after the user finished packaging of the application in a packet.
• Improved Template Management – the Template policy files (cfg) moved from a disk template to a basic image therefore they can just be updated by updating of the agent. App Volumes Manager provides the interface for loading and service of templates.
• Upgrading – can update App Volumes Manager from version 2.18 or more late, but to continue to manage agents 2.x.
• Prevent Modifications to Installed Applications (in Tech Preview stage) – some of users can have an opportunity to change or uninstall applications from a basic image. It can implicate in the form of influence on writable volume which is tied to other VM with the same application (and to cause unpredictable effects). Therefore the administrator can prohibit modifications of applications by users (by default such function is turned off).
• AppStack Migration Tool is a special utility which allows to migrate objects of AppStacks 2.x on application packages (Packages) of version 4.x.

Lifecycle extended through App Volumes 4.0 applications looks as follows:

• The administrator creates the application of the necessary version and saves metadata which reflect parameters of an environment in which the packet was created.
• Using App Volumes and ThinApp the administrator is convinced that this application version works in different OS and does not clash with other applications.
• In the pilot environment there is a testing of this application version on some set of relevant users.
• If testing took place successfully, there is a publication of applications in the production environment. Purpose of the rights happens in the same way, as in old App Volumes of versions 2.x.
• After an exit of updates there is a write-off of the old version of the App Volumes applications.

As the developer noted, on all App Volumes 4 functions it is possible to walk within interactive walk-through^[1]:

2019: Beta of VMware App Volumes 4.0

On October 22, 2019 it became known of release of the beta of the solution VMware App Volumes 4.0 (on it upgrade from version 2.18 is available).

According to the statement of VMware, key features of the solution App Volumes are the following functions:

• Decoupling package management and delivery - allows to work freely as owners of applications with packets, to separately organize their delivery and to quickly service user queries.
• Manage the full lifecycle of an application is a possibility of a nakatyvaniye of updating of the application just by a packet repablishing within the configured workflow.
• Packaging once and deploying everywhere is means for onpremizny and cloud mass deployment of application which are demanded preparation only once then they are freely rolled per any number of hosts.

As noted in VMware, possibilities of App Volumes 4.0 are provided in three categories:

• Single App Packaging - within uniform a vorkfloa can combine process of packaging and delivery of applications in any combination and within a configuration with several VMDK disks.
• Application Lifecycle Management is means on service of lifecycle of the unrolled applications. It allows to be convinced that the selected users receive the correct versions of applications in due time.
• Smarts Delivery and On-Demand Applications - these opportunities allow to lift limits for the number of applications which will be delivered to users. Applications which are unrolled on demand - important feature for big installations.

According to the developer, lifecycle extended through App Volumes 4.0 applications looks as follows:

• The administrator creates the application of the necessary version and saves metadata which reflect parameters of an environment in which the packet was created.
• Using App Volumes and ThinApp the administrator is convinced that the created application version works in different OS and does not clash with other applications.
• In the pilot environment there is an application testing on some set of relevant users.
• If testing took place successfully, there is a publication of applications in the production environment. Purpose of the rights happens in the same way, as in old App Volumes of versions 2.x.
• After an exit of updates there is a write-off of the old version of the App Volumes applications.^[2]

2016: VMware App Volumes 3.0

On February 2, 2016 the VMware company announced the version of App Volumes 3.0^[3].

Representation of interaction of App Volumes (2016)

As a part of App Volumes 3.0 functions:

• AppToggle is technology for installation of applications and safe purpose of the rights. It reduces number of necessary volumes for service, simplifies management of them and increase performance. Such architectural approach allows applications to have interdependence in one AppStack and to give access to them to other applications that provides high degree of flexibility of deployment of infrastructure of App Volumes.

• AppCapture with AppIsolation – now the AppCapture technology has interface CLI, is integrated with the product VMware ThinApp that allows to collect within one AppStack physically installed and virtualized applications for delivery to their certain users and working groups. Process of delivery of applications, their updating and control of isolation from each other became simpler (for example, it was necessary to start ThinApp earlier, and then separately means of AppCapture).

• AppScaling with Multizones – in the presence of several data-centers of App Volumes provides means for deployment of the same AppStacks on several platforms. If it was necessary to care manually for replication of application stores earlier, then now App Volumes can be integrated with vCenter copies on each of platforms and to select, where to create remarks of the required AppStacks with applications of users. Scanning of storages regarding synchronization of AppStacks will take place in DPC with the set interval.

• Integrated Application, User Management and Monitoring Architecture – the architecture of App Volumes collects in one place of control function by applications and their lifecycle, environments and user rights and also App Volumes infrastructure monitors. The solution is integrated with the unified monitor of virtual infrastructure vRealize Operations Manager.

• Unified Administration Console – all functions of the solution are brought together in one console of the administrator (Astro console). This administrator configures infrastructure of physical and virtual applications which is scaled in one or several data-centers on virtual PCs of users.

The VMware App Volumes 3.0 technology will be presented in three editions: Standard, Advanced, Enterprise.

For February 2, 2016 date of a release of the application is unknown.

Notes