Good Day,
We are deploying Linked Clones to users using VMware. We have many users that have Acrobat Standard/Pro X and XI. Has anyone successfully thinapp'd Acrobat? If you did, how did you get past it not seeing the virtual printer?
Thank you,
Jennifer
Thanks for the reply brogers_1.
That page will no doubt serve others who stumble across this page.
Now, for the record, if one searches for "EULA" on the page you linked, it will take them to AdobeViewer (PDF Viewer Settings) page here: http://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/AdobeViewer.html?zoom_hi ghlight=EULA
And that confirms that Acrobat uses 'EULAAcceptedForBrowser'. Although the path isn't specified there, its presumably:
Since this is a 64-bit machine, here's an export of the former registry location:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\10.0\AdobeViewer]
"EULAAcceptedForBrowser"=dword:00000001
"bLaunched"=dword:00000001
[HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\10.0\AdobeViewer]
"EULAAcceptedForBrowser"=dword:00000001
"bLaunched"=dword:00000001
Despite having set that, when I launch Acrobat, I get the Software License Agreement screen.
To be sure I even went as far as adding the above settings to the 32-bit location, but the problem persists.
So, if I'm missing something, kindly point it out!
Thanks for the reply Sabian Zildjian.
While the information you shared will likely prove helpful to others who find this post, it doesn't quite fit the bill.
Again, good information here, but unless I'm missing something, this isn't going to work for the current situation.
See if this helps:
Ben
Admin Guide (“http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/aip.html) says:
The correct steps for AIP deployment are:
While opening PDF file in Acrobat Pro 9 under the VDI user environment, the Acrobat starts and automatically simultaneously closes without any error message.
Opening the same file in Acrobat reader becomes without any problems.
We use VDI based on Citrix XenDesktop v.7.5;
Hypervisor - VMWare vSphere v.5.0.1U1;
MS AD - W2k8R2
User Virtual machines based on OS Windows 7 (32 bit);
All User files are stored on file server, which are provided by storage EMC VNX5400 and accessible through CIFS protocol. We user folder redirection for user folders
Thanks again for the reply brogers_1 and many many thanks for the clarification!
To clarify, as I was not clear my last post: 'EULAAcceptedForBrowser' is in both the 32-bit and 64-bit (just to be sure) HKCU registry locations, yet I'm still prompted. Is this normal/expected behavior?
As for APTEE, I must be missing something critical. Maybe someone can help point that out?
There are two different versions of command line utility: one for CS5.5 and another for CS6.
What 'family' does Acrobat X Pro fall under: CS5/5.5 or CS6?
I'm using the LEID's from here http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/identify.html and here http://helpx.adobe.com/creative-cloud/packager/creative-cloud-licensing-identifiers.html.
Are those the correct LEID's for Acrobat X Pro?
I'm using the commands for adobe_prtk in the Adobe Provisioning Toolkit Enterprise Edition Tech Note for
The CS5 version doesn't have an option to suppress the EULA so I tried `adobe_prtk --tool=ReplaceSN --serialize=AcrobatPro-AS1-Win-GM --serial=super-long-serial-number` and that succeeded (return code 0) but I'm still prompted to accept the Adobe Software License Agreement. I don't see anything else in the documentation that suggests an EULA option for CS5/5.5.
The CS6 version just isn't working:
What am I doing wrong?
Better start at the beginning. What kind of license do you have?
Ben
I must have overlooked the bootstrapper method a few times and just never bothered with it. You were right though, it was pretty simple. I have both versions in my original post working that way now and both seem to install without a problem. Do you know where the log file is stored?
This is a volume license; has been deployed to the entire organization (about 2000 seats).
Standalone.
Check the values here:
HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\<version>\AdobeViewer\EULAAcceptedForBrowser
HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\<version>\AdobeViewer\bLaunched
HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\<version>\AVPrivate\bshowEULA
Should be 1, 1, 0.
Set them if not right and report back.
Ben
Thanks for this Ben.
I've never seen bshowEULA in the AVPrivate key before.
I imported the registry file:
Windows Registry Editor Version 5.00 [HKEU_CURRENT_USER\SOFTWARE\Adobe\Adobe Acrobat\10.0\AdobeViewer] "EULAAcceptedForBrowser"=dword:00000001 "bLaunched"=dword:00000001 [HKEU_CURRENT_USER\SOFTWARE\Adobe\Adobe Acrobat\10.0\AVPrivate] "bshowEULA"=dword:00000000
But the behavior is the same:
I tried being clever & renamed the exe to something else but instead of the EULA prompt I get the following popup:
[Title]Acrobat X Pro Adobe Application Manager, required to run your product, is missing or damaged. Please download a new copy of Adobe Application Manager from http://www.adobe.com/go/applicationmanager. [OK Button]
And when I acknowledge the dialog, it and Acrobat close.
I also found an odd bug where for some users on 10x see the EULA after the product has been installed for 36 hours. It would be interesting to see if updating several of your users to the latest version resolves the problem.
Well at least we're gradually narrowing this down. Before you try the steps below, take a look at existing blogs/threads on a similar issue and see if they are related: Adobe Acrobat asking to accept EULA after updating 10.1.0 | InterWorks, Inc.
Next:
Your statement that "The CS5 version doesn't have an option to suppress the EULA" is incorrect though. See http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/Adobe_Provisioni ng_Toolkit_Enterprise_Edition_…
However, the cmd line you used is right:
adobe_prtk --tool=EULA --leid=AcrobatPro-AS1-Win-GM --eulasuppress
Retry with the right aptee version.
I'm guessing it won't work. If so, do this:
If that info is correct, which I bet it is, install the product on a clean machine yourself. You don't need APTEE. . . . just use the Wizard and bootstrapper. It should succeed. If it doesn't, possibly you don't have the license you think you have. If it does, perhaps your predecessor serialized or installed incorrectly. What was the install method? Imaged OS, aip, boostrapper, other ????
If you think the base install is ok, then update to the latest version of 10.x and see if the problem goes away.
hth,
Ben
For what its worth I spent quite a bit researching & testing before I came here. I'm not an expert that knows everything about everything, but I'm pretty good at what I do and I dig deep. At the moment I'm three-quarters the way to China on this one. About two weeks ago I ran Process Monitor and I noticed that several files and registry keys get created/updated when you accept the EULA. I recorded all those registry updates and imported them elsewhere but that didn't help which leaves me to believe one or more of those files is key. I haven't explored whether or not it would be possible to copy the files from machine to machine, as I'm concerned there may be some sort of machine specific token that'll trigger the EULA prompt again because something in that file doesn't match some other generated value, but that's the absolute last step. Unfortunately I've spent a tremendous amount of time on this and have bigger fish to fry at the moment so I'm not sure when I can get to it.
I don't have everything but I'm late for an engagement so I'll give you what I have:
Again, I'm just walking into this place and from what I've seen, I do not believe Acrobat was packaged with the Customization Wizard. I know that I can re-package it with the EULA suppressed and even add the property at run-time to be sure (unnecessary though) and re-deploy. But that's the problem: we cannot re-deploy!
I opened a case with Adobe and had one of their guys jump in. He added bshowEULA to the Original key in the same path above - something I had not ever seen either - and that produced the same results I mentioned before: Opens fine, closes, EULA prompt. He then went for CS6 version of the prtk and when that wasn't working, got the CS5/5.5 version and tried to execute the same commands for version 6, which naturally failed. I sat back and watched for more than an hour and 15 minutes as he went through the same process I did; God bless this man. He was sort of at a loss at the end of our call. I asked him to go back to the Adobe guys to get their take on what he was seeing.
To me, this is either an Adobe problem (issue with prtk or Acrobat 10 or something else) or an impossible-to-fix situation. (Or it can be fixed but they'll never tell me/us how.)
Everyone's help has been appreciated and I'm open to other potential tests.
Yes, like I said earlier: I believe the reg pref and aptee solutions won't work for you as I believe you've done everything right. Since very few admins have ever seen this issue, there is either a bug or a bad install.
After you've checked that the "CR" filename and 36 hour bug issue is not in play, then my earlier question becomes more important:
Ben