Posts Tagged ‘ Features ’

SQL Server 2008 R2 – Unattended Silent Install


There is existing documentation on MSDN about How to: Install SQL Server 2008 R2 from the Command Prompt, but this post focuses on creating a silent unattended install of SQL Server 2008 R2 (Standard or Enterprise) using a configuration file. With the instructions below, you’ll be able to create a new customized SQL silent installation in minimal time. Note that the configuration below doesn’t work with the Express edition of SQL Server 2008 R2.

  • Run setup.exe
  • Click on the installtion tab
  • Click “New Installation”
  • Go through the wizard: Enter product key, accept license, install setup support files, and select the features you want to install:
  • Continue the installation until you reach the “Ready To Install” step. Notice the path to the configuration file highlighted below in blue.

  • Now that you have the configuration file, copy it to your own folder or network share where you want to start the unattended installation.
  • Cancel setup since we’re interested in the unattended silent mode of installation; not the UI one.
  • Edit the configuration file as follows:
    • Set QUIET to “True”. This specifies that Setup will run in a quiet mode without any user interface (i.e. unattended installation)
      QUIET="True"
    • Set SQLSYSADMINACCOUNTS to “BUILTIN\ADMINISTRATORS”. This will ensure that administrators on the machine are added as members of the sysadmin role. You can set its value based on your needs (Ex: SQLSYSADMINACCOUNTS=”domain\YourUser”), but this is the more generic approach.
      SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS"
    • Add PID and set its value to your product license key. If your setup.exe already comes preloaded with the key, there is no need to add this option to the configuration file.
    • Add IACCEPTSQLSERVERLICENSETERMS and set its value to “True”. This is to required to acknowledge acceptance of the license terms when the /Q (i.e. QUIET) parameter is specified for unattended installations.
      IACCEPTSQLSERVERLICENSETERMS="True"
    • Remove the ADDCURRENTUSERASSQLADMIN parameter. The reason is that this parameter can’t be used when SQLSYSADMINACCOUNTS is specified, and it only applies to Express installations.
    • Remove the UIMODE parameter as it can’t be used with the QUITE parameter.
    • Remove INSTALLSHAREDDIR, INSTALLSHAREDWOWDIR, INSTANCEDIR parameters since we want to install on the default installation directories.
    • That’s it. If you want to change the features that this setup will install, there is no need to go with the full steps again. You can simply change the value for the FEATURES parameter. For example, the features I selected (shown in first screenshot above) will generate FEATURES=SQLENGINE,SSMS,ADV_SSMS in the configuration file.  You can change that based on your needs. The full list of available feature parameters and their descriptions is located here.

After getting the configuration file ready, you’ll need to create a batch file that will run the silent unattended setup. Simply, create a new file  “InstallSQL2008R2.bat” with extension = “.bat” with the following content, and make sure you replace <path to SQL setup folder> and <path to config file> with the proper values.

@ECHO off
echo Installing SQL Server 2008 R2
date/t
time /t
"<path to SQL setup folder>\setup.exe" /ConfigurationFile="<path to config file>"
date/t
time /t

All we’re doing in the script above is running SQL setup.exe and passing the configuration file as an argument to it. You can download both the batch and config files here.

SharePoint CAML IntelliSense


So you’ve been having some pain trying to put IntelliSense into your frequent CAML (Collaborative Application Markup Language) files. For every new XML file you create, you have to go to its properties and then point to the target schema located at ../TEMPLATE/XML/wss.xsd.

If you don’t know what I mean, usually, in order to display IntelliSense in an XML file opened through Visual Studio, we must link the XML file to an XSD. This is done by going to the file properties and linking to the XSD every time we open the XML file in Visual Studio.

One way to avoid having to link to the XSD every time, is to add the file(s) to a Visual Studio project. However, what if you create CAML files so frequently that you don’t want to add them to a Visual Studio project every time?

The best solution would be to load the XSD whenever a new XML file referencing it is opened; and I have the steps to do that!

Under the Schemas folder of the Visual Studio installation folder (Ex: C:\Program Files\Microsoft Visual Studio 9.0\Xml\Schemas), there is a file named Catalog.xml.

Reference wss.xsd from it by adding the following tag:

Make sure that href is pointing to the correct location of the wss.xsd file.

<Schema href="C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/12/TEMPLATE/XML/wss.xsd" targetNamespace="http://schemas.microsoft.com/sharepoint/" />

Enjoy!

Ali B

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: