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
Answers (3)
"i.e i have sequenced an application and now been told some fonts were needed."
it honestl depends on the application itself
enabling local interaction opens up the package almost entirely to the operating system, this alone does not mean that functionality will be identical to that of a locally installed program.
<VIRTUALENV TERMINATECHILDREN="FALSE">
<POLICIES>
<LOCAL_INTERACTION_ALLOWED>FALSE</LOCAL_INTERACTION_ALLOWED>
</POLICIES>
<ENVLIST/>
</VIRTUALENV>
for example some plugins for Microsoft word that are installed on the local machine will interact with a virtualized version of Microsoft word, some others will not and will need to be virtualised.
if you use AdminStudio, you can create Sequences with multiple MSI's
Or you can use DSC.
if the fonts are needed in the App and not available on the target machines, you need to add them?
Comments:
-
hi no that isnt what i meant, its a enquoiry as to what app-v can see, can it see the underlying operating system? or just what it needs in its bubble?, i am fully packager aware, just unsure on app-v how it all comes together - keane2012 11 years ago
