none
Run and accept licence agreement automatically RRS feed

  • Question

  • Hi Guys,

    Is it possible to run an app and have it accept the setup steps i.e agree the licence agreement and start it running automatically using either cmd.exe or PowerShell?

    Thank you in advance!

    Wednesday, October 21, 2015 6:56 PM

Answers

  • Hi theshooj,

    If you mean the desktop application, yes that should be possible.

    For the install command and the options, it should be published by the software manufacturer.

    Generally it should be something like:

    XXX.exe /quiet /feature-on

    and so on, with the options that was pre-designed for the application to run under command.

    And better confirm this with the manufacturer side.

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, October 22, 2015 8:34 AM
    Moderator
  • An MSI installer or an .MSI file?

    Here is an example for an .msi file.

    c:\windows\system32\msiexec.exe /i c:\temp\upekfp\x32\setup.msi /passive /norestart

    Thursday, October 22, 2015 3:53 PM
  • Well from a command prompt or shortcut running a msi package with a /? show the options. From a random msi I had lying around, MicrosoftFixit50833.msi /?

    Windows ® Installer. V 5.0.10565.0 
    
    msiexec /Option <Required Parameter> [Optional Parameter]
    
    Install Options
    	</package | /i> <Product.msi>
    		Installs or configures a product
    	/a <Product.msi>
    		Administrative install - Installs a product on the network
    	/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
    		Advertises a product - m to all users, u to current user
    	</uninstall | /x> <Product.msi | ProductCode>
    		Uninstalls the product
    Display Options
    	/quiet
    		Quiet mode, no user interaction
    	/passive
    		Unattended mode - progress bar only
    	/q[n|b|r|f]
    		Sets user interface level
    		n - No UI
    		b - Basic UI
    		r - Reduced UI
    		f - Full UI (default)
    	/help
    		Help information
    Restart Options
    	/norestart
    		Do not restart after the installation is complete
    	/promptrestart
    		Prompts the user for restart if necessary
    	/forcerestart
    		Always restart the computer after installation
    Logging Options
    	/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    		i - Status messages
    		w - Nonfatal warnings
    		e - All error messages
    		a - Start-up of actions
    		r - Action-specific records
    		u - User requests
    		c - Initial UI parameters
    		m - Out-of-memory or fatal exit information
    		o - Out-of-disk-space messages
    		p - Terminal properties
    		v - Verbose output
    		x - Extra debugging information
    		+ - Append to existing log file
    		! - Flush each line to the log
    		* - Log all information, except for v and x options
    	/log <LogFile>
    		Equivalent of /l* <LogFile>
    Update Options
    	/update <Update1.msp>[;Update2.msp]
    		Applies update(s)
    	/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
    		Remove update(s) for a product
    Repair Options
    	/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
    		Repairs a product
    		p - only if file is missing
    		o - if file is missing or an older version is installed (default)
    		e - if file is missing or an equal or older version is installed
    		d - if file is missing or a different version is installed
    		c - if file is missing or checksum does not match the calculated value
    		a - forces all files to be reinstalled
    		u - all required user-specific registry entries (default)
    		m - all required computer-specific registry entries (default)
    		s - all existing shortcuts (default)
    		v - runs from source and recaches local package
    Setting Public Properties
    	[PROPERTY=PropertyValue]
    
    Consult the Windows ® Installer SDK for additional documentation on the
    command line syntax.
    
    Copyright © Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.
    

    Thursday, October 22, 2015 5:09 PM

All replies

  • Sorry not sure what you are meaning, can you give an option \ example of what you are trying to do? What app a modern app? or an installer?
    Wednesday, October 21, 2015 8:09 PM
  • Hi theshooj,

    If you mean the desktop application, yes that should be possible.

    For the install command and the options, it should be published by the software manufacturer.

    Generally it should be something like:

    XXX.exe /quiet /feature-on

    and so on, with the options that was pre-designed for the application to run under command.

    And better confirm this with the manufacturer side.

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, October 22, 2015 8:34 AM
    Moderator
  • Sorry for not being clear!

    It an msi installer, which needs to run and accept a licence agreement on the first page then run the content.
    Can this be done in an unattended way?

    Hope this makes things clearer!

    Thursday, October 22, 2015 12:50 PM
  • An MSI installer or an .MSI file?

    Here is an example for an .msi file.

    c:\windows\system32\msiexec.exe /i c:\temp\upekfp\x32\setup.msi /passive /norestart

    Thursday, October 22, 2015 3:53 PM
  • Well from a command prompt or shortcut running a msi package with a /? show the options. From a random msi I had lying around, MicrosoftFixit50833.msi /?

    Windows ® Installer. V 5.0.10565.0 
    
    msiexec /Option <Required Parameter> [Optional Parameter]
    
    Install Options
    	</package | /i> <Product.msi>
    		Installs or configures a product
    	/a <Product.msi>
    		Administrative install - Installs a product on the network
    	/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
    		Advertises a product - m to all users, u to current user
    	</uninstall | /x> <Product.msi | ProductCode>
    		Uninstalls the product
    Display Options
    	/quiet
    		Quiet mode, no user interaction
    	/passive
    		Unattended mode - progress bar only
    	/q[n|b|r|f]
    		Sets user interface level
    		n - No UI
    		b - Basic UI
    		r - Reduced UI
    		f - Full UI (default)
    	/help
    		Help information
    Restart Options
    	/norestart
    		Do not restart after the installation is complete
    	/promptrestart
    		Prompts the user for restart if necessary
    	/forcerestart
    		Always restart the computer after installation
    Logging Options
    	/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    		i - Status messages
    		w - Nonfatal warnings
    		e - All error messages
    		a - Start-up of actions
    		r - Action-specific records
    		u - User requests
    		c - Initial UI parameters
    		m - Out-of-memory or fatal exit information
    		o - Out-of-disk-space messages
    		p - Terminal properties
    		v - Verbose output
    		x - Extra debugging information
    		+ - Append to existing log file
    		! - Flush each line to the log
    		* - Log all information, except for v and x options
    	/log <LogFile>
    		Equivalent of /l* <LogFile>
    Update Options
    	/update <Update1.msp>[;Update2.msp]
    		Applies update(s)
    	/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
    		Remove update(s) for a product
    Repair Options
    	/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
    		Repairs a product
    		p - only if file is missing
    		o - if file is missing or an older version is installed (default)
    		e - if file is missing or an equal or older version is installed
    		d - if file is missing or a different version is installed
    		c - if file is missing or checksum does not match the calculated value
    		a - forces all files to be reinstalled
    		u - all required user-specific registry entries (default)
    		m - all required computer-specific registry entries (default)
    		s - all existing shortcuts (default)
    		v - runs from source and recaches local package
    Setting Public Properties
    	[PROPERTY=PropertyValue]
    
    Consult the Windows ® Installer SDK for additional documentation on the
    command line syntax.
    
    Copyright © Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.
    

    Thursday, October 22, 2015 5:09 PM