**Note – I’m not a SQL guy, I just have to do the basics. Any post install configuration is specific to the environment and requirements of the system and organisation**
SQL 2014 unattended install is reasonably straightforward once you understand the switches.
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.
To create the Configuration File run the GUI install selecting all the necessary options required. At the final point before clicking Install you can see where the automatically created configurationfile.ini is located:
This configuration file now needs to be updated with the necessary information for the environment. For us its setting the GUI to progress only, service accounts, DB and logs locations etc. A sample configuration is shown below:
;SQL Server 2014 Configuration File
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
; Setup will not display any user interface.
; Setup will display progress only, without any user interaction.
; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.
; 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.
; If this parameter is provided, then this computer will use Microsoft Update to check for updates.
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components.
; Specify the location where SQL Server Setup will obtain product updates. The valid values are “MU” to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services.
; Displays the command line parameters usage
; Specifies that the detailed Setup log should be piped to the console.
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.
INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server”
; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.
INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server”
; 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).
; 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.
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.
; Specify the installation directory.
INSTANCEDIR=”C:\Program Files\Microsoft SQL Server”
; Agent account name
; Auto-start service after installation.
; CM brick TCP communication port
; How matrix will use private networks
; How inter brick communication will be protected
; TCP port used by the CM brick
; Startup type for the SQL Server service.
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
; Set to “1” to enable RANU for SQL Server Express.
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
; Account for SQL Server service: Domain\User or system account.
; Windows account(s) to provision as SQL Server system administrators.
; Default directory for the Database Engine backup files.
; Default directory for the Database Engine user databases.
; Default directory for the Database Engine user database logs.
; Directory for Database Engine TempDB files.
; Directory for the Database Engine TempDB log files.
; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express.
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
Note the UpdateSource option. For Service Packs or Cumulative Updates simply drop the .exe into this folder and it will be slipstreamed at install.
I now have a batch file to call setup.exe and specify the configuration file above. I put the configuration file into the same folder as the setup.exe but it doesn’t really matter. As I have added specific service accounts I also need to add the password switches.
## Create necessary Folders for DB/Log/Backup Files ## mkdir E:\SQL\Logs mkdir E:\SQL\Data mkdir E:\SQL\Backup "\\SQL-Files-Location\Setup.exe" /ConfigurationFile="\\SQL-Files-Location\SQL-ConfigurationFile.ini" /IacceptSQLServerLicenseTerms=True /AGTSVCPASSWORD=password /SQLSVCPASSWORD=password
Before anyone shouts yes I know the passwords are in clear in the setup batch file but my deployment folder is locked down tightly and this works while I work out a way to run this more securely.