My SharePoint 2013 Lab and Dev Environment – Part 1

2013lab-hyperv

I’ve been working on my SharePoint 2013 lab environment for about a month now and I’m while still tinkering with it I’ve gotten to the point that I’m ready to start blogging about my process and my results. This will be the first post in the series.

The Physical Rig

For starters I’m running Windows 2012 on all the machines and using Hyper-V.

  •  HP z420 Workstation
  • 64 GB RAM
  • 3.60GHZ Xeon CPU
  • 240GB SSD (Primary Drive) – OS (Plan to move the SP VM here if necessary in the future)
  • 500 GB (Secondary Drive) – ISO Storage and VMs
I went ahead and joined the Hyper-V server to the corporate domain so that I can easily manage the machines through the Hyper-V Administration tools directly from my laptop.

Virtual Server Roles

I decided to go with a minimal development farm in order to strike a balance between real world and being proficient during development tasks. So I decided on the following:

  • Virtual Server #1 (8GB Ram, 1 Virtual CPU)
    • DC
    • DNS
    • Exchange
    • Certificate Authority
  • Virtual Server #2 (2GB Ram, 1 Virtual CPU)
    • WAC (Web Application Companions… previously called OWA)
  • Virtual Server #3 (16GB, 4 Virtual CPU)
    • SQL Server 2012
    • SharePoint Server Enterprise 2013 (Single machine… search, workflow, etc.)

I decided to keep SharePoint isolated so that it would be easy for Visual Studio deployment and debugging but also to keep the components modular. This way I can spin up a SharePoint 2013 Standard Farm or a SharePoint 2013 Foundation Farm and keep the other infrastructure exactly the same.

Network Configuration

This actually took a little bit to get correct as I wanted my lab to be able to communicate with the outside world over the corporate network but also be isolated to it’s own subnet. Then later I had to add one more virtual NIC thanks to some SSL requirements that I’ll talk more about in a later post. Little disclaimer here… I’m a code monkey by trade and some of this network configuration was a bit outside of core wheel house so no promises if there is a better way of doing this.

Our final configuration is going to look something like this:

Hyper V Server

NIC1 (Lab Network)

  • IP Address – 5.5.5.5
  • Subnet mask – 255.255.255.0
  • Gateway – blank
  • DNS – blank

NIC1 will serve as the gateway for our internal network between our Hyper V virtual servers.

NIC2 (External Network)

  • Obtain automatically via DHCP
We take the defaults here because we want our second IP to be routable to the corporate network just in order to access the outside internet and have access to domain resources. All of our servers will have a secondary NIC using DHCP for direct access to the network.

Domain Controller and Exchange

NIC1 (Lab Network)

  • IP Address – 5.5.5.6
  • Subnet mask – 255.255.255.0
  • Gateway – 5.5.5.5
  • DNS – 5.5.5.6
NIC2 (External Network)

  • Obtain automatically via DHCP

Office Web Apps (WAC) Server

NIC1 (Lab Network)

  • IP Address – 5.5.5.7
  • Subnet mask – 255.255.255.0
  • Gateway – 5.5.5.5
  • DNS – 5.5.5.6
NIC2 (External Network)

  • Obtain automatically via DHCP

SharePoint and SQL Server

This is where the configuration gets a bit different due to the SSL requirements. Since we’re going to end up with two wildcard certificates (One for our SharePoint sites and one for our SharePoint Apps) we need to be able to bind a wildcard certificate to each of those IP addresses.

NIC1 (Lab Network)

  • IP Address – 5.5.5.8
  • Subnet mask – 255.255.255.0
  • Gateway – 5.5.5.5
  • DNS – 5.5.5.6

We’ll use this for our intranet, my sites, etc.

NIC2 (Internal Network)

  • IP Address – 5.5.5.9
  • Subnet mask – 255.255.255.0
  • Gateway – 5.5.5.5
  • DNS – 5.5.5.6
We’ll use this for our SharePoint apps. We’ll cover more on this later.
NIC3 (External Network)

  • Obtain automatically via DHCP

Next time we’ll talk about the Installation and Configuration of the base SharePoint features.

I'm a public speaker and the Chief SharePoint Architect for Eastridge, a Microsoft Gold Partner specializing in SharePoint and custom application development in Winston-Salem, NC. I focus on the SharePoint platform with a specialty in Information Architecture, Publishing and Best Practices.

Got something to say? Go for it!