You can configure
App Volumes Manager by selecting configuration options such as batch script files called at various points during system startup and login, registry options for services, drivers, and other parameters.
Batch Script Files App Volumes agent executes batch script files either when an AppStack or a writable volume is attached dynamically or at various points during system startup and login.
Timeouts When executing batch files, App Volumes can be configured to wait for a script completion before processing to the next step.
Advanced App Volumes Agent Configuration The App Volumes agent consists of two major components, SVdriver and SVservice.
SVdriver Configuration Parameters SVdriver can be configured by configuring registry keys and optional values in the HKLM\SYSTEM\CurrentControlSet\services\svdriver\Parameters registry key.
Drive Letter Settings App Volumes agent interacts with mapped volumes using a system path to the volume, without mapping it to a drive letter.
Configuring the SVservice Parameters You can configure SVservice with the following registry keys and optionally configuring the values in the HKLM\SYSTEM\CurrentControlSet\services\svservice\Parameters registry key.
Volume Behavior Parameters Volume behavior parameters are values that need to be configured for SVservice configuration.
General Behavior Parameters You need to configure services, drivers, and general behavior parameters values for SVservice configuration.
vCenter Server Custom Role You can use a custom vCenter Server account to create roles.
Create a Custom vCenter Server Role Using PowerCLI You can create custom vCenter Server roles by using PowerCLI.
Scaling the App Volumes Manager You can install an additional App Volumes Manager component on multiple servers and point them to a shared SQL database.