Install Acrobat Reader via Group Policy UNLESS already installed

Unfortunately there is no easy way to handle this in the manner you describe. What you are creating is a more heterogenious environment that you should.

If you really want to go down this path, you will need a tool like WinBatch to handle much of your scripting as it can do full registry interrogation and updating.

My honest recomendataion - keep everyone at the same Reader version - even if they are not at the same version of Acrobat.

With the newer versions of Reader (7.x + ) you can use the InstallShield/Tuner / Da' Customizer along with Reader. Your installation package (built with Tuner) can set which product will have the dominant role when both are present. This will cover both the .PDF file type as well as the application\PDF MIME type.

Our corporate deploymet has Reader on ALL desktops, with Acrobat on about 1/4. The advantage of this is, if Acrobat must be removed for some reason (Associate no longer has business need for product) they aren't left in a PDF black-hole. Reader will automatically take over the dominant role.

So, the general rollout would be:
-- Strip Reader from desktop - regardless of Acrobat being installed - Note - Pre A7 Acrobat installations may need to be repeated due to Reader/Acrobat code sharing. Install Acrobat first.
-- Use Tuner to create your Reader deployment package.
-- Deploy using your standard rollout tool.

Like ALWAYS - Test your deployment in a small (under 50) user population. Just to get a feel for how things are working and if you need to make any changes before breaking everyone's desktop. :)

For full disclosure - this WILL cause a short spike in support calls while everything gets sorted out. But when you move to the next version you have set yourself up for a quick and smooth deployment. Bit the bullet now (you are only loosing a toe) - after the royal mess of a multi-version-reader multi-version-Acrobat fiasco, you might get lucky with only losing your leg at the hip.

Installshield Tuner / Da' Customizer* - it's not just good for Acrobat!

* Adobe Acrobat Installation Customization Wizard.

Hope this helps.

Don't hesitate to holler if you have any questions.

Thanks.

Well, I have a similar issue with the current version 9.

Scenario, everyone is getting this version of Reader (9). Some people already have Acrobat 6, 7, 8 Professional installed.

1. When altering the application in Adobe Customizer and setting it to allow that Acrobat being the default reader it bombs when actually trying to open in a web browser. Giving an error that i can't remember right off the top of my head. Searching for the error turned up a problem with Acrobat and Reader being confused.. and of course gave several suggestions about fixing the problem, but didn't really help my situation.

2. Since the error, I did a little more research and some people figured out it was something to do with the customization wizard and says to leave it default. I did that, now when both are installed when you open up reader it asks to reinstall it and then goes through the installation.. problem is it does it everytime and if the user doesn't have rights to the location of where the files are at it bombs.. which they are never going to have rights to.

3. So ok, now I guess the question is.. Is there a way in group policy to check to see if the acrobat is installed if so cancel installing reader? I tried editing the package in an older version of Wise which is all we have license for.. I checked for it there and when it detected it, it canceled the installation.. problem is it never writes to the registry that it installed and was canceled.. so everytime you restart it trys to install on that machine.

wow this has been a headache.