用于安装Adobe Acrobat DC的自定义脚本

时间:2018-01-22 15:47:32

标签: batch-file scripting adobe acrobat

我认为这个问题在此之前没有被清楚地询问过。我一直在搜索谷歌,希望找到一个解决方案,但信息分散在网络上,很难及时拼凑起来(无论如何我都有有限的脚本知识)。所以,任何帮助都会受到赞赏,如果对我在这里想要完成的任何事情有任何疑问,请随时提出。我正在伸出援助之手,因为在创建比仅仅启动可执行文件更复杂的脚本时,我的知识非常有限。

我要做的是:

最终,我将使用ManageEngine Desktop Central将配置推送到我们的域/网络上的远程计算机。更简单的目标,我似乎无法取得成功,是获得一个批处理文件,就像运行它并成功安装Adobe Acrobat DC(不是免费的Adobe Reader应用程序)一样简单。我想要一个批处理文件来检查安装文件夹是否存在,如果是,请将其卸载以消除提示的消息,说明"错误1316.指定的帐户已存在。&#34 ;或任何其他会导致此安装错误的Acrobat痕迹。一旦安全措施到位以避免安装错误,例如前面提到的错误,它就会变得更加简单。之后,我只想安装Adobe Acrobat,然后我想删除快捷方式" Adob​​e Creative Cloud.lnk"来自所有用户'桌面,所以他们只看到" Adob​​e Acrobat DC"快捷方式。

UPDATE **

好的,在我发布原帖的时候,我试过把一个批处理文件放在一起,但它仍然无法正常工作。我正在使用第三方服务来部署此配置,因此联系Adobe将没有任何帮助。我不希望大多数人熟悉ManageEngine Desktop Central,但这就是我需要批处理文件的原因,Adobe支持无法帮助我。我现在拥有的是:

IF EXIST "C:\Program Files (x86)\Adobe\Acrobat DC" (
rmdir "C:\Program Files (x86)\Adobe\Acrobat DC" 
goto :install
) ELSE (
ECHO Acrobat Folder Doesn't Exist goto :install
)


:install

S:\Adobe_CC\AcrobatPro\AcrobatDC\AdobeAcrobatDC\Build\setup.exe --silent



IF /I "%ERRORLEVEL%" NEQ "0" (
ECHO execution failed
)

1 个答案:

答案 0 :(得分:0)

The answer here is a bit different, due to the fact most of the work is done in ManageEngine Desktop Central. What fixed the issue, in my case, was downloading the Creative Cloud Packager (CCPLauncher.exe) and advancing through the wizard. I disabled the end user being able to install updates or install other products. The only switches left on were the ones to allow my IT department to remotely manage and push out updates. I then ran through with defaults and selected only Adobe Acrobat DC [Pro] (the Adobe Creative Cloud Application Manager will be grayed out and cannot be unselected).

After the package was created and placed in my network share that contains all of my software executables, I opened and logged into Desktop Central. The first step was to create the Package in DTC. You do this by clicking Software Deployment tab, then click "+ Add Package" and select your operating system. Once you've done that, click "Create Package manually." After that, select the radio that fits the file type you are working with, in my case, I selected "MSIEXEC/EXE/ISS/Command." Then name your package and select the current license type (I selected Commerical). After that, in the field labeled "MSI File Name with Network path*:", enter the path of the executable/MSI file including the file and extension. Under Installation Enter the same path, if the same path applies here, which in most cases it will, but leave the file name and extension off. This is just for the folder where the installer resides. Then click the Add Package button below. At the top, I then clicked Configurations then on the left pane, Configuration. I chose to "Install/Uninstall Software" and selected Computer. I ran through the usual and named the configuration, then selected the "EXE" radio button and find the "Package" you just made and be sure the drop down list below that is set to Install Completely (or another option depending what your file is). For "Apply Deployment Policy:" select the correct one; I selected DC Default Policy. Below that, select the User/Computers you want to apply this configuration to on your network and click "Deploy" or "Deploy Immediately" and you are done. I made a Security Group in Active Directory and added machines to that and then in DTC, chose to deploy it to the Group that I named "Adobe Acrobat DC Pro" in AD. My configuration deployed successfully and I was able to recreate that successful deployment on every new computer I added to the group in AD. Hopefully there is someone out there that ran into the same problem with Desktop Central that now has somewhat of an answer. If this method does not work for you, hopefully you can find success with your issue.

相关问题