Client Management Suite

Ok we have a SMD policy that installs adobe reader 10 on all pc's.  I have some new users coming in with Adobe Reader 11 on their machines.  I don't want to remove adobe 11 to put this machine back to 10 I would just like to not install 10 on this box.

 

I have two methods to do this.  Detection rule modification or modify applied to resources.

I think the Detection rule would be best today it is on the MSI product code.  Should I add an "or" statement to that or how do I go about this??  I'm sure some others have run into this already so figured I would get some discussion going on it.

Normally you would use a filter that looks for machines that either have no reader installed or with a version less than the one you are deploying, as this would exclude those that have a higher versions. Now, if you have simply targeted the entire environment, then yes, you will need to use detection rules. You can either use the v11 product code or a v11 wildcard file version value.

I sometimes use an Applicability Rule for this. NOT file version Adobe Reader .exe > 10.3.1 or whatever the version of reader is in your package.

But bear in mind that this will stop explicit uninstalls too, uninstalls called by the uninstall superseded versions tickbox in a Policy will still work.

Thank you for now I'm blocking the single machine but will have to make a modification to the detection rule.

You shouldn't make artificial modifications to detection rules or you risk Inventory being reported wrongly. For example, if you modified the detection rule for Adobe Reader 11 to include 10 then machines with 10 might get reported as having 11.

That's why I use Applicability Rules for v10 to say AND NOT File Version acrord.exe >= 11

Andykn101 I appriciate the details but I already have a applicability rule applied I can't modify and has to be used.

In the end it is just like anything else use what is best suited for your environment. 

Now if software management worked as designed I should be able to apply 11 as an association to 10.  This is really how it should work and not modify Detection rules or apply applicability rules but I have been burnt by using associations and Software Management has basically told me DO NOT USE THEM.  Now maybe 7.5 fixes this which would be great but I have been seriously burnt to many times to test this out again.