Software Deployment

You'll need to find the Product Code for each product and then run a sequence of calls to MSIExec.EXE, adding the uninstall switch and other such switches as you need. For example, I *always* specify a verbose log, for installs AND uninstalls.

For example, I have Acrobat Reader 9.3.2 on the machine I'm using at the moment. Its Product Code is {AC76BA86-7AD7-1033-7B44-A93000000001}. To uninstall, I would use this command line:msiexec /x {AC76BA86-7AD7-1033-7B44-A93000000001}/qb /l*v %temp%\AcrobatReader090302.log

Can you be a bit more precise, please?
What embraces "ALL" versions of "ACROBAT"?
Acrobat [Pro/Std] [Versions] ?
Versions 7-9 (MSI's) are uninstalled, if you install a newer product.
Older ones need special treatment for each version.
Adobe Reader too?
Regards, Nick

Hello,
I manage a network of about 2,000 computers and each has a different version of Acrobat Reader.
I wanted to standardize the computer with a version of Acrobat same for everyone.
Using Landesk I wanted to create a script that I uninstall all versions of Acrobat and install Acrobat Reader version 9.3.

Thanks

If you were so interested, you can definitely accomplish this by using the win32_product class in WMI without having to find every product code from Adobe that ever existed.

are interested in everything that can help me solve the problem.
What do you advise me to do?

using the win32_product class in WMIThing is, Joe, do all the products use the same format for, say, the Name or Caption? I'm willing to bet that some are named as 'Adobe Acrobat Reader', others as 'Adobe Reader'. Creating code to correctly parse those is probably just as much work as finding the Product Codes. I'd wager LANDesk could produce a report which lists them, wouldn't you think?

The right way to identify products is via the GUID and VersionMin/Max as described in the admin guide. Here's my canned response to many questions which will point you there.

Hi folks,
Adobe recognizes a clear need to provide admins with more and better documentation and resources. To this end, resources are being updated and corralled in an enterprise portal here: http://kb2.adobe.com/cps/837/cpsid_83709.html. Note that one resource is an AIR application which contains much of the documentation and an ever growing Preference Reference documenting over 300 keys. Expect several hundred more pages of new and updated doc in the coming months.
thanks,
Ben

Ben,

the link you've provided to the Adobe Enterprise portal is a dead link - 404 error.

Do you have an updated URL?

thanks,

Dunnpy

ORIGINAL: dunnpy

Ben,

the link you've provided to the Adobe Enterprise portal is a dead link - 404 error.

Do you have an updated URL?

thanks,

Dunnpy




yes it does - you need to remove the full stop at the end of the line

Too early in the morning to notice a little thing like that when I posted [:)]

Removed the '.' and site is there.

Thanks,

Dunnpy

ORIGINAL: VBScab

using the win32_product class in WMIThing is, Joe, do all the products use the same format for, say, the Name or Caption? I'm willing to bet that some are named as 'Adobe Acrobat Reader', others as 'Adobe Reader'. Creating code to correctly parse those is probably just as much work as finding the Product Codes. I'd wager LANDesk could produce a report which lists them, wouldn't you think?



It definitely isn't the same syntax every time, but some WQL-fu like so: name like '%adobe%' AND name like '%reader%' . Has worked marvelously for me so far.

Hi Dunnpy,

You're right. Looks like AppDeploy includes the "." in the URL.

Enterprise Admin Portal: http://kb2.adobe.com/cps/837/cpsid_83709.html

Get the AIR-based AIM tool if you want registry key details for Acrobat-Reader tools.

ben

Looks like AppDeploy includes the "." in the URLIt does if you include it when pasting into the 'Insert link' dialog, or in the selected text when you use that same dialog.