VB script to look for folders & install patches
Hi all
I have a number of users using AcroPro8 & Standard with various versions:
To name a few - AcroPro 8.1.0, 8.1.3, 8.1.5. Latest versions on Adobe.com is 8.2.2.
What I'd like achieve:
1) Download all patches to a shared folder (to be installed based on individual versions that out there on our network.)
2) Create a VB script file, transformed into an msi file to be deployed from AD group policy; in effect this msi file will go and look for AcroPro install folder and install/apply appopriate the patches. For instance if the "AcroPro" folder is found on a machine named "pc123" currently using AcroPro 8.1.5 then VB script will apply the new patch for this particular version, and so on.
At this point I do not have specific info on who and pc names since those Acropro copies got installed at different points in time.
Any ideas much appreciated.
bobz
I have a number of users using AcroPro8 & Standard with various versions:
To name a few - AcroPro 8.1.0, 8.1.3, 8.1.5. Latest versions on Adobe.com is 8.2.2.
What I'd like achieve:
1) Download all patches to a shared folder (to be installed based on individual versions that out there on our network.)
2) Create a VB script file, transformed into an msi file to be deployed from AD group policy; in effect this msi file will go and look for AcroPro install folder and install/apply appopriate the patches. For instance if the "AcroPro" folder is found on a machine named "pc123" currently using AcroPro 8.1.5 then VB script will apply the new patch for this particular version, and so on.
At this point I do not have specific info on who and pc names since those Acropro copies got installed at different points in time.
Any ideas much appreciated.
bobz
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Herein you have learned the importance of using Administrative Installation Points. If you had done so, you would have been able to patch a single network location and deployed from there. Once you have unified your versions, you should set up an AIP as a matter of urgency. Ditto for any other apps you have which are frequently patched.
As it is, the work you're asking someone to do is pretty substantial. It's certainly not something I'd do for free.
As it is, the work you're asking someone to do is pretty substantial. It's certainly not something I'd do for free.
Posted by:
Lucid
14 years ago
Sounds like your first goal should be getting something in place so that you can identify machines that need the updates (maybe a logon script that records software inventory info to a central database). That way, if you can't get an automated solution like Microsoft SCCM or Altiris in place, at least you know which machines need to be tackled. Worst case, you could then start pushing out the older patches via GPOs to select machines, and work your way through them...
Posted by:
squeakstar
14 years ago
seems like i've been beaten to a sensible response from vbscab and lucid - one app version kept up to date the way to go
spiceworks can inventory your apps per computers across the network and it's lovely and free (http://spiceworks.com) and does a lot more besides [:D]
spiceworks can inventory your apps per computers across the network and it's lovely and free (http://spiceworks.com) and does a lot more besides [:D]
Posted by:
anonymous_9363
14 years ago
I had quite forgotten about the MouseTrax Domain Report Manager. It's also free and, because it's written entirely in VBS, highly customisable. I've used it as a basis for this kind of discovery at quite a few clients.
Posted by:
bobz
14 years ago
Hi again,
Thanks much for all ideas.
I do agree starting with getting a list of affected PC names in place.
I'll explore further software as suggested in the post.
Bob
Thanks much for all ideas.
I do agree starting with getting a list of affected PC names in place.
I'll explore further software as suggested in the post.
Bob
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.