I'm trying to do a silent install of SQL Server Express 2008R2 from SCCM2007.
Runing the following command,
SQLEXPRWT_x86_ENU.exe /ConfigurationFile=\\Server\Share\SQLExpr\ConfigurationFile_X86.ini /QUIET
When I run this from the commandline the installer starts and at some point quits without installing the instance. And removing the /quiet tag to see what happens results in a halt when the installer gets to Setup Support Rules. So I'm guessing this is where it halts in the real deployment also.
All prerequisites have been installed as a part of the operating system image and the setup rules show the client is ready to go. So my question is, is there any way to get past this in the quiet install?
Also here is the ConfigurationFile_X86.ini:
;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="RETAILPOS" ; 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,SSMS,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="True" ; Setup will display progress only without any user interaction. QUIETSIMPLE="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" ; 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 (x86)\Microsoft SQL Server" ; Specify the installation directory. INSTANCEDIR="C:\Program Files (x86)\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="RETAILPOS" ; 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="Finnish_Swedish_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="DEMO\Administrator" ; 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="1" ; Startup type for Browser Service. BROWSERSVCSTARTUPTYPE="Disabled" ; 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"
MCITP Server Administrator
To answer my own question. In the configuration file there are a few misstakes. UIMODE should be commented out when running silent. And if you supply QUIET=TRUE set QUIETSIMPLE=FALSE, also don't use /quiet in the commandline.
I got to this by starting the installer and copying the unpacked SQL server installation folder to another folder and running setup.exe with ConfigurationFile=filename
I'll try running this file with the original EXE now and report back in case someone else runs into the same problem.
MCITP Server Administrator
- Marked as answer by Mats HellmanMicrosoft employee Friday, July 29, 2011 3:50 PM