I just needs you to clarify a point, how i can configure the SETUP.EXE with configuration.ini? This is a brilliant idea that will save me. Therefore one needs to inform the Wix about this via ExitCode. Since the RAR will just increase the return code with 1000. One just need to take care at the returned code, which is 1000 on success This can be integrated in the Wix bundle almost the same as the original exe package. To silently extract, run the setup.exe with a configuration.ini as parameter and wait for the return code.
To create the Configuration File run the GUI install selecting all the necessary options required. There are two parts of the install, firstly the command line switches to run the install and the second is the configuration file referenced during install.
With the RAR, you can create a SFX archive from the original SQLEXPR_圆4_ENU kit, then configure the archive SQL 2014 unattended install is reasonably straightforward once you understand the switches. I found a pretty easy solution, which worked for me. We don't need a 500+ meg install for this thing.
It appears to work fine, but I am not sure if we will actually use this or not yet.ĭo you know if this behavior will be changed with the service pack - will it work like it used to? The application is built to download the latest SQL Server install package at runtime. it calls setup.exe with the necessary parameters, waits for it to exit, and passes the return code back to the WIX framework. Then the small exe runs next, getting passed the path to the extractedįiles. The arguments to SQLEXPR_圆4_ENU.exe are now just "/Q /X.\POS". I got around this behavior by creating a "shim", a small exe that I bundle after the SQL Server download. If you use the X parameter, all it does is extract the archive and quit. We don't merely want to extract it, we want to extract it and The problem is that the rest of the command line parameters do not get automatically passed to the setup executable. Net, Community and tagged Installing Microsoft SQL Server 2014 to Windows Server 2012 R2 Domain Controller, Installing Microsoft SQL Server 2014 to Windows Server Domain Controller, Installing Microsoft SQL Server to Windows Server 2012 R2 Domain Controller, Installing Microsoft SQL Server to Windows Server Domain. Also, before the installation of SQL or PDM, some important items should be considered. The recommendations made in the preceding link, should be considered as minimal recommendations. skiprules=RebootRequiredCheck /NPENABLED=1 /TCPENABLED=1 SQL Server 2014 should be installed on a compatible server. Q /X.\POS /IAcceptSQLServerLicenseTerms /action=Install /features=SQLENGINE /AddCurrentUserAsSqlAdmin /IAcceptSqlServerLicenseTerms /enableranu=1 /instancename=RADIOSHOP6X /SQLSVCSTARTUPTYPE=Automatic /sqlsvcaccount="NT Authority\SYSTEM" /SQLSYSADMINACCOUNTS="Builtin\Administrators" I had already seen this thing you referred me to, though.