Application dependency: is the dependent application also downloaded even if it is already installed?

I have this Office 2013 App-V package and a seperate pacakge for proofing tools.

Office 2013 App-V package is deployed correctly but when I deploy seperately the proofing tools (which has a dependency to the App-V Office 2013 package and automatically install when it is not there) then it (Proofing Tools) shows something like "remaining 2 components".

So what worries me: the Proofing tools package should see that Office is already installed so why it shows "2 components", it should only install Proofing tools that's 1 component. Is it actually downloading it (then this is a serious overload).

If I would remove the dependency, then packages are installed at random whereas I want first Office, then the proofing tools.

Please advise
May 29th, 2015 9:39am

Couple things of note here:

1.  SCCM will only download components it feels it needs.  It does this for applications by checking the detection string.  If your detection string isn't working properly, it will assume the app isn't installed regardless of if it was originally installed by SCCM or not.

2.  Rules are "Special" for App-V, as by default it "silos" apps running so they can't detect each other unless you group them with connection groups.  So make sure you have those established for App-V as well ... as that's the only way they will count as dependencies for each other (refering to two app-v packages, you can always classically install a dependent app).

3.  Traditionally I don't recommend using app-v for Office.  It sounds nice on paper, but _everything_ wants to hook into it so you almost always end up with one massive connection group which ends up defeating the purpose of App-V IMO.  Office is a borderline framework in this age.

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 11:07am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics