Breaking into the virtual environment in App-V 5.0 ★★★★★★★★★★★★★★★ Thamim KarimNovember 21, 201215 Share 0 0 This post has moved here
I see it properly in Local Registry under AppvClientPackages dont see it when virtual registry is launched. I tried different options like /appvve & /appvpid as well but same resutls. Any ideans on where I might be doing wrong
Hi Richard,
Your right all methods spawn a new process inside the VE. There is no way that I know of that will allow you to inject a process that is already running, there would some challenges around shifting the namespace visibility for a process that has already been launched.
I am interested in what you are trying to achieve and why the ability to insert a running process as you described would be useful?
Do you see the virtual system okay?
Are you sure they aren't just there under the Program Files x86 location?
Not much difference Anil, check out this post for a full explanation: blogs.technet.com/…/app-v-5-0-launching-native-local-processes-within-the-virtual-environment.aspx
Thanks!
Go on you legend ! 🙂
Great Work….!
Thanks, very helpful
Thanks for the information, yay
What are the pros and cons (if any) of using this method as opposed to using /appvve or /appvpid switches?
Hi Thamim,
I'm exploring the possibilities of 'breaking' into the virtual environment in App-V 5.
It seems the one thing I'm looking for does not exist…
I would like to be able to 'insert' a running process into a virtual environment.
Do you know if such a thing is even possible with App-V 5?
Thanks,
Richard
Thanks for you reply.
What I'm trying to achieve:
I built this "launcher" which is capable of handling several application virtualization types in a uniform way (App-V 4.x, Symantec SWV, VMware ThinApp and now App-V 5). After using a special shortcut or file type association the launcher will import/load/stream the application after which it can be customized/personalized INSIDE the VE.
As App-V 5 seems more similar to Symantec SWV than to App-V 4.6, I wondered if it might have the same functionality (like injecting a process into a VE, for which SWV has an API). In my case it would just improve performance, that's all.
Having said that, I have just found out from a colleague that the problem is with the Parent directory choice during sequencing. If you use c:program files as parent directory instead of choing the actual installation directory c:program filesAdobe, then there is a chance that you do see the application folders within the bubble. Good to know anyway although I won't sequence in this manner anyway
Whoops it seems my first post didn't get published. ok the post above is to follow on the fact that on x64 bit Windows I can never see the program directories within the bubbles say under c:program files, and this using any methods /appvid or powershell etc.. and then a colleague told me about the above. I think the problem is only with x64 bit.