My standard deployment involves using 3 AppStack assignments per user/group (each session gets 3 AppStacks). I've configured the "allvolattached.bat" batch file in 2 of the 3 AppStacks, but only 1 seems to be running. How does App Volumes handle multiple instances of this particular batch file? The user guide states that it is "called after all volumes have been processed," but if there are 3 instances of the batch file (in 3 separate AppStacks), will all 3 get called, or only 1?
Did you ever get this to run consistently? We had the same issue and are running with shellstart.bat and customizing the bat per appstack, because we were never able to control which appstack is attached as last and we did not want to maintain allvolattached.bat on all appstacks.
Please have a look at this blog:
allvolsattached.bat runs under Windows USER. If multiple volumes are attached at the same time (i.e., during user logon), then this is called only once.
Thanks, Laksman. Yes, I have seen this, but this is not what I have experienced with 2.9. The blog and docs should say this is called only once with the last attached appstack. The only way I got this bat to work consistently was with the same bat in ALL appstacks or only attach one appstack with the bat. Even with precedence, I had no luck, because it never seemed to make a difference what settings I used in conjunction with allvolattached in only one appstack while attaching multiple appstacks. But even if precedence was working, it would be hard to manage appstacks by departments/BUs and appstacks with one off per user licenses and configure precedence for the entire department group.
May be in the feature request realm to improve this. Would have loved to use this and have AppVolumes recognize the existence of the bat in ANY appstack and some logic to run it after all appstacks attach.
Could you check this behavior with 2.11 release please. There are bug fixes specific to allvolattached.bat file in the latest release.
Please have a look at the release notes here: VMware App Volumes 2.11 Release Notes