Understanding Templates used in App Volumes

In Omnissa App Volumes, a template is a .vmdk or a .vhd file which can be used to create application packages or Writable Volumes. You must specify a template when you create a volume or when you upload volumes packaged with your instance of App Volumes Manager to the selected datastore.

packages_templates and writables_templates are used for creating application packages and Writable Volumes.

Types of Writable Volume Templates

The following types of Writable Volume templates are available in App Volumes: Profile-only, UIA only, and UIA+profile. Depending on your requirement, you can use any of these types in your environment.

Writable Volume template types and their usage is listed as follows:

• Profile-only - Captures only the profile information of the users and does not include any configuration information related to user-installed applications in the Writable Volumes. The profile is delivered early in the boot process and considered only a local profile delivery. Additional profile tools like roaming profiles and Omnissa Dynamic Environment Manager still apply and work as expected. Use this template if a profile solution is not in place.
• UIA only - Captures all user-installed applications but does not capture any data that is written to the user profile. You can use this template with a third-party profile solution or Omnissa Dynamic Environment Manager.
• UIA+profile - Includes all user-installed applications and user profile data. The user profile data is only a local profile and is not a roaming profile or other managed user profiles.