App-V Dependent Applications

Question

Hi,
we are using SCCM 2012 sp1 cu5 on Windows 2008 R2, one primary (it is also the MP) with many DPs.
We have sequenced our applications using App-V 4.6 sp1, and for some applications we have mandatory dependencies as specified in the OSD.
I am deploying the App-V applications in the same way as I have always deployed MSI applications.
I create the applications and add the dependent applications to the primary application (I don't worry about the order they are installed in, I just add dependencies and I guess it looks at the osd to install them on the client). The user is then added to
the AD security group for the primary appv package which is advertised.
This seems to work ok for many apps I have tested. However, I get some that try to install and then fail with a message in the appenforce.log which says a CheckdependentPackages() failed and  "Mandatory dependent package {A.....}
is not installed ont he client, so we cannot install this Appv package [Appname].
The apps are all linked as dependencies, so I thought they would just be called and installed as normal.
I'm just wondering if I'm missing something i.e. does the dependency need to be a specific order (same as in osd?) or do I need to create AD security groups for every package and add the user to it?, (i.e. does it use the AD group as permissions that the
user is allowed to install the app-v app?)
When I use another system (not in the above SCCM scenario) which uses the Appv management Server to load appv apps for citrix thin clients, I create a group for each app, since it does use the group as permission to be able to install and
load the appv app.
Just wondering if an SCCM Appv deployment expert could clear this up for me or give me a link to the definitive answer.
Thxs
Jaz

Answer 1

Thanks Narcoticoo, but the question is more around how SCCM deployment handles the dependencies with the Appv Client when they Appv Apps.
The dependencies are all added in SCCM 2012 to the primary appv application which is advertised.
I know SCCM downloads the apps to its client cache and then appv client takes over and copies them to the Appv cache, and the appv client loads them.
Has anyone else had the error above: "Mandatory dependent package {A.....} is not installed on the client, so we cannot install this Appv package [Appname], even though I have listed the app as a dependency in SCCM?
I would have thought, that since it is listed as a dependency in SCCM then SCCM would pass this information on to the Appv client and it would just publish the shortcuts if didn't exist.
Any real world experience of this would be really helpful
thxs
Jaz