Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 6 – Installing SharePoint 2013

UPDATE: SharePoint 2016 development machine

I am doing a collection of blog posts, you can access the other parts of this post below.

Finally after 5 parts of setting up your virtual machine, we can now install SharePoint.

Windows Update.

Ensure your Server is up to date. I have attempted to install the SharePoint 2013 prerequisites twice now trying to write this blog. I found by ensuring all updates were install on the server before installing SharePoint 2013 I had more success.

Each time I got errors when installing the prerequisites. All I did was just run the prerequisites again, 3 times in total before I got a successful installation message.

Installing SharePoint Server 2013 Prerequisites

Select the SharePoint 2013 ISO in the Virtual Machine Settings.

  1. Run splash.hta
  2. Click the Install Software Prerequisites link.
  3. In the Microsoft SharePoint 2013 Products Preparation Tool dialog, click Next.
  4. Accept the License Terms,
    and click Next.
  5. The prerequisites for SharePoint 2013 will be installed and set up. When it has completed, you might need to reboot the machine. Please note I had to try installing the prerequisites 3 times before it fully worked. Each time I got an error message saying something could not be installed properly. But by running it again, it passed the first error and then had another. I kept running it until I had no more errors. I’m not 100% sure why this happened, but it did sort itself out. Click Finish.

  6. Although all prerequisites required by SharePoint 2013 are installed, Microsoft recommends you installing the following hot fixes if not already installed. Framework 4.5 that resolves an ASP.NET Race Condition Issue in Windows 8, Windows RT, and Windows Server 2012.


Installing SharePoint Server 2013

  1. Run splash.hta
  2. Click Install SharePoint Server.
  3. When prompted Enter your Product Key. Click Continue
  4. Accept the License terms. Click Continue.
  5. Accept the default file location (Unless you have reason not to). Click Install Now.
  6. When it has finished. Run the configuration wizard by clicking Close.
  7. On the Welcome to SharePoint Products click Next >.
  8. Accept the dialog warning that services may have to be started or reset during configuration.
    Click Yes.
  9. On Connect to a server farm, select Create a new server farm. Click Next >.
  10. On the Specify Configuration Database settings
    1. Database Server: SQL2012
    2. Database name: SharePoint_Config
    3. Username: cannonfodder\SP_Farm
    4. Password: Pa55w0rd
      Click Next.
  11. On Specify Farm Security Settings put the Passphrase as Pa55w0rd. Click Next >.
  12. On Configure SharePoint Central Administration Web Application tick Specify port number. Type in the number 10000. Select Negotiate (Kerberos) for security settings. Click Next >. Accept the warning about choosing Kerberos. You will set up the SPN later.
  13. On the final page Completing the SharePoint Products Configuration Wizard it will display a summary of what you have selected. Click Next >
  14. When the installer has finished, you will be presented with Configuration Successful. Click Finish. Internet explorer will open Central Administration allowing you to complete the installation.


Configuring SharePoint 2013

First thing we should do is set Kerberos SPN for Central Adminsitration.
Note: On a single machine like the one we are building, there is no real need to use Kerberos. Kerberos helps us get over the double hop issue. However, you never know if you will use multiple servers in the future, and it’s not too much work to enable Kerberos. Also another skill to learn.

  1. Open a Command prompt in Administrative mode.
  2. Type setspn –S HTTP/cannonfodderser:10000 cannonfodder\SP_Farm
    setspn –S HTTP/cannonfodderser.cannonfodder.local:10000 cannonfodder\SP_Farm
  3. To ensure it has been set up type setspn –L cannonfodder\SP_Farm

Now we will continue configuring SharePoint in the browser.

  1. Open up a web browser (if not already open) and browse to http://cannonfodderser:10000
  2. At the bottom of the home page of central admin click the Configuration Wizards

    Now most of the time when I’ve created SharePoint machines in the past, I’ve never used the Configuration wizard, I like to set up each service one at a time. However for simplicity, I’m going to use it this time. I will write further blogs in the future (hopefully) that will show you how to set up a given service from scratch.
  3. On the Configuration Wizards page, click Launch the Farm Configuration Wizard.
  4. On the Welcome page, click Start the Wizard.
  5. On the Services page, select Create a new managed account.
    1. Put the UserName as cannonfodder\SP_Services
    2. Password as Pa55w0rd
    3. Untick Access Services 2010 and App Management Services. The reason for this is because Access Services 2010 is included for backward compatibility and isn’t needed in new installations unless you are migrating solutions using Access Services 2010 from SharePoint Server 2010. The App Management will be created manually later in the next blog post.
    4. Click Next. This will take a long time to process.

There you have it, SharePoint 2013 installed on your machine. There are still some steps to set up, which I will discuss in the next few blogs.

  • Hosting Apps
  • My Sites and User Profiles
  • Workflow


2 thoughts on “Building Your SharePoint 2013 development machine on Windows Server 2012 – Part 6 – Installing SharePoint 2013

  1. Hi Paul,

    First of all great blog you have hear. I’m following it step by step and it’s working out great.
    I do have a minor problem under Step 6 “Configuring SharePoint 2013?. I can’t log into http://cannonfodderser:10000 using IE. I tried using cannonfodder\SP_Farm and cannonfodder\Administrator, but it just doesn’t accept my login and password.

    But I can login using either of those accounts using the same URL if I use FireFox or Chrome. So I’m guessing it’s a setting in IE along with using Kerberos.

    Any thoughts?

    • Hi pdmlink91,
      Thank you for following my blog, it nice to hear that someone else is using it.

      I had exact same problem as you, however I thought I got it further along, which is why you should find the solution in part 7 under the heading “Update Internet Explorer to Bypass the URL to log in automatically”. The mini explanation is also there.

      Good Luck

Comments are closed.