What is the difference between console installation and silent installation?


In this article, we are explaining the difference between console installation and silent installation

 Silent Installation – Silent setup, additionally referred to as unattended setup, permits device directors to automate the setup process. During a silent setup, the end-consumer isn’t always required to carry out any actions, With silent installation, you can only configure the installation once, and then use that configuration to replicate the installation on multiple computers. During silent installation, the installer will read the configuration settings from the previously created XML file. During the installation process, the installer will not display any configuration options. Unattended installation can be used on both Windows and UNIX.

Overview of unattended installation steps –

  1. Create a silent.xml file that defines the installation configuration that you just would commonly enter throughout an interactive installation process, like graphical-mode or console-mode installation. For example, in silent.xml, you’ll be able to provide the values for the Middleware home directory, the merchandise directory, and also the elements to be installed.

For a lot of information, see Creating a silent.xml File for Silent-Mode Installation.

2. Start the silent-mode installation as delineated  within the section that’s acceptable for your situation:

  • Starting the Installation Program in Silent Mode on Windows
  • Starting .bin Installation Programs in Silent Mode
  • Starting .jar installation programs in Silent Mode

Important concerns for Silent-Mode Installation

When victimization silent mode, keep the subsequent considerations in mind:

  • Silent-mode installation needs a similar quantity of temporary disc space associated uses the same temporary storage directories as a customary installation. The installation program doesn’t warn you if there’s not enough space within the temporary directory.

  • A silent-mode installation takes the same amount of your time as a standard installation. At the start of a silent mode installation, an initial installation program window or message is displayed briefly, indicating that the installation has started. No messages are presented to indicate that the installation is current or has completed successfully.

  • Incorrect entries in the silent.xml file will cause installation failures. to assist you to establish the reason behind a failure, Oracle recommends that you just produce a log file once you begin the installation.

  • The XML definition () must be at the terribly starting of the silent.xml file. don’t enter an area or line breaks before the XML definition.

  • You cannot put in any WebLogic product on prime of an antecedently put in a version of a similar product—in the same Middleware home directory or within the same file location. To reinstall the same version of a product, you want to 1st uninstall the previously installed instance of it or install the new instance in another location.

  • You can, however, add product and merchandise components to an existing installation. For example, you’ll be able to install Core Application Server, Administration Console, and Configuration Wizard Upgrade Framework throughout one installation, and add WebLogic JDBC Drivers and Server Examples during a separate installation.

Console installation

                                  Administrators use the Configuration Manager console to manage the Configuration Manager environment. Each Configuration Manager console can be connected to the management center site (CAS) or the main site. 

You cannot connect the Configuration Manager console to the secondary site. The Configuration Manager console is always installed on the site server of the CAS or main site. Run the offline installer to install the console independently of the installation site server.

Claim – 
You have local administrator rights on the target computer of the console.
You have read access to the location of the Configuration Manager console installation files.

Install from a command prompt
When you install the Configuration Manager console from a command prompt, the English version is always installed. This behavior occurs even if the target computer’s operating system is set to a different language. Use the configuration wizard to install the Configuration Manager console in a language other than English.

ConsoleSetup.exe command-line options

     Silently install the Configuration Manager console. When using this parameter, the TargetDir and DefaultSiteServerName parameters are required.
                            Uninstall the Configuration Manager console. Specify this option first when using it with the / q option.


Specify the path of the folder containing language files. You can use the installer loader to download language files. If this option is not used, the installer will look for the language folder in the current folder. If the language folder is not found, the installer will only install it in English. For more information.

            Specify the installation folder for the Configuration Manager console installation. This parameter is required when using the /q parameter.

Specifies the fully qualified domain name of the site server that the console will connect to when it is opened. This parameter is required when using the /q parameter.
Let’s Try Example

Silent installation

ConsoleSetup.exe/qTargetDir=”%ProgramFiles%ConfigMgrConsole” DefaultSiteServerName=MyServer.Contoso.com

Silent install with language packs

ConsoleSetup.exe/qTargetDir=”C:ProgramFilesConfigMgrConsole” DefaultSiteServerName=MyServer.Contoso.com LangPackDir=C:DownloadsConfigMgr

Silent uninstall

ConsoleSetup.exe /uninstall /q


Please enter your comment!
Please enter your name here