Allowing Better Interaction to App-V Virtual Applications

re: Allowing Better Interaction to App-V Virtual Applications

Daniel Oxley — Mon, 09 Jan 2012 17:38:49 GMT

@Jørn - the exclusions apply to the App-V SystemGuard which is local on the machine rather than to the App-V packages. In the example i described above, JAWS is installed locally on computers and with the solution provided here it allows it to work with the applications virtualised with App-V.

I have not tried Skype in App-V I'm afraid so don't have any help there.

re: Allowing Better Interaction to App-V Virtual Applications

Jørn Grotnes — Fri, 06 Jan 2012 12:30:17 GMT

I have the same challenge as Daniel, making Freedom Scientific JAWS and MAGic process events and objects from AppV packaged applications. Again, the registry solution is good as only some machines (XenApp 6.5 servers in my case) should run the accessibility software.

From what I read here, the exclusions applied to the registry refers to the locally installed JAWS? Bur it would appear that the exclusions should refer to the AppV packaged application. This is to a large extent confirmed by Kalles very good Skype example.

Is JAWS in your (Daniels) case packaged together with the AppV application so that it works with the Freedom Scientific DLL hook? That'd make for a very large package. Any help on understanding these two examples of exclusion (JAWS local and Skype as an AppV application) would help.

re: Allowing Better Interaction to App-V Virtual Applications

Chris 'Oz' Oswalt — Tue, 25 Oct 2011 18:13:56 GMT

I put together a couple of Powershell commands to automaticaly parse the Process Explorer log and import it into the registry.

social.technet.microsoft.com/.../f42f8092-1da0-4a50-a482-39f4ef548714

re: Allowing Better Interaction to App-V Virtual Applications

Kalle Saunamäki — Mon, 19 Sep 2011 11:30:54 GMT

Daniel,

I have done a "follow-up" post on my own on this very subject: blog.gridmetric.com/.../working-with-named-object-virtualization-exclusions

re: Allowing Better Interaction to App-V Virtual Applications

Kalle Saunamäki — Mon, 22 Aug 2011 14:24:55 GMT

But if the app requires passthrough settings in the first place, why wouldn't you want to have them for all users? Note that I'm not referring to LOCA_INTERACTION_ALLOWED, but rather doing those exclusions in the Sequencer's HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions -key, if it indeed propagates customized exclusions inside App-V package to all clients (and only for that app/package)..

re: Allowing Better Interaction to App-V Virtual Applications

Daniel Oxley — Mon, 22 Aug 2011 12:25:34 GMT

@ Kalle

That is right, you'll need to include the keys in the client's registry. i prefer it this way because it allows you to make these settings only on the computers that require it, rather than at a package level which means that every computer running the app has these exclusions whether they need them or not.

so, using the example from the post, these settings i only rolled out to the computers running the text-to-speech software rather than using LOCAL_INTERACTION_ALLOWED which would have meant that all users would have had this setting.

Daniel

re: Allowing Better Interaction to App-V Virtual Applications

Kalle Saunamäki — Fri, 19 Aug 2011 08:50:02 GMT

Daniel,

Very interesting article, thank you for it.

One question however about the object exclusion method you are describing: although it is not explicitly said I assume from the advice for service restart that you are adding the exclusions into App-V _Client_'s registry? This hardly is a "better" option than LOCAL_INTERACTION_ALLOWED per se because you need to touch each and every App-V Client's registry ;-)

However, there is also a object exclusion in the Sequencer's registry which - if I have not been mistaken (not yet tested it) - actually affects a list of object exclusions stored inside the SFT package (inside the osguard.cp file). Have you tested if App-V Client honors this objects exclusion list as I cannot fathom any other reason why the App-V package would carry such information? If it does work like this, too bad that the Sequencer does not expose this information in the GUI anywhere for editing per package basis, you just have to do it into registry prior to launching Sequencer.

br,

Kalle