I have some questions I hope Adobe can answer. First let me give a bit of a background. We have a 1591 serial number and every year we get hundreds of new computers that get Acrobat and CC programs (that I made with the packager) deployed. We use a MDT/WDS/SCCM combination to deploy our image as well as our application packages.
Last year, the process was to deploy Adobe via the Exception Deployer BEFORE installing the CC package I made. Is it my understanding the process has changed again? The latest documentation is outdated and consists of very confusing verbiage with one document saying to use the Exception Deployer pre CC (last years way), another saying to use setup.exe in Build folder and another part telling us to install via Acro.msi deep in Exceptions folder? Can someone just simply explain how I am going to roll this guy out to hundreds of machines?
The first part of MDT installs my customized image of Win7x64SP1, joins domain, ect, ect, ect and starts installing Applications.
Application 1 : msiexec /i Adobe.msi /qn /norestart - This installs my CC package
Application 2: msiexec /i AcroPro.msi /qn /norestart - This will install Acrobat DC?
1. Is this my process? Adobe CC Suite first followed by Acrobat DC?
2. Are my command lines correct? One of the documentation shows a boatload of extra commands that someone expressed don't even work anymore in another thread.
3. I do not need any users getting any "Enter serial number for Acrobat", a EULA, OR an Adobe Sign On. I don't want them getting ANYTHING except opening up Acrobat or Photoshop/Illustrator/Ect
I will do some extensive testing tomorrow, but I want to be prepared. Thanks.
