The GUIDs should be different. The ETK documents the differences: Identifying Existing Installs — Enterprise Administration Guide
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
I went to the ENU_GUID on both machines and they are Identical for Acrobat DC Pro and Standard
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\2015\Installer
ENU_GUID {AC76BA86-1033-FFFF-7760-0E0F06755100}
I do agree that Acrobat XI this did work and I was using it to verify. I did notice that when I used 7zip to extract the installers for the customization tool that both the standard and pro had the AcroPro.msi. In Acrobat XI the standard version had AcroStan.msi. I just re-downloaded Acrobat DC Standard and extracted the file again. The standard still has the AcroPro.msi inside it. I think this is why the GUIDs are the same for Acrobat DC.
The Acrobat DC title bar does state Pro and Standard correctly.
Product Download from the Adobe LWS website:
Adobe Acrobat Standard DC 2015 Installer for Windows
Extract with 7zip and it has the AcroPro.msi inside
↧
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
Pre-Deployment Planning — Enterprise Administration Guide States "
Installing Acrobat DC Standard¶
Acrobat DC products delivered via an ESD EXE download provide one installer that is used for both Acrobat Standard and Professional. The serial number you use determines which product is installed. What’s important to note is that when you extract the Acrobat ESD EXE (Acrobat_DC_Web_WWMUI.exe or Acrobat_2015_Web_WWMUI.exe), you’ll see AcroPro.msi in the output folder. This is the correct behavior. Simply remember to use AcroPro.msi in any command line scripts.
Note
Existing scripts that use AcroStan.msi should be updated."
Both Acrobat DC Pro and Standard have KEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\2015\Installer ENU_GUID {AC76BA86-1033-FFFF-7760-0E0F06755100}
On the laptop with DC standard installed C:\ProgramData\regid.1986-12.com.adobe\regid.1986-12.com.adobe_V7{}AcrobatESR-12-Win-GM-e n_US.swidtag
On the laptop with DC Pro installed C:\ProgramData\regid.1986-12.com.adobe\ is empty
Your guide does not have any information regarding Acrobat DC. Please explain how to verify if Acrobat DC Pro or standard is installed. or explain how to get the ENU_GUID for standard to start with {AC76BA86-1033-FFFF-BA7E.
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
Identifying Existing Installs — Enterprise Administration Guide states
| product type | The product using hexadecimal and telephone keypad indicators as follows:
|
Please correct the Acrobat DC standard installer to use "BA7E" it currently is using "7760"
Product Download from the Adobe LWS website: Adobe Acrobat Standard DC 2015 Installer for Windows
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
It has been a week now and your link does not resolve my issue. I have updated the form 3 more times without any follow up. Please help or I will have to escalate this issue.
↧
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
Hi Eric,
Your post led to the discovery of a bug. Docs will be updated with the following:
"For DC products, it is a current known issue that after deployment there is no way to identify whether Acrobat Professional or Standard has been installed. For both products, the SWIDs and GUIDs are identical. A fix for this issue is planned for a future release."
Ben
↧
Re: How to determine Which Acrobat DC version is installed? Pro or Std
Thank you for letting me know.
↧
Re: Sign In Required when using Classic/2015 installer
bump?
How do I pre-activate a volume license serial number?
↧
Re: Sign In Required when using Classic/2015 installer
Verify you're using the MST you created with the right name and the correct capitalization. You may want to cut and paste the cmd line you used.
Ben
↧
↧
Re: Sign In Required when using Classic/2015 installer
msiexec.exe /i "AcroPro.msi" ALLUSERS=1 /qn /norestart /log output.log TRANSFORMS="AcroPro.mst"
↧
Re: Sign In Required when using Classic/2015 installer
In your first post, you created myInstall.mst. Did you also create AcroPro.mst thinking that the name mattered?
↧
Re: Sign In Required when using Classic/2015 installer
When I clicked "save" in the wizard, it created AcroPro.mst and when I did Generate Transform, it asked me for a filename so I called it myInstall.mst.
I tried using both mst files on separate installs, and they both installed successfully, but both of them required the sign-in on first run.
After a few attempts, I deleted and started with fresh source files, and am only using AcroPro.mst currently.
↧
Re: Sign In Required when using Classic/2015 installer
Ok. The name doesn't matter as long as you point to the one you created. Your cmd looks right so I'm at a loss. You could double check the serial is right (right track), but what you said you did is correct.
Perhaps you can collect and examine the logs: http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/troubleshoot.html
Ben
↧
↧
Re: Sign In Required when using Classic/2015 installer
I made sure to copy/paste the serial
What about the ABCPY.ini file?
;***************************************************************
;OEM Installation Options
;***************************************************************
[OEM Install]
ISX_SERIALNUMBER=
USERNAME=
COMPANYNAME=
INSTALLDIR=
does that ISX_SERIALNUMBER line need to be populated?
thanks, Ben
-M
↧
Re: Sign In Required when using Classic/2015 installer
Sign-in at launch is mandatory until you click "Grant Offline exception" button next serial number field in CW. When you click this button your machine must be connected to internet.
↧
Re: Sign In Required when using Classic/2015 installer
You can disable sign in through the Grant Offline Exception button in the Personalization Options screen. You can then apply that mst.
Thanks,
↧
Re: Sign In Required when using Classic/2015 installer
Thank you kashifMohd and vdobhal that did the trick. I had tried that earlier but looking in the oobelib.log I see there were errors trying to grant the exception, but at the bottom of the log with this morning's timestamp it returned code 0. I just pushed out the package to a test computer and it did not ask me for a sign-in this time.
Many thanks to you both
↧
↧
Need help: Portfolio does not open in my browsers
I view a portfolio that opens in IE (v.10.0) but the same portfolio does not open in Chrome (v.42.0) or Firefox (v.37.0.1)-- instead only the Cover Sheet appears. I have Adobe Reader 11.0 and Acrobat XI Pro installed. Are there any special browser settings that I need to set? Thank you.
↧
Adobe Pro 11.0.10 patch has expired code signing cert
I can not patch my Adobe 11.0.0 installation to 11.0.10 using the automated process.
I manually downloaded 11.0.10 from this location: http://ardownload.adobe.com/pub/adobe/acrobat/win/11.x/11.0.10/misc/AcrobatUpd11010.msp
The MD5 of this MSP per my own check is 4cb5979f49bc5112731da0cce036ac66, while the SHA1 is 8b4130df183f69ab77f9f6748f2e535be5d3336e.
This download is signed with a code signing certificate issued by Symantec Class 3 Extended Validation Code Signing CA. The signature has a thumbprint of 111aa9b0c6da43594bb2ad3052567c12ef8d9607. This certificate expires later this year.
During the install I receive an error because it extracts a file to c:\config.msi which is code signed with a code signing certificate issued by Verisign Class 3 Code Signing 2010 CA. The certificate has a thumbprint of 70d566df844f3e2d9ac31e518256e7b6f2de9272. The certificate expired 9/20/2013. Today is 5/4/2015. The install fails on this file.
The certificate thumbprint for the Verisign Class 3 Code Signing 2010 CA intermediate authority is 495847a93187cfb8c71f840cb7b41497ad95c64f. This itself is signed by VeriSign Class 3 Public Primary Certification Authority - G5 having a thumbprint of 4eb6d578499b1ccf5f581ead56be3d9b6744a5e5.
The failing file with the invalid code signing certificate has an MD5 checksum of bddf785233f9d2b3ae43d72822fb74bc and SHA1 of 78e7e15c8baea3c6befc7336d153254777912bd4. This appears to be amtlib.dll which is part of Adobe AMT Licensing. These hashes are available on services such as Virus Total and Herd Protect.
Would it be possible for Adobe to release a 11.0.11 patch that has this issue fixed?
Thank you,
Edwin Davidson.
↧
Is it supported by Adobe to create an App-V package from Acrobat 12?
I know there are many recipes in the web to create an App-V package from Acrobat 10 or 11, but is this officially supported by Adobe?
I found this for Acrobat 11: App-V Deployment — Enterprise Administration Guide
It´s stated explicitly there that Acrobat is not supported, only the Reader.
Regards
tuxhater
↧