I've been struggling with the infamous Adobe Acrobat 6.0 Professional package. Trying to do all tips & trix found here. But I still have problems when publishing with GPO. Seems my MST-file doesn't work I get "This action is only valid for products currently installed".

I have created a new MST in InstallShield Tuner (added company and user name etc), modified it in Wise Editor to include serial and eula properties. When trying to open it again with InstallShield Tuner it looks different, company name and user name information is empty. What am I not getting?!?!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



I tried the Install Tuner yesterday (I'm packaging 6.0 standard but presume they are much the same) - I had no joy with it at all, half of the product didn't even seem to work! Was more sucessfull creating my own mst and adding the serial number etc into the property table manually.

Anyway I gave up and snapped the install in the end and it works fine - although I had to spend quite a bit of time to get the PDF Printer installed and working. Wise just couldn't snap it - so I capured the printer install with Prism then copied out the appropriate registry stuff into my wise MSI. Installs fine even under as a locked down user.

This also allows me to advertise the product (which I couldn't get working with the vendor MSI) - although not everyone wants to advertise so this may not be an issue. I would much rather have used the vendor install but there you go.

Haven't deployed my package via AD GPO yet but I don't forsee any problems there since I'm not using the vendor MSI...

Good luck,
Answered 07/30/2004 by: MSIPackager
Third Degree Black Belt

Please log in to comment
/me looks up and see's a trend?

Nice nick MSIPackager :)
Answered 08/01/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment

This helped me.


Acrobat 6 Professional GPO Package

Here are the steps I took to complete the package for deployment through the GPO.

Delete Custom Actions:

UnSupportedInstallType (Solution 2)

CA_QV (Deals with the serial number)

Create a script that will install new string values in the following registry keys at the end of the installation using custom a custom action.

Key=SOFTWARE\Adobe\Adobe Acrobat\6.0\Registration
Value Name=SERIAL

Key=SOFTWARE\Adobe\Acrobat Distiller\6.0\Registration
Value Name=SERIAL

Get the values after a successful manual installation of Acrobat using the correct serial number.
Answered 08/04/2004 by: sashi
Senior Yellow Belt

Please log in to comment
I just did the Standard version of it a few days back. I had the same trouble with the Pro version, but got around it.

What I did was to open the MSI file that it comes with. Then convert that file to a WSI file. It prompts you to choose a new location. What it does then is unpackage it to a new locations. Then once you have done that, compile it and you will get a new full MSI file.

From there use InstallTailor which comes with Wise and create a MST files.

And there you go, all sorted.

Plus I used the above in my MST file.
Answered 08/09/2004 by: Thegunner
Second Degree Green Belt

Please log in to comment
I've tried the GPO installation tips provided by other posts (removing
certain things from the msi to make it run etc).. but I keep running
into an error at the end of the installation (via the GPO):

Warning 20225 Setup was unable to create a new item: Adobe PDF Port
Monitor The Adobe PDF printer may be unavailable

The setup works fine if I run the msi directly, just not via GPO and a
Software Package.

Does anyone have a fix for this?


Answered 06/22/2005 by: markm75
Yellow Belt

Please log in to comment
Well having a little experience with this I suggest you repackage the app. I know this is against convention but its what I had to do and it works fine for me. Installing via GPO with the vendor install failed in most cases in our environment and so repackaging was the only solution.

It's easy to capture and all you need to do is make sure you capture the hardware settings changes and also search for ini files after the capture as Wise tends to miss them. Once you have the capture, stop and start the spooler service during the install in your msi and your nearly home. Tweak it to suit you and you will fine it works fine.
Answered 06/24/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment