MI: Persistent or one time?
I think I remember reading the answer to this at some point, but now I'm doubting myself. Are managed installs persistent or once they successfully install on a machine does the MI no longer check that machine?
I'm asking because we are preparing to push the most recent version of Flash Player 11 to campus. Once Adobe releases a patch for Flash Player and there is a newer version that will also get pushed via patching. Will the managed install for the older version try to install again?
I'm asking because we are preparing to push the most recent version of Flash Player 11 to campus. Once Adobe releases a patch for Flash Player and there is a newer version that will also get pushed via patching. Will the managed install for the older version try to install again?
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
jrscribner
12 years ago
Posted by:
LanhamA
12 years ago
Posted by:
steelc
12 years ago
This is the smart label query I'm using to identify machines that need the latest version (11.1.102.62 as of this writing):
select MACHINE.ID , S.ID, S.DISPLAY_NAME, S.DISPLAY_VERSION from MACHINE
JOIN MACHINE_SOFTWARE_JT MS ON MACHINE_ID=MACHINE.ID
JOIN SOFTWARE S ON S.ID=MS.SOFTWARE_ID
WHERE
S.DISPLAY_NAME like 'Adobe Flash Player%Plugin'
and S.DISPLAY_VERSION < '11.1.102.62'
I know that searching for display version like this doesn't always work, but it seems to in this case. I have a similar rule for the ActiveX version of Flash Player.
select MACHINE.ID , S.ID, S.DISPLAY_NAME, S.DISPLAY_VERSION from MACHINE
JOIN MACHINE_SOFTWARE_JT MS ON MACHINE_ID=MACHINE.ID
JOIN SOFTWARE S ON S.ID=MS.SOFTWARE_ID
WHERE
S.DISPLAY_NAME like 'Adobe Flash Player%Plugin'
and S.DISPLAY_VERSION < '11.1.102.62'
I know that searching for display version like this doesn't always work, but it seems to in this case. I have a similar rule for the ActiveX version of Flash Player.
Posted by:
sfigg
12 years ago
I have a similar question in another post right below this one...I have a 300mb MSI being pushed out. If I set it for 3 attempts...and it's already installed on the machine, my label is just looking for all PC's in a 10.17.X.X range. If I just apply that label and push the manage install out, will it constantly download the 300MB from the K1000 and attempt to install all 3 times? Or will it recognize that it has that software/version installed already every time it checks in, and not do anything unless it's missing the software for some reason?
Posted by:
steelc
12 years ago
Posted by:
dchristian
12 years ago
Posted by:
steelc
12 years ago
Thanks, David. I'm aware of the issues and that particular string matching only works for versions 10 and 11 (we have some Flash Player version 9 floating around and the smart label doesn't pick it up). I read through GillySpy's post covering how to do this (http://itninja.com/question/computer-smart-label-based-off-software-titles-and-software-version-number-less-than&mpage=1&key=firefox) but since this is a temporary solution for us and it works I went with it.
Posted by:
GillySpy
12 years ago
Here's the regex for
S.DISPLAY_VERSION < '11.1.102.62'
BTW, this is how i test these to compare apples to apples:
* launch a mysql tool
* run this:
If it returns a 1 then I'm correct. If it returns no results then i'm wrong. Change the "DISPLAY_VERSION" to test different values. Change the RLIKE expression if you dare.
How did I write it? I don't know, i was always the guy in calculus giving the derivative or the anti-derivative so maybe I'm somehow related to the rain man for better or worse ;)
In the end you are actually guessing because we don't know for sure how the vendor will format his version string. E.g. will they use "11.1.099.02" for example? I hope not. While I did consider that possibility here I often don't bother. They have demonstrated they don't use a leading zero in the other "sections" so far but no guarantees. It would certainly make it shorter to take that out.
You can also use a combination of functions to manipulate the string first which might make the regex easier, but then you're out of the wizard.
S.DISPLAY_VERSION < '11.1.102.62'
S.DISPLAY_VERSION RLIKE '^((10|[0-9])[[...]].*|11[[...]]0[[...]]|11[[...]]1[[...]](101|100|[0-9][0-9]|[0-9])[[...]].*|11[[...]]1[[...]]102[[...]]([0-5][0-9]|[0-9]|61|60))$'
BTW, this is how i test these to compare apples to apples:
* launch a mysql tool
* run this:
select 1 from (select '9.1.10.62' DISPLAY_VERSION) SOFTWARE
WHERE DISPLAY_VERSION RLIKE
'^((10|[0-9]|0[0-9])[[...]].*|11[[...]]0[[...]]|11[[...]]1[[...]](101|100|0[0-9][0-9]|[0-9][0-9]|[0-9]|00[0-9])[[...]].*|11[[...]]1[[...]]102[[...]]([0-5][0-9]|[0-9]|61|60))$'
If it returns a 1 then I'm correct. If it returns no results then i'm wrong. Change the "DISPLAY_VERSION" to test different values. Change the RLIKE expression if you dare.
How did I write it? I don't know, i was always the guy in calculus giving the derivative or the anti-derivative so maybe I'm somehow related to the rain man for better or worse ;)
In the end you are actually guessing because we don't know for sure how the vendor will format his version string. E.g. will they use "11.1.099.02" for example? I hope not. While I did consider that possibility here I often don't bother. They have demonstrated they don't use a leading zero in the other "sections" so far but no guarantees. It would certainly make it shorter to take that out.
You can also use a combination of functions to manipulate the string first which might make the regex easier, but then you're out of the wizard.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.