ExtranetDC Server Setup

 

This is part of Series Main: Comprehensive SharePoint 2013 Development Environment Installation and Configuration

Overview

This step is optional. If you are planning to install and test UAG then you will may follow this article to establish a separate Domain for your extranet users. Beware there are other alternatives such as ADFS and SQL Server based User identity providers and is beyond the scope of this blog. 

Installation Steps

Like we installed and configured the primary Domain Controller you can follow below steps to install and configure an Extranet DC on separate Windows 2012 server instance. First start by first assigning Static IP.

Install AD and DNS

 

Configure Password Policy

Install CA

Import-Module ServerManager
Add-WindowsFeature Adcs-Cert-Authority -IncludeManagementTools
Add-WindowsFeature Adcs-Enroll-Web-Svc -IncludeAllSubFeature -IncludeManagementTools
Add-WindowsFeature ADCS-Web-Enrollment -IncludeAllSubFeature -IncludeManagementTools

From <http://www.telnetport25.com/downloads/scripts/windows2012/instCertRoles.ps1>

Configure DNS

Restart DNS Service

Installation and Configuration of Windows 2012 Domain Controller

 

This blog is part of Series : Comprehensive SharePoint 2013 Development Environment Installation and Configuration

Overview

• Created a new instance of Windows 2012 server.
• Renamed the server as DC.
• The purpose of this server is to serve as new Domain Controller, DNS Server and CA

Steps

First assign Static IP to the network card, this is important since this server will play a role of DC and DNS Server.

Install AD and DNS

From the Server manager choose to add the new server role.

Choose your Domain name appropriately, I have very typical namespace below.

 

Here I have enter the same subdomain name space to maintain the same name space for the NetBIOS. This is the domain name that users will login against. having different sub domain and NetBIOS will later require additional steps to get your User Profile import setup.

At this stage AD Domain and DNS Server install completed.

Configure Password Policy:

I have simplified the password policy for my purpose to since this is not a production DC.

Install CA

Run the below Powershell from the standard PowerShell command under Administrator context.

Import-Module ServerManager 
Add-WindowsFeature Adcs-Cert-Authority -IncludeManagementTools 
Add-WindowsFeature Adcs-Enroll-Web-Svc -IncludeAllSubFeature -IncludeManagementTools 
Add-WindowsFeature ADCS-Web-Enrollment -IncludeAllSubFeature -IncludeManagementTools

From <http://www.telnetport25.com/downloads/scripts/windows2012/instCertRoles.ps1>

Configure DNS Forwarders

Open DNS Server and locate the Forwards as below

Switch to Interfaces tab and select only your server IP.

 

Now validate that your Name server resolves as below:

Restart your DNS Server

This completes AD/DNS/CA.

Server Platform Readiness

 

This blog is part of Series : Comprehensive SharePoint 2013 Development Environment Installation and Configuration

Overview

In order to install all the servers and toolset listed under the Work plan (under the main article), first I had repurposed a previously build VM Rig. Find out more on this rig build out here : Coming soon….

Virtualization selection:

• Hyper-V
  • Previously I had tried Hyper-v with Windows 2008 version, but found the networking was more complex for my networking knowledge.
• VMWare Free Server
  • This is lighter version of the bare metal hypervisor ESX.
  • Gave couple of retries for the VMWare Server Free version, but looks like this product is going out of support and no more updates.
  • I also had trouble with the VMWare ESX Server had trouble identifying my RAID, for lack of driver support.
  • In the end I had abandoned this approach as well.
• VMWare Workstation
  • Easy to use and much better and simpler networking support.
  • Much faster than Hyper-V.
  • Since already had personal license, finally I went with VMWare Workstation.

VM Host Server Readiness

• The VM Host was installed with Windows 7
• VMWare Workstation (Whatever latest is)
• Prepared baseline Windows 2008 and Windows 2012 Server with Sysprep

VM Instances

• Instantiated following VM instances based on the Linked Clones on my VMWare Workstations.
• Renamed each server as below names for simplicity.
• I did not join each of these servers to the domain yet.
• Follow nest steps on network configuration in the next blog post and then joined to the domain.

1. SP2013WFE
2. SP2013APP1
3. SP2013APP2
4. OWA2013
5. Exchange2013
6. UAG2010 (Optional)

At this stage each of the above server instances are ready with name but not joined to the domain. Have logged in to each server as local administrators to follow the next step.

Comprehensive SharePoint 2013 Development Environment Installation and Configuration

 

Overview

(*This topic was presented at SharePoint Saturday Silicon Valley, June 22nd, 2013 )

(Look below for list of blogs related)

Over the years working with SharePoint we all have built out various SharePoint related environments for the purpose of Development. In the past (Prior to SharePoint 2013) we could install MOSS 2007 and SP 2010 right in our Lap Top/Desk top over Windows 7.

Alternatively we could spin up a VM over VMWare workstation and run right in our lap top.

All of the above combination worked very well and we were on our happy path to build, learn and demo.

So initially I did the same with the new SharePoint 2013. But like we all know installing on Client OS (Win 7/8) is no more supported.

Next step was to start with a local VM in VMWare Workstation. Sure I got all of that. But I had faced a significant processing and memory problems. First for lack of processing and memory capabilities on a Lap Top type of device and second the SharePoint 2013 platform now introduces quite number of services that are processor and memory hungry.

 

On that account we have few options:

• All Inclusive Single Server Farm under your Corporate Network (Yes, you need an AD domain to install SP 2013).
• You could use a Workstation class server or your favorite VM software.
• You could do all in one Server with minimum of 24GB RAM and a Quad Core proc.
• For single server installations I recommend adopting AutoSPInstaller PowerShell script based codeplex solution. If you have your SQL Server ready, you could get your SharePoint server install in about hour. But for the beginners with this tool a ramp-up time is needed. (You can reference my other blog on this topic listed below:

AutoSPInstaller (http://autospinstaller.codeplex.com)

AutoSPInstallerGUI (http://autospinstallergui.codeplex.com)

Using AutoSPInstall to install SharePoint 2013 (http://rajeshagadi.blogspot.com/2013/03/using-autospinstall-to-install.html)

• You will still need additional Servers if you will need to install Office Web Apps 2013. The new Office Web Apps 2013 will not install on SP 2013 servers.

Goals

So now being a consultant, I cannot carry my big rig everywhere, so I set out with below goals that would server me well:

• Independent Development Environment
  • So that I can develop independently without the need to share with other team members.
• Comprehensive Setup for Development Opportunities
  • Have all the possible development opportunities available such as standard SharePoint development, client side programming, Business Intelligence to name a few.
• Modern Software (2012+2013 Editions)
  • Utilize all the new 2012 and 2013 wave of products so that I am learning the new tools.
• Ability to Make and Break
  • As we all know, there will be many situations where things won't just work, hence I would want to be able to break and re-make.
• Repeatability
  • So that I can re-try installing and try different approaches.

Work Plan

With the above goals, I started crafting the work plan as below:

• Windows 2012 AD, DNS, CA,
  • I will need an Active Directory to establish an AD domain.
  • DNS server to facilitate my SharePoint sites
  • Certificate authority to serve the Certificates
• Exchange 2013
  • To test the various SharePoint Email capabilities
• SQL Server 2012 with BI Components
  • Of course a SQL Server for serving the SharePoint
  • But also to build out the BI Stack to develop and test the SharePoint and SQL Server BI features
• SP 2013 with BI Support
  • To build the SharePoint farm that is SQL Server BI Capable.
• OWA 2013
  • The new Office Web App 2013 to integrate with the SharePoint platform.
• Workflow Manager
  • To build out the new SP 2013 Workflow capabilities
• VS.Net 2012 (TFS 2012)
  • VS.Net 2012 for the development purpose and accommodate all the new project templates as made available by Microsoft
• SPD 2013
  • The new SharePoint Designer 2013

 

Installation and Configuration

With the above work plan I went on step by step approach to building out the entire Farm and below are each sections. The order of installation really matters, so follow the steps in the below order:

(I will be updating these below sections as I find new updates and better approaches to simplifying these steps)

1. Server Platform Readiness
2. Installation and Configuration of Windows 2012 Domain Controller
3. (Optional) Extranet Domain Controller
4. VMWare Workstation Network Configuration
5. Exchange 2013 Installation and Configuration
6. Service Accounts Preparation
7. SQL Server 2012 and BI Components Installation and Configuration
8. SharePoint 2013 Installation
9. Default Services Fine Tune
10. Configuration of Initial Services
11. Post Default Services Configuration, Services Fine Tune
12. Registration of Managed Accounts
13. Create the first Portal Web Application
14. Create your Enterprise Search Center
15. Create your My Site Web Application
16. Create User Profile Service Application
17. Configure Search Service on a Dedicated Application Server
18. (Time dependent) Install April 2013 CU
19. Installing Latest CUs as of July 2013 
20. Installing Reporting Services in SharePoint Mode (Part I)
21. Configuring Security for SSRS in SharePoint Mode (Part II)
22. Installing PowerPivot for SharePoint 2013
23. Installing Office Web Apps 2013
24. Installing Development Tools 
25. Installing Workflow Manager
26. Configuring SharePoint farm for Apps support
27. Creating Extranet Web Application 
28. Installing and Configuration ExtranetDC
29. Installing UAG 2010
30. Configuring UAG

My conclusion from the above efforts and My Wish List for the next SharePoint Version and the toolset. Coming Soon…

I will look forward for the community feedback and any other installation and configuration related requests….

SharePoint Saturday Silicon Valley, June 22nd, 2013

 

I will be speaking at the – SharePoint Saturday Silicon Valley (#SPSSV), Saturday, June 22^nd, 2013, Oshman Family Jewish Community Center.

In the recent the SharePoint community has been pretty heads down to get to the details of development landscape. Likewise in the process I have spent ton of time figuring out to build out a development environment. For various use cases of my clients, I ended up building our Development Environment that would address situations such as BI Development, APPs Development, Workflow Development, Extranet etc. Eventually I started on new adventure to answer how would I build out an environment that would address most of these scenarios. With the right timing, I will be sharing my experience with the my topic focused on Building Practical SharePoint Development Environment.

I hope to let fellow SharePoint community members to build their development environment with more informed guidelines.

Website: http://www.spsevents.org/city/siliconvalley

Registration http://spssv2013.eventbrite.com

Here is my comprehensive blog on this topic later posted.

Cheers!

Rajesh