Some of these scripts are run in the user context while others are run in the system service account. You can create or modify a different set of scripts in the custom configuration directories, which are not affected by App Volumes agent upgrades. Script Nameīefore file and registry database (index information) is read from Writable Volume or an application package.īefore virtualizing a Writable Volume or an application package.Īpplication is still not available to the user at this stage.Īfter virtualization has started for a Writable Volume or an application package, but before services from that package have started.Īfter virtualization has started and after services from an application package or a Writable Volume have started.Īfter virtualization has started for all the application packages assigned to the user.ĭuring logoff processing, before virtualization is stopped for all the application packages and Writable Volumes.ĭuring logoff processing, after virtualization is stopped for all the application packages and Writable Volumes.Ĭustomizable Batch Scripts for App Volumes VMware does not recommend changing these scripts because the changes are not preserved acrossįor more information about the default configuration directories, see Default and Custom Configuration Files. Writable Volume, or application package, then such scripts are ignored. If the scripts are created in any other location on the base image, Important: These scripts are only read from the default configuration directories.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |