ObjExclusion & LOCAL_INTERACTION_ALLOWED
I am looking for some advice on the benefits and downfalls of doing the following.
Addition of a Registry key to modify the 'local interaction' behaviour or APP-V.
(Will create the following registry information:
Firstly, a bit of backgorund. We have some locally installed applications which need to interact with any virtualised application. The locally installed software is magnification software and screen reading software which is required for people with sight and hearing impairments.
The problem is that the screen reading software is not reading the data inside the Virtualised applications window. We have implemented the type of fix written about by Dan Oxley here - http://blogs.technet.com/b/deploymentguys/archive/2011/07/05/allowing-better-interaction-to-app-v-virtual-applications.aspx. However, this doesn't seem to work for the next iteration of the software and also we have discovered some more software that needs to read from the other APPV bubbles.
I know that setting LOCAL_INTERACTION_ALLOWED for each APP-V application would solve my issue but we are not going to revisit all of our applications and make this change. Also, this is a bit of a sledghammer approach in my view. So, Dan Oxley's approach of setting the relevant registry keys in the ObjExclusion registry key is the way forward. To find these for the working application we used ProcessExplorer and the process described above.
My question is this, why would you not set the registry key to a wildcard - "*"?
What are the disadvantages of doing this? Setting this registry key to "*" has fixed some of our applications but I'm afraid it will cause further problems with other applications and how applications interact with eachother. Any input/advice would be greatly appreciated.
There are no answers at this time