Page 1 of 6

Deployment Notes – UAT Environment

Version Control

Person / Version / Date / Comments
Paul Beck / 1.0 / 7 September 2010 / Create document based on HyperV Test build environment.

Table of Contents

Deployment Notes – UAT Environment

Version Control

Overview

Server Structure

Initial Checks

Preparation of machines with NLB (15 min) (Ignored in UAT)

SharePoint Installation (1.5hr)

Overview

This document outlines the exact steps used to create the User Acceptance Test (UAT) environment. The document must be updated continuously and mimic the steps to create the production environment. Subsequent changes to the production should be dealt with using your company’s internal change control procedures or as a minimum be documented in the appendix of this document. The UAT and Production environment must be synchronised continuously to provide the best possible service to the business.

The environment consists of 2 load balanced Web Frond end Servers running SharePoint 2010. One SQL Server. All servers were created on HyperV for UAT.

Server Structure

Role / IP / Name / Software
Database Server / 192.168.2.100 / demo\SQL / Win 2008 R2 stded
SQL 2008 R2 stded
SP2010 Server / 192.168.1.34
192.168.1.34
192.168.1.40 / demo\WFE1
demo\WFE2
NLB IP (Shared) / Win 2008 R2 stded
SP2010 stded
SMTP Server
Active Directory / Demo

Initial Checks

  1. Ensure you have 2 Windows 2008 R2 standard edition x64 servers with working networking and you have access to the machine. Each machine should be fully patched.
  2. Ensure you have 7 accounts:
  • Demo/install (install account)
  • Demo/farm (local admin & SQL roles of dbsecuritydbcreator)
  • Demo/web_app
  • Demo/service
  • Demo/search
  • Demo/sql :
  1. The demo/farm account needs to have local administrator rights, access via remote desktop to each machine & SQL admin access (or specifically give the account dbsecurity & creator sql roles).
  2. The all other account should be domain users only and preferably in the Managed accounts group within Active Directory (AD).
  3. SQL Server 2008R2 should be installed on machine demo\SQL. SQL Services should be running using the demo\sql account.

Preparation of machines with NLB (15 min)

  1. Setup Network Load Balancing (NLB), on each WFE, install the NLB feature.

  1. Add a new cluster to WFE1
  1. Enter the IP adr of WFE1 for the host

  1. Next > Next > Set the Cluster IP Address

  1. Next > Specify the cluster parameters

  1. Next > Specify Port Rules
  1. Uncheck “all” and select “Network” > OK > Finish
  2. Add the additional Hosts to the Cluster i.e. WFE2

  1. Add the WFE2 as a 2nd host
  2. When complete the NLB should look as shown below:

SharePoint Installation (1hr)

Install Sharepoint 2010 using the CodePlexAutoSPInstaller,

Copy the SP2010 folder (installation files) on WFE1.

Open the file on WFE1 \\SP2010\Scripted\SetInputs.xml amend the xml file to have the appropriate details. On WFE1 we willinstall SP prerequisites & binaries, config the farm and run key services, create a new web app and lastly create the web app for mysites.

Open the command prompt as an administrator and run the launch.bat file.

If prompted reboot the server and run the launch.bat script again.

Check WFE1 is working by opening the default web app and the mysite from the WFE1 server.

Check that the public url is working i.e. demo.dev should ping using the shared IP address and the web page should authenticate.

Ensure you can access CA. Check all the search services have started.

Rename the file on WFE2 \\SP2010\Scripted\SetInputs-join.xml you may need to delete setupinputs.xml.

Open the command prompt as an administrator and run the launch.bat file on WFE2.

If prompted reboot the server and run the launch.bat script again.

Check web sites are working & shut down WFE1 & WFE2 separately.

Version: 1.0UAT DeploymentDate: 7September 2010