Define, which CLI switches make sense to work in the GUI installer. Which switches should be just ignored. Verify that the GUI installation works according the defined specification. 

-> By default, we should restrict the options originally intended to be used with CLI to not work with GUI installer to keep this consistent. For example the message acceptance options - these do not necessarily provide any additional value to interactive GUI installation, they can be even detrimental to experience if the user misses some crucial message box information during installation or somehow manages to block further progress with a wrong choice. For automating graphical installation, most of the same functionality is already exposed through the scripting API and should be used instead.

The user should be able to easily distinguish the CLI-only options from command line help text.