Breaking into the virtual environment in App-V 5.0
This post has moved here
Comments
Anonymous
January 01, 2003
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 wrongAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Do you see the virtual system okay?Anonymous
January 01, 2003
Are you sure they aren't just there under the Program Files x86 location?Anonymous
January 01, 2003
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.aspxAnonymous
January 01, 2003
Thanks!Anonymous
December 15, 2012
Go on you legend ! :)Anonymous
February 01, 2013
Great Work....!Anonymous
February 26, 2013
Thanks, very helpfulAnonymous
April 10, 2013
Thanks for the information, yayAnonymous
April 12, 2013
What are the pros and cons (if any) of using this method as opposed to using /appvve or /appvpid switches?Anonymous
May 14, 2013
The comment has been removedAnonymous
May 15, 2013
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.Anonymous
October 09, 2013
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 anywayAnonymous
October 09, 2013
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.