Systems Management

One, there is a dedicated SCCM/SMS forum here on AppDeploy (a moderator may well move this thread there) and two, that kind of conditioning belongs in the package (MSI), not the deployment tool. If you wanted to go that route, I imagine you'd have to build a script and execute that.

Sorry for the improper placement.

And Thank you.

But Our issue is.
One application is user targeted and the other application is machine targeted.

1. We want the user targeted application to move along with the user but Not the other machine targeted application.

2. We want the user targeted application to move with them but if the dependent machine targeted application is not there on the machine the user currently logged in then the application should not try to install.

Regards,
Ram.

I've just been having a think, and because you are using targeted users and targeted machines, it's going to be difficult to populate a collection on a query, due to the mix of targets.

You could create a VB script to check for the dependency and then launch the MSI if applicable, but then you loose the error reporting on the MSI installation, because it will report back on the VB script execution to some extent.

If you condition the MSI, as Ian suggested, then you should see a different exit code for missing dependency than you would for a failed installation, so you can work with any genuine failures.

Hope that helps,

Dunnpy

Let me see if I've got this right...

The user-targetted app will always install, yes?

The machine-targetted app - which is dependent on the user-targetted app being present - should not install if the user-targetted app is not present. Is that right?

Ian,

I read it as the other way around. User targeted app should only install if machine targeted app is present.

We'll see what OP says :)

Dunnpy