Quantcast
Channel: Adobe Community: Message List - Enterprise Deployment (Acrobat and Reader)
Viewing all 6853 articles
Browse latest View live

Acrobat Standard 2017, Auswertung der MST bei der Installation schlägt fehl

$
0
0

Hallo,

 

wir verteilen als IT-Dienstleister für den öffentlichen Dienst in unsere Umgebung Acrobat Standard u. Professional 2017. Es handelt sich um ca. 220 Clients insgesamt. Bei vielen muss das Update noch von der Version XI vorgenommen werden.

 

Das Deployment wird mit SCCM 2007 auf Windows 7 durchgeführt. Das Paket besteht aus den Installationdateien der Version 1701130051 + dem aktuellen Patch der Version 1701130099. Die Konfiguration der Installation wird mit dem "Acrobat Customization Wizard DC", also per MST, vorgenommen.

 

Die Classic-Track Lizensierung wird mit einer Mengenlizenz über die MST mit der Offline Exception durchgeführt. Die Ausführung der Installation im Paket geschieht über ein Powershell-Script.

 

Seit ein paar Versionen haben wir das Problem das die Erstinstallation im Ersatz des Acrobat Readers unvollständig durchgeführt wird. Es werden anscheinend die Anpassungen der MST nicht mehr angewendet. Zum Beispiel ist die Lizensierung nicht angewendet und die Anpassung der "Online Services and Features" werden komplett ignoriert. Es macht den Anschein das die MST komplett ignoriert wird.

Das ist die Syntax unserer Installation: msiexec.exe /I AcroPro.msi TRANSFORM=AcroStan.mst EULA_ACCEPT=YES DISABLEDESKTOPSHORTCUT=1 /qn /l*v C:\Windows\Temp\AcroStd_2017_17.008.30051.log

 

Bis zur Version 70 hat alles funktioniert. Dies waren die Versionen der Umstellung von Acrobat XI. Danach wurden im wesentlichen nur die Updates durchgeführt, also die Installation des MSP der jeweiligen Version.

Aktuell steht de Umstellung der restlichen XI-Versionen an die wir so natürlich nicht durchführen können.

Im Moment behelfen wir uns in dem wir die funktionierende Version installieren und danach das aktuelle Update durchführen. Das ist ein Workaround und nur in Einzelfällen durchführbar.

 

Ich habe schon einiges versucht. In der Regel habe ich das bisherige Paket genommen und nur die MSP ausgetauscht.

Für die aktuelle Version habe ich die kompletten Sourcen der Installationsdateien von der Adobe-Seite heruntergeladen und die bisherigen damit ersetzt.

Ich habe die MST neu erstellt.

Ich habe die Installation des alten Paketes genommen und mit der neuen MST kombiniert.

 

All dies hat nicht zum Erfolg geführt.

Im Moment bin ich völlig ratlos was die Ursache betrifft und wie ich weiter vorgehen kann.


AcroPDF.dll

$
0
0

In a VS 2017 Winforms VB application dealing with package designs, predominatly based on PDF files, I felt the need to provide a preview of those files in several points along the workflow.
At first I used a third-party component, but in some cases the designers created one or more hidden layers in the PDF files and they were all made visble by the component, obviously creating some confusion.
In the begining of April I decided to use the Adobe ActiveX control instead, with good results since then ( AcroPDF.dll, which in my Windows 10 machine the Acrobat Reader DC installer placed in C:\Program Files (x86)\Common Files\Adobe\Acrobat\ActiveX ).
However, yesterday I had to make a slight change in a form ( not related with PDF files ), deployed the application, and a few hours later some users reported an exception in several forms using the PDF viewer ( "Could not load file or assembly 'AxInterop.AcroPDFLib', Version=1.0.0.0, Culture=neutral"... ).
At first I thought I could have inadvertently modified the list of deployed files, but both AxInterop.AcroPDFLib.dll.deploy and Interop.AcroPDFLib.dll.deploy were included, and besides I had no problems with the PDF viewer in my computer.
The only significant note I can remember is that there was an apparently large security update of Acrobat Reader DC a few days earlier ( and at least two or three VS updates since the last time I had to deploy a new version of my application ). Besides that, the customer's computers run Windows 8, but I until now it didn't seem to matter.

An extensive Google search on the issue failed to provide any clue, so at this point I can't even identify the source of the problem, much less a solution for it.
Does anybody know what might be going on ?
Thanks.

Acrobat 2017 Xenap login for first time user

$
0
0

During logon to Xenapp for first time (roaming profile and local profile does not exist)  user is presented for couple of minutes

during logon with following as seen in attachment.How to fix it?

acobat.jpg

Re: Acrobat 2017 Xenap login for first time user

Re: Where is the full package offline installer so I can test deployment of Acrobat Pro DC subscription?

$
0
0

You're right, no exe there. And I Googled it and also found myself wandering around various links.

 

So I pinged an expert, and was given this link:  Download Acrobat DC installer for Enterprise term or VIP license

 

That page links to the same URL support gave you which you pasted into your second post above: http://trials3.adobe.com/AdobeProducts/APRO/Acrobat_HelpX/win32/Acrobat_DC_Web_WWMUI.exe

http://trials3.adobe.com/AdobeProducts/APRO/Acrobat_HelpX/win32/Acrobat_DC_Web_WWMUI.exe

 

Why doesn't that work for you?

Re: Expected behaviour when using Acrobat in Citrix

$
0
0

meenakshin83966505,

 

Thank you for contacting us. This is an automated response confirming the receipt of your ticket. Our team will get back to you as soon as possible. When replying, please make sure that the ticket ID is kept in the subject so that we can track your replies.

 

     Ticket ID: OFF-464-56924

     Subject: Reply marked as helpful on Expected behaviour when using Acrobat in Citrix

     Department: Support Desk

     Type: Incident

     Status: Open

     Priority: Normal

 

You can check the status of or update this ticket online at: https://support.core.vc/index.php?/Tickets/Ticket/View/OFF-464-56924

 

Kind regards,

CORE Support

 

 

--

 

Latest News:

 

1. https://support.core.vc/index.php?/News/NewsItem/View/22/password-recovery-self-service

2. https://support.core.vc/index.php?/News/NewsItem/View/21/latest-firefox-update-causes-issu e-launching-desktop

3. https://support.core.vc/index.php?/News/NewsItem/View/20/desktop-logon-portal

4. https://support.core.vc/index.php?/News/NewsItem/View/19/notification-fake-xero-invoices-01-09-2017

5. https://support.core.vc/index.php?/News/NewsItem/View/18/new-spam-control-add-in-for-outlo ok

Re: Acrobat DC Customization Wizard Links to FTP are dead. FTP site now requires a logon? Adobe can you fix your links?

$
0
0

Hi there,

 

I'm getting a timeout or no response when I try the ftp site. It just sits doesn't actually download!

adobecap.PNG

Re: Acrobat DC Customization Wizard Links to FTP are dead. FTP site now requires a logon? Adobe can you fix your links?

$
0
0

Works for me. Downloaded several items from different dirs.


Re: Where is the full package offline installer so I can test deployment of Acrobat Pro DC subscription?

$
0
0

It doesn't work for me because the day to do this, was last Thursday...

Confirmation from yourself that the link from the CS was correct didn't come until Saturday.

Its now Monday...

 

The Users, they don't care, they just want their stuff to work so they can do their jobs.

I don't have the time to spend searching the internet for hints to the correct installer like its a "Choose Your Own Adventure" story.

 

But this isn't about me...  its not my website, its not my product.

 

 

This is Adobes website, and when the Staff at Adobe cant find the link for a staple product like Acrobat... that's a pretty good indication that there is something fundamentally wrong with the website and the information linking and dissemination process, don't you agree?

 

 

Feel free to dismiss the thread, or maybe... take the not so subtle hint that perhaps... just perhaps, the real issue lays with Adobe and that some change is required.

Acrobat Standard/Pro 2017, evaluation of TRANSFORM (MST) during installation fails

$
0
0

Hello,

 

we deploy Acrobat Standard and professional as IT service provider for the public service in our environment 2017. It's about 220 clients in total. For many, the update must be made by the version XI.

 

 

The deployment is performed with SCCM 2007 on Windows 7. The package now  consists of the installation files of version 1701130051 + the current patch version 1701130099. The installation is configured with the "Acrobat Customization Wizard DC", so via MST. The classic track licensing is performed with a volume license with the option "Grant Offline Exception".

The installation in the package happens via a PowerShell script. This is the syntax of our basic installation: msiexec.exe /i AcroPro.msi transform = AcroStan.mst EULA_ACCEPT = YES DISABLEDESKTOPSHORTCUT = 1 /qn / l * v C:\Windows\Temp\AcroStd_2017_17.008.30051.log The next stept installs the patch.

 

Since a few versions, we have the problem of the initial installation was incompletely performed. It the adjustments of the MST are no longer applied apparently. For example, the licensing is not applied and the adjustment of the '"online services and features" are completely ignored. It makes it seem that the MST is completely ignored. The behaviour already exists in the basic installation.

After the first start of the installed product the licensing procedure starts. It starts with the login with the Adobe-ID. Cause we use the classic track we have no seperate user IDs.

 

Everything worked up to version 17011.300.70. These were the versions we have used for the update of Acrobat XI in our surrounding. Then essentially only the updates were carried out, so the installation of MSP. This does not change the licensing of the installed product.

The conversion of the remaining Acrobat XI versions we currently cannot carry out with the current behaiour.

 

At the moment we install the functioning version and then perform the latest update. This is a workaround and meaningful only in exceptional cases.

 

I've tried quite a bit. Usually, I have used the previous package and only replaced the MSP.

I downloaded the complete sources of the installation files with the version 17.008.30051 from the Adobe site and rebuild the package with it.

I've recreated the MST.

I have used the installation sources of the old package and combined with the new MST.

I have tried the installation string also without SCCM and powershell in a console.

 

All this does not led to success.

At the moment, I'm completely at a loss what is the cause and how I can proceed.

Re: Error 1603 with Acrobat installer created by Creative Cloud Packager

$
0
0

Nobody has an idea about solving the issue ?

Re: Error 1603 with Acrobat installer created by Creative Cloud Packager

Re: Error 1603 with Acrobat installer created by Creative Cloud Packager

Re: AcroPDF.dll

pdfpreviewhandler Acrobat DC Server 2016 RDS prevent deleting .pdf

$
0
0

A customer of ours uses Server 2016 Remote Desktop Server.
They have Adobe Acrobat DC en Adobe Acrobat Reader installed on the Remote Desktop Server.

If Acrobat DC is the default PDF application:

When you turn the previewpane on in the Windows Explorer and you 'preview' a PDF file located on a networkshare the preview prevents you from deleting the file.
You can't delete the file because the file is in use by 'Windows Explorer'.

 

If Acrobat Reader is the default PDF application the preview works fine and you are able to delete the PDF-file.

This isn't a workable workaround for the customer because they edit +/- 200/300 PDF files a day.

 

We tried replacing the PDFPrevHndlr.dll from Acrobat DC with the PDFPrevHndlr.dll from AcrobatReader and from a clean Acrobat DC installation on Windows 10 (which doesn't experianced the problem). But the other PDFPrevHndlr.dll won't work with the installation they complete break the pdf-previewer.

 

Is there any way to resolve this issue for the customer?

 

Greetings,

 

Jorg Kouwijzer


Looking to install Adobe DC Standard on Virtual server

$
0
0

I am curently looking at installing Adobe DC Standard on a virtual server and have a few questions.

 

1) This remote desktop environment is used by multiple users however not all of the users will require Adobe Standard is it possible to only license a portion of the total users.

 

2) There is a possibility in the future that there will be a pool of remote desktops. multiple remote desktops (same environment) that users will be load balanced between. do i need to purchase a license for each user for each server? or can the one license be used regardless of what server they connect to?

 

Thanks,

Re: Looking to install Adobe DC Standard on Virtual server

Re: Error 1603 with Acrobat installer created by Creative Cloud Packager

Re: Deploy DC Reader with error Error 1334. the file 'natives_blob.bin' cannot be installed

$
0
0

Same issue here since months.  Help, Adobe.  Please.  Make this deployment process obvious. 

Re: Error 1603 with Acrobat installer created by Creative Cloud Packager

$
0
0

That log was for the CCP's MSI created file.   While it does give output it's not the output that I expected or really wanted.  [Edit] I was expecting the MSI log for AcroPro.msi's log and not the CCP's created MSI file. 

 

I have a suggestion that you are free to use or not use.  This is definitely a workaround suggestion but try going into the Acrobat folder and finding the files that look similar to this:

 

Screen Shot 2018-09-06 at 10.19.40 AM.png

 

Use the command line for Setup.exe syntax:

 

Setup.exe /sl "[LangCode]" /sALL 

Viewing all 6853 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>