AutoSPInstaller: Preparing the Base Media

This post is part of a series covering how to configure and run AutoSPInstaller, a set of scripts that can be used to automatically install SharePoint. In this post, we will look at the second step: preparing the base media that will be used to install SharePoint.

Update: This post has been running for years and the AutoSPInstaller team now has an official site with guides, Q&A and an automated, browser-based AutoSPInstaller GUI . You can find it at

More posts in the series:

  • Automated SharePoint Installations: Step-by-step (Overview)
  • Prepare Server Hardware, Software and System Accounts
  • Preparing the Base Media
  • Prepare for Unattended Installation
  • Prepare the Scripts
  • Executing the Scripts, Post-Execution Tasks


    Preparing the base media

    The installation media is compiled from the original SharePoint DVD or image together with service packs, hotfixes, language packs, Office Web Apps media and Forefront antivirus media.

    First, download the following files and packages:

  • Latest release of AutoSPInstaller from CodePlex
  • Pre-requisites downloader utility script
  • SharePoint 2010 or SharePoint 2013 either from DVD or ISO image
  • For SharePoint 2010, SharePoint 2010 Service Pack 1 (in case your DVD or ISO image is not already slipstreamed)
  • (Optional) Download the language packs you require using the SharePoint Language Pack Downloader from CodePlex
  • For SharePoint 2010, Adobe PDF iFilter and the official Adobe PDF icon
  • (Optional) SharePoint 2010 Cumulative Hotfix (should be used when your farm or setup requires such an update)
  • (Optional) Forefront for SharePoint from DVD or ISO image
  • (Optional) Office Web Apps from DVD or ISO image (for SharePoint 2010) 


    Extract the SharePoint media locally

    We must create a new installation media by using the files and packages mentioned above. I will combine these on my local drive and copy these later to a network location or external drive for safe-keeping.

    Extract the latest release of AutoSPInstaller from CodePlex into the local folder c:\SP. Now, either download the SharePoint ISO from MSDN subscriber downloads or copy them from the installation media. I extract the files from my ISO into the folder c:\SP\SharePoint using 7-zip.

    Enabling Installation on Windows 7 for SharePoint 2010

    For SharePoint 2010, the server will not install on Windows client machines unless you tweak the installation files. This is obviously only done for development machines. AutoSPInstaller is already prepared to enable client installs as the property <Setting Id="AllowWindowsClientInstall" Value="True"/> is present in the c:\SP\AutoSPInstaller\config file.

    Read more: Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008
    SharePoint 2013 does not allow installations on a Windows client machine.

    Download Pre-Requisite Files

    The SharePoint installer will download pre-prequisite files from the internet prior to installation. Not only does this take a long time but most servers I install are behind a firewall and do not allow direct access to the internet.Run Download-All SP2010 Prereqs.ps1 and add these files to



    Office Web Apps

    This is only applicable to SharePoint 2010 installations. OWA is installed on a separate server within SharePoint 2013 farms.

    Office Web Applications are downloadable from MSDN for enterprise customers.

    • Extract the contents of the Office Web Apps ISO into the folder c:\SP\OfficeWebApps.
    • Open the file c:\SP\AutoSPInstaller\config-OWA.xml and add your product key under the PIDKEY entry.

    Forefront Antivirus

    Forefront provides antivirus scanning for files on your front-end servers. To include this feature in your farm, extract the ISO contents into the C:\SP\ForeFront folder.

    Adobe PDF Files

    You can pre-download the Adobe PDF iFilter from here. The official PDF icon is available here.

    Place the .zip (or the extracted .msi) in the c:\SP\PDF folder along with the icpdf.gif, and AutoSPInstaller can automatically install them in order to be able to index PDF files and display the icon properly in SharePoint search results, document libraries, etc.

    Slipstreaming Service Packs and Hotfixes


    There is currently an open issue where slipstreaming of cumulative updates for SharePoint 2010 from August 2012 and onwards will fail. If you are planning on installing this CU or later, then you must apply this manually afterwards.

    The issue *should* be fixed with the release of SP2.

    More info

    Some media have Service Pack already added. If not, you should “slipstream” it in, which means extracting the update files and adding them to the media. This makes SharePoint automatically apply the updates during the base installation.

    After you have downloaded Service Pack 1, open a command prompt and run the following command:


    If needed, slipstream the latest/required hotfix by downloading the cumulative update package. Note that you have to slipstream SP1 first, but hotfixes are cumulative after that, i.e. you only have to download the latest one. Extract the contents (for example) as:


    Integrating Language Packs

    The SharePoint language packs allows the system to automatically detect the user language and switch all standard menus and command texts to that language. To install these, I use the SharePoint Language Pack Downloader from CodePlex


    Select “SharePoint Server 2010 Language Pack” and specify the location as “c:\SP\LanguagePacks”. Once downloaded, place the file (as is) inside a folder named after the language/culture. Do not unpack the language pack itself. For example, I name the Swedish language pack “ServerLanguagePack_sv-se.exe” and place it in “c:\SP\LanguagePacks\sv-se”.

    Download the service packs for the specific language and extract the file contents inside a subfolder inside each language/culture folder named updates using

    LanguagePackServicePackFile.exe /extract:c:\SP\LanguagePacks\sv-se\Updates

    The folder structure would, for example, look like this: