I tried deploying the 10.1.3 in the way I successfully deployed 1.1 and 1.2, but kept getting errors about a transform on install. I tried installing the patched MSI without any transforms, but still got the error. Then I tried running the download straight from the enterprise distribution link, but that didn't work either, even on a computer without Adobe Reader installed.
I think there might be something wrong with the enterprise distribution.
Once installed (Offline Exception added for License), Acrobat XI Pro starts nicely without issues. But when I right click a website and selects "Convert Webpage to PDF" I get a "Trial version. Try for 30 days or purchase license now".
How do I fix this before deploying the software in SCCM?
I've used the Adobe Customization WIzard XI to package Acrobat XI Pro with the following changes from "Blank"
Personlization Options:
* Username: Blank
* Organization: My Organization
* Serial Number: 1118-xxxx-xxxx-xxxx-xxxx-xxxx (Offline Exception granted)
* EULA Option: Checked
Installation Options:
* Default viewer for PDF files: Make Acrobat the defauilt PDF viewer
* Remove Previous: Checked
* Remove all versions of Reader: Unchecked
* Enable Optimization: Checked
* Enable Caching: Checked
* Run Installation: Unattended
* If reboot required: Suppress reboot
* Application Languages: English (United States)
* Acrobat MUI Languages: en_US
Features: Everything included
Files and Folders: No changes
Registry: Removed Acrobat Assistant 8.0 and Adobe ARM from CurrentVersion\Run
Shortcuts: Desktop shortcuts removed
Everything else down to Online and Adobe Services are standard
Online and Adobe online services:
* Disable product updates: Checked
* Load trusted root: Enable & Ask before Installing
* Disable registration: Checked
* When launching PDF in Internet Explorer, prompt user with Open/Save: Checked
* Disable Help > Digital Editions: Unchecked
* Disable Product Improvement Program: Checked
* Disable Viewing of PDF with Ads for Adobe PDF: Unchecked
* Disable all Adobe online services based on workflows and entry points: Checked
Everything else is untouched.
Generated transform file and deployed to test clients. All are reporting the Rightclick, Convert Webpage with a Trial dialog showing up. They can use Acrobat and create PDFs from within the application without problems. When in word, I get an error "Adobe Acrobat is not activated. Cannot create the PDF file".
I would think that granting the offline exception should have made this unnecessary?
My Enterprise PC does not allow regular user to have write access to C:\ProgramData folder. I ran ProcMon and found that the error is due to an ACCESS_DENIED to CreateFile(). The process is requesting write access to a temp file in C:\ProgramData\Adobe\SLStore. Can Adobe patch the program to work with only READ access to C:\ProgramData? Or change the write access path to some folders in C:\Users\%USERNAME%\AppData?
I can't seem to find anything out about the next yearly update of Adobe Reader. There are supposed to be quarterly and yearly updates for Reader, but Adobe don't seem to be sticking to the schedule.
I need the next full MSI package to come out so that I can get updates out to my office PCs, as I have never been able to get AIPs to work but I can't seem to find anything on it, even beta.
I understand this is the suggested method of disabling the "Display PDF in browser" is http://helpx.adobe.com/acrobat/using/display-pdf-browser-acrobat-xi.html However we would like to know if there is an API or something we can simply remove from the workstation to disable "Display PDF in browser".
Thanks in advance for any assistance you might be able to offer.
Ed
I beg your pardon if this "after deployment" question is posted in the wrong forum.
I really need some help with this one.. What am I missing here?
In Acrobat Pro 11.0.01 you configure display PDF in browser (yes/no) by enabling or disabling a add-on in the browser. I want my end users to be able to select how they wish to view PDF:s. According to http://helpx.adobe.com/acrobat/using/display-pdf-browser-acrobat-xi.html there should be a add-on called "Adobe PDF Reader".
This add-on is missing on all my deployments so far!
For troubleshooting purposes I have replicated my problems when I install the product from original media without my transform and the results are the same. Am I missing some setting in the Customization Toolkit Wizard in order for the add-on to be installed properly?
On two completely clean and fully patched machines (XP x86 and Win 7 x64, english OS) I install Acrobat Pro 11.0 (english) and apply 11.0.01 patch.
In IE I select Tools -> Manage add-ons -> Show: All add-ons.
Adobe Acrobat Create PDF from Selection
Adobe Acrobat Create PDF Toolbar Helper
Adobe PDF Link Helper
Adobe Acrobat Create PDF Toolbar
There is no "Adobe PDF Reader", yet PDF:s are displayed in IE.
If I disable the four add-ons above, PDF is still displayed in IE.
If I launch IE in safe mode without add-ons ("C:\Program Files (x86)\Internet Explorer\iexplore.exe" -extoff), PDF is still displayed in IE.
I terminate all visible Adobe processes (Acrotray, ARM for instance), PDF is still displayed inline in IE.
C:\Program Files (x86)\Common Files\Adobe\Acrobat\ActiveX\AcroPDF.dll is installed, if I rename this dll (using a SYSTEM account) PDF is displayed in Acrobat Pro XI.
How do I/end users control if PDF are to be displayed inline in IE or not *after deployment*??
(In Firefox everything works as expected and I can enable or disable the Adobe Acrobat plugin to control how PDF:s are displayed)
Regards
Hello,
we deploy Adobe Reader on approx. 60 Clients and 18 Terminalservers through GPO. This worked fine since version 10.x.
Today I was downloading AdbeRdrUpd11003.msp and try to slipstream it into our 11.0.2 AIP. It failed stating "Another version of this product is already installed..."
I was using msiexec /a <path2msi> /p <path2msp> like i did many times before.
Lastly i was able to sucesssfully slipstream the 11.0.03-msp into a newly created AIP with 11.0.0.
However, I cannot install it on any Client. The installation abort with "Another version of this product...". In the logfile i found Errorcode 1638 which does just mean the same.
Does anyone know whats the cause of this behavior resp. what i have to look for?
The relavent parts in the msi/mst seems to be OK, except the MinVersions in the upgrade table which were set to 10.0.03.
Changing the values to 11.0.02 didn't help, still the same error.
Thanks in advance
H.
As I've been doing for the past year and some since taking over deploying Flash/Reader etc here, I tried rolling out 11.0.03 starting yesterday. Followed the same procedure I always have which so far has not failed to work: dowload the offline install from the link provided when I signed up, extract the MSI, create an AIP, patch the MSI, create my Transform using Customization Wizard, start testing. However, this latest version fails. I thought maybe I had a corrupt download, went through all of the previous steps 2 more times. I continually get an erro 1638: Another version of this product is already installed. Yes, another version is... 11.0.02. Is there some issue with this version where it is incapable of installing over the top of previous Reader XI installs and needs a clean install? I have successfully run it over no Reader being installed, and Reader X.
. === Verbose logging started: 05/16/2013 09:45:48 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (A8:18) [09:45:48:866]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (A8:18) [09:45:48:866]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (A8:3C) [09:45:48:874]: Resetting cached policy values
MSI (c) (A8:3C) [09:45:48:874]: Machine policy value 'Debug' is 0
MSI (c) (A8:3C) [09:45:48:874]: ******* RunEngine:
******* Product: acroread11003.msi
******* Action:
******* CommandLine: **********
MSI (c) (A8:3C) [09:45:48:875]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A8:3C) [09:45:48:875]: Grabbed execution mutex.
MSI (c) (A8:3C) [09:45:48:884]: Cloaking enabled.
MSI (c) (A8:3C) [09:45:48:884]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (A8:3C) [09:45:48:888]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [09:45:48:892]: Running installation inside multi-package transaction C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi
MSI (s) (2C:4C) [09:45:48:892]: Grabbed execution mutex.
MSI (s) (2C:90) [09:45:48:894]: Resetting cached policy values
MSI (s) (2C:90) [09:45:48:894]: Machine policy value 'Debug' is 0
MSI (s) (2C:90) [09:45:48:894]: ******* RunEngine:
******* Product: C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi
******* Action:
******* CommandLine: **********
MSI (s) (2C:90) [09:45:48:894]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:90) [09:45:48:909]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0
MSI (s) (2C:90) [09:45:48:909]: SRSetRestorePoint skipped for this transaction.
MSI (s) (2C:90) [09:45:48:911]: File will have security applied from OpCode.
MSI (s) (2C:90) [09:45:48:917]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi' against software restriction policy
MSI (s) (2C:90) [09:45:48:917]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (2C:90) [09:45:48:917]: SOFTWARE RESTRICTION POLICY: C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi is not digitally signed
MSI (s) (2C:90) [09:45:48:919]: SOFTWARE RESTRICTION POLICY: C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (2C:90) [09:45:48:919]: End dialog not enabled
MSI (s) (2C:90) [09:45:48:919]: Original package ==> C:\Users\mt3449\Desktop\AdobeReader11003\AIP\acroread11003.msi
MSI (s) (2C:90) [09:45:48:919]: Package we're running from ==> C:\Windows\Installer\42d498.msi
MSI (s) (2C:90) [09:45:48:922]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (2C:90) [09:45:48:922]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (2C:90) [09:45:48:922]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (2C:90) [09:45:48:922]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1033-7B44-AB0000000001}'.
MSI (s) (2C:90) [09:45:48:922]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:90) [09:45:48:926]: MSCOREE not loaded loading copy from system32
MSI (s) (2C:90) [09:45:48:928]: Machine policy value 'DisablePatch' is 0
MSI (s) (2C:90) [09:45:48:928]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (2C:90) [09:45:48:928]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (2C:90) [09:45:48:928]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (2C:90) [09:45:48:929]: Looking for file transform: C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst
MSI (s) (2C:90) [09:45:48:930]: File will have security applied from OpCode.
MSI (s) (2C:90) [09:45:48:932]: Original transform ==> C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst
MSI (s) (2C:90) [09:45:48:932]: Transform we're running from ==> C:\Windows\Installer\42d499.mst
MSI (s) (2C:90) [09:45:48:933]: SOFTWARE RESTRICTION POLICY: Verifying transform --> 'C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst' against software restriction policy
MSI (s) (2C:90) [09:45:48:933]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (2C:90) [09:45:48:933]: SOFTWARE RESTRICTION POLICY: C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst is not digitally signed
MSI (s) (2C:90) [09:45:48:934]: SOFTWARE RESTRICTION POLICY: C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst is permitted to run at the 'unrestricted' authorization level.
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2205 2: 3: Patch
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (2C:90) [09:45:48:934]: TRANSFORM: Applying regular transform to database.
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AppId 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (2C:90) [09:45:48:934]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Component 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MIME 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: LaunchCondition 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiDigitalCertificate 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Registry 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: UpgradeCode 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: Verb 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiPatchCertificate 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ISComponentExtended 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ISCustomActionReference 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ISSetupFile 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: LockRegPermissions 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: LockFilePermissions 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: ISDistribution 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: AppsInUse 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: BackupAndRestoreRegistry 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DefragFiles 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DeleteComponents 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DeleteFiles 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DeleteProducts 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: DeleteRegistry 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: TransferRegistry 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: AppsInUseEx 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
MSI (s) (2C:90) [09:45:48:935]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1033-7B44-AB0000000001}'.
MSI (s) (2C:90) [09:45:48:935]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:90) [09:45:48:935]: Transforms are not secure.
MSI (s) (2C:90) [09:45:48:935]: Transforming table Property.
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Reader.log'.
MSI (s) (2C:90) [09:45:48:936]: Command Line: TRANSFORMS=acroread.mst" CURRENTDIRECTORY=C:\Users\mt3449\Desktop\AdobeReader11003\AIP CLIENTUILEVEL=2 CLIENTPROCESSID=1704
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{8017784A-94A5-40AD-AE48-D46040E2A00C}'.
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding TRANSFORMS property. Its value is 'C:\Windows\Installer\{AC76BA86-7AD7-1033-7B44-AB0000000001}\reader.mst'.
MSI (s) (2C:90) [09:45:48:936]: Product Code passed to Engine.Initialize: ''
MSI (s) (2C:90) [09:45:48:936]: Product Code from property table before transforms: '{AC76BA86-7AD7-1033-7B44-AB0000000001}'
MSI (s) (2C:90) [09:45:48:936]: Product Code from property table after transforms: '{AC76BA86-7AD7-1033-7B44-AB0000000001}'
MSI (s) (2C:90) [09:45:48:936]: Product registered: entering maintenance mode
MSI (s) (2C:90) [09:45:48:936]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (2C:90) [09:45:48:936]: Product {AC76BA86-7AD7-1033-7B44-AB0000000001} is admin assigned: LocalSystem owns the publish key.
MSI (s) (2C:90) [09:45:48:936]: Product {AC76BA86-7AD7-1033-7B44-AB0000000001} is managed.
MSI (s) (2C:90) [09:45:48:936]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (2C:90) [09:45:48:936]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (2C:90) [09:45:48:936]: Specifed source is not already in a list.
MSI (s) (2C:90) [09:45:48:936]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:90) [09:45:48:936]: Machine policy value 'DisableBrowse' is 0
MSI (s) (2C:90) [09:45:48:936]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (2C:90) [09:45:48:936]: Adding new sources is allowed.
MSI (s) (2C:90) [09:45:48:936]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (2C:90) [09:45:48:937]: Note: 1: 1729
MSI (s) (2C:90) [09:45:48:937]: Product: Adobe Reader XI (11.0.03) -- Configuration failed.
MSI (s) (2C:90) [09:45:48:937]: Windows Installer reconfigured the product. Product Name: Adobe Reader XI (11.0.03). Product Version: 11.0.03. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Reconfiguration success or error status: 1638.
MSI (s) (2C:90) [09:45:48:938]: Attempting to delete file C:\Windows\Installer\42d499.mst
MSI (s) (2C:90) [09:45:48:940]: MainEngineThread is returning 1638
MSI (s) (2C:4C) [09:45:48:940]: No System Restore sequence number for this installation.
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
{AC76BA86-7AD7-1033-7B44-AB0000000001}
MSI (s) (2C:4C) [09:45:48:940]: User policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [09:45:48:941]: Machine policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [09:45:48:941]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [09:45:48:941]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [09:45:48:942]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [09:45:48:942]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (2C:4C) [09:45:48:942]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (2C:4C) [09:45:48:942]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (2C:4C) [09:45:48:942]: Restoring environment variables
MSI (c) (A8:3C) [09:45:48:943]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (A8:3C) [09:45:48:944]: MainEngineThread is returning 1638
=== Verbose logging stopped: 05/16/2013 09:45:48 ===
Hi
My company has currently set new UAC security settings but we have an issue where we are not able to update Adobe products because UAC stops it, UAC also does not prompt for elevation it just out right blocks updates.
We really need a way to either allow the updater to run/install past the UAC restrictions OR find a way to distribute adobe updates via WSUS if it's possible
Thanks
Hello members,
I am looking to deploy the latest version of Reader to our workstations both during OS build and also on existing machines.
I have successfully created a custom install using the Adobe Customization Wizard I’m leaning towards the use of the .exe / bootstrapper
Double clicking the exe works just fine on my lab computers however getting this to work over a SCCM (2012) deployment is proving troublesome
As SCCM admins would know the SCCM client downloads the content to C:\windows\ccmcache\randomfoldername
SCCM then runs the command specified in the deployment you created, I appear to be having issues with the exe not knowing to look in the same directory for the MST MSP and setup.ini file,Being a randomly generating folder name this can’t be specified in the deployment unless I change the ‘Installation start in’ option
Sometimes the install is ignoring my custom install settings (disable updates and online features etc)
My setup.ini contains:
[Startup]
RequireMSI=3.0
CmdLine=/sall /rs
[Product]
msi=AcroRead.msi
PATCH=AdbeRdrUpd11004.msp
CmdLine=TRANSFORMS="CompanyName.mst"
[MSI Updater]
Path=http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.0/misc/WindowsInstaller-KB893803-v2 -x86.exe
Am I missing something simple ?
A few months back I made the change to my DOCICON.xml file to enable the integration with Acrobat and Sharepoint to prompt the user to "Check Out and Open" PDF files in document libraries in Sharepoint 2013. It worked fine and as expected.
After applying CU's to Sharepoint up to October 2013, this function seems to have gone away. I verified that the DOCICON.xml settings are correct. Ex: <Mapping Key="pdf" Value="pdficon_small.png" OpenControl="AdobeAcrobat.OpenDocuments" />
I can still get the "check out..." prompt if I open the document libraries with Windows Explorer, but not when PDF's are opened directly on Sharepoint. I have a support case opened with Microsoft, but they seem to point the problem at Adobe.
I have verified that the AcroPDF.dll is on each client and is enabled in IE. The PDF files open with Acrobat, but the check out prompt is not showing up unless I open the Sharepoint library with Explorer.
Have tried different Acrobat versions (10 and 11) as well as different IE versions (9,10,11)..etc...and Windows 7 or Windows 8, but the check out function does not seem to work when opening PDF's directly from Sharepoint 2013
The purpose of this thread is to identify EASIEST way to create/obtain an MSI file of the LATEST VERSION of Acrobat Reader (currently 10.1.3 as of 7/19/2012) to be deployed via GPO. I am not concerned with customizations of Reader settings as I have accomplished this already using Group Policy.
It sounds so easy, but I have found it to be quite frustrating and extremely time consuming to figure this out.
Here's what I have so far:
To download the full installer from Adobe, you must first apply on Adobe's website to distribute Reader:
http://www.adobe.com/products/reader/rdr_distribution1.html
Once you submit the request, a short time later you'll get an e-mail with a link to download the full exe file of reader 10.1.3.
Here's a link that explains how to extract an MSI from this exe:
http://blogs.adobe.com/dmcmahon/2010/06/16/how-to-extract-an-msi-file-from-the-exe-
Even with following those steps, I do not end up with an MSI file which will install 10.1.3.
To try another route:
There is also an Adobe FTP site. If you navigate down into the Reader 10.1.0 folder there is an MSI file. Good - but it's the old version.
You would think that if you navigate into the 10.1.3 folder there would be an MSI there as well.
Unfortunately there is not. However, there is an MSP file found in the misc folder:
I have tried several methods that are supposed to combine the MSP file with the MSI file - they have not worked.
I have also tried several methods of modifying MSI files, and using the Adobe Cusomization wizard downloadable here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4950
I am unable to end up with a deployable MSI file for Reader 10.1.3.
It's amazing that it's so complicated to deploy the latest version of Adobe Reader to my users.
Does anyone have a comprehensive answer to this simple problem? I do not want a link to a document with 20 pages explaining the theory of MSP files. I am looking for a concise, step by step method to obtain an MSI for 10.1.3 quickly and easily.
Thanks!
Hi we recently updated Reader9.3.1 to Reader9.3.2
(Reader9.3.1 worked just fine)
This new issue pops up saying
"(Security block) Acrobat does not allow connection to:
http://www.webpage.gov/link/filename.pdf " <------------as an example, not a real address
The way we got to 9.3.2:
We used the working Reader9.3.1 and slipstreamed that with the new UpdateFile9.3.2.msp
running command: msixec /a reader9.3.1.msi /p UpdateFile9.3.2.msp
Thanks,
bob
acrotray.exe is using TSR resources in Windows 7. What are my options?
Hi All,
i need some help with this freaky Acrobat Reader X version.
We have currently ~1000 computers with different old versions of AR (form 6 to 9)
We need to upgrade to 10.0.1 version all PC's
Will use SCCM for distributing the package.
OK... everything here seems good but ... a lot of problems and erros appear.
First we've installed on test group of 10 pc's the AR 10.0.0
all users start complainig that they can't open the pdf's from our file servers.
Solution - bring the patch 10.0.1
After that all users start complaining that they can't print - Windows Error - Acrobat need to be closed !
Solution - Protection mode disabled.
My questions :
1. How can I distribute both the Package of Acrobat and the update together with SCCM
All my tries and reaings failed !!!
i've try different methods and no success
msiexec /i /q \\server\d$\Workstation Baseline\AcrobatReaderX\AcroRead.msi TRANSFORMS="AcroRead.mst" PATCH=\\server\d$\Workstation Baseline\AcrobatReaderX\adbeRdrUpd1001_Tier1.msp
this do not work for me This is in SCCM program
2. How can i disable through Adobe Wizard the Protection Mode ?
I know how to do it manually but is not acceptable this way - i can't communicate with 1000 users to do this manually
I know how to disable it from registry with GPO , but i can't disable it before installation, also i can't disable it on all PC's after installation, because it will take several days to complete for all pc's and this "hole" of some days will stop the work of our end-users.
Any fresh ideia is wellcome. Also any help
Thanks
We ordered a lot of new Optiplex 3010's for business. We also specified Adobe Acrobat XI which only comes through via Dell Digital Delivery now. So we do not get a disc or a serial number card anymore.
We set up a model computer exactly how we want it. You know, run through all the nag prompts, import a script to customize pinned applications to the taskbar, accept first time license agreements, ensure all the software we need is installed and configured. Then after this is done we remove it from the domain again and as a local admin we go through everything one last time to make sure things are custom the way we want. We then take an image using Acronis (boot to it from network). Then we go back in and run the Windows 7 sysprep utility that points to an xml file with things like copy profile = true, and others.
After it shuts down we image it again so we have an after image. Now we just use Acronis and put this image on all of our Dell Optiplex 3010's. When its booted the only thing it asks for is computer name, and then once its booted we join it to our domain. Prior to deployment we run appwiz.cpl, go down to Microsoft Office 2010 and hit "Change" and choose enter a product key, and then we enter the product key from the computer that it is replacing.
Now today I got an e-mail from someone with one of these new computers along with a screen shot from Adobe Acrobat XI (which remember is via Dell digital delivery and we have no serial cards or installation media anymore).
It says The serial number 1016xxxxxxxxxxxxxxxxx is already in use by the maximum allowed computers. You need to deactivate another computer within 25 days to use this products.Then there are two options:
Well since Dell did not distribute Adobe key cards, where would I get another serial number from? I imagine the one presented was used in the original image. However Dell digital delivery verifies by the service tag that the PC is authorized for Adobe and it should have taken care of all of this. So what am I to do here? In the future if we do not choose this method and instead go through another retailer for Adobe Acrobat XI Standard, then we will get a CD and key card for each computer we deploy, although its much more expensive... were talking $150 vs the $50 add on for it when customizing the Dell computer.
So thanks for any input. I realize this could be an Dell problem (so I posted over there as well), however this was installed via Dell Digital Delivery and Dell did not send out any keys.
We legitimately paid for this. In the previous round of Optiplex 3010's when we could order Acrobat X standard, we were given a key card. After sysprep I would run a script (AAMEE was installed in the default image) to change the serial number via the command line. But now Acrobat XI is different and I'm not sure what to do. Dell doesn't even give us an option for Adobe X anymore, or else I would have just used that version which worked fine.
We order Dell computers with Acrobat X Std and Office 2010 pre-installed. We do not get media, but we do get the serial numbers on cards with each PC. We create an image of a PC the way we want it with our most commonly used programs, settings and customization. We use Windows 7 sysprep with a unattended.xml answer file and some scripts when we are done. When this is finished we image the machine and deploy it on others so everything starts with the same configuration.When the PC is freshly imaged all we have to do is name it (we use our asset tag) and join it to the domain. Then we go into appwiz.cpl (add/remove programs) and click on Microsoft Office 2010, then the change button then choose enter a product key. We enter the key from the card that shipped with the physical computer.
Now I don’t see a place to do this for Adobe. We are legit and pay extra per PC to Dell so we get the software license code on a card, as we do with Office. I just want to ensure that everything is kosher.
I know that sometimes after a PC is deployed, in a few days or weeks we may get a tech support call where the user has an Adobe Acrobat duplicate license detected screen. We remote on and just enter the new serial number from the proper key card we got from Dell. But I want to head this off at the pass here and ensure the licensing is working at deployment so we don’t have to take these calls a few days or weeks later.
Any idea where the change product key is? I tried the change function in appwiz.cpl but it looked like it would just take me to a reinstaller. It’s important that it does not mess with settings because I need one of our servers in the enhanced security trusted site area, as well as Topaz.GemPlus in our default signing, and a few other settings that carried over from us customizing it under the local Administrator and then setting the CopyProfile=True flag in unattended.xml answer file prior to sysprep.
So I have downloaded the most recent version of Adobe Reader 11.0.2. I extraced the contents and edited the MSI using the Adobe Customization Wizard.
My issue is this. When I install using the command msiexec /i file.msi TRANSFORMS=file.mst /qn It will install Adobe Reader 11.0.0 with all of the customizations that were created in the .mst file. Why is it not installing 11.0.2? If I run the .exe file it installs 11.0.2 but if I run the .msi file it only installs version 11.0.0. Any help would be great. Thanks.
The following error is produced in Acrobat when trying to click version history documents in SharePoint 2010. "The URL you have provided could not be reached. Please verify that the URL is correct and that the network location is reachable." The revision of the document is reachable, but through typical HTTP via a web browser...but not through the SharePoint <==> Acrobat X Pro COM object magic that works fine for currently checked out documents. Please see inserted image. Thoughts on a fix?
