If you use Adobe's Customation Wizard and configure to remove all versions, I have found that this does this reasonably well. Most of our clients only had one version of Reader installed, however, so not sure how well it would if multiple versions are installed.
The 11.x reader, however, upgraded 9.x and 10.x systems without issue. I used the full package because we had various instances of "slipstreamed" update installs and using the .MSP method would fail in these scenarios. Using the full package ensured
everyone had the exact same version and configuration once upgraded. Going forward, I can continue to use the full package method or simply deploy the .MSP.
We have the base 11.x .exe version extracted. We use the wizard to create the .mst. The setup.ini is configured with our command line and patch switches so we don't need to use any when setup.exe is run:
[Startup]
RequireMSI=3.0
CmdLine=/sPB /rs
[Product]
msi=AcroRead.msi
CmdLine=TRANSFORMS="AcroRead.mst"
PATCH=AdbeRdrUpd11010.msp
The .msp file is copied into the extracted folder, which should like this:
ABCPY.INI
AcroRead.msi
AcroRead.mst
AdbeRdrUpd11010.msp
Data1.cab
setup.exe
Setup.ini
You should be able to run setup.exe without any switches. Otherwise, you can do a batch file with removal commands for all other versions and then run the setup.exe. As suggested, the PowerShell App Deploy Kit works well for this also.