App Volumes has a feature to run scripts at various times during the mounting process of Appstacks:
- prestartup.bat : Runs as SYSTEM (if the volume is attached from boot, this will run when svservice starts)
- startup.bat : Runs as SYSTEM (if the volume is attached from boot, this will run when svservice starts)
- shellstart.bat: Runs as user (if the volume is attached before the user logs in, this is called just before the Windows shell launches)
- startup_postsvc.bat: Runs as SYSTEM (but only if there are services/drivers on the volume) logon_postsvc.bat: Runs as user (but only if there are services/drivers on the volume)
- allvolattached.bat: Runs as user (if multiple volumes are all attached at the same time such as during logon, this is called only once)
The best option to resolve the outlook issue is to create an allvolattached.bat & allvolattached_shellstarted.bat and put this in the AppStack that will be assigned to all users. You can also put it in all the Appstacks, this script will still only run once.
How to add the script to an Appstack?
- Mount the Appstack /Writable Volume to a VM that has no App Volumes agent installed.
- From the vSphere console or web client, edit settings on the VM, add existing disk, browse to the App Volumes datastore where the Appstack is located you want to edit. It is very important that the VM has no App Volumes agent installed!
- Log in to the VM, go to disk management and add a drive letter to the App Volumes disk.
- Assign a drive letter to the disk.
![]()
- Open Windows Explorer and browse to the Appstack volume.
- Create the batch files (allvolattached.bat & allvolattached_shellstarted.bat) and place it in the volume
- Remove the drive-letter from the Appstack volume.
![]()
Hope this helps you.