SharePoint 2013 Installation Guide – Development Environment

SharePoint 2013 Installation Guide – Development Environment

In this blog post I have document the steps for creating your own SharePoint 2013 development environment.

Unlike SharePoint 2010, you can’t install domain controller and SharePoint 2013 in same server if you would like to use workflow manager and office Web Apps. If you would like to install Workflow manager and Office WebApps then we need at least two virtual machines, one with domain controller and another with SharePoint 2013 and SQL Server.

Note: If you don’t have MSDN licenses then you can sign up for preview licenses and in most cases those will be good for 3 to 6 months.

Domain Controller Virtual Machine:

First step is to create a domain controller virtual machine (VM1).  Operating system for Domain Controller VM can be Windows Server 2003, Windows Server 2008 or Windows Server 2012. Once you install the operating system, configure Active Directory Domain Services. You can find the steps here.

You can give nice domain name for your test setup. For example:

Note: We don’t need lot of RAM for Domain controller. 512MB or 1GB is more than enough.

SharePoint 2013 Virtual Machine:

Once the domain server (VM1) is up and running, create virtual machine for SharePoint 2013 server (VM2).

Hardware and Software Requirements:

Following is the summary of the hardware and software requirements for SharePoint 2013 server.  For detailed hardware and software requirements please check this out.

  • RAM: 8 GB (Minimum)
  • Hard disk Space: 80GB
  • Processor: 64bit and 4 core
  • Operating System: 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter
  • SQL: 64-bit edition of Microsoft SQL Server 2012 or 64-bit edition of SQL Server 2008 R2 Service Pack 1

Note: If your domain controller VM has required operating system for SharePoint 2013, you can make copy of that VM to install SharePoint 2013. You have to run sysprep on the copied VM. Sysprep can be run from “C:\windows\System32\sysprep”. Sysprep will wipe out SID, machine name and custom network settings. Also you have to re-activate the windows.

Setup up internal network between Domain Controller and SharePoint 2013 Server:

After operating system is installed on the VM2, setup the internal network between VM1 and VM2.You can assign the static IP addresses for VM1 and VM2 as follows.

VM1: Use the Following IP Address Internet Protocol Version 4 (TCP/IPv4) settings
(feel free to use the ip addresses of your choices):

  • IP Address:
  • Subnet mast:
  • Default Gateway:
  • Use the Following DNS Server Addresses:
    • Preferred DNS Server:

VM2: Use the Following IP Address Internet Protocol Version 4 (TCP/IPv4) settings:

  • IP Address:
  • Subnet mast:
  • Default Gateway:
  • Use the Following DNS Server Addresses:
    • Preferred DNS Server:

Check if you can ping VM1 from VM2 to verify both the VMs are on internal network.

Join VM2 to Domain:

Follow steps mentioned here to attach VM2 to the domain ( . You can give the name SharePointLab01 to this VM.

Create Service Accounts:

All the service accounts are required to be domain accounts. Todd O. Klindt has nice blog post on service accounts. The steps to create new domain users are here. . When choosing service accounts, consider the principle of least privilege. The service account should have exactly the privileges that it needs to do its job and no more privileges. Create the following service accounts in VM1.

  • sharepointab\sp_sql_server
  • sharepointlab\sp_sql_agent
  • sharepointab\sp_admin
  • sharepointab\sp_farm

The following service accounts can be created in VM1 as and when needed.

  • sharepointab\sp_content
  • sharepointab\sp_serviceapps
  • sharepointlab\sp_app_pool
  • sharepointlab\sp_web_app
  • sharepointlab\sp_service
  • sharepointlab\sp_crawl
  • sharepointlab\sp_ups
  • sharepointlab\sp_bi

Make “sharepointab\sp_admin” local admin on VM2.

Install SQL 2012 Server on VM2:

Login to the VM2 using “sharepointab\sp_admin” account and run the setup.exe located inside SQL Server 2012 installation files.

Click Installation on the left-hand side of the SQL Server Installation Center.


Select “New SQL Server stand-alone installation or add features to an existing installation”.

Installer will check for issues before installation. If there are no errors, then you will get following page.


On the Setup Support Rules page, click OK.

You can skip product update.

Next page will prompt to enter the license key. Enter evaluation and click Next.


Accept the license terms and click Next.

The setup will then start installing files as shown below.


After that “Setup Support Rules” will check and identify if there is any problem that can occur during the installation. Click Next if there are no failures.


On the Setup Role page, select SQL Server Feature Installation and click Next.


On the Feature Selection page, check the following options and click Next.

  • Database Engine Services
    • Full-Text and Semantic Extractions for Search
    • Reporting Services – SharePoint
    • Reporting Services Add-in for SharePoint Products
    • Client Tools Connectivity
    • Client tools backward compatibility
    • Management Tools Basics
      • Management Tools Complete


If the installation fails because of .NET Framework 3.5 service pack 1 then Use the Server Manager to add the feature “.NET Framework 3.5.1. Features”. The steps to add the feature are found here


If there are no problems, Click Next on the following page.


In the Instance Configuration, select the default instance and click Next.


Click Next on the Disk Space Requirements page.

On the Server Configuration page, use the SQL service accounts “sharepointlab\sp_sql_agent” for services SQL Server Agent and “sharepointlab\sp_sql_server” for SQL Server Database Engine. Enter their respective passwords and click Collation. Select collation “Latin1_General_CI_AS_KS_WS” (Latin1-General, case-insensitive, accent-sensitive, kanatype-sensitive, width-sensitive) and then click next.



On the Database Engine Configuration page, add the SQL server Admins. To do that, on the Server Configuration tab, click Add. After adding SQL server admins click Next.


Click Next on the Reporting Services Configuration Page.

Click Next on the Error Reporting Page.

Click Next on the Installation Configuration Rules Page.

Click Next on the Ready to Install Page.

Installation will take some time depending on the speed/performance of the VM2.


After completion, setup will prompt to restart the machine as shown below. Click OK and then Close.


Restart VM2 to complete the installation.

Open SQL Server 2012 Management studio and grant “sharepointlab\sp_admin” SQL Server Roles “dbcreator”, “securityadmin” roles. The steps to add server roles are here.

Install SharePoint 2012 Server on VM2:

Login to VM2 using “sharepointlab\sp_admin” account and run the splash.hta located inside SharePoint Server 2013 installation files.

First install all prerequisites. During this process the VM2 will need access to internet. The VM2 will restart several times. When all the prerequisites are installed you will see following page.


Click “Install SharePoint Server”.


Enter License Keys.

Select Complete Installation.


During installation, you will get the following page.


When the installation is complete, select “Run the SharePoint Products Configuration Wizard now” checkbox and click Close.


Run the SharePoint Configuration Wizard (Gray Wizard).


Select “Create a new server farm”.


Specify the Configuration Database settings and Database access account.


Specify Farm passphrase. Note down the password at secure location which we will need in future. It is impossible to retrieve the farm passphrase. You can just reset it. The instructions are given here.

Specify the port number for central administration web application. Avoid using port 8888, because by default fiddler uses the same port and you will need to change that if you need to use fiddler to troubleshoot any issues.

Click next and you will see the configuration settings that will get applied.


Click next and the configuration wizard will run for 2-5 mins.


Known Issue:

If the configuration fails at step 3 with below error message


We need to change the “max degree of parrallelism” of the SQL 2012 Server. The steps are mentioned here.

Login to the SQL server with SQL service account (sharepointlab\sp_sql_server) and change the “max degree of parallelism” to 1 using following SQL script.

sp_configure ‘show advanced options’, 1;
sp_configure ‘max degree of parallelism’, 1;

Open the SQL 2012 Management Studio. Open a new SQL query and type/paste above commands.


Execute the query.

Till this point, config wizard has already created “SharePoint_Config” database. We need to delete that and re-run the configuration wizard.

If there are no errors during configuration, you will get the Configuration Successful page.


Clicking finish will launch the Farm Configuration Wizard (White Wizard). Using Farm Configuration Wizard, we can create the service applications. It is recommended to create service applications as and when needed and not to create them using Farm Configuration Wizard.

By default, SharePoint 2013 Configuration wizard (Gray Wizard) creates following Service Applications.

  • Application Discovery and Load Balancer Service Application
  • Security Token Service Application


Following are the screen shots of databases before and after SharePoint 2013 Configuration Wizard.

Databases before SharePoint 2013 Configuration Wizard:


Databases after SharePoint 2013 Configuration Wizard:


At this point you have successfully created the SharePoint 2013 development environment. You can now create the Web Application, create site collections and different service applications. If you are a developer then you can install the Visual Studio 2012.

About pgbhoyar

Prashant G Bhoyar is a Microsoft AI MVP and Microsoft Certified Professional. He currently works as a Senior Solution Architect at WithumSmith+Brown, P.C. (formerly Portal Solutions), one of the top 30 advisory and accounting firms in the United States. He is a trusted advisor and Subject Matter Expert in Intelligent Business Process Automation, development and post-implementation adoption of complex custom solutions in AI, Machine Learning, Bots, Azure, Office 365, and SharePoint. Prashant has supported a multitude of government agencies and non-profit organizations in the Washington D.C. metropolitan area. Prashant is the co-author of the book “PowerShell for Office 365 “and is the technical reviewer of the book "Pro SharePoint 2013 Administration." He serves on the leadership committee for the Azure Data Fest conference, Artificial Intelligence Fest conference, Artificial Intelligence and Machine Learning User Group, DC Metro Office 365 User Group, SharePoint Saturday Baltimore event, and SharePoint Saturday Washington DC event. He is a renowned international speaker and actively speaks at technical conferences, most recently in India, Canada, England, Bangladesh, Peru , Washington DC, Austin, New York, Chicago, Seattle, New Orleans, Baltimore, Philadelphia. Fun fact??, Prashant is a recipient of the "Antarctic Service Medal of the United States of America" for his outstanding service in Antarctica.
This entry was posted in SharePoint 2013, SharePoint 2013 Administration and tagged , , , , . Bookmark the permalink.

5 Responses to SharePoint 2013 Installation Guide – Development Environment

  1. Good article! We will be linking to this particularly great article on our site.
    Keep up the good writing.


  2. Lita says:

    Terrific article, keep up the good work mate.


  3. Kusum Rawat says:

    This is a very good article. However, i can i get more information when installing SQL farm using remote SQL?


  4. Wow I like this article a lot and it easy to understand


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s