Software Deployment

You can follow this format for 5.0

Acrobat Reader 5—uninstall
The next step is to uninstall Acrobat Reader 5.x, if it's installed. I suppose if you wanted to be thorough, you could also check for versions beyond 5.x, but a single version check for now will suffice.

The uninstall string for Acrobat Reader 5 is in the Registry in this section:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Acrobat 5.0\UninstallString

The complete uninstall string ( Listing B) can be broken into three parts:

The uninstall executable Isuninst.exe
The location parameter option for the uninstall log file—in this case, f\"C:\ Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.isu\
The DLL that's called—in this example, -c\"C:\Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.dll

Separating the uninstall string into three sections allows us to more easily see what is being executed and also shows us where to insert the parameter to perform a quiet uninstall. To uninstall in quiet mode, insert –y between the first and the second sections of the uninstall string—for example, Isuninst.exe –y –f "C:\Program Files\Common…. The UNINSTAR5 subroutine in Listing A handles the uninstallation of Reader 5.x. For a complete listing of command line parameters for InstallShield's Isuninst.exe, check out this InstallShield support page.

Hope this helps

Giz

Unfort this is not a script install - Pure GPO deployment

I have done some lateral thinking here which may work out. In a batch file, I put in the line
%windir%\ISUNINST.EXE -f"C:\Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.isu" -c"C:\Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.dll" /A

In the files section in the mst, I have added this batch file in the Adobe Reader folder for version 7. I then put the location for the batch file in the Run External application section of the mst.

Theory goes along the line that the batch file gets installed in a location I specified. I then call the batch file which then uninstalls version 5.

Will be testing to see how it works out.

Have u finally found ur way round it yet? Gimme ur mail so that i can send a doc on how this is done. Quite easy to understand if u don't want to script.

Giz

I have actually managed to remove the Adobe 5 from all test systems by in the GPO that installs Adobe 7.05, in the computer startup script, putting in the batch file with

c:\winnt\ISUNINST.EXE -f"C:\Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.isu" -c"C:\Program Files\Common Files\Adobe\Acrobat 5.0\NT\Uninst.dll" /A

in it.

My issue right now is that all the modifications made using Adobe InstallShield like no EULA and other custom stuff such as no Yahoo toolbar in the MST only applies to the Default User when I need it to apply to all users on the computer.

To hide the Yahoo Internet Search Toolbar for ALL USERS

Rename this HKCU key to HKLM and move it to HKLM KEY.


[HKEY_CURRENT_USER\Software\Adobe\Acrobat ACROBAT\7.0\AVGeneral\cToolbars\cWebSearchView\cPositions\cInternal]
"iDockPosition"=dword:00000000
"iFrameB"=dword:00000000
"iFrameL"=dword:00000000
"iFrameR"=dword:00000000
"iFrameT"=dword:00000000
"bHidden"=dword:00000001
"iLayout"=dword:00000000
"iOffset"=dword:00000000
"iOrder"=dword:00000032
"iStack"=dword:00000000
"bWindowHidden"=dword:00000000

THIS SHOULD SOLVE UR PROBLEM.

GIZ

Hi Claude,

I'm in a similar boat to you.
I've deployed 7.0.5 reader through GPO and have a startup script that calls a VBS script.
The VBS script checks for various previous versions and does the install.

The problem I have is that 7.0.5 is deployed before the startup script runs. This seems to cause problems with file associations ect getting broken by the removal of 5.0.

Is there some way to make the startup script run before the software deployment takes place?

Cheers,
Mark

I may be in a similar issue - The removal of Adobe 5 Reader after Adobe 7.05 installs breaks some settings in the MST like EULA appearing. Also if an Adobe document is opened - an error is given as the system looks for Adobe 5. Not until Adobe 7 is opened does some of the settings reapply - though the EULA does appear.

I am on a short break and will be working more on this. An alternative would be to have any script/batch run as a Computer Shutdown script. A reboot is required for Assigned Software so makes some sense - old version geets removed during shutdown and when system boots up, Adobe 7.05 installs as per normal.

I don't like it as much but it is a solution which should work with less, if anyerrors that comes about removing Adobe Reader 5 after Adobe 7 is deployed.

Mine works fine. I actually included the uninstall string for adobe 5 in our deploying script.

It uninstalls fine then the sript runs the setupapp script to installs the adobe 7.