You can configure some of the settings directly from the Settings page, and others through the environment variables.
Go toto view and edit the settings.
|General Settings||UI Session Timeout||The number of seconds App Volumes Manager remains active after the user logs in. The default value is 30 minutes. Set via the system environment variable SESSION_TIMEOUT.|
|General Settings||Certificate Authority File||Path of the certificate file used by machine managers. Set via the system environment variable SSL_CERT_FILE.|
|Volume Mounting||API Mounting||Enable the user to log in even if a Writable Volume or an AppStack cannot be attached to the user at the time of login. Set via the system environment variable AVM_ALLOW_API_MOUNT (or CV_ALLOW_API_MOUNT).|
|Writable Volumes||Delete Protection||Protect volumes from getting deleted directly from storage. Set via the system environment variable AVM_NO_PROTECT (or CV_NO_PROTECT).|
|Writable Volumes||Force Reboot on Error||If a Writable Volume is assigned to a user, and the volume does not get attached to the user, the user has the option to reboot the machine. Set via the system environment variable AVM_WRITABLE_REBOOT.
Note: The AVM_WRITABLE_REBOOT does not apply to Writable Volumes conflicts. Writable Volumes conflicts are handled by the the Block user login setting. See Create a Writable Volume (2.x) for information about this setting.
|Writable Volume Backups||Regular backups||Toggle the slider to enable or disable regular backups for Writable Volumes. If enabled, Writable Volumes are backed up on a regular basis based on the recurrent interval. For example, if the recurrent interval is set to 7 days, a Writable Volume will be backed up if 7 days have elapsed since the last back up. Back up is only performed for Writable Volumes that have been used at least once since the last backup.|
|Active Directory||Allow or Disallow||
The App Volumes Manager expects Computer and User accounts to be members of a registered Active Directory domain. Computer startups and user logins using local accounts are normally ignored.
If non-domain entities are allowed, the Manager will create a record for local entities when they are first seen. That entity can then have AppStacks assigned to it from the Directory tab.
|Writable Volume Backups||Storage Location||The location where the volumes are backed up. For example, [xxx]AV-LUN.|
|Writable Volume Backups||Storage Path||The folder name and path where the volumes are backed up. For example, cloudvolumes/writable_volumes_backup|
|Advanced Settings||Disable Agent Session Cookie||Toggle the slider to enable or disable Agent Session Cookie.
App Volumes uses a session cookie to optimize the communication between the App Volumes Manager and App Volumes Agent. If you have Agent session issues, you can use this setting to disable the session cookies.
|Advanced Settings||Disable Volume Cache||Toggle the slider to enable or disable volume cache. App Volumes caches AppStack or application objects to improve performance. However, if you experience increased memory usage, consider disabling volume caching.|
|Advanced Settings||Disable Token AD query||Toggle the slider to enable or disable token AD query. App Volumes queries for Active Directory group membership using cached object SIDs. Previous versions of App Volumes performed group membership queries against Active Directory domains directly and recursively. Disable token AD query to revert to the previous implementation.|
|Advanced Settings||Enable Volumes (2.x)||Toggle the slider to enable or disable the VOLUMES (2.X) tab.
VOLUMES (2.X) tab is for working with AppStacks and Writable Volumes along with App Volumes Agent 2.x. For upgraded deployments, this setting can be disabled after the AppStacks and Writable Volumes are completely migrated.
If you have newly installed App Volumes Manager, for more information about this setting, see Perform App Volumes 2.x Management Tasks.
If you have upgraded to the latest version of App Volumes Manager, for more information about this setting, see Configuring visibility and management of App Volumes Manager 2.x UI.
|Advanced Settings||Allow package delivery to any operating system||Toggle the slider to allow packages to be delivered to any operating system which is different from the operating system used during packaging.
By default, this setting is disabled.
Note: Enabling this setting might result in application inoperability. For optimum application compatibility, ensure that the same operating system is used to package and deliver the application.
Though any operating system can be used, the package must be captured and delivered in virtual machines that have the same Windows operating system architecture.
For example: if the package is captured in a virtual machine running 64-bit operating system architecture, then the package can be delivered to a machine running a 64-bit operating system architecture only. Package delivery cannot happen to a machine running 32-bit operating system architecture due to architecture mismatch.