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.

AD security groups are something that you've configured, they may or may not involve in your situation (depends if you have uninstall collections that have members of those who aren't members of the ad group etc.).

If dependencies are missing, then they are missing, if you've configured them correctly, ConfigMgr will install all the dependent applications if they're missing on the target.

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

Hi,

It seems that even though you put the dependencies into SCCM, it doesn't pass this on to the Appv client, so I'm having to advertise all the appv applications and tell the users to install the pre-requisite first e.g. oracle 10G

The error I get in the AppEnforce.log when the primary application tries to install is:

"The mandatory dependent package {E8AC3E46......} is not installed on the client, so we cannot install this Appv package (Package Name)"

"CAppVHandler:CheckDependentPackage()failed. (0x87d01285)"

"CAppVHandler:InstallApp() failed. (0x87d01285)"

If I install the dependencies separately, it all works, but I shouldn't have to do that. It's almost like SCCM isn't passing the dependency information on to the appv client.

Are you using the App-V 5 package or the App-V 5 MSI package for your deployments? Could you post a screenshot of your dependencies configuration?

It's correct that ConfigMgr does NOT pass dependency information to the App-V client. The dependencies configured in ConfigMgr are handled by ConfigMgr and not by App-V. Did you configure the dependencies to install when they are required?

Hi Peter,

Sorry for not replying earlier but I had a couple of days away.

The dependencies are configured to Automatically Install - Yes

All of our Appv applications are advertised, since even though they may be a dependency to another application, they user may just want to request that particular application e.g. Access 97 or Oracle 10g etc, and They are deployed as Install and available so that the user can install them themselves through the application catalog.

However, getting back to apps with dependencies, just the primary application is deployed, then the user will install it through application catalog, and the dependencies are supposed to just install first without user intervention due to the Automatically Install option.

Have I got this right, or should I change the dependent apps to install, required?

I know this is an old thread but if you have landed here looking for a solution then I might be able to help as I had the same issue as above.

It was caused by the dependency being named slightly differently in the OSD file compared to the SCCM Application dependency. In my case I had some dependent applications that had very similar names, so double check and make sure you have the same dependency in both the OSD file and in SCCM.

Cheers

Paul