Applied 11.0.07 msp to 11.0.00 msi, but patched msi defective

applied 11.0.07 msp to 11.0.00 msi, but patched msi fails with error 1334 (acroext.exe not found)

Check out this Awesome customer service:
As I mentioned in the forum post as
well, the workflow that you are using is not a supported workflow. So I would
recommend you to follow the steps below to create 11.0.07 AIP
1.
Download AdbeRdr11007_en_US.exe from www.get.adobe.com\reader
/p AdbeRdrUpd11007.msp
5.
Install Reader 11.0.07 using this AIP created in step 4 above.
If you face any issue in the above
workflow please reply back.
Regards,
Rohit
Hey Rohit,
Am I missing something, below your steps go from 1 to 5? If the
“workflow” has changed you should document it clearly step by step, rather than
leaving it vague and ambiguous.
VB
The workflow has not changed, I have
just put all the steps together for your convenience. The steps for creating
AIP are documented here<http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/aip.html>
Regards,
Rohit
“ As I mentioned in the forum post as well, the workflow
that you are using is not a supported workflow. So I would recommend you to
follow the steps below to create 11.0.07 AIP“
Those are your words. And now you merely sent me a link to the
“how to create an AIP” site. Clearly I know how to create the AIP as I did for
11.0.06. I want you to tell me verbatim how to generate a working MSI. Clearly
everyone else on the forum is having the same issue – that’s what it says not
resolved on the top of the page. Furthermore if you had a working MSI, why not
put it up on the FTP site? The answer to that is that you DO NOT have a working
MSI and neither does anyone else at the moment.
VB

Similar Messages

Acrobat 8.1.2 MSP will not update old MSI

Has anyone been able to update the Adobe Acrobat MSI file with the 8.1.2 MSP and push it out through Active Directory? I run the
msiexec /a "MSIFILE" /p "MSPFILE"
command and it says it updated the msi.
Then when I try to run the msi file it go to install/repair/remove 8.1.1. However when I just try to run the AcrobatUpd812_all_inc.msp it will let me install 8.1.2 with no problem. Is there something wrong with the patch or the way I am trying to patch it and push it out? I need it to be included into the MSI so I can push it out to all my users.

Here's some info that I found on the adobe forum sites that
corrected my problem with applying patches to an admin install point.
I recently got msiexec v4.5 from MSoft (which can't install on
Win 2K) but only on the later XP and Vista, and server 2003. Thus,
msiexec v3.1 will work too.
The common mistake people are making is that based on ones
interpretation of the MSoft msiexec documentation and which
AcroPro.msi to use. The first step to patching is to copy
all the files from the Acrobat install disk to ones hard drive.
After doing this, the person wants to create an admin install point
and then patch the AIP. What people are interpreting wrongly from
the msiexec documentation (an honest mistake) since they will perform
each step one at a time instead of all at once, and also that in the
future when a patch comes out, they will run the patch on the AIP
using the same sequence is filename AcroPro.msi. If all the patches
were applied in one commandline along with creating the AIP, the
AIP will be patched all at one. However, the easy thing for humans
to do is run one command at a time which is creating the problem with
the MAGAZINE_Ad_2006_JPN.jobopti file not found in the Data1.cab since each time the apply a patch they use the original AcroPro.msi
file that came from the Acrobat install disk, instead of the new
one that is created and updated in the AIP directory. Once people
create the AIP using the original AcroPro.msi file, they must then
patch the AIP using the new AcroPro.msi that is in the AIP directory.
Here's an example that a copied from Nhiem which fixed the problem.
Adobe web and technical support along with their KB articles
couldn't help because they didn't know why/how people were making
mistakes.
1). create an AIP using the original AcroPro.msi
msiexec /a "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcroPro.msi" TARGETDIR="c:\test\acroPro812"
2), Apply the patches, but use the NEW AcroPro.msi in the AIP directory and not the one used in step (1) above.
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd810_efgj_incr.msp" TARGETDIR="c:\test\acroProAIP"
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd811_all_incr.msp" TARGETDIR="c:\test\acroProAIP"
msiexec /a "c:\test\acroProAIP\AcroPro.msi" /p "c:\acrobat8pro\Adobe Acrobat 8 Professional\AcrobatUpd812_all_incr.msp" TARGETDIR="c:\test\acroProAIP"
3). I was able to apply the 6468.mst file to the new AcroPro.msi
and save it off using ORCA from Msoft. However, if I try to
use the commandline shown below, I get a 2203 Internal error and
it won't install (no filename specified when it does this). However,
if I specify the TRANSFORM file at the sametime I'm applying the
v8.1.2 patch, I get no error. But, when I view the AcroPro.msi
with ORCA and look at the entry, the port number that this transform
does which changes this number doesn't change the data. This transform
has conditions in it that check to see if the patch version is
greater than v8.1.1 and v8.1.2 since the port number was mistakenly
changed in these patches.
any ideas other than to apply it after the Acrobat software has
been installed from the install point using the /i switch which
commandline containing the transform option and filename?
Here's the command I'm running.
msiexec /a "c:\test\acroProAIP\AcroPro.msi" TRANSFORMS="c:\acrobat8pro\Adobe Acrobat 8 Professional\6468.mst" TARGETDIR="c:\test\acroProAIP"
See Adobe's kb article; however, the usage of the AcroPro.msi
is wrong since it implies to use the original one after the AIP
to patch Acrobat 7 files which is why people are mislead and
are getting all the problems they are getting. See,
http://kb.adobe.com/selfservice/viewContent.do?externalId=330817

Which patch to apply in OEM 12c 12.1.0.4 - PSU or Bundle patch

Hello All,
Could you please help me to understand - which patch to apply in OEM 12c 12.1.0.4 - PSU or Budle patch ? Per doc id - Enterprise Manager 12.1.0.4.0 (PS3) Master Bundle Patch List for Agent and Plug-ins (OMS and Agent side) (Doc ID 1900943.1) -
which of the below mentioned patch to be applied in OMS ?
1> System Patch 12.1.0.4.10 - Patch 20675595 (This is a single Sytem patch that includes all the OMS-Side Plug-in Bundles released this month as well as OMS-side Plug-ins released in previous months.)
or
2> For 12.1.0.4, this is Patch: https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1900943.1&id=20392036https://updates.oracle.com/ARULink/PatchDetails/process_form?parent=DOCUMENT&sourceId=1900943.1&aru=20392036 &patch_password=&no_header=020392036 (12.1.0.4.3 PSU). Please refer to Note.1995267.1 for the latest PSU patches available for Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4).
We recently upagraded our OEM from 12.1.0.2 to 12.1.0.4 with out using software updates option during upgrade, hence none of the PSUs are applied to OEM. Now we want to apply latest OEM patches which fixes all the fixes and bug/securities.
I thought BP will include PSU as well but why does DOC id - 1900943.1 says - NOTE: We recommend that you always apply the most recent quarterly PSU. For 12.1.0.4, this is Patch: https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1900943.1&id=20392036https://updates.oracle.com/ARULink/PatchDetails/process_form?parent=DOCUMENT&sourceId=1900943.1&aru=20392036 &patch_password=&no_header=020392036 (12.1.0.4.3 PSU). Please refer to Note.1995267.1 for the latest PSU patches available for Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4). ??
Please help .

The answer is Yes.
The PSU is core OMS patches (think console, incident rules, notifications, etc.) This gets applied to your OMS ORACLE_HOME (i.e. /u01/app/oracle/mw/oms)
The Plugin System Bundle is a compilation of all the latest plugin patch bundles (So for DB Plugin bundle it contains all the latest DB Plugin fixes). The system patch will apply required patches as necessary, skip what's not.
You can read more about the various patches here -
Patching 101 - The User Friendly Guide to Understanding EM Patches - Courtney Llamas
http://courtneyllamas.com/enterprise-manager-patching-faq/
I highly recommend this note as well. It will help identify exactly what should be applied to the entire EM env.
Applying Enterprise Manager 12c Recommended Patches (Doc ID 1664074.1)

I need to use Outlook Express to apply for jobs and I either don't have it but when I try to send an e-mail on Outlook Express, it won't go through and gives me an error report.....I really need to be able to use Outlook Express to apply for jobs. Help!

When I try to apply for job and when I try to e-mail my resume' and Outlook Express comes up to reply to on, I put in my information, etc but when I hit send, it doesn't go through and says? POP and then error report and doesn't go through.

I can't provide a solution with or without the error message, but without an error message, you are making everyone guess at what you see. I have no idea what you see, and I think someone who might be able to help you solve your problem would need to know what that message says. Is "Outlook Express" (Windows Live Mail) your default email processor, if not what is?

Folder Redirection policy is not applied to a user, when the server target is changed, but works after resetting the windows profile.

Folder Redirection policy is not applied to a user, when the server target is changed.
After server target is changed via group policy, when user login (roaming profile)first time, the the new server target has not been applied, instead it's pointing to the old folder redirection path.
But if we reset the windows profile (roaming ), the new folder redirection works, can you please specify a solutions that the new folder redirection works when the user login for the first time. so it reduce the time on resetting users profile.
it seems that we need to delete the old folder redirection path from the user profile (roaming user profile) via group policy or similar solutions..
Many Thanks

> But when the specific users login they all get the same error, it
Is the old server removed from the domain? Seems so - or some other
authentication related issue, hard to tell from here...
> seems that the roaming user profiles still keeps the old server details,
Yes - if you change redirection targets, FR moves content from old to
new, and only if this ends sucessfully, it will update the redirection
target.
Make the old redirection target accessible to the user and you'll be fine.
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Applying Support Pack taking Long time about 20 - 22 hrs per Patch.

Dear Gurus,
Recently we have upgraded from 4.7EE to ECC6.0, then we started applying Support Packs , and During the phase of IMPORT_PROPER it is taking time like any thing.. Near about 20 - 22 hrs .. for all the patches.
we have scheduled it in the Background. ... will there be any difference if we load them in Dialog.
tp, r3trans are working fine.
entries are there in PAT01,
Are there any Check points, Buffer size values that are needed to meet the Min Size values.
In general what should be the Shared Poool, Swap, Virtual Memory value,Export/import buffer sizes ?
How can we Improve this Import Phase ????
OS : Solaris 10 :- RAM = 8 GB, 2 CPU Processor,
DB : Oracle 10.2.0.2
SAP: ECC 6.0, Rel 700,
Kernel : 700 , patch level 146.
SPAM : patch level 23.
Gurus Pl suggest me ... to overcome this issue.
Thanks in advance.

Hi,
Thanks For your Prompt reply.
as u have mentioned to increase the SWAP space, we have increased by 2 GB, 2 days before only... But still the Loading of SAPKW70010 is going on. its all about 23 hrs till now.
No, I ve defined only one support pack in the Q.. that is SAPKW70010.
Pl any body help me in this regard.
Thank u.

Update connection shows pending or in progress, but patches were applied

I have two boxes, one which on the web shows in progress, and the other box, which on the web shows pending.
Still both are fully up to date, and the jobs the web shows as in progress/pending, have already been applied.
How/when would they become in sync ? Both boxes are checking in on a regular basis...
TIA...

Hi.
A script runs every week on the portal to clean up old updates, so any out of sync jobs should be re-synchronised within that time.

HT1386 I have an iPod 5, IOS 7.1 and Macook pro OS Maverick, i've updated my iTunes but when I want to sync my iPod it gets stuck on the 5th step "Waiting for changes to be applied" I let them at night for about 8 hours but the syncing hadn't done.

This problem has been happening for the past 3 months. Please help me.

Try:
"Waiting for changes to be applied": Apple Support Communities

HT1535 ting stuck on "Waiting for changes to be applied" does i keep trying to sync my iphone 4s but it wont finish the sync it keeps getting stuck on anyone know why ?

i keep trying to sync my iphone 4s but it wont finish the sync it keeps getting stuck on "Waiting for changes to be Applied" has anyone had a similar problem? and what should i do ?

I know that most of these posts were put up a little while ago
But.
I too had a similar problem and an "error" message (waiting for changes to be applied)
- my thoughts were:
Something to do with update to IOS 7.4
Corruption
Itunes software issue
After a LOT of research, I found a simple step that solved this issue for me.
I had been running my sync (pre - IOS 7.4) as automatic - see the options section under the summary tab
This can be viewed when you click on your device - right up the top you'll see tabs
SUMMARY / INFO / APPS / TONES / MUSIC / MOVIES / TV SHOWS / BOOKS / PHOTOS etc.
I changed my selection to manually manage music and videos and tried another sync
Wha La!
It began to copy over 700 songs that had not properly synced to my Ipad 2
BONUS: it then started to sync my videos again.
Hope this helps somebody.
It certainly made my life less frustrating
Downside: I have to MANUALLY manage - but it's better than all the hassles
NB: I don't know why this error occurs and I'm not sure this fix will work for everyone's issues but it can't hurt.

Each time I open Firefox, I get a popup window that says "It is strongly recommended that you apply this update for Firefox as soon as possible." But I have updated Firefox.

But I have updated Firefox. And if I tell it to do the update, it runs and runs and runs but nothing ever happens. It has a 'view more information about this update' link but the link does not work.

According to your user agent string you are not using the latest version of Firefox. It shows you have version 4.0, the latest version is 4.0.1
In the Help menu select "About Firefox", this should check for updates and then let you install the latest version.
If that does not work, try downloading the latest version from http://www.mozilla.com/ then installing it over your current version.

HT201209 I have redemed my itunes card for $25.00. This amount shows next to my name. I cannot figure out how to purchase items using this amount. When I try to apply this, it tells me the promotion has been redeemed but I have not been able to buy anythi

I have redeemed my itunes card for $25.00. This amount shows next to my account name. I chose songs from the itunes store and added to my wish list, but when I try to purchase these using my $25.00, it tells me this has already been redeemed. How do I buy songs and use my gift card to pay for them?

The amount is already credited to your account. Purchase something and it will use this balance.

Firefox update downloads an update, but when "Apply Update" is clicked, the softward update screen comes up but stays in "connecting to the update server" screen and never advances.

I am using Windows XP Professional and Mozilla Firefox Yahoo Edition, Yahoo 1.8

If you have problems with updating then easiest is to download the full version and uninstall the currently installed version.<br />
You may need to remove the Firefox program folder to do a clean install of the new version.
Do a clean (re-)install:
* Download a fresh Firefox copy and save the file to the desktop.
* Firefox 4.0.x: http://www.mozilla.com/en-US/firefox/all.html
* Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
* Do not remove personal data if you uninstall the current version.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder] and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.

Adobe Acrobat X Pro problem with 10.1.1 MSP

I have an AIP for Adobe Acrobat X Pro and applied the 10.1.1 MSP to it yesterday.
When I attempt to deploy through Group Policy, I receive:
Error 1334: The file 'acidviewobj.tx' cannot be installed because the file cannot be found in cabinet file Data1.cab
I expanded Data1.cab and the file is definitely not there.
I have built this package using the following:
Downloaded AcrobatPro_10_Web_WWEFD.exe (10.0.0)
Ran -nos_o -nos_ne commands to extract
Created MST using Customization Wizard X
Applied 10.1.1 MSP patch
Am I doing something wrong?

OK, figured it out.
My problem was that I was reusing AIPs, which Adobe discourages in their Enterprise Admin Guide.
For every quarterly update, you have to recreate the AIP, then apply the new quarterly patch. I don't feel this is adequately explained in the guide, but it's the only series of steps that worked for me.
So:
Create a new 10.0.0 AIP
msiexec /a C:\Acrobat\AcroPro.msi (where AcroPro.msi is an unmodified, original 10.0.0 package. Re-extract from the 10.0.0 installer if you only have patched versions left)
choose a unique subfolder for this AIP, something like C:\Acrobat\AIP_1011\
Patch this new AIP with your quarterly patch
msiexec /a C:\Acrobat\AIP_1011\AcroPro.msi /p AcrobatUpd1011.msp
Now you can push out installs with this new, patched AcroPro.msi in your new AIP folder
msiexec /i C:\Acrobat\AIP_1011\AcroPro.msi TRANSFORMS=C:\Acrobat\transform.mst REINSTALLMODE=vomus REINSTALL=all REBOOT=reallysuppress /qb
For more details, see: http://secunia.com/community/forum/thread/show/9808/update_10_10_will_not_install

How to apply Adobe Reader updates in correct sequence

I have read the update article listed below.
http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Reader_Update_QuickKey9.x.pdf
I find it confusing. I currently have the latest MSI of Adobe Reader 9.4 installed view group policy. I want to apply the latest update of 9.4.1. It sounds like I just need to apply each .msp file in order.
I guess it will all be clear if this question can be answered.
Do the quarterly updates have anything other then all of the out of cycle patches in them?
If they are just all of the out of cycle patches put together, then I won't be missing anything by just installing the .msp files in order. I am asking this because it says not to install quarterly updates over an .msp update.
Thanks,
Justin

The document is confusing indeed. Here's what to do:
Since you already have Adobe Reader 9.4 installed (distributed via GPO), all you need to do is create an administrative installation point (AIP) for version 9.4.1 so you can deploy it to upgrade version 9.4.
Here's an example:
- Copy AdbeRdr940_en_US.msi (the 42MB MSI installation file) and AdbeRdrUpd941_all_incr.msp (the 3.24MB patch) to C:\Temp folder
- Create a new subfolder under C:\Temp folder (let's call it AdbeRdr941)
- Run this command:
msiexec /a C:\Temp\AdbeRdr940_en_US.msi
- When prompted, specify target drive C:\Temp\AdbeRdr941
- When the above process completes, run the following command to slipstream version 9.4.1 into 9.4.0:
msiexec /a C:\Temp\AdbeRdr941\AdbeRdr940_en_US.msi /p C:\Temp\AdbeRdrUpd941_all_incr.msp
Note: the above AdbeRdr940_en_US.msi in folder C:\Temp\AdbeRdr941 file size is about 3.8MB
- When prompted, once again the target is C:\Temp\AdbeRdr941
When the process completes, copy C:\Temp\AdbeRdr941 folder to a shared network folder and create a new GPO to distribute the new version. Hope that helps.

Applying 9.1.2 to existing admin install point

I am trying to patch my existing admin install point of Adobe Reader 9.1.1 to 9.1.2 but get this error:
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on yoru computer and that you have the correct upgrade patch.
I get the same error on my PC when I double click the msp file
This is the msi log from when I tried to patch the existing admin install of 9.1.1:
MSI (c) (00:58) [16:18:02:876]: Final Patch Application Order:
MSI (c) (00:58) [16:18:02:876]: Other Patches:
MSI (c) (00:58) [16:18:02:876]: Unknown\Absent: {AC76BA86-7AD7-0000-2550-7A8C40000912} - C:\CustomInstalls\AdobeReader\patches\adobe912.msp
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\CustomInstalls\AdobeReader\acroread.msi
MSI (c) (00:58) [16:18:02:876]: Product: Adobe Reader 9.1.1 - Update '{AC76BA86-7AD7-0000-2550-7A8C40000912}' could not be installed. Error code 1642. Additional information is available in the log file c:\adobe.log.
MSI (c) (00:58) [16:18:02:923]: Product: Adobe Reader 9.1.1 -- Installation failed.
Any help is greatly appreciated.

I don't even know why I continue to use adobe products. Adobe software development is a joke. So are their UIs.
First, this forum crashed my FireFox 3.0.10 browser, twice. The second time, I figured out it was Adobe's fault. Why doesn't Adobe learn to script AJAX properly so it doesn't crash browsers? So here I am in IE8 typing a reply.
All of you guys were beating around the bush in regards to the "solution" to this problem. I have found a way to apply the patch and use an MST generated by the Adobe Customization Wizard. Granted, it would be much better if Adobe would just generate their patches correctly to begin with.
As you all have found out, you cannot create an MST using the ACW (Adobe Customization Wizard) and then use the following command
msiexec /i AcroRead.msi /p AdbeRdrUpd912_all_incr.msp /t
This will cause the aforementioned problem. Below is the proper sequence of events:
Make a backup copy of the 9.1.0 AcroRead.msi (just in case).
Run the following command: msiexec /a AcroRead.msi /p AdbeRdrUpd912_all_incr.msp This command will create an Administrative Install Point (AIP) in the directory you choose. I will place it in a directory called Patched The AcroRead.msi file will be rewritten and will be version 9.1.2 (check the Property table with ORCA and look at the value ProductVersion). In addition, the files that were in Data1.cab will be expanded and patched and are in the Patched folder I specified above. At this point, we no longer need the Data1.cab file. If you know how, you could compress all the files back into a cab and insert them back into the media table, but that is overly complicated and I forget how to do it successfully. In any event, the major benefit would be some space savings. If you had a lot of apps like this, it would be beneficial; but for one, not so much so.
Open AcroRead.msi with ACW. Make any changes you want for your installation. However, the following changes must be made or browser integration will be broken (per an earlier post in this thread):
Go to the Registry item in the left-hand menu.
Under the Destination Computer section, navigate to the following key: HKEY_CLASSES_ROOT\acrobat\DefaultIcon.
Modify the (Default) value to the following: [READER]AcroRd32.exe. NOTE: This only applies if you are installing Adobe Reader. If you are installing Acrobat, this may not apply, but I am not sure. YMMV.
This step was updated 10 July 2009 11:30:00 EST (GMT-05:00). If your are performing application virtualization, you will want to make te following changes to the MSI (via ORCA or ACW). I'm making these changes from ACW. The installer will fail during application sequencing during the installation of the Adobe Updater Manager (AUM). For virtualized applications, this component is unnecessary and should not be installed. Other sites lead you through a lengthy, risky process to eliminate the installation of the AUM. This step will eliminate the installation of AUM with two simple changes to the MSI.
In ACW, select the Direct Editor node from the left hand side.
Select the Feature table.
On the right side, locate the features named AUM and Updater. Note that the Level field for both features are 1. Change the Level field for both fields to be 200. Actually, any number greater than 100 will do, but 200 is a nice round number. Since the installer defaults to INSTALLLEVEL=100 (see the Property table), any feature with a Level value of 100 or less will be installed. Since we have now given these features an install level of 200, these features will not be installed. Generally, this tactic can be used on any component you wish not to have installed (for Adobe Reader and some other applcations with simple installers), such as AIR and Acrobat.com. Those are the only two changes that need to be made to not have AUM installed.
To make sure your users don't encounter an error while running Adobe Reader, make sure, in ACW, to uncheck the box Disable all updates under the Online and Acrobat.com Features section.
Save the package (in ACW, File->Save Package). This modifies the setup.ini file so that it will use the changes you just made (saved by default in AcroRead.mst).
I left my original instructions below, but marked as deleted. Please see step 5 below these deleted instructions. This is a new step. If you are performing application virtualization, you want to make the following changes to the MSI (via ORCA or ACW). I'm making these changes via ACW. The installer will fail during application squencing due to not being able to create to two certain registry keys. This is the easiest way that I can think of to get this to work.
Start your sequencing machine (in my case, a VM).
Install Adobe Reader 9.1.x (do not sequence, simply install).
Once installation completes, open the Registry Editor (assuming Windows Vista; if using WinXP or below, try RegEdt32.exe).
Browse to HKEY_CLASSES_ROOT\Installer\Win32Assemblies\Global
Double click the following entry (make sure you get the right one, there are two similar entries!): Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name Microsoft.VC80.CRT.txt
Back in the registry editor, double-click the following entry: policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Copy the value of the entry (on Vista, the value is already highlighted,simply right-click and choose Copy. Otherwise, right-click and choose Select All and then right-click again and choose Copy.).
Paste this value into Notepad. Save the file, making sure to select the Unicode encoding type from the Encoding drop-down list. Save it with the name policy.8.0.Microsoft.VC80.CRT.txt
Close the registry editor.
Reset your VM so it is clean for the sequencing (i.e. revert to a snapshot).
Back in the ACW, at the Registry portion, navigate to HKEY_CLASSES_ROOT.
Right-click HKEY_CLASSES_ROOT and selet New->Key. Name the new key Installer.
Right-click the Installer key and select New->Key again. Name the key Win32Assemblies.
Create a new key in Win32Assemblies called Global.
Select the Global key you just created.
On the right-side of the editor, right-click and choose New->Multi-String Value. Name the new value: Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762", processorArchitecture="x86".
Right-click the new value and select Modify
Open the text file Microsoft.VC80.CRT.txt you created aboe.
Press CTRL+A or Edit->Select All (in Notepad) and then press CTRL+C (or Edit->Copy).
Back in ACW, paste the value from the clipboard and click OK.
Now right-click the editor and choose New->Multi-String Value again. Name it policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc8b3b9a1e18e3b",type="win32-policy",versio n="8.0.50727.762",processorArchitecture="x86".
Open the policy.8.0.Microsoft.VC80.CRT.txt file created above.
Copy the file contents as the value of the new entry in the ACW.
Save the package. You should now be ready to install Adobe Reader via Setup.exe for sequencing.
Updated 10 July 2009 12:00:00 EST (GMT-05:00). We have one more step to perform just to clean things up bit. I'm going to create another AIP using the patched MSI and our newly created MST. However, this does not work quite as one would expect.
Run the following command: msiexec /a AcroRead.msi /t <Your_transform.mst>. I created this AIP in a folder called PatchedTransformed.
The above step created another AIP in the PatchedTransformed folder. What's different about this AIP compared to the one made at the beginning of this procedure is that the MSI file was copied to the PatchedTransformed folder as well. However, the MSI is not merged with the changes from the MST as I expected. There are two things you can do:
Modify the setup.ini file and add the following line to the [Product] section: CmdLine=TRANSFORMS="<Your_Transform.mst>", or
Use ORCA. Open your patched MSI in ORCA. Choose Transform->Apply Transform... and select the transform generated by the ACW. Then choose File->Save Transformed As... and give the transformed MSI a new name, e.g. Custom-AdobeReader-9.1.2.msi.
That's it. You now have a fully patched and modified Adobe Reader installer ready for installation or application virtualization.
At this point, you should have an MSI and MST. If you want, you can use ORCA to merge the MST into the MSI. If you're using Setup.exe, you're going to have to change th Setup.ini file.
To test that everything works, you can copy the files to a test directory and perform the following command: msiexec /a <AdobeReader.msi> [/t <Your_transform.mst>] Replace with the name of your MSI file and optionally, pass in your transform (definitely do this if you made a separate MST!). If all goes well, the installation should go well, too. During sequencing, you will still get an MSI installer error (actually, 2), number 1406, about not being able to write to two registry keys. These were the registry keys we added in the steps above. This does not happen on normal installatons.
Please also note that I don't know whether the roaming user profile problem menioned in http://kb2.adobe.com/cps/404/kb404597.html is fixed in version 9.1.2. It was not fixed as of 9.1.0.163. This is all posted AS-IS. YMMV.
UPDATE:
In case you don't know, I will share a bit of enlightenment I had with my procedure above. This specifically relates to application virtualization and sequencing Adobe Reader for MS App-V.
In step 4, I had you install Adobe Reader on a clean machine and obtain some registry information because otherwise, the installation may not be successful for virtualization. These steps are unneccessary. Here's why: you cannot "patch/upgrade" vitualized applications within the application itself. To patch/upgrade a virtual application, you have to use (in the case of MS App-V) the Application Virtualization Sequencing MMC to load the virtualized app, then run the upgrade/patch so that MS App-V can detect the changes and properly update the package. So what does this mean? Two things. First, whenever I use the ACW, under the Online and Acrobat.com Features section I always uncheck <b>Disable all updates</b>. However, checking this does not necessarily mean Adobe Reader does not install the Adobe Update Manager (AUM); in fact, it does install AUM, which is the feature that contains the component that attempts to write those registry entries and therefore, which is causing the error.
Therefore, the solution (and what should be step 4) is to disable the installation of AUM. Now some have posted at various sites how to disable the installation of AUM by deleting a whole bunch of stuff in the MSI. This is not necessary. The steps are outlined in the new step 4 above. This should resolve sequencing issues.
UPDATE 10 July 2009 12:00:00 EST (GMT-05:00) - Pertains to virtualizing Adobe Reader only.
This doesn't work for virtualizing the application. When importing the application into MS App-V Server Management Console, the application version is still 9.1.0.163 even though the splash screen says 9.1.2. I think that my assessment is correct because of two reasons: 1) I still got the MS VC++ Runtime error when using a normal user with a roaming profile which Adobe said the latest 9.1.1 release fixed (and hence 9.1.2) (the AppData folder included) and for which Adobe's solution is a joke; 2) When I installed my "patched" Reader (as a normal install) with AUM and proceeded to go to Help->Check for Updates, the 9.1.2 update appeared in the list of updates (again, even though the splash screen said it was version 9.1.2). Adobe has got to get their patchng correct!!!
For application virtualization, I'm going to recommend that you sequence the 9.1.0 version through to completion. Then, save the sequence and close it. Then re-open the sequence project for upgrade and applythe 9.1.2 patch. Whether you can use an ACW transform on the 9.1.0 installation and then patch, that's debatable. I sure hope so. If not, perhaps there's a way I can fudge it, namely, create an MST via ACW. Then, manually create an MST with the pertinent settings via ORCA and see if that works, instead.
Having said all that, I seriously doubt this works at all even for GPSI deployment. Sorry all. Will post again when I finally get this application to sequence. Hopefully, the same principles will apply to GPSI deployment.
Message was edited by: TTEConline on 10 July 2009 12:00:00 EST (GMT-05:00)

Applied 11.0.07 msp to 11.0.00 msi, but patched msi defective

Similar Messages

Maybe you are looking for