You can also add some other parameters, like a. With the parameter /v you can send parameters to msiexec, but its important that there is no space between this parameter and the parameters for msiexec. You have to change your command line to setup.exe /s /v/qn (with no space between '/v' and '/qn'). resilience, so I'm trying everything I can think of. zap file and using the msiexec cmd line arguments, which may be barking entirely up the wrong tree, but this app is chafing my. I've found the msiexec command line (MsiExec.exe /i AcroPro.msi /qb- ISX_SERIALNUMBER=%ISX_SERIALNUM% TRANSFORMS=AcroPro.mst EULA_ACCEPT=YES USERNAME='%USERNAME%' COMPANYNAME='%COMPANYNAME%' INSTALLDIR='%INSTALLDIR%' ) under the faq for this package on this website, but that won't help me in the GPO arena, will it? When creating the GPO, I find no place to input cmd line arguments (and actually just discovered the place to specifiy the. How can I force this app to run silently while using W2K GPO deployment? The only difference seems to be that the Company name, user name, and serial number fields are already populated, so a portion of the. When I go to add/remove as my test user and select Install for the app, I get all the installation dialogue, just as I would were I running the install from cd.

mst file, publish the app to my test user. I then save the complete package to another location. I've used Installshield Tuner 7.0 and input our serial number, user name, and company name, as well as accepted the EULA, and done some other small modifications, including adding the setup.exe /s /v /qn line (also tried just using setup.exe /qn, as a poster on Adobe's msg boards suggested, with no luck).

Working on preparing Acrobat 7.0 Pro for my users, and cannot seem to get the install to run in silent mode.

Adobe acrobat professional 7.0