Adobe Setup.exe Silent Install

[Ceumar Pee]

Hello friends,
I would like to distribute Adobe Reader DC via Workspace One and in order to do that I have to get the installer to start in the silent mode.
I have tried several commands like /s, /?, /help, /sAll, /qn, /quiet.... etc. and all of them just start the .Exe normally. I also found an Msi file but that one just has the 32 Bit Version.

So my question is, how do I start the .exe silently? Anyone could help me there?

Ah sorry I kind off explained it wrong.
So before I can deploy it via Workspace one I always test it out on my own PC via CMD.
So normally you can launch most .exe files in cmd silently with the /s command.
"setup.exe /s" for Adobe Acrobat Reader DC this doesnt work for some reason.
What I would like to know is how I can install Adobe Acobat Reader DC on my own PC via CMD silently.

Thanks for the help and again sorry for the mistake.

Additionally, if I am not mistaken, before you deploy any installtion package (.msi) remotely, it is easier if you customize an installation package into a new .msi taylored to the needs of your work environment.

Hey I got another question, is there any Installer for the free Version of Adobe Acrobat Reader DC? I am unable to find these.
-dc-downloads.html

This one only has Standard and Pro while the other one only has a simple Exe with no way of starting it silently.

Can anyone please advise what the silent switch is now to install adobe reader dc 15.023 for the exe as I cant find any msi installer and the usually silent switches are all failing. This s getting very tiresome as they seem to keep changing the switches from one release to another.

Looks like Adobe have reorganised their web site. Again. I do wish web site designers were given the job of keeping all old links working, FIRST, and then adding fabulous new stuff SECOND. Anyway, the enterprise deployment guide is here Acrobat-Reader Enterprise Toolkit Home and the Forum for discussing it is here: Enterprise Deployment (Acrobat and Reader)

I'm just going to through it out there... One of the key teachings for A+ Certification is read the manual. If you have looked at the documentation and still need assistance, then, go ask for help. I get some manuals are pretty thick, and even hard to understand... But this documentation flat out lists the switches and how to do everything pretty clear. One shouldn't be upset when asked to go read the manual especially when it is as clear as this one.

I must say I am surprised at the attitude of people who claim to be sysadmins but don't want to read a manual. To me the sysadmin is basically an ordinary user who is prepared to read manuals. Yeah, yeah, we're all busy, read the damn manual.

Must say... Came here looking for official documentation for our tech's repository, and I was shocked at the attitude from the company itself. The community, not the company, provided not only the solution, but also the correct documentation. Adobe was wrong, and then got mad that they didn't have it together. Perhaps I'll madate Foxit and Phantom, as your updated EULA which allows for the collection of PII is rubbing me wrong to begin with.

I have tried the following Set-up.exe --silent and it keeps popping up the Adobe Sign In Windows. So please share with me what is the silent switch to install this application silently?

Also I have a side question, if the Adobe Creative Cloud application is installed on users system who has No Admin Rights, will they be able to log into the application and download/install for example Acrobat without Admin Rights?

Thanks for the feedback, but the issue is with deploying the application. Even for test purpose when I run the Set-up.exe --silent, instead of installing the application, it launches the Sign-In Window. If the switch suppose to install silently, why is this happening?

So I have download the current version Adobe Creative Cloud off Adobe Website and I am packaging it up using PowerShell. Here is the command I am using in PowerShell Execute-Process -Path "Set-up.exe" -Parameters "--silent"

Thank you for the feedback that was the common answer that I have been getting while researching this topic online. Lol the only problem is that I don't have access to that tool. Reaching out to my internal contacts and see if I can get access to the application.

I know this post is coming up on a year old, but I ran into this issue as well. To silently install Adobe CC without having to use the Package Tool and get rid of the sign-in window, you can do the following:

I do this for my MDT deployment of Windows 10 Enterprise 1903. I don't have access to the Package Tool or Admin Console because I'm not part of the IT of my university that handles that. However, we do our own deployments within my entity and I need to install Adobe CC to save time with post-deployment configuration. I add this PowerShell script after the app installs. Run that script after every reboot as well.

@Joseph36504943n152 If you are an admin and have access to the admin console, kindly create a package which acts as an offline package and no need to sign in for the deployment.
Here is the help article for more details: -nul-packages.html

In Upload Job Options, the default Layer name value under Photoshop Options, is now Photoshop and Layer Name. Layers in the PSD file are uploaded as separate images.

The command that you use is for a basic MSI silent installation. However, the Adobe Dynamic Media Classic desktop app installer is an InstallScript MSI installer created using InstallShield. When you run the installer in record mode, any user interaction is recorded in a response file. This response file is then used for a silent installation as described in Running installations in silent mode.

Publish state (green indicator) of an asset is not reflected correctly.
In the browser user interface, a relogin to the UI was required to see the correct publish state of assets. In the desktop app, Adobe has introduced a Refresh icon in the toolbar, to the right of the Select None button. Tap the Refresh icon to see the latest status of all the assets on the given page. No relogon required as with the browser UI.

The OSID Generator application has been replaced by the ARHutility. The OSID Generator program is still supplied for developerswho have existing installation code. If you are developing a newinstaller, use ARH instead. The OSID Generator helps you discoverthe file path to an installed AIR application, given the applicationID and publisher ID of the application. See Using the OSID Generator application .

Once Adobe has approved your request to distribute AdobeAIR, you can include the stand-alone runtime installer file on individualsystems or on an intranet. For Windows, this installer is an EXEfile. For Mac OS, this is a DMG file. For Linux, this is an RPM,DEB, or BIN file. Administrative users can run this file to installAdobe AIR.

Download the bundled runtime installer from the runtimeredistribution download site. For Mac OS, this is a DMG file. ForWindows, this is a ZIP file. For Linux, this is a tar.bz2 archive.Extract the contents of the file to a directory, which this documentrefers to as the bundled runtime installer directory .

Rename the Adobe AIR installer to match your applicationname. For example, on Mac OS or Linux if your application is namedMyApp 2.0, rename the installer MyApp 2.0 Installer. On Windows,rename it MyApp 2.0 Installer.exe.

You can also call the AIR installer from a bootstrapper application.A bootstrapper application is a native application that managesmultiple processes (such as the installation of many files and applications).You can also use a bootstrapper application to manage the processof downloading all files and calling the appropriate installer commandswhen downloaded. The bootstrapper application can provide a customuser interface (for example giving users options to install other filesor applications). The ARH utility can be used to initiate most ofthe AIR-related tasks of the installation.

Generally, the AIR Installer presents its own user interfacewhile installing the runtime and the AIR application. The silent installation featurelets you install an application without presenting or interactingwith the AIR Installer interface.

Ifyou do not include the -eulaAccepted optionand Adobe AIR is installed during a silent installation, Adobe AIRwill later present the Adobe AIR end-user license agreement to eachuser of the machine. Users see the end-user license agreement (withthe option to accept it) upon first running an AIR application.

You cannot use the silent installer optionto update an installed AIR application. This is because theAIR installer cannot determine whether the version to be installedis newer than the installed version, and it would pose a security riskto downgrade the application.

An OSID, or operating system identifier , is a platform-specificidentifier for an installed application. The OSID Generator applicationreports the OSID of an AIR application. The OSID for an applicationis the same on every computer. The OSID generator uses the applicationID and either the publisher ID string, or, if a publisher ID isnot used, an empty string.

For AIR applications published before AIR 1.5.3, you can determinethe publisher ID by reading the contents of the publisherid file,which is in the META-INF/AIR directory in the installed AIR application.

On Mac OS, the OSID Generator application returns a bundle identifier.To find the application, pass the OSID as the inBundleID parameterof the LaunchServices LSFindApplicationForInfo() function.The object passed as the outAppURL parameter ofthe LSFindApplicationForInfo() function is setas a pointer to the application.

On Windows, the OSID Generator application returns a globallyunique identifier (GUID). This GUID is the upgrade GUID as wellas the component GUID of the component containing the main applicationexecutable. You can use these to locate the installed application:

c80f0f1006