Skip to main content
JackFetter
JackFetter
Inspiring
August 13, 2018
Answered

Adobe Customization Wizard allows users to click "cancel" during install!

  • August 13, 2018
  • 1 reply
  • 7348 views

This is pretty simple, it is determined by whatever switches are being passed by the Adobe Setup.exe but the way it is now, when you create a custom install using the Adobe Customization Wizard and run Acrobat DC via Setup.exe, it allows the user to cancel install, as the "cancel" dialog is there and displayed to the user. If Adobe would just pass the "/QB-!" switches to the MSI for the basic UI, it would also suppress this ability but I don't think there is a way for me to change this programatically. Having it run hidden is not a good workaround either as we try and never run hidden when possible, too many users mistake slow response for "needing a reboot". Is there any workaround for this?!

Jack

This topic has been closed for replies.
Correct answer JackFetter

My current CmdLine looks like this:

CmdLine=/spb /rs /smur

Please review and let me know what needs to be removed, since I don't have /sAll (I have the Customization Wizard setup for "Unattended, only a progress bar")...

Regards,

Jack


JackFetter  wrote

My current CmdLine looks like this:

CmdLine=/spb /rs /smur

Please review and let me know what needs to be removed, since I don't have /sAll (I have the Customization Wizard setup for "Unattended, only a progress bar")...

Regards,

Jack

It was right there, after I typed "Unattended, only a progress bar", it sounds a lot like "Silent, no progress bar", or "/spb" ;-)

Simply remove "/spb" from the [Startup] CmdLine and add "/QB-!" to the [Product] CmdLine!

Thank you for the help, much appreciated!

Jack

1 reply

EnterpriseHelp
EnterpriseHelp
Inspiring
August 13, 2018

Here you go: Windows cmd line and msiexec — Enterprise Administration Guide

Refer to the /q switches.

JackFetter
JackFetterAuthor
Inspiring
August 13, 2018

I understand the /q switches well and I see the line that reads "When using the bootstrapper, command line parameters can be sent to msiexec from Setup.ini using /msi" but I'd like to see the proper syntax as I already tried a few variations before posting this (it just seemed like this might work when I looked at the Setup.ini. IN fact the existing Setup.ini has these 2 lines already:

[Product]

msi=AcroPro.msi

...

...

CmdLine=TRANSFORMS="AcroPro.mst"

I tried adding to the CmdLine and that didn't work, should I append to the existing msi= line (the explanation shows a slash /msi but that seems wrong?), that seems to only expect the name of the msi to call? Any example of the proper syntax would be very welcome...

Jack

EnterpriseHelp
EnterpriseHelp
Inspiring
August 13, 2018

Without providing the cmds that didn't work, commenting on that is somewhat difficult.

I wouldn't try to use the ini file to pass cmds. Just do it on the cmd line and it's easier to troubleshoot (because then you don't have to troubleshoot the ini file itself).

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices