Silent or unattended installation

What is silent or unattended installation
Simply said silent install is installation without any UI. In this case it’s about how to run “setup.exe” in silent mode. It’s recommended that you only run “setup.exe” when you install a new NAV installation, because the installer have been tested by them using this procedure only. So by that said it’s no longer supported to install from the different msi files directly. This is true for all NAV 2009 releases. The major problem you may run into if you are installing directly from the msi files is that you will not get prerequisites (as .Net, Report Viewer and so on) installed and you will also miss out one some pre installs checks (validating that you have everything needed as outlook).

How to-do it?
It’s very simple. “setup.exe” does support some different parameters for this purpose:
/quiet <– will turn of the UI
/log [filename] <– create a log text file in the specified location
/config [filename]<– point to the configuration file to use during the installation
/uninstall <– will simple un install the product
/repair <– repairs a bad installation

The first thing that needs to be done is to create the configuration file that we will use.

  1. Star “setup.exe”
  2. Click “next”
  3. Click “I accept”
  4. Click “Choose an installation option”
  5. Click “Custom Components”
  6. Select the product that you want to install
  7. Update destination folder if needed by clicking on the “destination folder” link
  8. Click “next”
  9. Click on the component that you have picked to setup the different parameters as “server name” and so on. When done apply your changes.
  10. Click “save configuration”
  11. Pick a good location, name and save the xml file

You can create as many configuration files as you want for different purposes. Now, you can run the silent install by simply doing start -> run -> [setupExepath] /quiet /config [configfilepath.xml]. Be sure to take a look to the log file, to ensure everything went OK.

Example D:\setup.exe /quiet /config C:\configfiles\config1.xml /log C:\log.txt

Comments (9)

  1. Mirko says:

    I'm just backlinking my blog for the same article……/silent-or-unattended-installation-of-nav-2009

  2. Andreas says:

    What does that mean for deployment via GPO (that still is in the training manuals)??

  3. Peter Wibeck says:

    Installing the MSI files directly is still possible as the training manuals states. You just need to ensure that all required prerequisites is installed on the machine also. All prerequisites is shipped on the DVD and should not be hard to handle with GPO.

  4. Andrew says:

    only issue with this is it bombs out when running under the system account, which is what our KACE agent deploys software as so its user independent.

  5. Eric says:

    Do you know if this will automatically uninstall prior versions if run as noted above?  We have a client asking us to perform an automated update and I'm not sure if I can do it with only one job or not?

  6. Roendi says:

    I need to change the language as User Settings as command Line. Have anyone a idea how this work.

    I cannot find the currend Language Settings.

  7. To Get around the Install Kicking you out mid install for SCCM and Dell Kace, you can create directories under the system user profile dir prior to installation.

    For Example.

    @echo off



    mkdir "C:WindowsSysWOW64configsystemprofileAppDataRoaming"

    mkdir "C:WindowsSysWOW64configsystemprofileDesktop"

    mkdir "C:WindowsSysWOW64configsystemprofileFavorites"

    mkdir "C:WindowsSysWOW64configsystemprofileDocuments"

    mkdir "C:WindowsSysWOW64configsystemprofileAppDataRoamingMicrosoftWindowsTemplates"

    mkdir "C:WindowsSysWOW64configsystemprofileAppDataRoamingMicrosoftWindowsSendTo"

    mkdir “C:WindowsSysWOW64configsystemprofileAppDataRoamingMicrosoftWindowsStart Menu”

    mkdir “C:WindowsSysWOW64configsystemprofileAppDataRoamingMicrosoftWindowsStart MenuProgramsStartup”

    setup.exe /quiet /config clientconfig.xml /log "C:TempNavlog.txt"

    goto END


    mkdir "C:WindowsSystem32configsystemprofileAppDataRoaming"

    mkdir "C:WindowsSystem32configsystemprofileDesktop"

    mkdir "C:WindowsSystem32configsystemprofileFavorites"

    mkdir "C:WindowsSystem32configsystemprofileDocuments"

    mkdir "C:WindowsSystem32configsystemprofileAppDataRoamingMicrosoftWindowsTemplates"

    mkdir "C:WindowsSystem32configsystemprofileAppDataRoamingMicrosoftWindowsSendTo"

    mkdir “C:WindowsSystem32configsystemprofileAppDataRoamingMicrosoftWindowsStart Menu”

    mkdir “C:WindowsSystem32configsystemprofileAppDataRoamingMicrosoftWindowsStart MenuProgramsStartup”

    setup.exe /quiet /config clientconfig.xml /log "C:TempNavlog.txt"


  8. Andrew says:

    Another odd issue I noticed is this method does not include the uninstall information in the registry for add/remove programs.

  9. Nick Johnston says:

    I am trying to perform a silent install of NAV 2009 R2 Classic Client into the C:\Program Files directory on a x64 OS, like Windwos 8.1 and Windwos 10.
    Even when doing a manual install and purposefully changing the path from C:\Program Files X86\ to C:\Program Files NAV 2009 R2 it still installs into C:\Program Files X86. If I choose a folder in the root of C:\ like C:\Dymanics_NAV it installs into this location without issue. The key reason for wanting to do this is we deploy the Navision shortcut with DB name etc via GPO and having the same installation path in the shortcut makes this process much easier.
    Does anyone have an idea why this may be happening?

Skip to main content