What is merge with or override local in App-V 4.6?
What is merge/override local key/directory in App-V 4.6?
How the above related to Local_interaction_allowed variable?
The advice given was to read the white papers, which contain the answers to your questions.
If you have a particular query about an aspect of App-V then you could post a question explaining that you've read the information and your understanding of the setting is 'X' - but you are not getting the desired results.
No one is going to find the section in the white papers and type out the answer for you.
I got below link but they didn't elaborated it.
http://blogs.technet.com/b/virtualworld/archive/2009/01/27/merge-and-override-settings-for-the-virtual-registry-and-file-system-in-the-app-v-sequencer.aspx - ur00361883 6 years ago
Thank you, but in the white papers, only how to sequence is there and backround files of client is also explained and SCCM deployment also.But I didn't find above options, so posted seperately. - ur00361883 6 years ago
Lets say you have sequenced an application which created a file under C:\Test\App\123.txt. There are some other files[Lets say 456.txt & 789.txt] in the same directory on a machine where you have published the application. There will be some cases where your virtualized application may need to read information from the files/registries which are part of your local OS[which means not virtualized].
If you set the Directory App as Merge with Local then your AppV Client will be able to read the information[if required] from all the files in that Directory though the files 456.txt & 789.txt are not part of your virtualized package.
If you set the Directory App as Override Local then your AppV Client will not be able to get the information from any other files in that folder other than the file that your application has created. In the above case AppV Client will only be able to read information from 123.txt.
By default, while sequencing if a new folder gets created then that will be marked as Override Local. If files get copied to a folder which already exists then that will be marked as Merge with Local.
LOCAL_INTERACTION_ALLOWED is kind of configuration by which you can let your virtualized application interact with the OS. This is required for some virtualized applications to function properly. The values can either be TRUE - Interact or FALSE - Don't Interact.
My personal opinion is that LOCAL_INTERACTION_ALLOWED & Override/Merge does not relate to each other.
Many thanks for the explanation Vinod.
I tried to understand this concept by creating a test package and creating a shortcut to vbscript whcih displays the current file contents.
What I understood is, With Mergewithlocal it will read both the files in the folder and also if a file with same name exists in both the locations(local and virtual) then preference given to virtual.With Override it won't read the contents at all, so no need to check this preference.
From the Whitepapers, it is mentioned that App-V package interacts with local applications by default and so if any dependency is there in local machines, then it interacts directly.Then what is the need of LOCAL_INTERACTION_ALLOWED??
Can you explain this. - ur00361883 6 years ago
This is how it works,
Application which are virtualized will be Isolated from the OS & other Virtual Applications. Though it is virtualized, it'll still have Integration up to an extent & for some components such as Shortcuts, FTA's & so. The Interaction with OS & other local application is very limited.
But, there will be some cases where your virtualized application will need to closely interact with any of the local applications in order to perform some of it's operations such as virtualized application requires office to send an email. You then have to loosen the Isolation using the LOCAL_INTERACTION_ALLOWED=TRUE. This will break the Isolation & that is the reason why we should make it to True only if required. - Vinodreddy597 6 years ago