AutoSPInstaller: Getting Prepared

by wahidsaleemi

This entry is part 1 of 4 in the series AutoSPIn­staller
VN:F [1.9.22_1171]
Rat­ing: 4.6/5 (14 votes cast)

This post will focus on how to get started with AutoSPIn­staller. Along the way, I’ll write some tips that I’ve learned and hope to give read­ers some more details on how to most effec­tively use AutoSPIn­staller. Tobias Lek­man (@tobiaslekman) also has a step-by-step guide on his blog here.

AutoSPIn­staller is a Code­Plex project started by Brian Lalancette (@brianlala). The aim of the project is to pro­vide a set of uni­fied scripts to install Share­Point by fol­low­ing best prac­tices. You can find more on the project by vis­it­ing


  • You have at least one SQL Server (or clus­ter) up and run­ning that will be used for the Share­Point databases.
  • You have a Win­dows Server 2008 R2 server up and run­ning. The server is joined to your domain, has net­work con­nec­tiv­ity and the fire­wall is turned off. No pre-requisites, server roles, or fea­tures are installed yet.
  • You have access to a file share (could be a local drive) where we’ll stage the software.
  • You have (at least) Share­Point 2010 Foun­da­tion. In this exam­ple, I’m going to use Enter­prise edi­tion and addi­tional soft­ware such as Office Web Apps. These are not required though.


  • I’m going to install Share­Point using AutoSPIn­staller and my locale is en-US (United States). 
  • My SQL Server name is SQL2008R2 and I have a default instance installed (MSSQLSERVER).
  • My Share­Point server is called SHARECLOUD and I have set the Pow­er­Shell pol­icy to Unre­stricted (Set-ExecutionPolicy Unrestricted).
  • My install account is svc.spsetup; always use a com­mon install account. This account is a local admin­is­tra­tor on my Share­Point server(s).
  • My file share is mapped to the Z: drive, svc.spsetup (my install account) has Full Control.

Preparing the file share

The first step is to pre­pare the file share. 

Step 1. Extract AutoSPInstaller:

I’m going to start with AutoSPIn­staller. Down­load a copy from and extract the files to your file share.


Step 2. Copy SharePoint bits:

Once extracted, AutoSPIn­staller gives you the proper folder struc­ture. You have to stick to this because the scripts use rel­a­tives paths (for exam­ple: ../../xyz.exe) in many places.

So now, I’m going to take a copy of my Share­Point DVD or extract the con­tents of my Share­Point ISO to the SP2010\SharePoint folder, as shown here:


Tip: If you have an ISO, con­sider using 7-zip to extract its contents.

Step3: Tweak Windows settings (optional)

I do this to pre­vent pop-ups regard­ing untrusted loca­tions. With­out this, your install can’t really be unat­tended because you’ll have to click Con­tinue (or Can­cel) when the warn­ing for Open File Secu­rity shows up. This hap­pens when you copy files from the inter­net (as we’re doing with the AutoSPIn­staller scripts) or from file shares, even a DVD (as with the Share­Point bits).

  • First, make sure you are logged in as the setup account. This is a user-based set­ting. Click Start –> Run –> gpedit.msc –> Press Enter or OK
  • Browse to User Con­fig­u­ra­tion –> Admin­is­tra­tive Tem­plates –> Win­dows Com­po­nents –> Attach­ment Man­ager –> Inclu­sion list for low file types.
  • Add .exe;.ps1;.bat to the list, as shown.


Step 4. Copy SharePoint Prerequisites:

Since I may be installing a large farm, I don’t want to keep down­load­ing the pre­req­ui­sites each time. I want to keep a copy of the files and use the offline instal­la­tion method (faster).

I’m going to go back to and click on the Down­loads tab. On the right-hand side, under “Other Down­loads” there’s a script to down­load all the pre­req­ui­sites. Down­load and save that some­where. I choose to put it in the SP2010\SharePoint folder.


Now run the Pow­er­Shell script. It will ask for a folder, I’ve spec­i­fied cur­rent folder in my screen­shot. The script will use the exist­ing Pre­req­ui­site­In­staller­Files folder or cre­ate one if there isn’t any in the folder you spec­ify. This is how it looks while its running.


When its done, you’ll see all the files down­loaded to the folder you spec­i­fied. They should be in the SP2010\SharePoint\PrerequisiteInstallerFiles folder.

Step 5: Slipstream Updates

Your media may already have Share­Point 2010 Ser­vice Pack 1, mine doesn’t so I’m going to slip­stream it. I’ll also slip­stream the lat­est cumu­la­tive update (CU) that I’ve tested. Find out more infor­ma­tion on Share­Point 2010 at the Update Resource Cen­ter.

First, I need to down­load the update for Share­Point Server 2010 (link). I’ll save this to my desk­top (or a temp folder). Next, I’m going to grab the CU, which should be optional and is intended to fix an issue you’re expe­ri­enc­ing. How­ever, this state­ment posted on the KB for Ser­vice Pack 1 encour­ages installing a CU:

After you install Share­Point Foun­da­tion 2010 SP1 or Share­Point Server 2010 SP1, you must also install the cor­re­spond­ing June 2011 Cumu­la­tive Update refresh package.”

As of this writ­ing, the lat­est is the Octo­ber 2011 CU. How­ever, this con­tains regres­sions that I don’t want to deal with. For a list of known regres­sions, Todd Klindt (@toddklindt) has been keep­ing track on his blog:

I’m going to go with the August 2011 CU. This also means that I don’t need two pack­ages (one for Share­Point Foun­da­tion and one of Share­Point Server). Prior cumu­la­tive updates required both pack­ages. So, the August CU is avail­able here, lets down­load that to the desk­top as well.

In a com­mand prompt, I’m going to type in the following:

officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe /extract:Z:\SP2010\SharePoint\Updates


office2010-kb2553048-fullfile-x64-glb.exe /extract:Z:\SP2010\SharePoint\Updates


If you’d like a walk through, Todd Klindt comes to the res­cue again. View his blog post here:

Step 6: Download Adobe PDF iFilter (optional)

I want to be able to search and index PDF files so I’ll need the Adobe PDF iFil­ter. AutoSPIn­staller can set this up for me. I just need to do a cou­ple things to pre­pare.

  • First down­load the iFil­ter zip from here and place it in the SP2010\PDF folder.
  • Sec­ond, down­load the PDF icon from here and place it in the same folder. Rename it to icpdf.gif

UPDATE: Brian informed me that the PDF func­tion in AutoSPIn­staller will do all of this for you. So, if you want the PDF stuff, just enable it in the con­fig­u­ra­tion. There are no prepara­tory steps needed.

Step 7: Extract Office Web Apps (optional)

If you’d like to install Office Web Apps, down­load and extract the instal­la­tion to the SP2010\OfficeWebApps folder. Office Web Apps is gen­er­ally avail­able to enter­prise cus­tomers, you can’t just go online some­where and down­load it, so if you’re inter­ested talk to your Microsoft licens­ing representative. 

Here, I’ve down­loaded the Office Web Apps installer to my desk­top and am extract­ing it to the SP2010\OfficeWebApps folder.

en_office_web_apps_x64_517488.exe /extract:Z:\SP2010\OfficeWebApps


Since I’m installing Ser­vice Pack 1 for Share­Point, I need SP1 for Office Web Apps too. I down­loaded it from this site, and extract it to the “Updates” folder under SP2010\OfficeWebApps.

wacserver2010sp1-kb2460073-x64-fullfile-en-us.exe /extract:Z:\SP2010\OfficeWebApps\Updates

Step 8: Extract Forefront Protection 2010 for SharePoint (optional)

Sim­i­lar to Office Web Apps, you may not have this or may chose not to use it. Share­Point can use anti-malware soft­ware from sev­eral ven­dors. In this case, I’ve down­loaded Fore­front Pro­tec­tion 2010 for Share­Point to my desk­top and am extract­ing it to the SP2010\ForeFront folder. It’s an ISO in my case, so I’m using 7-zip to extract it. That gives me the setup file. I still need to extract that so, in the com­mand line I type in:

C:\Users\svc.spsetup\Desktop>FOREFRONTSHAREPOINTSETUP.EXE /extract:Z:\SP2010\ForeFront


Step 9: Slipstream Language Packs (optional)

I saved this for last because it can be com­plex and there are a cou­ple ways to do this. How­ever, I’m going to show you my pref­er­ence. I like this method because it ensures that Ser­vice Pack 1 for my lan­guage packs also get installed properly.

For my exam­ple, I’m going to use French and Span­ish lan­guage packs. To make things eas­ier, I’m going to use another Code­Plex project. The Share­Point 2010 Lan­guage Pack Down­loader here. I sim­ply select my lan­guages and the folder.


  • I’ll down­load the orig­i­nal lan­guage packs for each lan­guage I want and then down­load the ser­vice pack for each of those.
  • Next, I need to extract them to a sub­folder that I’ll cre­ate. The sub­folder will be named for the “Cul­ture Short Code” of the lan­guage. For a list of cul­ture short codes see this MSDN arti­cle.
For example: SpanishLanguagePack.exe /extract:Z:\SP2010\Language Packs\es-es
  • Finally, I need to extract the ser­vice pack for each lan­guage into the “Updates” folder for that lan­guage pack.

For exam­ple:

SpanishLanguagePack_SP1.exe /extract:Z:\SP2010\LanguagePacks\es-es\Updates

Here’s how my four com­mands look:


For now, we’ve accom­plished our goal of prepar­ing our file share. From here, we have every­thing ready to install a sin­gle server or 10 servers, in the same farm or mul­ti­ple farms. Our SP2010 folder is now over 4 GB.

In the next post in the series, we’ll con­tinue by con­fig­ur­ing sev­eral files that will help auto­mate our Share­Point deployment.

And as a note, although I don’t mind answer­ing ques­tions or respond­ing to com­ments on my blog, if you have spe­cific ques­tions related to AutoSPIn­staller, its best to use the dis­cus­sion boards there:

I do respond there and so do oth­ers, so your chances of get­ting an answer, more quickly are greater.

AutoSPIn­staller: Get­ting Pre­pared, 4.6 out of 5 based on 14 rat­ings
Series Nav­i­ga­tionAutoSPIn­staller: Configuration

Previous post:

Next post: