Hello community!
Is there a way to attach a newly created App Volumes package to a running VDI session with the help of a batch file or any other trigger?
I often test packages but I don't want to logoff and login again only for a new package. So, I'am looking for a faster way to attach a newly created App Volumes package.
Thanks in advance!
Good question - I'm curious as well ... again for testing packages you are assigned to, and not as a way to "bypass" anything.
I'am pretty sure it’s possible because when a package is assigned "on-demand" the user triggers the mounting of the vmdk by clicking a shortcut.
It would be great to attach all available/assigned packages with a batch-file or similar.
I believe this was a feature in previous version of AppVolume.
I have a testpool, which is a duplicate of my production pool, but with an ID "TestPool", which I now publish my newly created/updated appstacks to.
Then i assign my appstack directly to my user and use "assigntype: Package" and choose my latest update, and also use "Limit delivery for these assignmnts:" directly to the testpool.
This way I can test my appstack before I change the marker to "Current".
And with my testpool, i can log on, check if things seems ok, and log of again. Even with my regular VDI connected.
Hi Lansti,
it's very similiar to my procedure but I want to change this, because I'am too lazy for the numerous logins and logoffs in my test-pool all the time.
Totally get the “login/logout” fatigue in testing AppStacks. Hope we get to figure it out
You should be able to use the command-line delivery feature to do what you're looking for using the svservice deliver and svservice run commands! There is information about the process here:
Thanks @Merb - had a peek and that seems promising, much appreciated!
