Setup SharePoint 2013 Single Server Environment – Part 4: SQL Server setup

Intro

This series describes the details and required steps for setting up a SharePoint 2013 Single Server Environment. This is typically used by developers in order to write custom solutions without interfering with one another. This type of environment is also is good for evaluation, training and demonstration purposes.
The series contains 6 parts:
  1. Environment Details
  2. VM setup
  3. Windows Server 2012 setup
  4. SQL Server setup
  5. SharePoint Installation and Initial Configuration
  6. Post-Installation Steps

SQL Server setup

This article contains the required steps to properly setup the SQL Server environment to properly run a single server SharePoint 2013 environment.

Install SQL Server 2012 Features

As per the previous article in this series, we should have downloaded the SQL Server 2012 ISO installation file and added it to the VM as a Virtual Optical Drive by now.
  1. From the virtual drive containing SQL installation, Run SETUP.EXE
  2. Select at least the following Core Features:
    1. Database Engine Services
    2. Management Tools – Basic
    3. Management Tools – Complete
  3. Select additional features based on specific needs

Setup Max Degrees of parallelism

Update the following PowerShell script, specifying the appropriate server instance.

#### Set MDOP to 1
Import-Module "sqlps" -DisableNameChecking
$sql = "EXEC sys.sp_configure N'show advanced options', N'1' RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'max degree of parallelism', N'1'
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N'show advanced options', N'0' RECONFIGURE WITH OVERRIDE
GO"
Invoke-Sqlcmd -Query $sql [-ServerInstance "SERVER\instance"]

Open a PowerShell console with administrator credentials and execute the above script.

Note: If you are unable to execute PowerShell commands on the server, you may need to change the execution policy. See this link for reference. 

Delegate Permissions

  1. Open SQL Management Studio
  2. Create SQL Login for sp_admin service account
  3. Assign server roles:
    1. dbcreator
    2. securityadmin

 

<< Windows Server 2012 Setup SharePoint Installation & Config..>>

 Reference

Using the Set-ExecutionPolicy Cmdlet in PowerShell

 

Setup SharePoint 2013 Single Server Environment – Part 3: Windows Server 2012 Setup

Intro

This series describes the details and required steps for setting up a SharePoint 2013 Single Server Environment. This is typically used by developers in order to write custom solutions without interfering with one another. This type of environment is also is good for evaluation, training and demonstration purposes.
The series contains 6 parts:
  1. Environment Details
  2. VM setup
  3. Windows Server 2012 setup
  4. SQL Server setup
  5. SharePoint Installation and Initial Configuration
  6. Post-Installation Steps

Windows 2012 Server setup

This article contains the required steps to properly setup Windows Server 2012 with the required features to run a single server SharePoint 2013 environment, which includes setting Active Directory and Domain Controller.

Windows Server 2012 Installation

As per the previous article in this series, we should have downloaded the Windows Server 2012 ISO installation file and added it to the VM as a Virtual Optical Drive by now. When the VM is started, the Windows installation will kick in automatically.

Configure Server Roles

After the Windows installation is complete, follow this steps to properly add the required server roles and features:
  1. Setting Computer Name and Network Settings
    1. From the Server DashBoard go to Local Server
    2. Change Computer Name and Restart
    3. After restart, select Ethernet > Properties > Internet Protocol Version 4
    4. Specify network settings such as:
      1. IP address: 192.168.100.10,
      2. Subnet mask: 255.255.255.0,
      3. Subnet Gateway: 192.168.100.1
  2. Adding Server Roles
    1. From the Server Manager DashBoard click Add Roles and Features
    2. Set Installation Type to Role-Based or Featured-Based installation
    3. Under Server Roles, select Active Directory Domain Services
    4. Accept popup with required features
    5. Leave everything else as default and click through the end of the wizard
  3. Promote Server to Domain Controller
    1. Go to Server Manager > AD DS
    2. There should be a warning message on top displaying “Configuration required for Active Directory …”. Click More…
    3. On All Server Task Details click “Promote this server to a domain…”
    4. Under Deployment Configuration, select “Add a new forest” and specify the domain name
    5. Enter Administrator password
    6. Leave everything else as default and click through the end of thee wizard
    7. Computer will be restarted at the end
  4. Add users to Domain Controller
    1. After restart, open Active Directory Users and Computers
    2. Under Users, add all required accounts (tick “User cannot change password” and “Password never expires” options):
      1. sp_admin
      2. sp_instal
    3. Add sp_admin to the local “Administrators” group
  5. Install .NET 3.5 Features as prerequisite for SQL Server features installation
    1. From Server Manager > DashBoard click “Add roles and features”
    2. From Features tab select “.Net Framework 3.5 Features”
    3. Click through the end of the wizard.

 

<< VM Setup SQL Server Setup >>

Setup SharePoint 2013 Single Server Environment – Part 2: VM Setup

Intro

This series describes the details and required steps for setting up a SharePoint 2013 Single Server Environment. This is typically used by developers in order to write custom solutions without interfering with one another. This type of environment is also is good for evaluation, training and demonstration purposes.

The series contains 6 parts:

  1. Environment Details
  2. VM setup
  3. Windows Server 2012 setup
  4. SQL Server setup
  5. SharePoint Installation and Initial Configuration
  6. Post-Installation Steps

VM setup

This article describes the steps to create a virtual machine using Virtual Box. It also assumes that a MSDN subscription is available in order to download the required software installation.

  1. Get the software installations from MSDN
    • Windows Server 2012 (64-bit)
    • SQL Server 2012
    • SharePoint 2013 Server
  2. Download and Install Virtual Box
  3. Create a new VM
  4. Assign the following parameters:
    • Type: Microsoft Windows
    • Version: Windows 2012 (64-bit)
    • Memory Size: 8192 MB
    • Hard Disk: Create a virtual hard disk now
    • File Size: 100 GB
    • Hard Disk File Type: VDI (VirtualBox Disk Image)
    • Storage on Physical Hard Disk: Dynamically Allocated
  5. After the VM is created, click Settings from the top menu and set the following from the left menu:
    1. Storage: Add the all the ISO installation files, starting by Windows Server 12
    2. System: Increase the number of processors to 2
    3. Network: On the Adapter 2 tab, select Bridge Adapter and use the current adapter from the host machine

 

<< Environment Details Windows Server 2012 Setup >>

Reference

VirtualBox Site

MSDN Subscriber Downloads

Setup SharePoint 2013 Single Server Environment – Part 1: Environment Details

Intro

This series describes the details and required steps for setting up a SharePoint 2013 Single Server Environment. This is typically used by developers in order to write custom solutions without interfering with one another. This type of environment is also is good for evaluation, training and demonstration purposes.
The series contains 6 parts:
  1. Environment Details
  2. VM setup
  3. Windows Server 2012 setup
  4. SQL Server setup
  5. SharePoint Installation and Initial Configuration
  6. Post-Installation Steps

Environment Details

This article contains the environment details, including hardware requirements, minimum recommended services, minimum software, an required service accounts.

Hardware Requirements

  • Processor: 4 cores, 64-bit
  • RAM: 10GB
  • Hard-Drive Space: 100GB

Minimum Recommended Services for Development Environment

  • App Management Service Application
  • Central Administration Website
  • Claims to Windows Token Service (C2WTW)
  • Distributed Cache Service
  • Microsoft SharePoint Foundation 2013 Site and Subscription Setting Service
  • Secure Store Service
  • User Profile Service Application (SP 2013 only)

Minimum Software

Optional Extra Software

  • Microsoft SharePoint Designer 2013
  • Google Chrome
  • Firefox
  • ULSViewer

Service Accounts

Account Purpose Requirements
SQL Service Account

sp_sql

Used to run SQL Server services:

  • MSSQLSERVER
  • SQLSERVERAGENT
  • Use either a Local System account or a domain user account.
SharePoint Setup Account

sp_admin

Used to run the following:

  • Setup
  • SharePoint Products Configuration Wizard
  • Domain user account.
  • Member of the Administrators group on each server on which Setup is run.
  • SQL Server login on the computer that runs SQL Server.
  • Member of the following SQL Server roles:
    securityadmin
    dbcreator
 Server farm account or database access account

sp_farm

Used to perform the following tasks:

  • Configure and manage the server farm.
  • Act as the application pool identity for the SharePoint Central Administration Web site.
  • Run the Microsoft SharePoint Foundation Workflow Timer Service.
  • Domain user account.
  • Additional permissions are automatically granted for the server farm account on Web servers and application servers that are joined to a server farm.
  • The server farm account is automatically added as a SQL Server login on the computer that runs SQL Server.
  • The account is added to the following SQL Server security roles:
    • dbcreator
    • securityadmin
    • db_owner for all SharePoint databases in the server farm

 

VM Setup >>

Reference

Install and Configure SharePoint 2013
Install SharePoint 2013 on a single server with SQL Server

Tools and techniques for Agile teams

The following list is meant to be a compilation of practices used by teams following an agile development process. This is not an absolute list, as I intend to update it periodically, but it should represent the most common practices being adopted and exercised in the field.

Requirements

  • Product and Sprint Backlogs
  • Kanban Boards
  • User Stories
  • DoD (Definition of Done)
  • Acceptance Criteria

Estimation

  • Sprint Planning
  • Story Points
  • Planning Poker

Feedback

  • Burnup and burndown charts
  • Daily Stand-up
  • Sprint Review
  • Retrospective Analysis
  • Automated Tests
  • Continuous Integration
  • Code Reviews

Quality & Productivity

  • Source Control
  • Pair Programming
  • Automated Testing
  • Test-Driven Development
  • Continuous Integration
  • Design Patterns
  • Code Refactoring
  • Product Increment

Project Roles

  • Scrum Master
  • Product Owner
  • Cross-Functional team

Template for Retrospective Analysis used by Agile Teams

Intro

The following is one of the principles described in the Agile Manifesto:

Continuous attention to technical excellence and good design enhances agility.

One technique to materialize this principle is to conduct a retrospective analysis after each iteration. This allows the team to identify issues and reflect on how to become more effective, then fine tune the behavior accordingly and improve the process. The goal is always to become better at what we do and deliver the best possible results, while keeping all team members engaged.

I will share a very simple template that could be used to gather data about a previous iteration of work from all team members. This could serve as a guide for a productive discussion.

Retrospective Analysis Template

The following template can be used to collect some information from team members after an iteration of work:

What went well?
In other words, what took place that we want to recognize and acknowledge as having gone well?
What didn’t go so well?
What took place that didn’t go as we would have liked?
What did I learn?
We want to think about what we’ve learned about how we worked together. It’s less about the content and more about the process.
What still puzzles me?
This question allows us to capture things that happened but leave us feeling unclear or puzzled.

Summary

Constant improvement is a key aspect of any Agile project. Conducting retrospective analysis allows teams to gather feedback after each iterations and  identify what areas need attention. There are many recommended approaches and frameworks for conducting a successful retrospective analysis session, and they all focus on identifying three things:

  • what went good
  • what went bad
  • what actions we should take to improve the process

This articles provides a specific template that could be used to request information from team members after each iteration, and then be used as support for in-person session.

Reference

Agile Retrospective by Margaret Rouse

Agile Manifesto

Agile Retrospective Wiki