SQL: SQL Server 2008 Express Missing ConfigurationFile.ini


If you need to install SQL Server 2008 Express from the command line one of the options is to provide a file path to a ConfigurationFile.ini file that specifies all the necessary configuration for the instance you want to install. One of the really nice features provided with the installation package is that you can configure the instance how you want using the GUI and then it will supply you with the corresponding ConfigurationFile.ini file that would be used to setup the instance you just configured in the Ready to Install dialog (see below).

The problem is that with the release of the SQL Server 2008 R2 Express version, the developers reduced the number of dialogs displayed during the installation for the Express version and as a result, the Ready to Install dialog is not displayed anymore! Further the ConfigurationFile.ini is never actually created!

Luckily after combing through the How to: Install SQL Server 2008 R2 from the Command Prompt I found that if you set the UIMODE command line switch to ‘Normal’ the whole set of dialogs will be displayed during installation and consequently the ConfigurationFile.ini will be created. Just start the setup process from the command line with the following:

Note: Make sure you include the /ACTION=Install flag or this will not work.

For those interested, here is the excerpt for the UIMODE switch from the SQL Server 2008 R2 Installation documentation:

Specifies whether to present only the minimum number of dialog boxes during setup.

/UIMode can only be used with the /ACTION=INSTALL and UPGRADE parameters.

Supported values:

  • /UIMODE=Normal is the default for non-Express editions and presents all setup dialog boxes for the selected features.
  • /UIMODE=AutoAdvance is the default for Express editions and skips nonessential dialog boxes.
About these ads
Posted in SQL. Tags: . 46 Comments »

46 Responses to “SQL: SQL Server 2008 Express Missing ConfigurationFile.ini”

  1. Aben Says:

    Hi Nick,

    Many thanks for the comments on http://wellytonian.com/2010/08/sql-server-2008-r2-unattended-installation/ have put a link back for the readers.

    Cheers

    Aben

    • Nick Olsen Says:

      No problem. Thanks for the info.

  2. stimms Says:

    Hey thanks a lot for posting this, saved me a bunch of hair pulling.

    • Nick Olsen Says:

      No problem! At least one of us will have hair!

  3. Tattoo Says:

    I’m getting a /HIDECONSOLE error when i try to run the SQLExpress.exe /CONFIGURATIONFILE=C:\Test\Test.ini.

    I tried putting the hideconsole in the ini and in the command line with =1,2.

    I’m hoping its something stupid but can’t figure it out

    Thanks

    • Nick Olsen Says:

      Interesting. I just did a test using both the following command lines and it worked fine hiding the console window:

      SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE
      SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE=1

      What is the exact error you are receiving? Does the installation start at all? Do you see the console window or not?

  4. Tattoo Says:

    Thanks for the reply, you solved that issue.

    I had the HIDECONSOLE after the executable, now it runs but still asks for input.

    Do i need to change something in the ini once its created from my install?

    • Nick Olsen Says:

      In order to perform an unattended install you need to add two switches to you ConfigurationFile.ini:

      IACCEPTSQLSERVERLICENSETERMS=”True”
      QUIET=”True” OR QUIETSIMPLE=”True”

      The first, obviously indicates that the user accepts the license agreement for SQL Server. Second, add either QUIET=”True” and no user interface will be shown at all or QUIETSIMPLE=”True” which will display the user interface and show installation progress but require no user input.

      Alternatively, you can supply these at the command line. In this case, the QUITESIMPLE chages to /QS and QUITE changes to /Q. For example:

      SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE /Q
      SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE /QS

      • tattoo Says:

        Thanks for all your information and it seems so easy following your instructions. I don’t understand why it still doesn’t work and don’t want to waste your time anymore because i’m sure its something stupid.

        I tried /QS /Q and inserting QUIET, QUIETSIMPLE into ini without success. Now it starts, unpacks, puts up 1 SQL window saying current operation then nothing.

        The sad part is i do scripts and automation all the time but SQL is kicking my ass.

      • Nick Olsen Says:

        It could be anything. If it helps, here is the list of command line switches I used on an unattended installation recently. These can obviously be pasted into a ConfigurationFile.ini if you just remove the leading ‘/’

        Good luck!

        /INSTANCEID=”SQLINSTANCE”
        /ACTION=”Install”
        /FEATURES=SQLENGINE
        /HELP=”False”
        /INDICATEPROGRESS=”False”
        /QUIETSIMPLE=”True”
        /X86=”False”
        /ROLE=”AllFeatures_WithDefaults”
        /ENU=”True”
        /ERRORREPORTING=”False”
        /IAcceptSQLServerLicenseTerms=”True”
        /INSTANCEDIR=”C:\InstanceDir”
        /SQMREPORTING=”False”
        /INSTANCENAME=”SQLINSTANCE”
        /AGTSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”
        /AGTSVCSTARTUPTYPE=”Disabled”
        /ISSVCSTARTUPTYPE=”Automatic”
        /ISSVCACCOUNT=”NT AUTHORITY\NetworkService”
        /ASSVCSTARTUPTYPE=”Automatic”
        /ASCOLLATION=”Latin1_General_CI_AS”
        /ASDATADIR=”Data”
        /ASLOGDIR=”Log”
        /ASBACKUPDIR=”Backup”
        /ASTEMPDIR=”Temp”
        /ASCONFIGDIR=”Config”
        /ASPROVIDERMSOLAP=”1″
        /FARMADMINPORT=”0″
        /SQLSVCSTARTUPTYPE=”Automatic”
        /FILESTREAMLEVEL=”0″
        /ENABLERANU=”True”
        /SQLCOLLATION=”SQL_Latin1_General_CP1_CI_AS”
        /SQLSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”
        /SQLSYSADMINACCOUNTS=”nickolsen-PC\Administrator”
        /SECURITYMODE=”SQL”
        /ADDCURRENTUSERASSQLADMIN=”True”
        /TCPENABLED=”1″
        /NPENABLED=”0″
        /BROWSERSVCSTARTUPTYPE=”Automatic”
        /RSSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”
        /RSSVCSTARTUPTYPE=”Automatic”
        /RSINSTALLMODE=”FilesOnlyMode”
        /SAPWD=”adminSQL!”

      • Roger Bamforth. Says:

        After a whole morning failing to get this working I found out that

        IACCEPTSQLSERVERLICENSETERMS=”True”

        needs to have a boolean parameter, not a string. So it actually needs to be:

        IACCEPTSQLSERVERLICENSETERMS=True

        Thanks for that bit of nonsense Microsoft!

        Also, the only way I found out that this was the reason my configuration file wasn’t working was by unzipping SQLEXPRWT_x64_ENU.exe and running the setup.exe that is inside this (giving it same command line switches as SQLEXPRWT_x64_ENU.exe). This then ran in a console and produced an error message telling me what was wrong.

      • Nick Olsen Says:

        Thanks for the tip!

      • Luiscperu Says:

        Finnally I got this installation smoothly and silent (SQL R2 on W2K8 R2). Worked like a charm !!!. But….. I used the following sintax:

        SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=Config_x64.ini /HIDECONSOLE /Q

        Note that I suppresed the quotations because it appeared an error message of .ini file missing. What remains untested is the fact that I had to customize de .ini file from an x86 version. Then added the parameter:

        INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server”

        So I wonder if the x64 ini file can also be used for win32 silent instalation.

        Finnaly this is the most automated process thanks to you Nick !!!. It is a ONE LINE SILENT INSTALATION.

        Regards

        PS: I would contribute much more (If I could) but I can’t because I hate to register. All blogs must be aware of that !!!

  5. Tattoo Says:

    Thanks for the help Nick

    After looking over your .ini i noticed i was missing the /SAPWD switch.

    Your the Man

    • Nick Olsen Says:

      Glad it helped!

  6. Guillaume Says:

    Hi Nick,

    I would like to know if there is a way to install everything on another drive? I’ve been trying few times by modifying the Configuration File to the D drive for example, but there is always some files (over 900!!) that remains under “C:\Program Files\Microsoft SQL Server”.

    My server is a 2003 SP2 and in the configuration file I’m setting INSTANCEDIR=”D:\Microsoft SQL Server” and INSTALLSHAREDDIR=”D:\Microsoft SQL Server”.

    Thanks for your help

    • Nick Olsen Says:

      Strange. I think that should do it. Have you tried doing an install with the wizard instead of the command line and specifying the installation paths that way? Maybe using the wizard, specifying D:\Microsoft SQL Server as the installation directory, and then looking at the ConfigurationFile.ini will shed some light on the situation. Look for any file paths that say C:\Program Files\Microsoft SQL Server and then replace them with D:\Microsoft SQL Server. Let me know if you find anything out.

      • Guillaume Says:

        I’ve done everything you said,… but unfortunately, even a bunch of files are installed in the right folders, there is always a lot of files remaining in the “C:\Program Files\Microsoft SQL Server”. The majority of the files looks to be files that are installed directly when launching the application, before selecting the INSTANCEDIR path.

        Let me know if you have any idea.

        Thanks for your help!

        Guillaume

    • Nick Olsen Says:

      Turns out that you can’t do anything about this. There are only certain files that have configurable destination paths. Such a restriction is well documented on MSDN here. Sorry to deliver such news.

  7. nonolde1er Says:

    thanks for all information

    here are steps :

    1) install sql serveur express manually with this command to force .ini file install :
    SQLEXPR_x64_ENU.exe /ACTION=INSTALL /UIMODE=Normal

    2) save CONFIGURATIONFILE.ini in another folder

    3) uninstall sql server (delete all folder, registry key with ccleaner for example)

    4) in powershell window, execute the following command to install sql server in silence mode :

    & “T:\SQLEXPRADV_x64_ENU.exe” /CONFIGURATIONFILE=”T:\ConfSetupSql2008Express.ini”

    5) ConfSetupSql2008Express.ini is :

    ;SQLSERVER2008 Configuration File
    [SQLSERVER2008]

    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.

    INSTANCEID=”SQLExpress”

    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

    ACTION=”Uninstall”

    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.

    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,RS,BIDS,SSMS,SNAC_SDK,OCS

    ; Displays the command line parameters usage

    HELP=”False”

    ; Specifies that the detailed Setup log should be piped to the console.

    INDICATEPROGRESS=”True”

    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.

    X86=”False”

    ; Detailed help for command line argument ROLE has not been defined yet.

    ROLE=”AllFeatures_WithDefaults”

    ; Detailed help for command line argument ENU has not been defined yet.

    ENU=”True”

    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.

    ERRORREPORTING=”False”

    ; Specify the root installation directory for native shared components.

    INSTALLSHAREDDIR=”E:\Program Files\Microsoft SQL Server”

    ; Specify the root installation directory for the WOW64 shared components.

    INSTALLSHAREDWOWDIR=”E:\Program Files (x86)\Microsoft SQL Server”

    ; Specify the installation directory.

    INSTANCEDIR=”E:\Program Files\Microsoft SQL Server”

    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.

    SQMREPORTING=”False”

    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).

    INSTANCENAME=”SQLEXPRESS”

    ; Agent account name

    AGTSVCACCOUNT=”AUTORITE NT\SERVICE RÉSEAU”

    ; Auto-start service after installation.

    AGTSVCSTARTUPTYPE=”Disabled”

    ; Startup type for Integration Services.

    ISSVCSTARTUPTYPE=”Automatic”

    ; Account for Integration Services: Domain\User or system account.

    ISSVCACCOUNT=”NT AUTHORITY\NetworkService”

    ; Controls the service startup type setting after the service has been created.

    ASSVCSTARTUPTYPE=”Automatic”

    ; The collation to be used by Analysis Services.

    ASCOLLATION=”Latin1_General_CI_AS”

    ; The location for the Analysis Services data files.

    ASDATADIR=”Data”

    ; The location for the Analysis Services log files.

    ASLOGDIR=”Log”

    ; The location for the Analysis Services backup files.

    ASBACKUPDIR=”Backup”

    ; The location for the Analysis Services temporary files.

    ASTEMPDIR=”Temp”

    ; The location for the Analysis Services configuration files.

    ASCONFIGDIR=”Config”

    ; Specifies whether or not the MSOLAP provider is allowed to run in process.

    ASPROVIDERMSOLAP=”1″

    ; A port number used to connect to the SharePoint Central Administration web application.

    FARMADMINPORT=”0″

    ; Startup type for the SQL Server service.

    SQLSVCSTARTUPTYPE=”Automatic”

    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3).

    FILESTREAMLEVEL=”0″

    ; Set to “1″ to enable RANU for SQL Server Express.

    ENABLERANU=”True”

    ; Specifies a Windows collation or an SQL collation to use for the Database Engine.

    SQLCOLLATION=”French_CI_AS”

    ; Account for SQL Server service: Domain\User or system account.

    SQLSVCACCOUNT=”MyUserSQLSrv”

    ; Windows account(s) to provision as SQL Server system administrators.

    SQLSYSADMINACCOUNTS=”MyUserAdm”

    ; The default is Windows Authentication. Use “SQL” for Mixed Mode Authentication.

    SECURITYMODE=”SQL”

    ; Default directory for the Database Engine backup files.

    SQLBACKUPDIR=”S:\VUR\MSSQL10_50.SQLEXPRESS\MSSQL\BACKUP”

    ; Default directory for the Database Engine user database logs.

    SQLUSERDBLOGDIR=”J:\VUR\MSSQL10_50.SQLEXPRESS\MSSQL\Data”

    ; Directory for Database Engine TempDB files.

    SQLTEMPDBDIR=”H:\VUR\MSSQL10_50.SQLEXPRESS\MSSQL\Data”

    ; Provision current user as a Database Engine system administrator for SQL Server 2008 R2 Express.

    ADDCURRENTUSERASSQLADMIN=”True”

    ; Specify 0 to disable or 1 to enable the TCP/IP protocol.

    TCPENABLED=”1″

    ; Specify 0 to disable or 1 to enable the Named Pipes protocol.

    NPENABLED=”0″

    ; Startup type for Browser Service.

    BROWSERSVCSTARTUPTYPE=”Automatic”

    ; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.

    RSSVCACCOUNT=”MyUserSSRS”
    RSSVCPASSWORD=”myPassword”

    ; Specifies how the startup mode of the report server NT service. When
    ; Manual – Service startup is manual mode (default).
    ; Automatic – Service startup is automatic mode.
    ; Disabled – Service is disabled

    RSSVCSTARTUPTYPE=”Automatic”

    ; Specifies which mode report server is installed in.
    ; Default value: “FilesOnly”

    RSINSTALLMODE=”FilesOnlyMode”

    ; Add description of input argument FTSVCACCOUNT

    FTSVCACCOUNT=”NT AUTHORITY\LOCAL SERVICE”

    ; licence terms

    IACCEPTSQLSERVERLICENSETERMS=”True”

    ; Specifies the path to the installation media folder where setup.exe is located.
    ;MEDIASOURCE=”T:\”

    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI, and AutoAdvance for a simplied UI.
    ;UIMODE=”Normal”

    ; Setup will not display any user interface.
    ;QUIET=”False”

    ; Setup will display progress only without any user interaction.
    QUIETSIMPLE=”True”

    ; password sql server connexion
    SAPWD=”myPassword”

    6) powershell command with parameter (same as 5):

    in powershell window, fill this

    C:\InstallSqlServer2008.ps1 “T:\SQLEXPRADV_x64_ENU.exe” “T:\ConfSetupSql2008Express.ini”

    in InstallSqlServer2008.ps1 file :

    Write-Host “– installing slq server express 2008 r2 extended…”

    $fileExe = $args[0]
    $CONFIGURATIONFILE = $args[1]
    & $fileExe /CONFIGURATIONFILE=$CONFIGURATIONFILE

  8. nonolde1er Says:

    hi

    even if there is a log file, is there a way to catch return code install with .bat command or powershell command :

    C:\InstallSqlServer2008.ps1 “T:\SQLEXPRADV_x64_ENU.exe” “T:\ConfSetupSql2008Express.ini”

    • Nick Olsen Says:

      I’m not sure about catching the return code but what I have done in one of my applications that installs SQL Server 2008 is to check the installation log file once the installation is complete for certain strings indicating that the installation was successful. That will actually be better than a return code as you can see if particular components failed to install or not.

  9. nonolde1er Says:

    i found and i tested : it’s ok : to catch return code at the end of sql server install , you have to add “out | null” at the end powershell command; like this :

    in ps1 file :

    Write-Host “– installing slq server express 2008 r2 extended…”

    # $args[0] = name exe
    # $args[1] = configuration file name sql serveur .ini
    $fileExe = $args[0]
    $CONFIGURATIONFILE = $args[1]
    & $fileExe /CONFIGURATIONFILE=$CONFIGURATIONFILE | out-null

    Write-Host “install sql serveur done – return code = $LASTEXITCODE”

    to call this :

    C:\VUR\InstallSqlServer2008.ps1 “T:\SQLEXPR_x64_ENU.exe” “T:\ConfSetupSql2008Express.ini”

    and then , powershell focus wait and appear after only the end of install
    so you can disply the return code with $LASTEXITCODE

    • Nick Olsen Says:

      Good to know. Thanks for the info.

  10. nonolde1er Says:

    hi,

    i have return code = -2067529698. Have you already had this error ?

  11. Troy G Says:

    Your instructions worked for me.

    Thanks for the post!

  12. David Says:

    Hi Nick,
    Great detail, thanks. Have you had any experience running the Service Packs unattended? Do you know what the switches would be to push SP2 for example to all instances on a machine? This was pretty easy in SQL2005.
    David

    • Nick Olsen Says:

      I have never done an install of SP2 unattended. I will see what I can find.

  13. David Says:

    In 2005 it was as simple as this…
    start /wait ..\..\SQL2K8ENT.nnnn\SQLServer2008_R2-x64-ENU.exe /quiet /allinstances

    …but seems no more.

  14. David Says:

    Oh, and no config file is setup when you manually run the service pack.

  15. David Says:

    Me again!
    Is there any documentation on the default values for each parameter?

    • Nick Olsen Says:

      Yes. The MSDN documentation for the unattended install has a list of all available switches and the ones that have default values are defined. See http://msdn.microsoft.com/en-us/library/ms144259.aspx

  16. Claus Says:

    Hi Nick,

    great job, thank you. Unfortunately, I’m facing a problem that the installation of sqlexpr_x64_enu.exe exits with “UIMODE settings specified not recognized, Errorcode 0x84B40003.

    thanks for your help
    Claus

    • Nick Olsen Says:

      What is the script that you are using? If you post it here, I can take a look and see if I see any issues with how it is written.

  17. nonolde1er Says:

    it’s ok for me. install with SQLEXPRADV_x64_ENU.exe

    i have no longer this error -2067529698.
    the changes are :

    1) /ACTION=INSTALL must be in command script even if it is in config file.

    2) all info in config.ini file, generated first in manual install with command ,must be present cause then, the silent install is very sensitive if you remove some useless parameters, depending on your preference

    thanks for all

    • Nick Olsen Says:

      Thanks for providing your solution.

  18. Saqib Ali Says:

    Dear, thx a lot u try to help solve my problem.

  19. Suleyman Ozturk (@SimonOzturk) Says:

    Thanks Nick I fix my problem..

  20. Milo Says:

    Thx a lot for this solution!

  21. Jocke Says:

    Having problems installingSQL Server Express 2012 automated on Win 7 64 , using a config file ,after extracting , I run setup.exe ConfigFile.ini

    This error occurs :The specified value for setting MEDIALAYOUT is invalid
    The expected values are
    None Core Advanced Full

    But there is no such config item , MEDIALAYOUT, in the properties of the configFile
    ,and no such item is in the specs.

    I have used your excellent posts, to build the configfile first, but it seems I am stuck on this MEDIALAYOUT error

    Have googled the error but to no avail

  22. David Wingler Says:

    Hey Nick,

    I am trying to install SQL Server 2008 R2 SP2 doing an unattended install. I can manually install the software fine however when I try to do it unattended something in my config file is bombing the install. My company just purchased a Dell Kace appliance to manage inventory and push out software. I got the software uploaded to the Kace server and am able to start the install. Part way through the install an error comes up and then the whole install shuts down. I am posting my config file for your review.

    Thanks,
    David W.

    ;SQLSERVER2008 Configuration File
    [SQLSERVER2008]

    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.

    INSTANCEID=”SQLExpress”

    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.

    ACTION=”Install”

    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.

    FEATURES=SQLENGINE,REPLICATION,SNAC_SDK

    ; Displays the command line parameters usage

    HELP=”False”

    ; Specifies that the detailed Setup log should be piped to the console.

    INDICATEPROGRESS=”False”

    ; Setup will not display any user interface.

    QUIET=”False”

    ; Setup will display progress only without any user interaction.

    QUIETSIMPLE=”False”

    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.

    X86=”False”

    ; Detailed help for command line argument ROLE has not been defined yet.

    ROLE=”AllFeatures_WithDefaults”

    ; Detailed help for command line argument ENU has not been defined yet.

    ENU=”True”

    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI, and AutoAdvance for a simplied UI.

    UIMODE=”Normal”

    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.

    ERRORREPORTING=”False”

    ; Specify the root installation directory for native shared components.

    INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server”

    ; Specify the root installation directory for the WOW64 shared components.

    INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server”

    ; Specify the installation directory.

    INSTANCEDIR=”C:\Program Files\Microsoft SQL Server”

    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.

    SQMREPORTING=”False”

    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).

    INSTANCENAME=”SQLEXPRESS”

    ; Agent account name

    AGTSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”

    ; Auto-start service after installation.

    AGTSVCSTARTUPTYPE=”Disabled”

    ; Startup type for Integration Services.

    ISSVCSTARTUPTYPE=”Automatic”

    ; Account for Integration Services: Domain\User or system account.

    ISSVCACCOUNT=”NT AUTHORITY\NetworkService”

    ; Controls the service startup type setting after the service has been created.

    ASSVCSTARTUPTYPE=”Automatic”

    ; The collation to be used by Analysis Services.

    ASCOLLATION=”Latin1_General_CI_AS”

    ; The location for the Analysis Services data files.

    ASDATADIR=”Data”

    ; The location for the Analysis Services log files.

    ASLOGDIR=”Log”

    ; The location for the Analysis Services backup files.

    ASBACKUPDIR=”Backup”

    ; The location for the Analysis Services temporary files.

    ASTEMPDIR=”Temp”

    ; The location for the Analysis Services configuration files.

    ASCONFIGDIR=”Config”

    ; Specifies whether or not the MSOLAP provider is allowed to run in process.

    ASPROVIDERMSOLAP=”1″

    ; A port number used to connect to the SharePoint Central Administration web application.

    FARMADMINPORT=”0″

    ; Startup type for the SQL Server service.

    SQLSVCSTARTUPTYPE=”Automatic”

    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3).

    FILESTREAMLEVEL=”0″

    ; Set to “1″ to enable RANU for SQL Server Express.

    ENABLERANU=”True”

    ; Specifies a Windows collation or an SQL collation to use for the Database Engine.

    SQLCOLLATION=”SQL_Latin1_General_CP1_CI_AS”

    ; Account for SQL Server service: Domain\User or system account.

    SQLSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”

    ; Windows account(s) to provision as SQL Server system administrators.

    SQLSYSADMINACCOUNTS=”WF\davidwingler”

    ; The default is Windows Authentication. Use “SQL” for Mixed Mode Authentication.

    SECURITYMODE=”SQL”

    ; Provision current user as a Database Engine system administrator for SQL Server 2008 R2 Express.

    ADDCURRENTUSERASSQLADMIN=”True”

    ; Specify 0 to disable or 1 to enable the TCP/IP protocol.

    TCPENABLED=”0″

    ; Specify 0 to disable or 1 to enable the Named Pipes protocol.

    NPENABLED=”0″

    ; Startup type for Browser Service.

    BROWSERSVCSTARTUPTYPE=”Automatic”

    ; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.

    RSSVCACCOUNT=”NT AUTHORITY\NETWORK SERVICE”

    ; Specifies how the startup mode of the report server NT service. When
    ; Manual – Service startup is manual mode (default).
    ; Automatic – Service startup is automatic mode.
    ; Disabled – Service is disabled

    RSSVCSTARTUPTYPE=”Automatic”

    ; Specifies which mode report server is installed in.
    ; Default value: “FilesOnly”

    RSINSTALLMODE=”FilesOnlyMode”

  23. wildchild2citymom Says:

    FOr some reason, the 32-bit install wont still create a config file. NO problem, I just took the entries from the above posts and made my own. Thanks for this post and all the comments.

  24. Nagarjuna Says:

    Dont worry guys!!! i have the solution…..

    if you wnna do silent install follow the below steps
    - install the application with the required features, while installing it wont create the ConfigurationFile.
    - Uninstall the application from the add/removeprograms, while uninstalling it will genarate the ConfigurationFile with the installed features in the “C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130823_131455\” .
    - so in palce of ACTION=”Uninstall” use ACTION=”install”.
    - Run the command as Nick Olsen’s SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE /Q.
    so simple..

    • Nagarjuna Says:

      use
      SQLEXPR_x64_ENU.exe /CONFIGURATIONFILE=”ConfigurationFile.ini” /HIDECONSOLE /QS

  25. Simon Says:

    I had a problem with the configuration file, and found out, that the uimode parameter in the configuration file cannot be used with the quiet or quietsimpel argument. I deleted the uimode parameter and everythink worked good. Be aware of that!

  26. Jerry Dodge Says:

    Awesome, exactly what I was looking to find :D Thank you tons


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 69 other followers

%d bloggers like this: