Looking for help.  I soooo need help.  I'm trying to get Adobe Pro XI deployed/distributed to 400 staff.  I have installed the Wizard, Created a TRANSFORM and have a MST but with no background in IT, I have no idea what is stalling it out or what is missing.  The manual installation is no longer an option with the tools available I just need to know how to fix.  So with no IT background at all (Legal Secretary) I am reaching out to see if anyone can help?  
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
You haven't said what deployment system you're using but, whatever it is, use this as your command line:

MSIExec /I "[path to MSI]" TRANSFORMS="[path to MST] /qn /l*v "[path to a log file]"

Make sure the word "TRANSFORMS" is in all upper-case.

For the failures, open the log file and search for the text "return value 3". The half-dozen or so lines above that will show you what failed. If you can't work out what that might be, post those lines here and we'll do our best to help. By the way, after you've pasted the text, select it and then apply the 'Code' style: it makes the post easier to read.
Answered 10/02/2015 by: VBScab
Red Belt

  • what do I need to put in the [path to a log file]
    I am trying to use both Scripting or Managed Installations through K1000 Appliance 6.3 (or at least one of the two whichever I can get to work first) with the best accuracy
  • And thank you for replying. I really do appreciate it.
  • These are the variations I am working with presently: (I am just going through one at a time to see if I can get it to run)
    msiexec /i "AcroPro.msi" /qn

    msiexec /i "AcroPro.msi" EULA_ACCEPT=YES /qn

    msiexec /i "AcroPro.msi" /qb

    msiexec /i "AcroPro.msi" /q

    msiexec /i <C:\Downloads\AcroPro.msi> LANG_LIST=en_US TRANSFORMS=1033.mst /qb

    msiexec /i <C:\Downloads\AcroPro.msi> LANG_LIST=en_US TRANSFORMS=1033.mst EULA_ACCEPT=YES /qn

    msiexec /i <C:\ProgramFiles\AcroPro.msi> LANG_LIST=en_US TRANSFORMS=1033.mst EULA_ACCEPT=YES /qn

    msiexec /i <path to AcroPro.msi> LANG_LIST=en_US TRANSFORMS=<1033.mst> /qb

    msiexec /i <path to AcroPro.msi> LANG_LIST=en_US TRANSFORMS=<1033.mst> /qn

    msiexec /i "C:\Program Files(x86)\Adobe\AcroPro.msi" LANG_LIST=en_US TRANSFORMS=1033.mst /qn
  • This was the error I was receiving

    2015-10-01 13:19:15: Alert not enabled, moving to next phase....
    2015-10-01 13:19:20: Sending script script.bat to client....
    2015-10-01 13:19:44: Script sent
    2015-10-01 13:19:44: Executing script....
    2015-10-01 13:20:06: Error 1619 received while executing script
Please log in to comment

Answers

1

Here's the command we're using for Reader DC, but the syntax is the same to your version:

msiexec /i AcroRead.msi TRANSFORMS=AcroRead.mst /qb- /l*v "c:\windows\logs\Acrobat Reader DC 15.007.20033 Install.log"

If you run the command form the folder containing the MSI & MST, you don't need to specify the path.  If your path(s) contain spaces, you'll need to supply the path & filename surrounded by quotes, similar to the log file above.

Answered 10/02/2015 by: vjaneczko
Seventh Degree Black Belt

  • Thank you for getting back to me. I would like to reduce the number of steps and folders created when running if at all possible. I will be testing again today.
  • I am still getting the 1619 error.
  • Ok, have moved from 1619 error to this:

    2015-10-09 11:20:32: Alert not enabled, moving to next phase....
    2015-10-09 11:20:33: Sending script script.bat to client....
    2015-10-09 11:20:57: Script sent
    2015-10-09 11:20:57: Executing script....
    2015-10-09 11:45:58: The last step timed out after no response from the client. Please try again.
    2015-10-09 11:45:58: Error -1 received while executing script
Please log in to comment
0
>what do I need to put in the [path to a log file
Put in a path to a writable area. I tend to use %SystemRoot%\TEMP and a suitable name for the file, e.g. %SystemRoot%\TEMP\Install_Acrobat_Pro_XI.LOG

The additions you have on the command line could go in your transform, in the 'Property' table. I wouldn't bother with the language transform (1033.MST).
Answered 10/04/2015 by: VBScab
Red Belt

  • Thank you. I am hoping to reduce the number of steps and folders created. I appreciate your help.
Please log in to comment
0
Hi

First off all you have to get Adobe Customization Wizard XI  find it here Adobe Customization Wizard XI
This will help you to create acrostan.mst
Remember to add language MST

Install like this
msiexec /i acrostan.msi TRANSFORMS=acrostan.mst REBOOT=ReallySuppress /L* C:\acroxi.log /qn

Install with elevated rights, if problem try to install manuel in Admin CMD and use PSEXEC.exe -i -s cmd from symantec tools to test in NT System kontekst deployment logfile will tell what is missing.
Regards Sweede

Answered 10/05/2015 by: Sweede
Second Degree Green Belt

Please log in to comment
0
>language transform
I have never yet had to use any vendor's language transforms.

If you're advising the OP to do so, you should have included its addition in your command line.
Answered 10/05/2015 by: VBScab
Red Belt

  • Language MST is applied when you create the acrostan.mst using the special Adobe tuner program
Please log in to comment
0
Not unless it writes out a new MSI it doesn't. And even if it did, I think most of us could manage without 1033.MST (which the OP specifies on the sample command lines) since all it does is remove the property 'InstallshieldTempProp'.
Answered 10/05/2015 by: VBScab
Red Belt

  • I agree no need for OP to apply language MST but I did im Danish you have the option to do so. And It wont change the original MSI.
Please log in to comment
0
1619 means that MSIExec couldn't find the MSI.

Change your command line, prefixing the MSI and MST names with '%~dp0' (without the quote marks) and enclose the whole path and that prefix in speech marks:

MSIExec /I "%~dp0blah.MSI" TRANSFORMS="%~dp0blah.MST" [remainer of command line here]


Answered 10/06/2015 by: VBScab
Red Belt

  • Have now moved from 1619 error to this:
    2015-10-09 11:20:32: Alert not enabled, moving to next phase....
    2015-10-09 11:20:33: Sending script script.bat to client....
    2015-10-09 11:20:57: Script sent
    2015-10-09 11:20:57: Executing script....
    2015-10-09 11:45:58: The last step timed out after no response from the client. Please try again.
    2015-10-09 11:45:58: Error -1 received while executing script
Please log in to comment
0
Also, make sure that .Net Framework 4.5 is installed on all workstations or it will not deploy.
Answered 10/07/2015 by: FSU Facilities
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share