Hi All

In 9.1 installation I have customized the msi to suppress the EULA. After upgrading Adobe Reader 9.1 to 9.1.2 with msp patch (using group policy) users are prompted to accept EULA first time they open Reader.
Have anyone else seen this?

Thanks,

Itreial
0 Comments   [ + ] Show Comments

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.

Answers

0
In 9.1 installation I have customized the msi to suppress the EULA. How, via a transform, or directly editing the MSI? I suspect the latter, because it sounds like the patch has now obliterated your change. Still, you have a back-up of the original MSI against which you can create a transform, right?

After upgrading Adobe Reader 9.1 to 9.1.2 with msp patch (using group policy) Presumably, you mean you patched an Administrative Installation point, since GP can't handle patches natively?
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
0
You should install to an admin point, apply the MSP patch and then use the "Adobe Customization Wizard 9" to create a transform file (.MST) that supresses the EULA and anything else you want to modify.
Pat
Answered 07/29/2009 by: pmarshbu
Orange Belt

Please log in to comment
0
Thank you for your answers,

sorry i didn´t give enough information first time.

i used upgrading to 9.1.2 using this http://www.404techsupport.com/2009/06/26/how-to-apply-patches-msp-to-group-policy-deployed-software-msi/

The initial 9.1 installation was customized with Adobe Customization Wizard 9.
And after i upgraded the customized msi with 9.1.2 msp patch and installed it via gp as suggested in above link the situation occured.

If i open the upgraded msi with Adobe Customization Wizard 9 it says that the EULA is suppressed, but after installing it to test group every user had to accept the EULA.

thanks,

itreial
Answered 07/29/2009 by: itreial
Yellow Belt

Please log in to comment
2
Once you have applied the update (to an admin point), you'll need to re-create the transform because you have changed your MSI during the upgrade and your MST was built for an earlier version of the MSI. If you just deploy the MSP, you will not get any of the benefits built into your transform for the previous install and the EULA will be displayed. This is why the admin point install works so well. You can apply all the required updates, then recreate the MST and deploy the package together. Hope this helps!
Pat
Answered 07/29/2009 by: pmarshbu
Orange Belt

Please log in to comment
0
I have the done the same thing. However, can I use this 9.1.2 AIP to upgrade older versions of Reader? i.e. 7 or 8?
Answered 07/29/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
you'll need to re-create the transform I'd suggest creating a whole new one for the 912 release. Always, always, ALWAYS have a fall-back capability!
Answered 07/29/2009 by: VBScab
Red Belt

Please log in to comment
2
Hi Pmarshbu, when you say You can apply all the required updates, then recreate the MST and deploy the package together. , exactly how would I go about in doing that? I'm *thinking* that i'd have to go the customization wizard and then choose *generate transfrom* from the transform menu? Sorry, but I'm new at this.
Answered 07/29/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
vtt5142,
Don't start your Adobe Customization 9 tool to create the transform until after you've upgraded the software to the latest version. I would recommend doing an admin install, to a network location. In addition, you will not need to apply the 9.1.1 update. Here are a couple of commands to help you to do an admin install and then apply the patches to it. Once you have applied the patches, open the .msi with the Customization tool, modify what you want, and create your transform by selecting <Transform> <Generate Transform> in the installation directory where your new AcroRead.msi is located. Here are a couple of generic commands that will help you create the admin install:
Installation:
msiexec /a <path to msi> TARGETDIR=C:\temp\admin
Upgrades:
msiexec /p <path to msp> /a C:\temp\admin\<msi>

Note: Adobe is supposed to release a security patch for a vulnerability by July 31st (tomorrow) so you may want to wait until you can apply that patch also (before you create the transform) and before you deploy. You can get help extracting your msi from the installer by going to http://kb2.adobe.com/cps/404/kb404146.html
Good Luck,
[font="microsoft sans serif"]Pat
Answered 07/30/2009 by: pmarshbu
Orange Belt

Please log in to comment
0
Hi Pat,

Thanks for the thorough response. I've actually done everything to the tee that you had mentioned. Here's what I'm encountering:

1) Using SCCM,. I can push the 9.1.2 slipstreamed version to 8.X reader and below clients and see a successful upgrade.

2) Any machines that has 9.1 or 9.11, the upgrade does not work. What's interesting is that I see *Adobe Reader 9.1.2* under add/remove programs but while launching Reader, the original version (either 9.1 or 9.11) is stil there.

3) The EULA is still popping up on successful installs. Just to reitierate, I created a brand new 9.1 AIP, upgrade that AIP to 9.1.2, run the wizard with my options, create the transform and save the MSI. The transform resides in the same directory as my MSI. When I create the package in SCCM, i use the "msiexec /i acroread.msi /q" command for a silent install. Of course the mst is in the same directory as the msi. What am I doing wrong here?

I'm actually more concerned about getting the 9.x reader clients to upgrade to 9.1.2. Any ideas?

Thanks in advance for your advice and input.
Answered 07/30/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
I'm actually more concerned about getting the 9.x reader clients to upgrade to 9.1.2. Any ideas? ORIGINAL: vtt5142

Correction to that. I just checked a 9.0 Reader client and it was successfully upgraded to 9.1.2. It's just the 9.1 and 9.11 is what I'm having issues with.
Answered 07/30/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
2
What am I doing wrong here? You haven't specified the transform file. Its presence alone is insufficient:msiexec /i acroread.msi TRANSFORMS="whatever.MST" /QN /L*V %TEMP%\AcroRead.LOG The '/L*V' switch I have also added tells the engine to create a verbose log, a habit you should get into as, without a log, it will be impossible to determine why an install has failed.
Answered 07/30/2009 by: VBScab
Red Belt

Please log in to comment
0
That was it! As you can tell, I'm new at this but learning lots along the way. However, I could not find the log file, checked under c:\temp and c:\windows\temp and did not see acroread.log. The install went through w/o issues so does that mean that no log was stamped? Unless there's another location that I have failed to check.

Any suggestions on upgrading 9.1 and 9.11 to 9.12? Running the slipstreamed 9.12 MSI on these machines doesn't work (as you can see from my earlier posts).

Thanks again!
Answered 07/30/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
However, I could not find the log file, checked under c:\temp and c:\windows\temp and did not see acroread.log.ORIGINAL: vtt5142

Solved my own problem. Found it under "my profile\local settings\temp"

Now I know where it's located at. [;)]
Answered 07/30/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
That's why it pays to read posts properly (talk about do as I say, not as I do!). %TEMP% resolves to the user profile TEMP folder, as you found. Remember that the 'Local Settings' folder has its 'Hidden' attribute set. Packagers should, of course, have set Explorer to display hidden and system files.
Answered 07/30/2009 by: VBScab
Red Belt

Please log in to comment
0
On that note, is there a way to place the log file under c:\temp instead of profile\temp?
Answered 07/30/2009 by: vtt5142
Senior Yellow Belt

Please log in to comment
0
%SystemRoot%\TEMP

You could also enable MSI Logging via Group Policy. The long way, via GPEdit or the quick way:REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
The downsides of the policy route is that it's an all-or-nothing thing, meaning that you get logs for everything, including advertisements and that the logs are created with random names (albeit prefixed with 'MSI'.)
Answered 07/31/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity