microsoft private cloud fast track reference deployment guide.pdf

Microsoft Private Cloud Fast Track Reference Deployment Guide

Published: July 2012

For the latest information, please see the Microsoft Server and Cloud Platform

site.

Contents

Introduction ................................................................................................................... 7

Private Cloud Fast Track Program Description ............................................................ 8

Business Value ................................................................................................................................................................................... 8

Technical Benefits ............................................................................................................................................................................ 8

Using this Document ...................................................................................................................................................................... 9

1 Solution Overview ................................................................................................. 10

1.1 Core Private Cloud Fast Track Infrastructure ...................................................................................................... 10

2 Fabric Management ............................................................................................... 12

2.1 Fabric Management Infrastructure Host and Guest Installation ................................................................. 12

2.1.1 Provisioning Fabric Management Infrastructure Hosts ..............................................................................12

2.1.2 Create Fabric Management Virtual Guests ......................................................................................................14

2.1.3 Create Required User Accounts and Security Groups .................................................................................18

3 SQL Server 2008 R2 Cluster Installation ............................................................... 21

3.1 Overview ........................................................................................................................................................................... 21

3.2 Prerequisites .................................................................................................................................................................... 22

3.2.1 Accounts .......................................................................................................................................................................23

3.2.2 Groups ...........................................................................................................................................................................23

3.2.3 Create the SQL Server 2008 R2 Slipstreamed Source ..................................................................................24

3.2.4 Establish the SQL Server Guest Cluster .............................................................................................................29

3.2.5 Add the .NET Framework 3.5.1 Features ..........................................................................................................38

3.2.6 Cluster MSDTC on Node 1 .....................................................................................................................................40

3.3 Installation ........................................................................................................................................................................ 41

3.3.1 Install the SQL Server Named Instances on the Guest Cluster (Node 1) ..............................................41

3.3.2 Install the SQL Server Named Instances on the Guest Cluster (Additional Nodes) .........................55

4 Virtual Machine Manager...................................................................................... 60

4.1 Overview ........................................................................................................................................................................... 61

4.2 Prerequisites .................................................................................................................................................................... 62

4.2.1 Accounts .......................................................................................................................................................................62

4.2.2 Groups ...........................................................................................................................................................................63

4.2.3 Adding the .NET Framework 3.5.1 Features ....................................................................................................64

4.2.4 Install the Windows Automated Installation Kit ............................................................................................66

4.2.5 Install the Windows Automated Installation Kit Supplement for Windows 7 SP1 ...........................69

4.2.6 Install the Windows Server Update Services Administration Console ...................................................70

4.2.7 Install the SQL Server 2008 R2 Command Line Utilities .............................................................................73

4.2.8 Install .NET Framework 4 ........................................................................................................................................78

4.2.9 Install Windows Fail-over Clustering (Design Pattern 1, Clustered Virtual Machine Manager Only) 80

4.2.10 Create the Virtual Machine Manager Distributed Key Management Container in Active Directory Domain Services .........................................................................................................................................................................88

4.3 Design Pattern 1 Installation HA Virtual Machine Manager Management Server (Failover Clustering) 92

4.4 Design Pattern 1 Installation Creating the HA Virtual Machine Manager Library Share on a Failover Cluster 108

4.5 Design Pattern 2 Installation - Stand-alone Virtual Machine Manager Management Server ....... 120

5 Operations Manager ............................................................................................ 129

5.1 Overview ......................................................................................................................................................................... 129

5.2 Prerequisites .................................................................................................................................................................. 130

5.2.1 Accounts .................................................................................................................................................................... 130

5.2.2 Groups ........................................................................................................................................................................ 131

5.2.3 Add the .NET Framework 3.5.1 Features ....................................................................................................... 132

5.2.4 Install the SQL Server Reporting Services and Analysis Services (Split Configuration) ................ 134

5.2.5 Install .NET Framework 4 ..................................................................................................................................... 147

5.2.6 Install Microsoft Report Viewer 2010 SP1 ..................................................................................................... 148

5.2.7 Configuration of Operations Manager SQL Server Prerequisites ........................................................ 152

5.3 Installation Management Server ........................................................................................................................ 155

5.4 Installation Reporting Server ............................................................................................................................... 163

5.5 Design Pattern 1 Installation Add an Additional Management Server ............................................... 168

5.6 Post Installation Tasks ................................................................................................................................................ 173

5.6.1 Register the Required Service Principal Names for the Operations Manager Management Servers 173

5.6.2 Deploy and Configure the Operations Manager Agent on the Virtual Machine Manager Management Server .............................................................................................................................................................. 175

5.6.3 Install Microsoft Report Viewer 2010 SP1 on the Virtual Machine Manager Management Server179

5.6.4 Install Operations Manager Console on the Virtual Machine Manager Management Server . 182

5.6.5 Download and Import the Required Prerequisite Management Packs in Operations Manager185

5.6.6 Perform Virtual Machine Manager and Operations Manager Integration ...................................... 189

6 Service Manager .................................................................................................. 193

6.1 Overview ......................................................................................................................................................................... 193

6.2 Prerequisites .................................................................................................................................................................. 195

6.2.1 Accounts .................................................................................................................................................................... 195

6.2.2 Groups ........................................................................................................................................................................ 196

6.2.3 Add the .NET Framework 3.5.1 Features on all Server Manager Servers .......................................... 197

6.2.4 Install Microsoft Report Viewer 2008 SP1 Redistributable on the Management and Data Warehouse Servers 198

6.2.5 Install SQL Server 2008 R2 Native Client on the on the Management and Data Warehouse Servers 201

6.2.6 Install SQL Server 2008 R2 Analysis Management Objects on the Management and Data Warehouse Servers 204

6.2.7 Install SQL Server Reporting Services (Split Configuration) on the Data Warehouse Server .... 207

6.2.8 Install SharePoint Foundation 2010 on the Self-Service Portal Server .............................................. 218

6.2.9 Install .NET Framework 4 on the Self-Service Portal Server ................................................................... 227

6.2.10 Request and Install an SSL Certificate on the Self-Service Portal Server...................................... 229

6.3 Installation ...................................................................................................................................................................... 233

6.3.1 Installation Management Server ................................................................................................................... 236

6.3.2 Design Pattern 1 Installation Add an Additional Management Server .......................................... 247

6.3.3 Installation Data Warehouse Server............................................................................................................. 255

6.3.4 Installation Self-Service Portal Server.......................................................................................................... 274

7 Orchestrator ......................................................................................................... 282

7.1 Overview ......................................................................................................................................................................... 282

7.2 Prerequisites .................................................................................................................................................................. 283

7.2.1 Accounts .................................................................................................................................................................... 283

7.2.2 Groups ........................................................................................................................................................................ 283



7.2.5 Install Silverlight Runtime 4 ................................................................................................................................ 288

7.3 Installation Runbook, Orchestration Console, Web Service, and Designer Server.......................... 289

7.4 Pattern 1 Installation Add an Additional Runbook Server ....................................................................... 299

7.5 Post-Installation Tasks ............................................................................................................................................... 306

7.5.1 Install the Virtual Machine Manager Console ............................................................................................. 306

7.5.2 Install the Microsoft Report Viewer 2010 SP1 ............................................................................................. 310

7.5.3 Install the Operations Manager Console ....................................................................................................... 312

7.5.4 Install Integration Packs ....................................................................................................................................... 316

7.5.5 Deploy Integration Packs .................................................................................................................................... 320

7.5.6 Deploy Integration Packs to the Secondary Server ................................................................................... 326

8 App Controller ..................................................................................................... 329

8.1 Overview ......................................................................................................................................................................... 329

8.2 Prerequisites .................................................................................................................................................................. 329

8.2.1 Accounts .................................................................................................................................................................... 330

8.2.2 Groups ........................................................................................................................................................................ 330



8.2.5 Install Silverlight Runtime 4 ................................................................................................................................ 336

8.2.6 Request and Install an SSL Certificate............................................................................................................. 337

8.2.7 Install the Virtual Machine Manager Console ............................................................................................. 339

8.3 Installation ...................................................................................................................................................................... 344

9 System Center Cloud Services Process Pack ...................................................... 351

9.1 Overview ......................................................................................................................................................................... 351

9.2 Prerequisites .................................................................................................................................................................. 352

9.2.1 Import the Virtual Machine Manager Discovery Management Pack into Service Manager ..... 352

9.2.2 Create the OrchestratorUsersGroup local group on the Orchestrator Server ................................ 356

9.3 Installation Cloud Services Process Pack ......................................................................................................... 357

9.4 Installation Cloud Services Runbooks .............................................................................................................. 360

10 Appendix A: SQL Server Cluster Named Instance Worksheet ....................... 364

11 Appendix B: Installing a Windows Deployment Services Server .................. 365

11.1.1 Adding the Windows Deployment Services Role.................................................................................. 365

12 Appendix C: SlipSQL.PS1 ................................................................................. 367

13 Appendix D: High-Level Fast Track SQL Server Multi-Instance Configuration370

Contributors

Microsoft Consulting Services

Joel Yoker ([email protected])

Solution Architect

Jeff Baker ([email protected])

Architect

Adam Fazio ([email protected])

Solution Architect

Business stakeholders

Mike Truitt ([email protected])

Senior Product Planner

Bryon Surace ([email protected])

Senior Program Manager, Windows Server

Jim Dial ([email protected])

Principal Knowledge Engineer, Server & Cloud Division, Information Experience Solutions

Copyright information

This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web

site references, may change without notice.

Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is

intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may

copy and use this document for your internal, reference purposes.

2012 Microsoft. All rights reserved.

Active Directory, Forefront, Hyper-V, Microsoft, SharePoint, SQL Server, Windows, Windows Server, Windows PowerShell,

and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Introduction The Microsoft Private Cloud Fast Track Program is a joint effort between Microsoft and its hardware partners.

The goal of the program is to help organizations decrease the time, complexity, and risk of implementing

private clouds. The program provides:

Reference implementation guidance: Lab-tested and validated guidance for implementing multiple

Microsoft products and technologies with hardware that meets specific, minimum, hardware vendor-

agnostic requirements. Customers can use this guidance to implement a private cloud solution with

hardware they already own, or that they purchase.

Reference implementations: Microsoft hardware partners define physical architectures with

computing, network, storage, and value-added software components that meet (or exceed) the

minimum hardware requirements defined in the reference implementation guidance. Each

implementation is then validated with Microsoft and made available for purchase to customers. Further

details can be found by reading the information at Private Cloud How To Buy.

The customer has the choice of building the solution by using the reference implementation guidance or

purchasing a solution from a Microsoft hardware partner that couples the guidance with optimized hardware

configurations. Although both options decrease the time, cost, and risk in implementing private clouds,

purchasing a reference implementation from a Microsoft hardware partner will result in the fastest, lowest-risk

solution. This is due to the fact that in this option, all of the hardware and software best practice

implementation choices have been determined by Microsoft and its hardware partners engineering teams. As a

result, this will often also prove to be the most inexpensive option.

The private cloud model provides much of the efficiency and agility of cloud computing in addition to the

increased control and customization that is achieved through dedicated private resources. With the Microsoft

Private Cloud Fast Track Program, Microsoft and its hardware partners can help provide organizations with the

control and flexibility required to reap the potential benefits of the private cloud.

The Private Cloud Fast Track Program includes three documents to help you create your private cloud solution.

Refer to the following companion guides:

Microsoft Private Cloud Fast Track Reference Architecture Guide

Microsoft Private Cloud Fast Track Reference Operations Guide

Private Cloud Fast Track Program Description The Microsoft Private Cloud Fast Track Program is a joint reference architecture for building private clouds,

which combines Microsoft software, consolidated guidance, and validated configurations with hardware partner

computing power, network, and storage architectures; and value-added software components.

Specifically, the Microsoft Private Cloud Fast Track Program utilizes the core capabilities of the Windows Server

operating system, Hyper-V technology, and Microsoft System Center 2012 to deliver the building blocks of a

private cloud infrastructure as a service offering. The key software components of every reference

implementation are the Windows Server 2008 R2 SP1 operating system, Hyper-V, and Microsoft System Center

2012.

Business Value

The Microsoft Private Cloud Fast Track Program includes a set of three documents that provide reference

implementation guidance and reference implementations (as described previously). The program can be used

to build private clouds that are flexible and extensible. A Microsoft Private Cloud Fast Track solution helps

organizations implement virtualization and private clouds with increased ease and confidence. The potential

benefits of the Microsoft Private Cloud Fast Track Program include faster deployment, reduced risk, and a lower

cost-of-ownership.

Faster Deployment

End-to-end architectural and deployment guidance

Streamlined infrastructure planning due to predefined capacity

Enhanced functionality and automation through deep knowledge of infrastructure

Integrated management for virtual machine and infrastructure deployment

Reduced Risk

Tested end-to-end interoperability for compute, storage, and network (if the solution is purchased from

a Microsoft hardware partner)

Predefined, out-of-box solutions based on a common cloud architecture

High degree of service availability through automated load balancing

Lower Cost-of-Ownership

Near-zero downtime with exceptional fault tolerance, providing high availability

Dynamic pooling that can enhance the use of virtualization resources with Hyper-V and with supported

storage and network devices

Utilization of low-cost switches that consume less power and deliver high throughput for large

bandwidth requirements

Technical Benefits

The Microsoft Private Cloud Fast Track Program integrates multiple Microsoft products and technologies, in

addition to hardware requirements, to create reference implementation guidance. If the solution is purchased

from a Microsoft hardware partner, the reference implementation guidance is implemented with partner

hardware and sold as a reference implementation. Whether the customer decides to implement the Microsoft-

validated reference implementation guidance with their own hardware or with hardware from a Microsoft

partner, it goes through a validation process. In either case, Microsoft and its hardware partners have created a

solution that is ready to meet customer needs.

Using this Document

This document can be used by system engineers to implement a private cloud solution. The detailed

implementation steps contained within this document are for implementing the physical architecture defined in

the Reference Architecture Guide of the Private Cloud Fast Track Reference Implementation Guidance Set. Thus,

its recommended that if you havent yet read the Reference Architecture Guide, you do so before reading this

document. Following the steps detailed in this document will result in a private cloud solution that provides

high availability, scalability, and performance, while providing security to the infrastructure and the virtual

machines within it. The document includes many best practice deployment recommendations from Microsoft

product and enterprise service teams.

1 Solution Overview

1.1 Core Private Cloud Fast Track Infrastructure

The recommendations for the Microsoft Private Cloud Fast Track physical architecture are detailed in Section

4.7.3, Management Systems Architecture, of the Private Cloud Fast Track Reference Architecture Guide. Two

design patterns are identified: Design Pattern 1 and Design Pattern 2. For Design Pattern 1, a dedicated two-

node Hyper-V cluster hosts the fabric management virtual machines. In Design Pattern 2, the fabric

management virtual machines are hosted directly on a compute cluster along with other workload virtual

machines. Additionally, Design Pattern 1 utilizes both scaled-out and highly available deployments of the

Microsoft System Center 2012 components, whereas Design Pattern 2 utilizes the minimum number of System

Center component servers recommended in order to provide full functionality in a production environment.

This document covers the steps for installing both patterns. The design patterns are outlined in Figures 1 and 2.

Figure 1: Fabric management infrastructure: Pattern one

Figure 2: Fabric management infrastructure: Pattern two

2 Fabric Management

2.1 Fabric Management Infrastructure Host and Guest Installation

2.1.1 Provisioning Fabric Management Infrastructure Hosts

In order to properly size these systems, the following table outlines the virtual machines (and their default

configurations) that are deployed to compose the fabric management component architecture. These virtual

machines are hosted on a dedicated two-node Hyper-V cluster in fabric management infrastructure pattern

one. In fabric management infrastructure pattern two, these virtual machines are collocated on one of the fabric

compute clusters. These virtual machines that run System Center 2012 components serve as the basis for fabric

management operations.

Fabric management component virtual machine Virtual

central

processing

unit

(vCPU)

Memory Virtual

network

interface

cards

(vNICs)

Storage

Microsoft SQL Server data management software

(at least two nodes in a cluster configuration)

4 16 to 32

gigabyte

(GB)

2 C: 60 GB

20 additional

logical unit

numbers

(LUNs)1

Microsoft System Center 2012 - Virtual Machine

Manager management server

4 8 GB 2 C: 60 GB2

Virtual Machine Manager management server

(in a two-node cluster)

4 8 GB 2 C: 60 GB3

Microsoft System Center 2012 - Operations Manager

management server

4 16 GB 1 C: 60 GB

Operations Manager reporting server 4 16 GB 1 C: 60 GB

Operations Manager (additional management server) 4 16 GB 1 C: 60 GB

Microsoft System Center 2012 - Service Manager

management server

4 16 GB 1 C: 60 GB

Service Manager (additional management server) 4 16 GB 1 C: 60 GB

Service Manager Data Warehouse 4 16 GB 1 C: 60 GB

Service Manager self-service portal 4 8 GB 1 C: 60 GB

1 SQL Server LUN size is dependent on Solution scale.

2 Additional disks may be created for Virtual Machine Manager library expansion as required.


Fabric management component virtual machine Virtual

central

processing

unit

(vCPU)

Memory Virtual

network

interface

cards

(vNICs)

Storage

Microsoft System Center 2012 - Orchestrator

Runbook Server, Web Service, and Designer

4 8 GB 1 C: 60 GB

Orchestrator Runbook Server 4 8 GB 1 C: 60 GB

Microsoft System Center 2012 - App Controller 4 8 GB 1 C: 60 GB

[Optional] Microsoft Windows Server Update Services

(WSUS) and Microsoft Windows Deployment Services

(WDS)

2 4 GB 1 C: 60 GB

Table 1: Fabric management infrastructure: Pattern one

Fabric management component virtual machine vCPU Memory vNICs Storage

Microsoft SQL Server

(at least two nodes in a cluster configuration)

4 16 to 32

GB

2 C: 60 GB

20 additional

LUNs4

Virtual Machine Manager 4 8 GB 1 C: 60 GB5

D: 120GB

Operations Manager management server 4 16 GB 1 C: 60 GB

Operations Manager reporting server 4 16 GB 1 C: 60 GB

Service Manager 4 16 GB 1 C: 60 GB

Service Manager Data Warehouse 4 16 GB 1 C: 60 GB

Service Manager self-service portal 4 8 GB 1 C: 60 GB

Orchestrator 4 8 GB 1 C: 60 GB

App Controller 4 8 GB 1 C: 60 GB

[Optional] Windows Server Update Services and

Windows Deployment Services

2 4 GB 1 C: 60 GB

Table 2: Fabric management infrastructure: Pattern two

At this stage, you are expected to have a supportable fabric management cluster or fabric compute cluster built

to supports the virtual machine specifications outlined above. Compute, storage, and network functionality

should all be verified.

4 SQL Server LUN size is dependent on Solution scale.


2.1.2 Create Fabric Management Virtual Guests

Windows Failover Cluster Manager is used to create the fabric management virtual machines. The installation of

the required Windows operating systems can utilize existing automated deployment solutions or a manual build

of each virtual machine.

Perform the following steps on the first fabric management host computer in the Fabric Management

Cluster.

Open the Failover Cluster Manager Microsoft

Management Console (MMC) snap-in. Navigate

to the Services and applications node, right-

click and point to Virtual Machines, and then

click New Virtual Machine on the shortcut

menu.

The New Virtual Machine Wizard will appear.

In the Specify Name and Location dialog box,

provide the following values:

Name specify the name of the virtual

machine based on the naming

conventions of your organization.

Select the Store the virtual machine in a

different location check box. In the Location

box, specify the location of the cluster shared

volumes (CSV) on your fabric management host

cluster.

Click Next to continue.

In the Assign Memory dialog box, provide the

following value:

Memory specify the amount of

memory in megabytes (MB) required for

each virtual machine. Identify this value

in the configuration table above.


Note: For virtual memory, the products will post

a warning if memory is below 8 GB and each

virtual machine must have at least 2 GB of

startup random access memory (RAM) if

dynamic memory is enabled.

In the Configure Networking dialog box,

provide the following value:

Connection specify the Virtual Switch

network connection this system should

participate in from the available

connections in the drop-down menu.


In the Connect Virtual Hard Disk dialog box,

select the Create a virtual hard disk option and

provide the following values:

Name specify the name of the virtual

hard disk (VHD). For simplicity this

should match the name of the virtual

machine.

Location accept the default location of

the CSV on your fabric management

host cluster combined with the virtual

machine name.

Size specify the size of the VHD (for

operating system partitions this should

be 60 GB).


Note: Absent of any automated imaging

process for the new VMs, a VHD (with Windows

Server 2008 R2 installed and then Sysprepped)

can be leveraged in place of the new VHD

created in this step. This will greatly speed up

the provisioning process for the management

virtual machines.

In the Installation Options dialog box, select

the Install an operating system later option,

and then click Next to continue.

The Completing the New Virtual Machine

Wizard dialog box will display the selections

made during the wizard. Click Finish to create

the virtual machine based on the options

selected.

Note: This operation must be completed for

each fabric management virtual machine.

After completion, the virtual machines will be

available for management in the Services and

applications node of the Failover Cluster

Manager.

Install Windows Server 2008 R2 on each virtual

manager.

If a Windows Server 2008 R2 VHD that was

prepared for the installation with Sysprep is

attached to the virtual machines, just complete

the mini setup process.

2.1.3 Create Required User Accounts and Security Groups

Though each System Center 2012 component installation section in this document outlines the individual

accounts and groups required for each installation and operation, a short summary appears in the following

tables. The following Microsoft Active Directory Domain Services (AD DS) user accounts are required for the

Private Cloud Fast Track System Center 2012 installation.

Component User account Suggested name Description

App Controller App Controller

services account

FT-SCAC-SVC This account is used to run all App Controller

services.

Operations

Manager

Management

server action

account

FT-SCOM-Action This account is used to carry out actions on

monitored computers across a network

connection.

Operations

Manager

System Center

Operations

Manager

configuration

service and data

access service

account

FT-SCOM-SVC This account is one set of credentials that is

used to update and read information in the

operational database. Operations Manager

verifies that the credentials used for the

System Center Operations Manager

configuration service and data access service

account are assigned to the sdk_user role in

the operational database.

Operations

Manager

Data Warehouse

write account

FT-SCOM-DW The Data Warehouse write account writes data

from the management server to the reporting

Data Warehouse and reads data from the

operational database.

Operations

Manager

Data reader

account

FT-SCOM-DR The data reader account is used to define

which account credentials Microsoft SQL

Server 2008 Reporting Services uses to run

queries against the Operations Manager

reporting Data Warehouse.

Orchestrator Orchestrator

services account

FT-SCO-SVC This account is used to run the Orchestrator

Management Service, Orchestrator Runbook

Service and Orchestrator Runbook Server

monitor service.

Service Manager Service Manager

services account

FT-SCSM-SVC This account becomes the operational system

account. It is assigned to the logon account for

all Service Manager services on all Service

Manager servers. This account becomes a

member of the sdk_users and configsvc_users

database roles for the Service Manager

database as part of installation. This account

also becomes the Data Warehouse system Run

As account.

If you change the credentials for these two

services, make sure that the new account has a

SQL Server login in the ServiceManager

database and that this account is a member of

Component User account Suggested name Description

the Builtin\Administrators group.


workflow

account

FT-SCSM-WF This account is used for all workflows and is

made a member of the Service Manager

workflows user role.


reporting

account

FT-SCSM-SSRS This account is used by SQL Server Reporting

Services (SSRS) to access the DWDataMart

database to get data for reporting. The

account becomes a member of the

db_datareader database role for the

DWDataMart database and becomes a

member of the reportuser database role for

the DWDatamart database.

Service Manager Microsoft SQL

Server 2008

Analysis Services

account for

OLAP cubes

FT-SCSM-OLAP This account is used by SQL Server Analysis

Services (SSAS) for Service Manager reports.

Service Manager Operations

Manager alert

connector

FT-SCSM-OMAlert This account is used for Service Manager

Operations Manager Alert connector

operations.

Service Manager Operations

Manager CI

connector

FT-SCSM-OMCI This account is used for Service Manager

Operations Manager continuous integration

(CI) connector operations.

Service Manager Active Directory

connector

FT-SCSM-ADCI This account is used for Service Manager

Active Domain connector operations.

Service Manager Virtual Machine

Manager CI

connector

FT-SCSM-VMMCI This account is used for Service Manager

Virtual Machine Manager connector

operations.

Service Manager Orchestrator CI

Connector

FT-SCSM-OCI This account is used for System Center

Orchestrator connector operations.

SQL Server SQL Server

instance service

account

FT-SQL-Service This account is used as the service account for

all instances of SQL Server used in System

Center.

System Center Component

installation

account

FT-SCInstall This optional account is used to install all

System Center 2012 components.

Virtual Machine

Manager

Virtual Machine

Manager service

account

FT-VMM-SVC This account is used to run the Virtual Machine

Manager service.

Table 3: Required user accounts and security groups

The following Active Directory security groups are required for the Private Cloud Fast Track System Center 2012

installation.

Component Group Name Group notes

Operations

Manager

Operations Manager

Administrators

FT-SCOM-Admins This groups members are administrators for

the Operations Manager installation and hold

the Administrators role in Operations

Manager.

Orchestrator Orchestrator

Administrators

FT-SCO-Admins This groups members are administrators for

the Orchestrator installation.

Orchestrator Orchestrator Operators FT-SCO-Operators This groups members gain access to

Orchestrator through membership in the

Orchestrator Operators group. Any user

account added to this group is granted

permission to use the Runbook Designer and

Deployment Manager tools.

Service

Manager

Service Manager

Admins

FT-SCSM-Admins This group is added to the Service Manager

Administrators user role and the Data

Warehouse Administrators user role.

SQL Server SQL Server

Administrators

FT-SQL-Admin This groups members are sysadmins on all

SQL Server instances and local administrators

on all SQL Server nodes.

System

Center 2012

System Center

Administrators

FT-SC-Admins This groups members are full Admins on all

System Center components.

Virtual

Machine

Manager

Virtual Machine

Manager

Administrators

FT-SCVMM-

Admins

This groups members are administrators for

the Virtual Machine Manager installation and

hold the Administrators role in Virtual

Machine Manager. Table 4: Active Directory security groups required for the Private Cloud Fast Track System Center 2012 installation

3 SQL Server 2008 R2 Cluster Installation

The SQL Server 2008 R2 installation process includes the following high-level steps.

SQL Server 2008 R2 Installation

Perform Prerequisites

1

Install the SQL Named Instances on Node 1 of the

Guest Cluster

Add additional SQL Nodes for each named

instance

Install the .NET Framework 3.5.1

Feature

Cluster MSTDC

Instantiate the Guest Cluster

Figure 3: SQL Server 2008 R2 installation process

3.1 Overview

There is a decision point in the SQL Server architecture that must occur prior to deployment. There are multiple

valid SQL Server deployment scenarios, as follows.

Architecture:

o Physical servers

o Virtual machines

Storage:

o Fibre Channel (not feasible for virtual machines in guest failover cluster)

o iSCSI

o SAS (not feasible for virtual machines in guest failover cluster)

From the choices described above, the standard Private Cloud Fast Track architecture recommends a

minimum two-node virtualized SQL Server guest cluster scaled accordingly for your deployment. The

subsequent sections of this document contain guidance for deploying a two-node cluster.

This section provides a high-level walkthrough about how to install SQL Server 2008 R2 SP1 with Cumulative

Update 4 (CU4) (version 10.50.2796.0) into the Private Cloud Fast Track fabric management.6 The following

assumptions are made prior to installation:

Two to four base virtual machines running Windows Server 2008 R2 (x64) have been provisioned for

SQL Server.

6 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released - http://support.microsoft.com/kb/981356.

20 iSCSI LUNs have been assigned to the virtual machine guests.

o One LUN quorum (1 GB)

o One LUN Microsoft Distribution Transaction Coordinator service (MSDTC) (1 GB)

o Two LUNs for each fabric management component database (18 LUNs for all components)

As discussed in the Private Cloud Fast Track Reference Architecture Guide, virtual machines running SQL Server

will be deployed as a guest failover cluster to contain all the databases for each System Center product in

discrete instances by product and function. In cases that require SQL Server Reporting Services, SQL Server

Reporting Services will be installed on the hosting System Center component server (for example, the

Operations Manager reporting server). However, this installation will be Files Only and the SQL Server

Reporting Services configuration will configure remote Reporting Services databases hosted on the component

instance on the SQL Server cluster. All instances are required to be configured with Windows Authentication.

The following table outlines the options required for each instance.

Database Instances and Requirements

Fabric management

component

Instance name

(suggested)

Components Collation7 Storage

requirements

SCSMAS Analysis Services SQL_Latin1_General_CP1_CI_AS 2 LUNs

SCSPFarm Database Engine SQL_Latin1_General_CP1_CI_AS 2 LUNs

App Controller SCACDB Database Engine SQL_Latin1_General_CP1_CI_AS 2 LUNs

Operations Manager SCOMDB Database Engine,

Full-Text Search

SQL_Latin1_General_CP1_CI_AS 2 LUNs

Operations Manager

Data Warehouse

SCOMDW Database Engine,

Full-Text Search


Orchestrator SCODB Database Engine SQL_Latin1_General_CP1_CI_AS 2 LUNs

Service Manager SCSMDB Database Engine,

Full-Text Search


Service Manager

Data Warehouse

SCSMDW Database Engine,

Full-Text Search


Virtual Machine

Manager

SCVMMDB Database Engine SQL_Latin1_General_CP1_CI_AS 2 LUNs

Windows Server

Update Services

(optional)

SCWSUSDB Database Engine SQL_Latin1_General_CP1_CI_AS 2 LUNs

Table 5: Database instances and requirements

Appendix D outlines the required SQL Server instances and associated recommended node placements.

3.2 Prerequisites

The following environment prerequisites must be met before proceeding.

7 The default SQL Server collation settings are not supported for multi-lingual installations of the Service Manager component. Only use the default

SQL Server collation if multiple languages are not required. Note that the same collation must be used for all Service Manager databases

(Management, Data Warehouse, and Reporting Services).

3.2.1 Accounts

Verify that the following accounts have been created.

User name Purpose Permissions

\FT-SQL-SVC SQL Server Service

Account

This account will need full admin

permissions on all target SQL

Server systems and will serve as

the service account for all

instances. This account must also

be added to the FT-SQL-Admins

group and a sysadmin in all

instances.

3.2.2 Groups

Verify that the following security groups have been created.

Security group name Group scope Members

\FT-SQL-Admins Universal All SQL Server Administrators for

the fabric management Solution.

3.2.3 Create the SQL Server 2008 R2 Slipstreamed Source

For the Private Cloud Fast Track solution, the SQL Server installation will use SQL Server 2008 R2. In order to

perform the installation, a slipstreamed version of the SQL Server 2008 R2 with SP1 and CU4 must be created.

To support this operation, a script has been created to automate this process. Creating slipstreamed builds of

SQL Server with this script (SLIPSQL.PS1) is a non-destructive action and does not modify the source files. To

create a slipstreamed build using this automation, follow the provided steps.8

Once complete, perform the following steps.

Perform the following steps on the first fabric management host computer.

On a local drive with sufficient space, create a

directory called SQL.9

In the \SQL folder, create the following

subfolders:

\SQL2008R2CU

\SQL2008R2RTM

\SQL2008R2SP

Copy the original SQL Server 2008 R2 source

media to \SQL\SQL2008R2RTM created in the

previous step.

Copy the three Service Pack files to the folder

named \SQL\SQL2008R2SP created in the

previous step.

Note: SQL Server 2008 R2 Service Pack 1 can

also be downloaded from

http://www.microsoft.com/download/en/details.

aspx?id=26727. The three architectures of

Service Pack 1 should be included. The required

package names are listed in the following table

row.

SQLServer2008R2SP1-KB2528583-IA64-ENU.exe

SQLServer2008R2SP1-KB2528583-x64-ENU.exe

SQLServer2008R2SP1-KB2528583-x86-ENU.exe

8 The actions in the script are adapted from http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-

server-2008-r2-service-pack-1-sp1.aspx.

9 The final slipstreamed source is ~6.5GB in size.

Copy the three SQL Server 2008 R2 SP1 CU4 files

to the folder named \SQL\SQL2008R2CU

created in the previous step.

Note: SQL Server 2008 R2 SP1 CU4 can also be

downloaded from

http://support.microsoft.com/kb/2633146. The

three architectures of CU4 should be included.

Expand zip to SQLServer2008R2-KB2633146-

IA64.exe

Expand zip to SQLServer2008R2-KB2633146-x64.exe

Expand zip to SQLServer2008R2-KB2633146-x86.exe

Run Microsoft Windows PowerShell command

line interface as an Administrator.

Copy the text for SLIPSQL.PS1 from Appendix C

and save it in a file named SLIPSQL.PS1 in the

SQL directory.

Run the script SLIPSQL.PS1 in Windows

PowerShell.

Note: before this script can be run the

execution policy in Windows PowerShell must

be set to Bypass or Unrestricted. This can be

performed with the following command:

Get-ExecutionPolicy

Note: Capture the policy state for later use:

Set-ExecutionPolicy ExecutionPolicy Bypass

After the script is complete, the execution policy

can be returned to its previous state by running

the Set-ExecutionPolicy command and

specifying the prior state.

The SQL Server Slipstream Script will launch. At

each prompt, provide the location of the

following folders:

SQL RTM Source Path

(\SQL\SQL2008R2RTM).

SQL Service Pack Source Path

(\SQL\SQL2008R2SP).

SQL Cumulative Update Source Path

(\SQL\SQL2008R2CU).

Note: Folder paths must not contain spaces.

When prompted, provide a path for the new

slipstreamed build to be created. Note that this

folder must not exist prior to running this script.

Note: If a folder exists with this name, the script

will return an error and exit gracefully.

A confirmation page will be presented. Verify

that the correct locations are specified. If not,

press N to re-enter the values. If they are

correct, press Y and press Enter.

The script will begin to create the slipstreamed

build. The initial phase requires the duplication

of the source RTM media to the new location.

This can take several minutes and the script may

not appear to be performing any actions. Please

be patient during this process and do not

perform any action that may otherwise interrupt

the process.

After a few minutes the Service Pack files will be

extracted one by one. This process may require

interaction depending on the source of the

downloaded Service Pack and security settings

of the operating system.

Note: If security warnings are displayed due to

the platform security configuration, click Run.

When complete, each architecture will be

integrated with the source build to update the

media to include SP1.

Cumulative Update files will be extracted one by

one. This process may require interaction

depending on the source of the downloaded

Cumulative Update files and security settings of

the operating system.

Note: if a security warning is displayed due to

the platform security configuration, click Run.

When complete, each architecture will be

integrated with the source build to update the

media to include SP1 CU4.

When completed, the folder specified for the

destination build will be created containing the

newly slipstreamed SQL Server build.

Verify that each architecture folder (\x86, \x64

and \ia64) has a DefaultSetup.ini with the edited

PCUSOURCE and CUSOURCE. These values can

also be supplied in a command line installation.

In order to verify if SQL Server 2008 R2 SP1 CU4

was properly slipstreamed, right-click the

setup.exe file and click the Details tab. The

Product version value should be 10.50.2796.0

to reflect the updated, slipstreamed version.

When completed, copy the folder to an

accessible share for installation into the virtual

machine.

3.2.4 Establish the SQL Server Guest Cluster

Assuming storage with iSCSI interface is available and youre implementing a SQL Server guest cluster, the

following steps can be followed to create the SQL Server guest cluster. Access to iSCSI LUNs is required to allow

each guest virtual machine in the cluster to access shared storage. Prior to completing the following steps, the

storage should be provisioned and presented to the nodes, but not yet made online, initialized, and formatted.

As stated previously, the recommended storage for the Private Cloud Fast Track Solution is as follows:

One LUN quorum (1 GB).

One LUN MSDTC (1 GB).

Two LUNs for each fabric management component instance (20 LUNs for all products).

During the provisioning process, four virtual machines were built to the specifications outlined in the Private

Cloud Fast Track Reference Architecture Guide to support SQL Server operations for fabric management. Once

created, the iSCSI targets must be configured within each virtual machine to make them accessible by each

candidate cluster node.

Perform the following steps on all fabric management SQL Server virtual machines.

Log on to the first node in the SQL Server cluster

with a user with local admin rights.

Verify that the following accounts and/or groups

are members of the Local Administrators group

on the first and second SQL Server nodes:

Fast Track SQL Server service account.

Fast Track SQL Server Admins group.

Virtual Machine Manager computer

accounts.

Fast Track Service Manager OLAP

account.

Fast Track Service Manager SSRS

account.

Fast Track Service Manager workflow

account.

Fast Track Service Manager service

account.

Fast Track Operations Manager action

account.

Fast Track Virtual Machine Manager

service account.

To attach the guest cluster to the iSCSI LUNs,

the iSCSI Initiator must be configured on each

SQL Server virtual machine.

Note: If using third-party Storage Area Network

(SAN) connectivity software, the in-box iSCSI

initiator steps can be skipped.

From the Start Menu, navigate to the

Administrator Tools folder and click the iSCSI

Initiator shortcut. When the iSCSI Initiator

Properties dialog box appears, click the

Targets tab. In the Target box, supply the IP

address or fully qualified domain name (FQDN)

of the iSCSI target and click Quick Connect to

establish connectivity with the desired iSCSI

target.

The Quick Connect dialog box will provide a list

of discovered targets. When the Progress

report pane shows Login Succeeded, click Done

to close the dialog box.

In the iSCSI Initiator Properties dialog box,

click the Volumes and Devices tab. In some

cases you may need to click Auto Configure to

establish connectivity with the LUNs advertised

to this initiator.

Click OK to close the iSCSI Initiator Properties

dialog box.

Perform the following steps on the first fabric management SQL Server virtual machine. Perform these

operations on a single node prior to creating the failover cluster.

Within Server Manager, navigate to the

Storage node and expand the Disk

Management snap-in. The iSCSI LUNs should

be visible in the snap-in, but should appear

offline.

Right-click each disk and click Online on the

shortcut menu. This step must be completed for

each attached iSCSI LUN. As described above,

perform this action on a single node of the

cluster.

Once each disk is online, right-click the first disk

and click Initialize Disk on the shortcut menu.

As described above, perform this action on a

single node of the cluster.

The Initialize Disk dialog box will appear. Verify

that each iSCSI LUN check box is selected in the

Select disks section. Verify that the MBR

(Master Boot Record) option is selected and

click OK to initialize the disks.

Once initialized, on the first node, right-click

each disk and click New Simple Volume on the

shortcut menu.

The New Simple Volume Wizard will appear.


In the Specify Volume Size dialog box, specify

the maximum disk space value in the Simple

volume size in MB box. Click Next to continue.

In the Assign Drive Letter or Path dialog box,

select the Mount in the following empty

NTFS folder option and specify a path in the

available text field. Click Next to continue.

In the Format Partition dialog box, select the

Format this volume with the following

settings option. In the File system drop-down

menu, select NTFS. In the Allocation unit size

drop-down menu, select Default. Optionally,

place a descriptive label in the Volume Label

box. Verify that the Perform a quick format

check box is selected and click Next to format

the partition.

Once complete, a confirmation dialog box will

appear. Click Finish to complete the operation

and repeat the operation for each disk.

Organizations should configure the interfaces according to their specific deployment characteristics. If there is a

separate physical networks used for iSCSI and/or inter-cluster private communications (also known as

heartbeat), you should reconnect the vNICs appropriately. Once complete, each disk should be brought online

one at a time, initialized, and formatted on the first candidate cluster node. Specifying meaningful volume

labels while formatting the disks can help in the future if one or more of the disks lose their assignment to the

cluster or virtual machines themselves and need be identified.

Important Note: The installation of a SQL Server cluster creates computer accounts in AD DS for each instance

in the cluster called cluster name objects (CNOs). By default, these objects are created in the default Computers

container (in other words, cn=Computers) of the target Active Directory domain. The account used to perform

the installation of the SQL Server cluster requires the rights in AD DS to create the associated CNOs for each

product SQL Server instance. This occurs as a standard part of the SQL Server installation process. There are

several approaches to mitigate this, including using a higher privileged account for installation, delegating

rights in AD DS for the account used for installation, or pre-creating the computer accounts in the target Active

Directory domain. Further discussion of this aspect of Windows Server Failover Cluster installation (and

mitigation strategies) can be found in the Windows Server 2008 R2 Failover Cluster Step-by-Step Guide.10

Perform the following steps on the first fabric management SQL Server node virtual machine with an

account that has both local Administrator rights and permissions in AD DS to create the SQL Server CNOs.

From an elevated Command Prompt within each

guest virtual machine (Node 1, Node 2, and

additional nodes such as Node 3 and Node 4, if

desired), run the following command to install

the Failover Clustering feature on Windows

Server 2008 R2:

servermanagercmd i Failover-Clustering11

Alternatively, the Failover Clustering feature can

be installed from an elevated Windows

PowerShell prompt using the following

commands:

Import-Module ServerManager

Add-WindowsFeature Name FailoverClustering

10

Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory - http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx.

11 While the use of servermanagercmd is deprecated for future releases in favor of PowerShell cmdlets, this method is satisfactory for the installation

and the warning can be safely ignored.

The first step is performing Cluster Validation.

From an elevated Windows PowerShell prompt

on the first SQL Server node, run the following

commands to test the cluster configuration:

Import-Module FailoverClusters

Test-Cluster , , ,

If successful, the Test-Cluster cmdlet provides a

validation report that can be opened in a local

browser from %TEMP% as outlined below.

Note: The validation stage of the cluster

creation may take up to an hour to complete.

Navigate to %TEMP% and review the Failover

Cluster Validation Report for errors and

warnings. Perform any required remediation and

reperform the cluster tests above as required.

The next step is to create the cluster. From the

same elevated Windows PowerShell prompt, run

the following commands to test the cluster

configuration:

New-Cluster -Node , , ,

-Name -StaticAddress

If successful, the cluster name will be displayed

as output once the process is complete.

Note: If using Dynamic Host Configuration

Protocol (DHCP) for the cluster nodes the

StaticAddress parameter should not be used.

Once cluster creation is complete, verify the

correct LUN was assigned as the quorum disk. If

the incorrect disk was assigned, the correct

assignment can be made using the following

Windows PowerShell cmdlet:

Set-ClusterQuorum -NodeAndDiskMajority

Note: For a three-node initial cluster installation,

this command is not applicable.

Verify all cluster networks are assigned properly.

Take care to document which cluster network

name is assigned to the public and private

network interfaces.

Document all disk assignments in the cluster.

Create a mapping table of available storage (by

name) to drive letters or mount points. This

information will be used during the SQL Server

installation.

3.2.5 Add the .NET Framework 3.5.1 Features

The SQL Server installation requires the Microsoft .NET Framework 3.5.1 Features be enabled on each host to

support installation. To enable the .NET Framework 3.5.1 Features, perform the provided steps.

Perform the following steps on both fabric management SQL Server virtual machines.

To add the .NET Framework 3.5.1 Features, from

Server Manager, select the Features node and

click Add Features. The Add Features Wizard

will appear. In the Select Features dialog box,

select .NET Framework 3.5.1 Features, and

then select the .NET Framework 3.5.1 check

box only. Leave the WCP Activation check box

clear.

In the Confirm Installation Selections dialog

box, review the choices made during the wizard

and click Install to add the feature.

The Installation Progress dialog box will show

the progress of the feature install.

When complete, the Installation Results dialog

box will appear. Verify that the .NET Framework

3.5.1 Features installed correctly. After you have

verified their installation, click Close to complete

the installation of the .NET Framework 3.5.1

Features.

3.2.6 Cluster MSDTC on Node 1

Prior to performing the installation of SQL, the MSDTC service must be clustered. Note that prior to installation,

the first node of the SQL Server cluster must have ownership of the LUNs. The following steps and automation

are provided to assist with the clustering of this service.



To cluster the MSDTC service, from an elevated

Windows PowerShell prompt, run the following

commands:

Import-Module FailoverClusters

Add-ClusterServerRole -Name

-Storage

-StaticAddress

Get-ClusterGroup | Add-

ClusterResource -Name -

ResourceType "Distributed Transaction Coordinator"

Add-ClusterResourceDependency

Add-ClusterResourceDependency

Start-ClusterGroup

( gwmi -Namespace root/MSCluster -Class

MSCluster_ResourceGroup | ?{ $_.Name -eq

} ).SetGroupType(103)

Move-ClusterGroup -Node

Within the Failover Clustering MMC, verify that

the MSDTC service has been properly created

and clustered. It is important to verify that the

icon for MSDTC is not that of a generic service

to promote proper operation.

Once the clustering of the MSDTC service is completed and verified, the installation of SQL Server in a cluster

configuration can proceed.

3.3 Installation

3.3.1 Install the SQL Server Named Instances on the Guest Cluster (Node 1)

Prior to performing installation of the SQL Server cluster, the information gathered in previous steps must be

compiled to provide a point of reference for the steps required during setup. The following example is

provided.

Component Virtual

Machine

Manager

App

Controller

Orchestrator Operations

Manager

Operations

Manager

Data

Warehouse

Service

Manager

management

server

Service

Manager

analysis

server

Service

Manager

Data

Warehouse

server

Microsoft

SharePoint

services Farm

Cluster

Service

Name

SQL Server

(SCVMMDB)

SQL Server

(SCACDB)

SQL Server

(SCODB)

SQL Server

(SCOMDB)

SQL Server

(SCOMDW)

SQL Server

(SCSMDB)

SQL Server

(SCSMAS)

SQL Server

(SCSMDW)

SQL Server

(SCSPFarm)

Clustered

SQL Server

Instance IP

Address

10.1.1.22 10.1.1.23 10.1.1.24 10.1.1.25 10.1.1.26 10.1.1.27 10.1.1.28 10.1.1.29 10.1.1.30

Host

Cluster

Public

Network

Interface

Name

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Cluster

Network 2

Host

Cluster

Public

Network

Interface

Subnet

Mask

255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

SQL Server

Instance

DATA

Cluster

Disk

Resource

Cluster Disk 2 Cluster Disk 4 Cluster Disk 6 Cluster Disk 8 Cluster Disk 10 Cluster Disk 12 Cluster Disk

14

Cluster Disk

16

Cluster Disk

18

SQL Server

Instance

DATA Drive

E: G: I: K: M: O: Q: S: U:

SQL Server

Instance

Failover

Cluster

Network

Name

SQLSCVMMDB SQL SCACDB SQLSCODB SQLSCOMDB SQLSCOMDW SQLSCSMDB SQLSCSMAS SQLSCSMDW SQLSCSPFarm

SQL Server

Instance

Install

Drive

E: G: I: K: M: O: Q: S: U:

SQL Server

Instance

LOG

Cluster

Disk

Resource

Cluster Disk 3 Cluster Disk 5 Cluster Disk 7 Cluster Disk 9 Cluster Disk 11 Cluster Disk 13 Cluster Disk

15

Cluster Disk

17

Cluster Disk

19

SQL Server

Instance

LOG Drive

F: H: J: L: N: P: R: T: V:

SQL Server

Instance

Name

SCVMMDB SCACDB SCODB SCOMDB SCOMDW SCSMDB SCSMAS SCSMDW SCSPFarm

Component Virtual

Machine

Manager

App

Controller

Orchestrator Operations

Manager

Operations

Manager

Data

Warehouse

Service

Manager

management

server

Service

Manager

analysis

server

Service

Manager

Data

Warehouse

server

Microsoft

SharePoint

services Farm

SQL Server

Instance

TEMPDB

Drive

F: H: J: L: N: P: R: T: V:

Table 6: SQL Server named instances on guest cluster

The template provided in Appendix A of this document should assist with capturing this information for the

installation process. Once gathered, the following steps are provided to perform installation. Note that at this

point during the installation, the first node of the SQL Server cluster must have ownership of the LUNs.



As outlined before, the physical architecture in

the Private Cloud Fast Track Reference

Architecture Guide recommends separate

instances for each System Center component.

The instances associated with these components

are:

1. SCACDB (App Controller database

instance).

2. SCODB (Orchestrator database

instance).

3. SCOMDB (Operations Manager

database instance).

4. SCOMDW (Operations Manager Data

Warehouse instance).

5. SCSMAS (Service Manager SQL Analysis

Services instance).

6. SCSMDB (Service Manager database

instance).

7. SCSMDW (Service Manager Data

Warehouse instance).

8. SCSPFarm (Service Manager self-service

portal Microsoft SharePoint Foundation

2010 services instance).

9. SCVMMDB (Virtual Machine Manager

database instance and optional WSUS

database instance).

For multi-instance failover clusters, installation

for SQL Server 2008 R2 must be performed once

for each instance. As such, these steps must be

performed for each instance sequentially.

From the SQL Server 2008 R2 slipstreamed

installation media source, right-click setup.exe

and click Run as administrator on the shortcut

menu to begin setup.

The SQL Server Installation Center will appear.

From the SQL Server Installation Center, click

the New SQL Server failover cluster

installation link.

The SQL Server 2008 R2 Setup wizard will

appear. In the Setup Support Rules dialog box,

verify that each rule shows a Passed status. If

any rule requires attention, remediate the issue

and rerun the validation check. Click OK to

continue.

In the Product Key dialog box, select the Enter

the product key option and type the associated

product key in the provided box. Click Next to

continue.

Note: If you do not have a product key, select

the Specify a free edition option and select

Evaluation from the drop-down menu for a

180-day evaluation period.

In the License Terms dialog box, select the I

accept the license terms check box. Select or

clear the Send feature usage data to

Microsoft check box based on your

organizations policies, and then click Next to

continue.

In the Setup Support Files dialog box, click

Install and allow the support files to install.

In the Setup Support Rules dialog box, verify

that each rule shows a Passed status. If any rule

requires attention, remediate the issue and

rerun the validation check. Click Next to

continue.

In the Feature Selection dialog box, features for

the various instances will be selected. Note that

not all features are supported for failover cluster

installations, so the features for Private Cloud

Fast Track are limited to the features as listed

below. SQL Server with failover clusters requires

the selection of the SQL Server Replication

check box and the Full-Text Search check box

with every instance. The following additional

selections are required for each instance:

SCACDB

o Database Engine Services

SCODB


SCOMDB


SCOMDW


SCSMAS

o Analysis Services

SCSMDB


SCSMDW


SCSPFarm


SCVMMDB


Select the Management Tools Basic check

box and Management Tools Complete check

box for at least one instance installation pass.

When all selections are made, click Next to

continue.

Database Engine Services (all instances except SCSMAS):

Analysis Services (SCSMAS instance only):

In the Instance Configuration dialog box,

make the following selections (refer to the

worksheet created earlier):

SQL Server Network Name specify

the cluster network name of the failover

cluster instance being installed.

Select the Named instance option. In the

provided box, specify the instance name being

installed.

Instance ID specify the instance name

being installed. Verify that it matches the

Named instance value.

Instance root directory accept the

default location of

%ProgramFiles%\Microsoft SQL Server.


In the Disk Space Requirements dialog box,

verify that you have sufficient disk space and

click Next to continue.

In the Cluster Resource Group dialog box, in

the SQL Server cluster resource group name

drop-down menu, accept the default value of

SQL Server (). Click Next to

continue.

In the Cluster Disk Selection dialog box, refer

to the worksheet created earlier to make the

proper disk selections. Two cluster disks will be

selected to support separation of databases and

logs for each database instance. Make the

selections by selecting the appropriate Cluster

Disk check boxes and click Next to continue.

In the Cluster Network Configuration dialog

box, refer to the worksheet created earlier to

assign the correct IP for each instance. Clear the

DHCP check box if you are using static

addressing and enter in the TCP and/or IP

address in the Address field box. Once

complete, click Next to continue.

In the Cluster Security Policy dialog box, select

the Use service SIDs (recommended) option

and click Next to continue.

In the Server Configuration dialog box, click

the Service Accounts tab. Specify the Fast Track

SQL Server Service Account and associated

password for the SQL Server Agent and SQL

Server Database Engine services.

Note: The Fast Track SQL Server Service Account

will also be used for the SQL Server Analysis

Services service for the instances where these

feature are selected.

In the same Server Configuration dialog box,

select the Collation tab. Accept the default

collation in the Database Engine box (unless

multiple language support is required in

SCSM12), and then click Next to continue.

12

http://social.technet.microsoft.com/wiki/contents/articles/7784.collation-in-system-center-2012-service-manager.aspx.

In the Database Engine Configuration dialog

box, click the Account Provisioning tab. In the

Authentication Mode section, select the

Windows authentication mode option. In the

Specify SQL Server administrators section,

Add Current User to add the current

installation user. Click Add to select the

previously created Fast Track SQL Server Admins

group from the object picker.

In the same Database Engine Configuration

dialog box, click the Data Directories tab. The

proper drive letter or mount point associated

with the Cluster Disk resource for SQL Server

data should be specified. If not, verify that the

proper Cluster Disk resource check boxes were

selected earlier and type the proper drive letter

in the Data root directory box. To redirect log

files by default to the second Cluster Disk

resource, change the drive letter in the User

databaselog directory and Temp DB log

directory boxes. It is also recommended to

change the Backup Directory to a separate drive

such as the log drive. Do not change the folder

structure unless your organization has specific

standards for this. When complete, click Next to

continue.

In the Analysis Services Configuration dialog

box, click the Account Provisioning tab. In the

Specify which users have administrative

permissions for Analysis Services section, click

Add Current User to add the current

installation user. Click Add to select the

following groups:

Service Manager instance:

Fast Track SQL Server Admins group.

Fast Track SM Admins group.

Fast Track SM OLAP account.


In the same Analysis Services Configuration

dialog box, select the Data Directories tab. The

proper drive letter or mount point associated

with the Cluster Disk resource for SQL Server

data should be specified. If not, verify that the

proper Cluster Disk resource check boxes were

selected earlier and enter the proper drive letter

in the Data root directory box. To redirect log

files by default to the second Cluster Disk

resource, change the drive letter in the User

databaselog directory and Temp DB log

directory boxes. Do not change the folder

structure unless your organization has specific

standards for this. When complete, click Next to

continue.

In the Error Reporting dialog box, select or

clear the Send Windows and SQL Server Error

Reports to Microsoft or your corporate

report server check box based on your

organizations policies and click Next to

continue.

In the Cluster Installation Rules dialog box,



and rerun the validation check. Click Next to

continue.

In the Ready to Install dialog box, verify all of

the settings that were entered during the setup

process, and then click Install to begin the

installation of the SQL Server instance.

In the Installation Progress dialog box, the

installation progress will be displayed.

When complete, the Complete dialog box will

appear. Click Close to complete the installation

of this SQL Server database instance.

Repeat these steps for each associated SQL

Server instance required for Fast Track

installation (nine instances total).

Verify the installation by inspecting the instances

in Failover Cluster Manager and in SQL Server

2008 Management Studio (SSMS) prior to

moving to the next step of installation.

Configure Microsoft Windows Firewall for SQL.

By default, named SQL Server instances will use

a unique dynamic port for each instance. If you

wish to leave the Windows Firewall enabled, you

must set each SQL Server instance to a static

port and open the corresponding port in the

Windows Firewall. In addition to each instance

port, you will need to open the standard SQL

Server ports of 1433 and 1434 for SQL Server to

function.

Note: The process for setting SQL Server named

instances to use static ports is documented at

http://support.microsoft.com/kb/823938.

3.3.2 Install the SQL Server Named Instances on the Guest Cluster (Additional

Nodes)

Once the creation of all required SQL Server instances on Node 1 is complete, additional nodes (Node 2

required, additional nodes are optional) can be added to each instance of the cluster. Follow the steps below to

begin the installation of additional nodes of the cluster.

Perform the following steps on each additional fabric management SQL Server node virtual machine.

From the SQL Server 2008 R2 slipstreamed

installation media source, right-click setup.exe

and select Run as administrator from the

shortcut menu to begin setup.

The SQL Server Installation Center will appear.

From the SQL Server Installation Center, click

the Add node to a SQL Server failover cluster

link.

The SQL Server 2008 R2 Setup wizard will

appear. In the Setup Support Rules dialog box,



and rerun the validation check. Click OK to

continue.

In the Product Key dialog box, select the Enter

the product key option and type the associated

product key in the provided box. Click Next to

continue.

Note: If you do not have a product key, select

the Specify a free edition option and select

Evaluation from the drop-down menu for a

180-day evaluation period.

In the License Terms dialog box, select the I

accept the license terms check box. Select or

clear the Send feature usage data to

Microsoft based on your organizations policies,

and then click Next to continue.

In the Setup Support Files dialog box, click

Install and allow the support files to install.

In the Setup Support Rules dialog box, verify

that each rule shows a Passed status. If any rule



continue.

In the Cluster Node Configuration dialog box,

select the desired instance name from the SQL

Server instance name drop-down menu. Each

instance will be listed along with the nodes

currently assigned to each instance. Click Next

to continue.

In the Service Accounts dialog box, specify the

Fast Track SQL Server Service Account and

associated password for the SQL Server Agent

and SQL Server Database Engine services.

When complete, click Next to continue.

Note: For the SCSMAS instance only, an

additional password must be supplied for the

SQL Server Analysis Services service account.

In the Error Reporting dialog box, select or

clear the Send Windows and SQL Server Error

Reports to Microsoft or your corporate

report server check box based on your

organizations policies, and then click Next to

continue.

In the Add Node Rules dialog box, verify that

each rule shows a Passed status. If any rule



continue.

In the Ready to Add Node dialog box, verify all

of the settings that were entered during the

setup process and click Install to begin the

installation of the second SQL Server node for

the selected instance.

Once complete, the Complete dialog box will

appear. Click Close to complete the installation

of this SQL Server database instance.

Repeat these steps for each associated SQL

Server instance required for Fast Track

installation (nine instances total).

Verify the installation by inspecting the instances

in Failover Cluster Manager and in SQL Server

Management Studio prior to moving to the next

step of installation.

Configure Windows Firewall for SQL Server.

By default, named SQL Server instances will use

a unique dynamic port for each instance. If you

wish to leave the Windows Firewall enabled, you

must set each SQL Server instance to a static

port and open the corresponding port in the

Windows Firewall. In addition to each instance

port, you will need to open the standard SQL

Server ports of 1433 and 1434 for SQL Server to

function.

Note: The process for setting SQL Server named

instances to use static ports is documented at

http://support.microsoft.com/kb/823938.

4 Virtual Machine Manager

The System Center 2012 - Virtual Machine Manager installation process includes the following high-level steps.

System Center 2012 Virtual

microsoft private cloud fast track reference deployment guide.pdf

Documents