sequencing app-v, interaction of underlying operating system
Can app-v see the underlying operating system
i.e i have sequenced an application and now been told some fonts were needed.
do i need to resequence this or will it work if the fonts are on the base build when they werent on the build when sequenced?
can someone clarify this?
i also have msi's which werent installed as part of the sequence of a particular application, do i need to resequence these so they can interact the functions of the msi? and have the msis installed prior to sequencing? i dont want to use location interaction allowed
Community Chosen Answer
"When local interaction is enabled via an OSD policy, named objects and COM objects are created in the global namespace rather than isolated inside a particular virtual environment. "
This allows the application to fully interact with the local Operating System and allows other App-V virtualization bubbles to fully interact with that bubble. This neatly solves the some of the conundrum's with isolation, integration and dependency management with App-V.
But.. "enabling LOCAL_INTERACTION_ALLOWED can introduce application conflicts it is best that you only implement this if absolutely necessary "