By Softlanding

How to Deploy SharePoint 2010 & 2013 using PowerShell

September 29, 2017


First of all, I would like to start by thanking Brian Lalancette and many others for their great work on the AutoSPInstaller Project.

AutoSPInstaller is a PowerShell based tool which automates the deployment of SharePoint 2010 and 2013. It has the ability to granularly configure most aspects of the farm and includes some interesting features such as: centralized farm deployment, granular database naming, XML configuration and more.

AutoSPInstallerGUI is a .NET Application which we built that assists in configuring the AutoSPInstallerInput.xml. If you haven’t seen the insides of it, it is a very lengthy XML file with tones of configuration. It takes a significant amount of time and knowledge of the script in order to configure successfully. Furthermore, if you are as clumsy with typing as I am, you will make a few mistakes. Something as simple as forgetting a quote or adding an extra space could cause issues, without a strong understanding of PowerShell and XML you may spend hours trying to fix it.

The goal of AutoSPInstallerGUI is to simplify this process. It will assist you with all of the configuration including some of the more complicated configurations such as adding additional Web Applications or Site Collections. Furthermore, there is a large amount of code just to make sure that all of the data is valid.

How to:

  • Create the following domain accounts (They can be named anything):
    • SP_Farm (Farm Account)
    • SP_CacheSuperUser (Object Caching Account)
    • SP_CacheSuperReader (Object Caching Account)
    • SP_Services (Service Application Account)
    • SP_PortalAppPool (Portal Application Pool Account)
    • SP_ProfilesAppPool (MySites Application Pool Account)
    • SP_SearchService (Search Service Application Pool Account)
    • SP_SearchContent (Search Content Access Account)
    • SP_ProfileSync (User Profile Sync Account)
      • Requires Replicate Directory Changes permission on the domain with which you'll synchronize
  • Optionally for Enterprise Service Applications (Can be a single account)
    • SP_ExcelUser (Excel Unttanended ID)
    • SP_VisioUser (Visio Unattended ID)
    • SP_PerfPointUser (Performance Point Unattended ID)
  • Download the latest version of the AutoSPInstallerGUI Here
  • Download the latest version of the AutoSPInstaller Here
  • Assuming that we are going to use this on SharePoint 2010 and that all of your SharePoint servers have Internet access
    • There is more work required to place all the files in the correct locations if there is no internet access
  • Please Note: The process is almost identical for SharePoint 2013
    • Disable Windows Firewall or allow the following ports through the firewall, 22233,22234,22235 and 22236.
      • Causes issues with Distributed Cache
    • I would recommend enabling the Auto Admin Login in the GUI as 2013 requires a number of reboots
    • Make sure that all the Web Applications use Claims Based Authentication as Classic Based Authentication is now obsolete
  • Extract the contents of the anywhere ie D:\Temp\
  • Place the contents of the SharePoint iso in D:\Temp\SP\2010\SharePoint\
  • At this point you should have a folder structure similar to this
    • \SP\2010\
      • ForeFront
      • LanguagePacks
      • OfficeWebApps
      • PDF
      • SharePoint (Place the SP2010 binaries here)
    • SP\2013\
      • ForeFront
      • LanguagePacks
      • PDF
      • SharePoint (Place the SP2013 binaries here)
    • SP\AutoSPInstaller
      • AutoSPInstallerConfigureRemoteTarget.ps1
      • AutoSPInstallerFolderStructure.txt (Explains the folder structure further)
      • AutoSPInstallerFunctions.ps1
      • AutoSPInstallerFunctionsCustom.ps1
      • AutoSPInstallerInput.xml (Example XML Configuration, do not edit this one. Leave it for reference)
      • AutoSPInstallerLaunch.bat (Drag and Drop the XML configuration into this file to start the installation)
      • AutoSPInstallerMain.ps1
  • Please Note: You can keep both SharePoint versions binaries in the directories. The XML specifies which version will be installed.


  • At this point we can begin configuring AutoSPInstaller using the GUI
  • Extract the contents of the to any location ie D:\Temp\SP\AutoSPInstaller
  • Run AutoSPInstallerGUI.exe
    • Optionally, you can drag and drop the AutoSPInstallerInput.xml into the executable
  • To Load the Configuration
  • Click on File then Load XML File
  • Browse to the AutoSPInstaller dir ie D:\Temp\SP\AutoSPInstaller
    • Select the AutoSPInstallerInput.xml
  • At this point complete all the configuration in the GUI
    • Please Note: Almost all of the controls have a Tool Tip associated with them
    • Simply highlight the control and the Tool Tip will appear
  • To Save the Configuration
    • Do not overwrite AutoSPInstallerInput.xml, keep it as a reference file
    • Click on File then Save AS XML File
    • Save the file as a new file name



  • Copy the SP directory to all of the SharePoint Servers
    • Optionally, the installation can be ran from a File Share
  • Make sure that the logged on user has Local Admin on all the SharePoint Servers and SQL Permissions dbcreate and securityadmin
  • Browse to the AutoSPInstaller dir ie D:\Temp\SP\AutoSPInstaller
  • On each SharePoint Server (One at the time):
  • Drag the new XML file ie Farm A.xml into the AutoSPInstaller.bat
  • Please Note: If you double click on AutoSPInstaller.bat, it will use the AutoSPInstallerInput.xml config file by default
  • AutoSPInstaller will now run, it will create a file on the Desktop which will contain the output of the PowerShell window and any errors

If you have any questions please leave a comment.


Tags: Share Point SharePoint 2010 2013 deploy deployment script scripted automated automation installation configure configuration wizard Install SharePoint 2010 SharePoint 2013.

Loading Conversation