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
Solution Overview ................................................................................................. 10

1.1
Core Private Cloud Fast Track Infrastructure ...................................................................................................... 10
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
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
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
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
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
Servers
6.2.7
6.2.8
6.2.9
6.2.10
Install SQL Server 2008 R2 Analysis Management Objects on the Management and Data Warehouse
204
Install SQL Server Reporting Services (Split Configuration) on the Data Warehouse Server .... 207
Install SharePoint Foundation 2010 on the Self-Service Portal Server .............................................. 218
Install .NET Framework 4 on the Self-Service Portal Server ................................................................... 227
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
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
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
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 (joely@microsoft.com)
Solution Architect
Jeff Baker (jebaker@microsoft.com)
Architect
Adam Fazio (adamfaz@microsoft.com)
Solution Architect
Business stakeholders
Mike Truitt (mtruitt@microsoft.com)
Senior Product Planner
Bryon Surace (bryons@microsoft.com)
Senior Program Manager, Windows Server
Jim Dial (jdial@microsoft.com)
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 vendoragnostic 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 Microsoftvalidated 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
1.1
Solution Overview
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 twonode 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
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
Memory
Virtual
network
interface
cards
(vNICs)
Storage
(vCPU)
Microsoft SQL Server data management software
(at least two nodes in a cluster configuration)
16 to 32
gigabyte
(GB)
C: 60 GB
20 additional
logical unit
numbers
(LUNs)1
Microsoft System Center 2012 - Virtual Machine

Manager management server
8 GB
C: 60 GB2
Virtual Machine Manager management server

(in a two-node cluster)
8 GB
C: 60 GB3
Microsoft System Center 2012 - Operations Manager

management server
16 GB
C: 60 GB
Operations Manager reporting server
16 GB
C: 60 GB
Operations Manager (additional management server)
16 GB
C: 60 GB
Microsoft System Center 2012 - Service Manager

management server
16 GB
C: 60 GB
Service Manager (additional management server)
16 GB
C: 60 GB
Service Manager Data Warehouse
16 GB
C: 60 GB
Service Manager self-service portal
8 GB
C: 60 GB
SQL Server LUN size is dependent on Solution scale.
Additional disks may be created for Virtual Machine Manager library expansion as required.
Virtual
central
processing
unit
Memory
Virtual
network
interface
cards
(vNICs)
8 GB
C: 60 GB
Orchestrator Runbook Server
8 GB
C: 60 GB
Microsoft System Center 2012 - App Controller
8 GB
C: 60 GB
[Optional] Microsoft Windows Server Update Services

(WSUS) and Microsoft Windows Deployment Services
(WDS)
4 GB
C: 60 GB
(vCPU)
Microsoft System Center 2012 - Orchestrator
Storage
Runbook Server, Web Service, and Designer
Table 1: Fabric management infrastructure: Pattern one
vCPU
Memory
vNICs
Microsoft SQL Server

(at least two nodes in a cluster configuration)
16 to 32
GB
Virtual Machine Manager
8 GB
Storage
C: 60 GB
20 additional
LUNs4
C: 60 GB5
D: 120GB
Operations Manager management server
16 GB
C: 60 GB
Operations Manager reporting server
16 GB
C: 60 GB
Service Manager
16 GB
C: 60 GB
Service Manager Data Warehouse
16 GB
C: 60 GB
8 GB
C: 60 GB
Orchestrator
8 GB
C: 60 GB
App Controller
8 GB
C: 60 GB
[Optional] Windows Server Update Services and

Windows Deployment Services
4 GB
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.
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, rightclick 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
FT-SCAC-SVC
Operations
Manager
App Controller
services account
Management
server action
account
System Center
Operations
Manager
configuration
service and data
access service
account
Operations
Manager
Data Warehouse
write account
FT-SCOM-DW
Operations
Manager
Data reader
account
FT-SCOM-DR
Orchestrator
Orchestrator
services account
FT-SCO-SVC
Service Manager
Service Manager
services account
FT-SCSM-SVC
This account is used to run all App Controller

services.
This account is used to carry out actions on
monitored computers across a network
connection.
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.
The Data Warehouse write account writes data
from the management server to the reporting
Data Warehouse and reads data from the
operational database.
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.
This account is used to run the Orchestrator
Management Service, Orchestrator Runbook
Service and Orchestrator Runbook Server
monitor service.
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
Operations
Manager
FT-SCOM-Action
FT-SCOM-SVC
Component
User account
Suggested name
Description
the Builtin\Administrators group.
Service Manager
Service Manager
Service Manager
Service Manager
Service Manager
Service Manager
Service Manager
Service Manager
SQL Server
System Center
Virtual Machine
Manager
Service Manager
workflow
account
Service Manager
reporting
account
FT-SCSM-WF
Microsoft SQL
Server 2008
Analysis Services
account for
OLAP cubes
Operations
Manager alert
connector
Operations
Manager CI
connector
Active Directory
connector
Virtual Machine
Manager CI
connector
Orchestrator CI
Connector
SQL Server
instance service
account
Component
installation
account
Virtual Machine
Manager service
account
FT-SCSM-OLAP
FT-SCSM-SSRS
FT-SCSM-OMAlert
FT-SCSM-OMCI
FT-SCSM-ADCI
FT-SCSM-VMMCI
FT-SCSM-OCI
FT-SQL-Service
FT-SCInstall
FT-VMM-SVC
This account is used for all workflows and is

made a member of the Service Manager
workflows user role.
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.
This account is used by SQL Server Analysis
Services (SSAS) for Service Manager reports.
This account is used for Service Manager

Operations Manager Alert connector
operations.
Operations Manager continuous integration
(CI) connector operations.
Active Domain connector operations.
Virtual Machine Manager connector
operations.
This account is used for System Center
Orchestrator connector operations.
This account is used as the service account for
all instances of SQL Server used in System
Center.
This optional account is used to install all
System Center 2012 components.
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
Orchestrator
FT-SCO-Admins
Orchestrator
Orchestrator
Administrators
Orchestrator Operators
Service
Manager
Service Manager
Admins
FT-SCSM-Admins
SQL Server
SQL Server
Administrators
FT-SQL-Admin
System
Center 2012
Virtual
Machine
Manager
System Center
Administrators
Virtual Machine
Manager
Administrators
FT-SC-Admins
This groups members are administrators for

the Operations Manager installation and hold
the Administrators role in Operations
Manager.
the Orchestrator installation.
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.
This group is added to the Service Manager
Administrators user role and the Data
Warehouse Administrators user role.
This groups members are sysadmins on all
SQL Server instances and local administrators
on all SQL Server nodes.
This groups members are full Admins on all
System Center components.
the Virtual Machine Manager installation and
hold the Administrators role in Virtual
Machine Manager.
FT-SCO-Operators
FT-SCVMMAdmins
Table 4: Active Directory security groups required for the Private Cloud Fast Track System Center 2012 installation
SQL Server 2008 R2 Cluster Installation

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

Installation
Perform
Prerequisites
Install the SQL

Named Instances
on Node 1 of the
Guest Cluster
Add additional
SQL Nodes for
each named
instance
Instantiate the
Guest Cluster
Install the .NET

Framework 3.5.1
Feature
Cluster MSTDC
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:
Physical servers
Virtual machines
Storage:
o
Fibre Channel (not feasible for virtual machines in guest failover cluster)
iSCSI
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)
One LUN Microsoft Distribution Transaction Coordinator service (MSDTC) (1 GB)
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
Components
Collation 7
Storage
requirements
SCSMAS
Analysis Services
SQL_Latin1_General_CP1_CI_AS
2 LUNs
SCSPFarm
Database Engine
2 LUNs
App Controller
SCACDB
Database Engine
2 LUNs
Operations Manager
SCOMDB
Database Engine,
2 LUNs
2 LUNs
(suggested)
Full-Text Search
Operations Manager
Data Warehouse
SCOMDW
Database Engine,
Orchestrator
SCODB
Database Engine
2 LUNs
Service Manager
SCSMDB
Database Engine,
2 LUNs
2 LUNs
Full-Text Search
Full-Text Search
Service Manager
Data Warehouse
SCSMDW
Database Engine,
Virtual Machine
Manager
SCVMMDB
Database Engine
2 LUNs
Windows Server
Update Services
(optional)
SCWSUSDB
Database Engine
2 LUNs
Full-Text Search
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.
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 Manag er databases
(Management, Data Warehouse, and Reporting Services).
3.2.1 Accounts
Verify that the following accounts have been created.
User name
Purpose
Permissions
<DOMAIN>\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
<DOMAIN>\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.
SQLServer2008R2SP1-KB2528583-IA64-ENU.exe
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
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-x86-ENU.exe
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-sqlserver-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.
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.
Expand zip to SQLServer2008R2-KB2633146IA64.exe
Expand zip to SQLServer2008R2-KB2633146-x64.exe
Expand zip to SQLServer2008R2-KB2633146-x86.exe
The SQL Server Slipstream Script will launch. At

each prompt, provide the location of the
following folders:
SQL RTM Source Path
(<drive>\SQL\SQL2008R2RTM).
SQL Service Pack Source Path

(<drive>\SQL\SQL2008R2SP).
SQL Cumulative Update Source Path

(<drive>\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
11
Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory - http://technet.microsoft.com/en-us/library/cc731002(WS.10).aspx.
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 <Node1>, <Node2>, <Node3>,
<node4>
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 <Node1>, <Node2>, <Node3>,
<Node4> -Name <ClusterName> -StaticAddress
<ClusterIPAddress>
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
<ClusterQuorumDisk>
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:
Add-ClusterServerRole -Name
<DTCClusterGroupName> -Storage
<DTCClusterDisk> -StaticAddress
<DTCClusterIPAddress>
Get-ClusterGroup <DTCClusterGroupName> | AddClusterResource -Name <DTCClusterResName> ResourceType "Distributed Transaction Coordinator"
Add-ClusterResourceDependency
<DTCClusterResName> <DTCClusterGroupName>
Add-ClusterResourceDependency
<DTCClusterResName> <DTCClusterDisk>
Start-ClusterGroup <DTCClusterGroupName>
( gwmi -Namespace root/MSCluster -Class
MSCluster_ResourceGroup | ?{ $_.Name -eq
<DTCClusterGroupName>} ).SetGroupType(103)
Move-ClusterGroup <DTCClusterGroupName> -Node
<Node1>
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
Host
Cluster
Public
Network
Interface
Subnet
Mask
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
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
SQL Server
Instance
TEMPDB
Drive
F:
H:
Orchestrator
J:
Operations
Manager
Operations
Manager
Data
Warehouse
Service
Manager
management
server
Service
Manager
analysis
server
Service
Manager
Data
Warehouse
server
Microsoft
SharePoint
services Farm
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
SCSPFarm
o
SCSMDW
o
Analysis Services
SCSMDB
o
SCSMAS
o
SCOMDW
o
SCOMDB
o
SCODB
o
Database Engine Services (all instances except SCSMAS):
SCVMMDB
o
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.
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 (<InstanceName>). 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
Specify which users have administrative
permissions for Analysis Services section, click
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.
and select Run as administrator from the
shortcut menu to begin setup.

the Add node to a SQL Server failover cluster
link.
continue.

continue.

Microsoft based on your organizations policies,


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.

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

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.

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

Virtual Machine
Manager Installation
Installation of
System Center
2012 Virtual
Machine Manager
Perform
Prerequisites
Install the .NET

Framework 3.5.1
Feature
Install the SQL

Server 2008 R2
Command Line
Utilities
Pattern 1
Installation: HA
Management
Server
Install the
Windows
Automated
Installation Kit
(AIK)
Install the .NET

Framework 4
Redistributable
Pattern 1
Installation:
Create the HA
SCVMM Library
Share
Install the AIK

Supplement for
Windows 7 SP1
Create the VMM

Distributed Key
Management
Container in
Active Directory
Pattern 2
Installation:
Stand-alone
Management
Server
Install the
Windows Server
Update Services
Administration
Console
Figure 4: Virtual Machine Manager installation process
4.1
Overview
This section provides a high-level walkthrough about how to set up and run the task sequence and scripts for
deploying Virtual Machine Manager into the Private Cloud Fast Track fabric management architecture. The
following assumptions are made prior to the installation:
If deploying Design Pattern 1, a base virtual machine running Windows Server 2008 R2 (x64) has been
provisioned for Virtual Machine Manager.
The selected installation type during install must be Full Installation.
The startup RAM must be at least 2 GB for a virtual machine with Dynamic memory.
If deploying Design Pattern 2, two base virtual machines running Windows Server 2008 R2 (x64) have
been provisioned and configured as a Windows Failover Cluster.
o
For high-availability (HA) Virtual Machine Manager management server, you must use the
Enterprise or Datacenter editions of Windows Server 2008 R2.
Requires at least two iSCSI shared storage LUNs.
Requires a dedicated virtual network adapter for cluster communication.
Requires at least one dedicated virtual network adapter for iSCSI.
The selected installation type during install must be Full Installation.
The Microsoft .NET Framework 4 Redistributable is installed.
The target virtual machines must have the Windows Automated Installation Kit 3.013 and Windows
Automated Installation Kit 3.0 supplement for SP114 installed.
The target virtual machine must have the WSUS 3.0 console installed.
A four-node, SQL Server 2008 R2 cluster with dedicated instance has been established in previous steps
for Virtual Machine Manager.
The Virtual Machine Manager SQL Server instance has two drives configured in SQL Server for the
instance devoted for Virtual Machine Manager:
Data
Logs
The Virtual Machine Manager SQL Server instance must be case-insensitive (default on SQL Server 2008
R2).
The SQL Server name must not exceed 15 characters.
The account used to install Virtual Machine Manager must have the rights needed to connect to the
remote SQL Server instance and create databases.
The installation account must have rights to create the VMMDKM container in AD DS, or this
container must already exist prior to running Virtual Machine Manager setup.
4.2
Prerequisites
4.2.1 Accounts
User name
Purpose
Permissions
<DOMAIN>\FT-VMM-SVC
Virtual Machine
Manager Service
Account

permissions on all target systems
to be managed and the Virtual
Machine Manager server virtual
machine.
<DOMAIN>\FT-SQL-SVC
SQL Server Service

Account

permissions on the Virtual
Machine Manager server virtual
machine.
13
The Windows Automated Installation Kit for Windows 7 - http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5753.
14
The Windows Automated Installation Kit Supplement for Windows 7 SP1 - http://www.microsoft.com/download/en/details.aspx?id=5188.
Note: The user account that initiates the installation process must have dbowner permissions in the SQL Server
instance dedicated to Virtual Machine Manager. This can be achieved by adding this account to the FT-SQLADMINS group.
4.2.2 Groups
Security group name
Group scope
Members
<DOMAIN>\FT-VMM-Admins
Global
FT-VMM-SVC
<DOMAIN>\FT-VMMDelegatedAdmins
Global

Delegated Admins
<DOMAIN>\FT-VMM-SSUsers
Global
Virtual Machine Manager SelfService Users
<DOMAIN>\FT-VMM-ROAdmins
Global
Virtual Machine Manager Read

Only Admins
4.2.3 Adding the .NET Framework 3.5.1 Features

The Virtual Machine Manager installation requires the .NET Framework 3.5.1 Features to be enabled to support
installation. The following steps show how to enable the .NET Framework 3.5.1 Features.
Perform the following steps on the Virtual Machine Manager virtual machine. For Design Pattern 1,
clustered Virtual Machine Manager, perform this step on both Virtual Machine Manager virtual machines.
select the .NET Framework 3.5.1 check box
only. Leave the WCF Activation check box clear.


the progress of the feature installation.

3.5.1 Features installed correctly. When verified,
click Close to complete the installation of the
.NET Framework 3.5.1 Features.
4.2.4 Install the Windows Automated Installation Kit

The Virtual Machine Manager installation requires that the Windows Automated Installation Kit (AIK) is installed
on the Virtual Machine Manager management server. The following steps show how to install the Windows AIK
on the Virtual Machine Manager management server.
Perform the following steps on the Virtual Machine Manager virtual machine.
From the Windows AIK installation media
source, right-click setup.exe and select Run as
administrator from the shortcut menu to begin
setup.
The Welcome splash screen will appear. Click

the Windows AIK Setup option from the
sidebar to begin installation.
The Windows Automated Installation Kit

wizard will appear. Click Next to continue.

Agree option. Click Next to continue.
In the Select Installation Folder dialog box,

accept the default folder location of
%ProgramFiles%\Windows AIK. Select the
Everyone option and click Next to continue.
In the Confirm Installation dialog box, click

Next to continue.
In the Installation Complete dialog box, click

Close to exit the installation wizard.
4.2.5 Install the Windows Automated Installation Kit Supplement for Windows
7 SP1
The Windows Automated Installation Kit (AIK) Supplement should be installed in addition to the core AIK
binaries. The following steps show how to install the AIK Supplement.
Perform the following steps on the Virtual Machine Manager virtual machine. For clustered Virtual
Machine Manager, perform this step on both Virtual Machine Manager virtual machines.
Mount the supplement ISO to the virtual
machine and browse to the contents. Note the
drive letter of the ISO once it is mounted to the
virtual machine.
Note: The Windows AIK Supplement for
Windows 7 SP1 can be downloaded from
aspx?id=5188.
Open an elevated command prompt.

Replace the installed Microsoft Windows
Preinstallation Environment (PE) 3.0 files with
the corresponding Microsoft Windows PE 3.1
files from the ISO. To do this, run the following
command:
xcopy D:\ "C:\Program Files\Windows
AIK\Tools\PETools" /ERDY
In this example D:\ is the root directory of the

ISO image.
Note: C:\Program Files\Windows AIK\ is the
default installation location. If you installed the
AIK Supplement to a different location, modify
the command accordingly.
For full details on the AIK and the AIK

Supplement, refer to the readme file located at
http://technet.microsoft.com/enus/library/dd349350(WS.10).aspx.
4.2.6 Install the Windows Server Update Services Administration Console

The Virtual Machine Manager installation requires that the WSUS Administration is installed on the Virtual
Machine Manager management server. Follow the steps below to install the WSUS Administration on the Virtual
Machine Manager management server.
From the WSUS 3.0 Service Pack 2 (SP2)
installation media source, right-click WSUS30KB972455-x64.exe and select Run as
setup.
Note: WSUS can be downloaded from
aspx?displaylang=en&id=5216.
The Windows Server Update Services 3.0 SP2
Setup Wizard will appear. Click Next.
In the Installation Mode Selection dialog box,

select Administration Console only option and
click Next.
In the License Agreement dialog box, select the

I accept the terms of the License agreement
option. Click Next to continue.
In the Required Components to use

administration UI dialog box, accept the
installation of the Microsoft Report Viewer 2008
Redistributable and click Next to continue.
The Installing dialog box will show the

installation progress.
The wizard will complete once the installation is

finished. Click Finish to complete the installation
and exit the wizard.
4.2.7 Install the SQL Server 2008 R2 Command Line Utilities

The Virtual Machine Manager installation requires that the SQL Server 2008 R2 Command Line Utilities and
Management Tools are installed on the Virtual Machine Manager management server. Follow the steps below
to install the Command Line Utilities and Management Tools on the Virtual Machine Manager management
server.
From the SQL Server 2008 R2 SP1 with CU4
slipstreamed installation media source, rightclick setup.exe and select Run as
setup.

the New installation or add features to an
existing installation link.

and re-run the validation check. Click OK to
continue.

continue.

continue.


requires attention, remediate the issue and rerun the validation check. Click Next to continue.
In the Setup Role dialog box, select the SQL

Server Feature Installation option and click
Next to continue.
In the Feature Selection dialog box, select the

Client Tools Connectivity, Management Tools
Basic, and Management Tools Complete
check boxes. When all selections are made, click
Next to continue.
In the Installation Rules dialog box, verify that

requires attention, remediate the issue and rerun the validation check. Click Next to continue.

verify that the installation has enough space on
the target drive and click Next to continue.

continue.
In the Installation Configuration Rules dialog

box, verify that each rule shows a Passed status.
If any rule requires attention, remediate the
issue and re-run the validation check. Click Next
to continue.

process and click Install to begin the installation
of the SQL Server instance.
Once complete, the Complete dialog box will

of SQL Server tools.
4.2.8 Install .NET Framework 4

Additionally, Virtual Machine Manager also requires the .NET Framework 4 package be installed prior to
installation. Perform the steps described below to install the .NET Framework 4 package.
From the installation media source, right-click
dotNetFx40_Full_x86_x64.exe and select Run
as administrator from the shortcut menu to
begin setup.
Within the Microsoft .NET Framework 4 Setup

dialog box, select the I have read and accept
the license terms check box and click Install to
begin the installation.
The installation progress will be displayed in the

setup wizard.
When completed, click Finish to exit the

installation.
4.2.9 Install Windows Fail-over Clustering (Design Pattern 1, Clustered Virtual

Machine Manager Only)
During the provisioning process for Design Pattern 1, two virtual machines were built to the specifications
outlined in the Private Cloud Fast Track Reference Architecture Guide to support HA Virtual Machine Manager
for fabric management. Once created, the iSCSI targets must be configured within each virtual machine to make
them accessible to each candidate cluster node.
Perform the following steps on both Virtual Machine Manager virtual machines.
To attach the guest cluster to the iSCSI LUNs,
the iSCSI Initiator must be configured on each
SQL Server virtual machine.
Note: Third-party SAN connectivity software can
be used in place of the in-box iSCSI Initiator. If a
third-party solution is used, the in-box iSCSI
Initiator steps can be skipped.

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 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 Virtual Machine Manager virtual machine. These operations
must occur on a single node prior to creating the failover cluster.
In Server Manager, navigate to the Storage
node and expand the Disk Management snapin. The iSCSI LUNs should be visible in the snapin, 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
then 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 (for example, WitnessDisk). Verify that the
Perform a quick format check box is selected
and click Next to format the partition.
When complete, a confirmation dialog box will

appear. Click Finish to complete the operation
and repeat the operation for each disk.
Perform the following steps on both Virtual Machine Manager virtual machines with an account that has
both local Administrator rights and permissions in AD DS to create the Virtual Machine Manager CNOs.
From an elevated Command Prompt within both
guest virtual machines (Node 1 and Node 2), run
the following command to install the Failover
Clustering feature on Windows Server 2008 R2:
servermanagercmd i Failover-Clustering15
Alternatively the Failover Clustering feature can

commands:
Add-WindowsFeature Name FailoverClustering
Perform the following steps on the first Virtual Machine Manager virtual machine with an account that
has both local Administrator rights and permissions in AD DS to create the Virtual Machine Manager
CNOs.
The first step is to perform Cluster Validation.
From an elevated Windows PowerShell prompt
on the first SQL Server node, run the following
commands to test the cluster configuration:
Test-Cluster <Node1>, <Node2>
If successful the Test-Cluster cmdlet will display

a validation report.
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
re-perform the cluster tests above as required.
15
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 next step is to create the cluster. From the

same elevated Windows PowerShell prompt,
perform the following commands to create the
cluster:
New-Cluster -Node <Node1>, <Node2> -Name
<ClusterName> -StaticAddress <ClusterIPAddress>
If successful, the cluster name will be displayed

as output once the process is complete.
Note: If using 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
<ClusterQuorumDisk>
Verify all cluster networks are assigned properly.

Take care to document which cluster network
name is assigned to the public and private
network interfaces.
4.2.10 Create the Virtual Machine Manager Distributed Key Management

Container in Active Directory Domain Services
The Virtual Machine Manager installation requires that an Active Directory container be created to house the
distributed key information for Virtual Machine Manager. 16 Note: if Virtual Machine Manager will be deployed
using an account with rights to create containers in AD DS, this step can be skipped. Perform the following steps
to create an AD DS container to house the distributed key information.
Perform the following steps on a Domain Controller in the domain where Virtual Machine Manager is to
be installed.
Log on to a Domain Controller with a user that
has Domain Admin privileges and run
adsiedit.msc.
Right-click the ADSI Edit node and click

Connect to on the shortcut menu.
16
Configuring Distributed Key Management in VMM - http://technet.microsoft.com/library/gg697604.aspx.
In the Connections Settings dialog box in the

Connection Point section, select the Select a
well known Naming Context option. Select
Default naming context from the drop-down
menu and click OK.
Expand Domain Default naming context

[<computer fully qualified domain name>],
expand <distinguished name of domain>, rightclick the root node, point to New, and then click
Object on the shortcut menu.
In the Create Object dialog box, select

Container and then click Next.
In the Value box, type VMMDKM and then click

Next.
Click Finish to create the container object.
Within ADSI Edit, right-click the new VMMDKM

object, and then click Properties on the
shortcut menu.
In the VMMDKM Properties dialog box, click

the Security tab. Click Add to add the VMM
Service account and VMM Admins group.
Grant the security principles Read, Write and
Create all child objects permissions.
Click OK three times, and then close ADSI Edit.
4.3
Design Pattern 1 Installation HA Virtual Machine Manager Management

Server (Failover Clustering)
Perform the following steps on the first Virtual Machine Manager virtual machine.
Log on to the Virtual Machine Manager

virtual machine with a user with local admin
rights.
Verify the following accounts and/or groups
are members of the Local Administrators
group on the Virtual Machine Manager
virtual machine:
Orchestrator service account.
Operations Manager action account.
Virtual Machine Manager Admins

group.
Virtual Machine Manager service

account.
SQL Server service account.
From the Virtual Machine Manager

installation media source, right-click
setup.exe and click Run as administrator
on the shortcut menu to begin setup.
The Virtual Machine Manager installation

wizard will begin. At the splash page, click
Install to begin the Virtual Machine Manager
server installation.
Attempting to select any feature will cause

the cluster management server notice to
appear.
Click Yes to switch to the highly available
Virtual Machine Manager setup wizard.
In the Select features to install dialog box,

verify that the VMM management server
check box is selected. After selecting it, the
VMM console check box will be selected by
default. Click Next to continue.
Note: Do not select the VMM Self-Service
Portal option because it is out of the scope
of the Private Cloud Fast Track solution, and
it is not supported in a HA Virtual Machine
Manager deployment.
In the Product registration information

dialog box, type the following information in
the provided boxes:
Name specify the name of primary

user or responsible party within your
organization.
Organization - specify the name of

the licensed organization.
Product key provide a valid

product key for installation of Virtual
Machine Manager. If no key is
provided, Virtual Machine Manager
will be installed in evaluation mode.

In the Please read this license agreement
dialog box, verify that the I have read,
understood, and agree with the terms of
the license agreement installation option
check box is selected. Click Next to continue.
In the Join the Customer Experience

Improvement Program (CEIP) dialog box,
select the option to either participate or not
participate in the CEIP by providing selected
system information to Microsoft. Click Next
to continue.
In the Microsoft Update dialog box, select

the option to either allow or not allow Virtual
Machine Manager to use Microsoft Update
to check for and perform Automatic Updates
based on your organizations policies. Click
Next to continue.
In the Installation location dialog box,

specify a location or accept the default
location of %ProgramFiles%\Microsoft System
Center 2012\Virtual Machine Manager for
the installation. Click Next to continue.
Note: The setup wizard has a prerequisite

checker built in. If for any reason a
prerequisite is not met, the setup user
interface will notify you of the discrepancy.
The following is just an example of that
UI.
If the system passes the prerequisite check,
no screen will be displayed and the setup
wizard will proceed to the Database
configuration screen.
In the Database configuration dialog box,

type the following information in the
provided boxes:
Server name specify the name of

SQL Server cluster created in the steps
above.
Port - specify the TCP port used for

the SQL Server, if not the default.
Verity that the Use the following

credentials check box is clear. In the
Instance name drop-down menu, select the
Virtual Machine Manager database instance
deployed earlier in the SQL Server cluster.
In the Select an existing database or create
a new database option, select the New
database option and accept the default
database name of VirtualManagerDB.
In the Cluster configuration dialog box, in

the Name field, provide a name for the
Virtual Machine Manager cluster service.
DHCP:
If the cluster node you are installing is

configured with static IP addresses you will
also need to provide an IP address for the
Virtual Machine Manager cluster service. If
the cluster node is configured to use DHCP,
no additional information is required.
Static IP:
In the Configure service account and

distributed key management dialog box, in
the Virtual Machine Manager Service
Account section, select the Domain account
option. Enter the following information in the
provided boxes:
User name and domain specify

the Virtual Machine Manager service
account identified in the section
above in the following format:
<DOMAIN>\<USERNAME>.
Password specify the password for

account identified above.
In the Distributed Key Management

section, select the Store my keys in Active
Directory check box. In the provided box,
type the distinguished name (DN) location
created earlier within Active Directory:
cn=VMMDKM,DC=domain,
In the Port configuration dialog box, accept
the default values in the provided boxes:
Communication with the VMM

console default: 8100.
Communication to agents on
hosts and library servers default:
5985.
File transfers to agents on hosts

and library servers default: 443.
Communication with Windows

Deployment Services default:
8102.

Preinstallation Environment
(Windows PE) agents default:
8101.
Communication with Windows PE

agent for time synchronization
default: 8103.
In the Library configuration dialog box, no

options are available for a highly available
installation. The Library must be configured
separately and should point to a highly
available file share. The process will be
covered separately in this guide. Click Next
to continue.
The Installation summary dialog box will

appear and display the selections made
during the installation wizard. Review the
options selected and click Install to continue.
The wizard will display the progress while

installing features.
When the installation completes, the wizard

will display the Setup completed
successfully dialog box. Click Close to
complete the installation.
When complete, launch the Virtual Machine

Manager console to verify the installation
occurred properly. Set the Server name
value to match the name that was provided
for the Cluster Resource name during setup
(for example, HAVMM: 8100). Verify that the
console launches and connects to the Virtual
Machine Manager instance installed.
Perform the following steps on the second Virtual Machine Manager virtual machine.
Log on to the second Virtual Machine

Manager virtual machine with a user with
local admin rights.
Verify that the following accounts and/or
groups are members of the Local
Administrators group on the Virtual Machine
Manager Virtual Machine:

group.

account.
From the Virtual Machine Manager

setup.exe and click Run as administrator
The Virtual Machine Manager installation

wizard will begin. On the splash page, click
Install to begin the Virtual Machine Manager
server installation.
Attempting to select any feature will cause

the cluster management server notice to
appear.
Click Yes to switch to the highly available
Virtual Machine Manager setup wizard and
add the second node.
Note: Virtual Machine Manager can be
deployed on up to 16 cluster nodes, but only
a single node can be active at any time.

Virtual Machine Manager console check
box will be selected by default. Click Next to
continue.
Note: Do not select the VMM Self-Service
Portal option because it is outside of the
scope of the Private Cloud Fast Track
solution, and it is not supported in a highly
available Virtual Machine Manager
deployment.
In the Product registration information
dialog box, provide the following information
in the boxes:

organization.
Organization specify the name of

the licensed organization.
Product key provide a valid

product key for installation of Virtual
Machine Manager. If no key is
provided, Virtual Machine Manager
will be installed in evaluation mode.

understood, and agree with the terms of
the license agreement check box is
selected. Click Next to continue.

participate in the CEIP by providing selected
system information to Microsoft. Click Next
to continue.
In the Microsoft Update dialog box, select

the option to either allow or not allow Virtual
Machine Manager to use Microsoft Update
to check for and perform Automatic Updates
based on your organizations policies. Click
Next to continue.
In the Installation location dialog box,

specify a location or accept the default
location of %ProgramFiles%\Microsoft System
Center 2012\Virtual Machine Manager for
the installation. Click Next to continue.

checker built in. If for any reason a
prerequisite is not met, the setup UI will
notify you of the discrepancy.
The following is just an example of that
UI.
If the system passes the prerequisite check,
no screen will be displayed and the setup
wizard will proceed to the Database
configuration dialog box.

all options are unavailable when adding an
additional node to an existing Virtual
Machine Manager cluster.

distributed key management dialog box,
when deploying additional nodes to a Virtual
Machine Manager cluster, all fields other
than Password are unavailable.
Password specify the password for

In the Port configuration dialog box, when

deploying additional nodes to a Virtual
Machine Manager cluster, all fields are
unavailable.
In the Library configuration dialog box, no

options are available for a highly available
installation. The Library must be configured
separately and should point to a highly
available file share. The process will be
covered separately in this guide. Click Next
to continue.

appear and display the selections made
during the installation wizard. Review the
options selected and click Install to continue.

When the installation completes, the wizard

will display the Setup completed
successfully dialog box. Click Close to
complete the installation.
Launch the Virtual Machine Manager console

to verify that the installation occurred
properly. Set the Server Name value to
match the name that was provided for the
Cluster Resource name during setup (for
example, HAVMM: 8100). Verify that the
console launches and connects to the Virtual
Machine Manager instance installed.
In the Virtual Machine Manager Console,

expand Servers and select VMM Server.
Verify that both cluster nodes are listed as
VMM Servers under Role and that both
nodes are listed as Responding under Agent
Status.
4.4
Design Pattern 1 Installation Creating the HA Virtual Machine Manager

Library Share on a Failover Cluster
In a highly available installation of Virtual Machine Manager, the Virtual Machine Manager Library must reside
on a server outside of the Virtual Machine Manager Cluster infrastructure; it is not a supported configuration to
reside upon the Virtual Machine Manager cluster or its nodes.17 In addition, making the Virtual Machine
Manager Library highly available is a recommended practice given that the Virtual Machine Manager servers
themselves are highly available. The Private Cloud Fast Track physical architecture makes no recommendations
on where the Virtual Machine Manager Library resides, other than that it should be as highly available as other
aspects of Design Pattern 1 (HA) installations. While any file server cluster will suffice, the document will detail
the steps required to host the Virtual Machine Manager Library upon the SQL Server Cluster created in earlier
portions of this document.
Perform the following steps on each SQL Server virtual machine.
From an elevated Command Prompt within each
guest virtual machine (Node 1, Node 2, Node 3,
and Node 4), run the following command to
install the File Serve feature on Windows Server
2008 R2:
servermanagercmd i FS-FileServer
Alternatively, the Failover Clustering feature can

commands:
Add-WindowsFeature Name FS-FileServer
Add an additional iSCSI LUN and prepare it as

described in previous steps. This should appear
as available storage in the Failover Cluster
Manager Storage node.
Perform the following steps on the first SQL Server cluster node.
Within Failover Cluster Manager, right-click
Services and applications and click Configure
a Service or Application on the shortcut menu.
17
How to Add a Library Server or Library Share - http://technet.microsoft.com/en-us/library/gg610579.aspx.
The High Availability Wizard will appear. In

the Before You Begin dialog box, click Next to
begin the wizard.
In the Select Service or Application dialog box,

from the available services and applications,
select File Server and click Next to continue.
In the Client Access Point dialog box, specify a

unique name for the clustered file server in the
Name box. Additionally, for static IP
configurations, select the appropriate network
and assign a unique IP address to the service.
In the Select Storage dialog box, from the

available storage, select the Cluster Disk that will
be used for the Virtual Machine Manager
Library, and then click Next to continue.
In the Confirmation dialog box, verify the

options selected and click Next to continue.
The progress of the installation will be shown in

the Configure High Availability dialog box.
When complete, the Summary dialog box will

show a report of the actions taken by the
wizard. Verify success and click Finish to
complete the wizard.
Note that in some cases the number of cluster

name objects will exceed the configurable
amount for the cluster computer account in the
target Active Directory domain. If this is the
case, the ability to create the cluster name
object will prevent the service from starting and
record an 1194 event.
If the preceding situation is the case, there are a

number of ways to remedy this situation,
including increasing the quota for computer
account creation or precreating a computer
account in the target domain. If the computer
account is created, you must change the The
following user or group can join this
computer to a domain value to Authenticated
Users.
Note that the new highly available file server is

available as a new service in Failover Cluster
Manager.
In the file server storage volume, create a folder

called VMMLibrary.
In Failover Cluster Manager, right-click the

newly created file server service and click Add a
shared folder on the shortcut menu.
The Provision a Shared Folder Wizard will

appear. In the Shared Folder Location dialog
box, select the newly created VMMLibrary
folder and click Next to continue.
In the NTFS Permissions dialog box, select the

Yes, change NTFS permissions option. Click
Edit Permissions.
In the Permissions for VMMLibrary dialog

box, add the following accounts with NTFS Full
Control permissions over the folder:
The VMM service account.
The VMM Admins group.
Both VMM computer accounts.
The VMM CNO computer account.
Click OK to save the changes and Next to

continue in the wizard.
In the Share Protocols dialog box, select the

SMB check box and specify the Share Name of
VMMLibary in the provided box. Click Next to
continue.
In the SMB Settings dialog box, accept the

defaults and click Next to continue.
In the SMB Permissions dialog box, select

Users and groups have custom share
permissions, and then click Permissions to edit
the permissions.
In the Permissions for VMMLibrary dialog

box, add the following accounts with Share Full
Control permissions over the folder:
The VMM service account.
The VMM Admins group.
Both VMM computer accounts.
The VMM CNO computer account.
Click OK to save the changes and Next to

continue in the wizard.
In the DFS Namespace Publishing dialog box,

verify that the DFS options are not selected and
that the Publish the SMB share to a DFS
namespace check box is clear. Click Next to
continue.
Note: Virtual Machine Manager does not
support DFS Namespaces (DFSN), formerly
known as Distributed File System (DFS), or DFS
Replication (DFSR).18
18
System Requirements: Virtual Machine Manager Library Server - http://technet.microsoft.com/en-us/library/gg610631.aspx.
In the Review Settings and Create Share

dialog box, review the options you selected.
Click Create to begin the creation of the Virtual
Machine Manager Library share.
In the Confirmation dialog box, verify that the

shared folder was provisioned properly and click
Close.
In the Virtual Machine Manager console, select

the Library node. On the Home tab, click Add
Library Server.
The Add Library Server wizard will appear. In

the Enter Credentials dialog box, select the
Enter a user name and password option. In
the User name and Password boxes, enter
credentials that have administrative rights over
each of the target servers where the new HA
Virtual Machine Manager Library share will
reside. Click Next to continue.
In the Select Library Servers dialog box, specify

the FQDN of the target domain in the Domain
box. In the Computer name box, type the name
of the newly created HA File Server CNO, and
then click Add.
In the Specified servers pane, the cluster object

will appear in the dialog box. Click Next to
continue.
In the Add Library Shares dialog box, select the

check box associated with the VMMLibrary share
created earlier. Verify that the Add Default
Resources check box is selected and then click
Next.
The Jobs dialog box will appear showing the

progress of the Add Library server action.
In the Jobs dialog box, verify that all steps have

completed.
In the Virtual Machine Manager console,

navigate to the Library Servers node and verify
that all of the correct objects are created. When
verified, exit the console.
4.5
Design Pattern 2 Installation - Stand-alone Virtual Machine Manager

Management Server
The following steps needs to be completed in order to install Virtual Machine Manager into the target virtual
machine.
Log on to the Virtual Machine Manager virtual

machine with a user with local admin rights.
on the Virtual Machine Manager Virtual
Machine:

group.

account.
From the Virtual Machine Manager installation

media source, right-click setup.exe and click
Run as administrator on the shortcut menu to
begin setup.
The Virtual Machine Manager installation wizard

will begin. On the splash page, click Install to
begin the Virtual Machine Manager server
installation.

VMM console check box will be selected by
default. Click Next to continue.
In the Product registration information dialog

box, provide the following information in the
provided boxes:

organization.
Organization specify the name of the

licensed organization.
Product key provide a valid product

key for installation of Virtual Machine
Manager. If no key is provided, Virtual
Machine Manager will be installed in
evaluation mode.

understood and agree with the terms of the
license agreement check box is selected. Click
Next to continue.

participate in the CEIP and provide selected
system information to Microsoft. Click Next to
continue.
In the Microsoft Update dialog box, select the

option to either allow or not allow Virtual
Machine Manager to use Microsoft Update to
check for and perform Automatic Updates based
on your organizations policies. Click Next to
continue.
In the Installation location dialog box, specify

a location or accept the default location of
%ProgramFiles%\Microsoft System Center
2012\Virtual Machine Manager for the
installation. Click Next to continue.

checker built in. If for any reason a prerequisite
is not met, the setup user interface will notify
you of the discrepancy.
The following is just an example of that UI.
If the system passes the prerequisite check, no
screen will be displayed and the setup wizard
will proceed to the Database configuration
screen.

provide the following information in the
provided boxes:
Server name specify the name of SQL

Server cluster created in the steps above.
Port specify the TCP port used for the

SQL Server, if not the default.
Verify that the Use the following credentials

check box is cleared. In the Instance name
drop-down menu, select the SCVMM database
instance deployed earlier in the SQL Server
cluster.
In the Select an existing database or create a
new database option, select the New database
option and accept the default database name of
VirtualManagerDB.

distributed key management dialog box, in
the Virtual Machine Manager Service account
section, select the Domain account option.
Enter the following information in the provided
boxes:
User name and domain specify the

account identified in the section above in
the following format:
<DOMAIN>\<USERNAME>.
Password specify the password for the

In the Distributed Key Management section,

select the Store my keys in Active Directory
check box. In the provided box, type the DN
location created earlier within Active Directory:
cn=VMMDKM,DC=domain,
In the Port configuration dialog box, accept
the default values in the provided boxes:
Communication with the VMM

console default: 8100.
Communication to agents on hosts

and library servers default: 5985.
File transfers to agents on hosts and

library servers default: 443.

Deployment Services default: 8102.

Preinstallation Environment
(Windows PE) agents Default: 8101.
Communication with Windows PE

agent for time synchronization
default: 8103.
In the Library configuration dialog box, in the

Specify a share for the Virtual Machine
Manager library section, select the Create a
new library share option. Accept the defaults
or specify the following in the provided boxes:
Share name specify the Virtual

Machine Manager Library share name.
Default value: MSSCVMMLibrary.
Share location specify the physical

location where the Virtual Machine
Manager Library share will reside. Note
that in some installations, additional
LUNs can be provisioned for storing
Virtual Machine Manager Library
content. Default value:
%ProgramData%\Virtual Machine
Manager Library Files.
Share description a short descriptive

name for the library share. Default value:
VMM Library Share.

appear and display the selections made during
the installation wizard. Review the options
selected and click Install to continue.

When the installation completes, the wizard will

display the Setup completed successfully
dialog box. Click Close to complete the
installation.

to verify that the installation occurred properly.
Verify that the console launches and connects to
the Virtual Machine Manager instance installed.
Operations Manager
The Operations Manager installation process includes the following high-level steps.
3
System Center 2012

Operations Manager
Installation
Perform
Prerequisites
Installation of
System Center
2012 Operations
Manager Database
and Server Roles
Post Installation
Configuration of
Operations
Manager
Install the .NET

Framework 3.5.1
Feature
Installation:
Management
Server
Register the
Required Service
Principal Names
for the
Management
Servers
Install SQL Server

Reporting Services
and Analysis
Services
Installation:
Reporting Server
Deploy and
Configure the OM
Agent on VMM
Servers
Install the .NET

Framework 4
Redistributable
Pattern 1
Installation:
Add an Additional
Management
Server
Install the Report

Viewer 2010 SP1
on the VMM
Servers
Install the Report

Viewer 2010 SP1
Install the
Operations
Manager Console
on the VMM
Management
Servers
Configure SQL
Server Prerequites
Download and
Import the
Prerequisite
Management
Packs in OM
Perform Virtual
Machine Manager
and Operations
Manager
Integration
Figure 5: Operations Manager installation process
5.1
Overview
This section provides a high-level walkthrough about how to set up and run the task sequence and scripts for
deploying Operations Manager into the Private Cloud Fast Track fabric management architecture. The following
assumptions are made:
A base virtual machine running Windows Server 2008 R2 (x64) has been provisioned for Operations
Manager:
o
Both .NET Framework 3.5 SP1 and .NET Framework 4 are required.
A SQL Server 2008 R2 cluster with dedicated instances has been established in previous steps:
o
The default SQL Server collation settings are required - SQL_Latin1_General_CP1_CI_AS.
SQL Server Full Text Search is required.
The SQL Server cluster instances supporting the Operations Manager databases have two drives each
already configured:
Data
Logs
The installation will follow a remote SQL Server configuration with multiple SQL Server instances:
o
SQL Server Reporting Services and SQL Server Analysis Services and associated databases will
run on one instance locally on the server.
The Operations Manager databases on will run on a separate SQL Server instance on the
cluster.
5.2
Prerequisites
5.2.1 Accounts
Verify that the following domain accounts have been created.19
19
User name
Purpose
Permissions
<DOMAIN>\FT-SCOMSVC
System Center configuration

service and System Center
data access service account
(sdk_user role)
Domain account with local admin

permissions on all Operations
Manager management servers and
local admin rights on all SQL Server
nodes as well as sysadmin rights on
all Operations Manager SQL Server
instances.
<DOMAIN>\FT-SCOMAction
Operations Manager action

account

permissions on all target systems that
will be managed using the action
account.
<DOMAIN>\FT-SCOM-DR
Operations Manager data

reader account

nodes.
<DOMAIN>\FT-SCOMDW
Operations Manager, Data

Warehouse write account

nodes.
Specific rights for Operations Manager are outlined in http://technet.microsoft.com/en-us/library/d81818d2-534e-475c-98e165496357d5a5#BKMK_BeforeYouBegin.
5.2.2 Groups
Security group name
Group scope
Members
<DOMAIN>\FT-SCOMADMINS
Global
<DOMAIN>\FT-SCOM-Action
<DOMAIN>\FT-SCOM-SVC
<DOMAIN>\FT-SCOM-DR
<DOMAIN>\FT-SCOM-DW
Operations Manager Administrators
privileged admin account
Operations Manager computer account
<DOMAIN>\FT-VMM-SVC
<DOMAIN>\FT-OMOperators
Global
Operations Manager Operators privileged

admin accounts
<DOMAIN>\FT-OMAdvOperators
Global
Operations Manager Advanced Operators

privileged admin accounts

The Operations Manager installation requires the .NET Framework 3.5.1 Features be enabled to support
installation. Follow the steps below to enable the .NET Framework 3.5.1 Features.
Perform the following steps on all Operations Manager virtual machines.
box only. Leave WCF Activation check box
clear.



3.5.1 Features installed correctly. Click Close to
complete the installation of the .NET Framework
3.5.1 Features.
5.2.4 Install the SQL Server Reporting Services and Analysis Services (Split
Configuration)
The Operations Manager installation requires SQL Server Reporting Services and SQL Server Analysis Services to
be installed to support the Operations Manager reporting features and integration with Virtual Machine
Manager. Perform the provided steps to install SQL Server Reporting Services and SQL Server Analysis Services
to support the Operations Manager reporting features.
Perform the following steps on the Operations Manager Reporting Server virtual machine only.
Log on to the Operations Manager virtual
machine with a user with local admin rights.
on the Operations Manager reporting server
virtual machine:
Operations Manager Admins group.
Operations configuration service and

data access service account.
SQL Server Admins group.


continue.

the product key option and enter the
associated product key in the provided box.

Microsoft based on your organizations policies.


continue.

Next to continue.

Analysis Services, Reporting Services,
Management Tools Basic, and Management
Tools Complete check boxes. When all
selections are made, click Next to continue.

continue.

select the Named instance option and specify
SCOMASRS in the provided box. Verify the
Instance ID is listed as SCOMASRS in the
associated box. Keep the default Instance root
directory values, and then click Next to
continue.
Note: A post-installation configuration process
will occur to configure the reporting server
database within the Operations Manager SQL
Server instance.

verify that you have sufficient disk space. Click
Next to continue.

the Service Accounts tab.
Specify the NETWORK SERVICE

account for the SQL Server Reporting
Services service.
Specify the Fast Track SQL Server

Service account for the SQL Server
Analysis Services service.
In the Analysis Services Configuration dialog

Specify which users have administrative
permissions for Analysis Services section, click
following groups:

SQL Server Admins group.
BUILTIN\Administrators.SQL Server
Admins group.

In the Reporting Services Configuration
dialog box, select the Install, but do not
configure the report server option. Note that
other options should not be available because
the database engine was not selected as a
feature for installation. Click Next to continue.

organizations policies. Click Next to continue.

issue and rerun the validation check. Click Next
to continue.

When complete, the Complete dialog box will

Verify the installation in SSMS prior to moving

to the next step of installation.
Verify that SQL Server Reporting Services

installed properly by opening the console. From
the Start Menu, navigate to the Microsoft SQL
Server 2008 R2 folder, and then click
Reporting Services Configuration Manager.
The Reporting Services Configuration

Connection dialog box will appear. In the
Server Name box, specify the name of the
Operations Manager server. In the Report
Server Instance box, use the default
SCOMASRS drop-down menu value. Click
Connect.

Manager tool will appear.

Manager tool, click the Database option from
the sidebar. Within the Current Report Server
Database section, click Change Database.
The Reporting Services Database

Configuration Wizard will appear. In the
Action section, choose Create a new report
server database. Click Next to continue.
In the Database Server section, specify the

following values:
Server Name specify the name of the

SQL Server CNO and the database
instance created for the Operations
Manager installation.
Authentication Type specify Current

User Integrated Security from the
drop-down menu.
Click Test Connection to verify the credentials

and database connectivity. Once verified, click
Next to continue.
In the Database section, specify the following
values:
Database Name accept the default

value of ReportServer.
Language specify the desired

language option from the drop-down
menu.
Report Server Mode select the

Native Mode option.
In the Credentials section, specify the

Authentication Type as Service Credentials
from the drop-down menu. Click Next to
continue.
In the Summary section, review the selections

made, and then click Next to create the SQL
Server Reporting Services database.
The Progress and Finish section will display the

progress of the database creation. Review the
report to verify successful creation and click
Finish.

Manager tool, the Database option will now
display the database and report server database
credentials specified in the wizard.

Manager tool, click the Web Service URL
option on the toolbar. Specify the following
values:
In the Report Server Web Service

Virtual Directory section, set the
Virtual Directory value to
ReportServer_SCOMASRS in the
provided box.
In the Report Server Web Service Site

Identification section, set the following
values:
o
IP Address set the All

Assigned drop-down menu
value.
TCP Port specify the desired

TCP Port (default 80).
SSL Certificate select the

available certificate or choose
the default of (Not Selected).
Click Apply to save the settings and create the

Web Service URL.
Manager tool, click the Report Manager URL
value:
In the Report Manager Site

Identification section, set the Virtual
Directory value to
Reports_SCOMASRS in the provided
box.

Report Manager URL.
Connect to the Report Manager URL within a

web browser to verify the SQL Server Reporting
Services portal is operating properly.
Connect to the Web Service URL within a web

browser to verify the SQL Server Reporting
Services web service is operating properly.

Additionally, the Operations Manager installation also requires the .NET Framework 4 package be installed prior
to installation. Follow the provided steps to install the .NET Framework 4 package.
Perform the following steps on all Operations Manager virtual machines.

dotNetFx40_Full_x86_x64.exe and click Run as
administrator on the shortcut menu to begin
setup.

the license terms check box, and then click
Install to begin the installation.

setup wizard.

installation.
5.2.6 Install Microsoft Report Viewer 2010 SP1

The Operations Manager installation also requires that the Microsoft Report Viewer 2010 SP1 package is
installed prior to installation.20 Follow the provided steps to install the Microsoft Report Viewer 2010 SP1.
20
Microsoft Report Viewer 2010 SP1 Redistributable Package - http://www.microsoft.com/downloads/details.aspx?FamilyID=3EB83C28-A79E-45EE96D0-41BC42C70D5D&displaylang=r&displaylang=en.
Perform the following steps on the Operations Manager management server virtual machine. For Design
Pattern 1 deployments with two Operations Manager management server virtual machines, perform
these steps on both virtual machines.
ReportViewer.exe and click Run as
setup.
In the Microsoft ReportViewer 2010 SP1

Redistributable Setup dialog box, click Next to
Select the I have read and accept the license

terms check box, and then click Install.

setup wizard.
Click Finish to exit the installation.
5.2.7 Configuration of Operations Manager SQL Server Prerequisites

The following prerequisite steps must be completed prior the installation of Operations Manager roles. 21
Perform the following steps on the Operations Manager management server virtual machine. For
Design Pattern 1 deployments with two Operations Manager management server virtual machines,
perform these steps on both virtual machines.
Log on to the Operations Manager virtual
machine as a user with local admin rights.
on the Operations Manager virtual machine:

Perform the following step on an Active Directory Domain Controller in the target environment.
In the domain where Operations Manager will
be installed, verify that the Operations Manager
computer account and the groups outlined in
the table above are members of the OM Admins
group created earlier.
Perform the following steps on the primary SQL Server cluster node.
21
Deploying System Center 2012 - Operations Manager - http://technet.microsoft.com/en-us/library/d81818d2-534e-475c-98e165496357d5a5#BKMK_BeforeYouBegin.
Using Administrative credentials, log on to the

first SQL Server and open SSMS. Connect to the
Operations Manager SQL Server instance using
the values specified earlier. Create a new login
by navigating to the Logins node under
Security within SQL Management Studio. Rightclick the Logins node, and then click New
Login on the shortcut menu.
In the Login New dialog box, specify the
Operations Manager Admins group created
earlier as the new Login name. Click OK to
create the new login.
While still in SQL Management Studio and

connected to the Operations Manger SQL Server
instance, navigate to the Server Roles node
under Security within SSMS. Locate the
sysadmin role and double-click it to modify the
roles properties.
In the Server Role Properties - sysadmin
dialog box, add the Operations Manager
Admins login that was created above, and then
click OK to add this login to the sysadmin role
of the instance.
5.3
Installation Management Server

The following steps must be completed in order to install and configure the Operations Manager database and
server roles.
Perform the following steps on the Operations Manager management server virtual machine. For
Design Pattern 1 deployments with two Operations Manager management server virtual machines,
perform these steps only the first virtual machine.
From the Operations Manager installation media
source, right-click setup.exe and click Run as
setup.
The Operations Manager installation wizard will

begin. On the splash page, click Install to begin
the Operations Manager management server
installation.

verify that the Management server and
Operations console check boxes are selected.
In the Select installation location dialog box,

specify a location or accept the default location
of %ProgramFiles%\System Center
2012\Operations Manager for the installation.
Setup will verify that all system prerequisites are

met in the Proceed with Setup dialog box. If
any prerequisites are not met, they will be
displayed in this dialog box. When verified, click
Next to continue.
In the Specify an installation option dialog

box, two installation options are provided:
Create the first management server

in a new management group.
Add a Management server to an

existing management group.
Select Create the first Management server in

a new management group and supply a
unique name in the Management group name
box. Note that this name must be unique across
System Center products and components.
understood and agree with the terms of the
license agreement installation option check
box is selected. Click Next to continue.
In the Configure the operational database

dialog box, specify the following information in
the provided boxes:
Server name and instance name

specify the name of the SQL Server
cluster network name (CNO) and the
database instance created for the
Operations Manager installation.
SQL Server port specify the TCP port

used for SQL Server connectivity (1433
by default, may be different based on
instance).
Database name specify the name of

the Operations Manager database. In
most cases the default value of
OperationsManager should be used.
Database size (MB) specify the initial

database size. 22 The following values
can be used as a general guideline:
Up to 500 agents: 12 GB.
Data file folder specify the drive letter

associated in the SQL Server cluster for
the database data files for the
Operations Manager database. This
should be cross-checked with the
worksheet identified earlier.
Log file folder specify the drive letter

the log files for the Operations Manager
database. This should be cross-checked
with the worksheet identified earlier.
22
Supported Configurations for System Center 2012 are located here: http://technet.microsoft.com/en-us/library/hh205990.aspx#4 which contains
the Operations Manager Sizing Helper http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23016. This helper is being updated
for System Center 2012 Operations Manager, but provided general guidance for database sizing.
In the Configure the data warehouse

database dialog box, specify the following
information in the provided boxes:

specify the name of the SQL Server
cluster network name (CNO) and the
database instance created for the
Operations Manager installation.

by default; may be different based on
instance).

the Operations Manager Data
Warehouse database. In most cases the
default value of OperationsManager
should be used.
Database size (MB) specify the initial

database size. 23 The following values
can be used as a general guideline:

associated in the SQL Service cluster for
the database log files for the Operations
Manager Data Warehouse database.
This should be cross-checked with the

the database log files for the Operations
23
Supported Configurations for System Center 2012 are located here: http://technet.microsoft.com/en-us/library/hh205990.aspx#4 which contains
the Operations Manager Sizing Helper http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23016. This helper is being updated
for System Center 2012 Operations Manager, but provided general guidance for database sizing.
In the Configure Operations Manager

accounts dialog box, for each of the following
accounts, specify whether the account is a Local
System or Domain Account using the available
options:
Management server action account.
System Center Configuration service

and System Center Data Access
service.
Data Reader account.
Data Writer account.
If the use of a Domain Account is specified,

enter the user account information as
<DOMAIN>\<USERNAME> and enter the
appropriate password.
Once completed, click Next to continue.
The Help Improve Operations Manager 2012
dialog box provides options for participating in
various product feedback mechanisms. These
include:
Customer Experience Improvement

Program.
Error Reporting.
Select the appropriate option based on your

continue.

option that best matches your organizations
policies and click Next to continue.
The Installation Summary dialog box will



display the Setup is complete dialog box. Verify
that the start the Operations console when
the wizard closes check box is selected, and
then click Close to complete the installation.
The Operations Manager console will open.

From this console, the installation can be
validated by reviewing the configuration and
proper operation of the console.
5.4
Installation Reporting Server

The following steps must be completed in order to install and configure the Operations Manager reporting
server role.
Perform the following steps on the Operations Manager reporting server virtual machine.
setup.

begin. At the splash page, click Install to begin
installation.

verify that the Reporting server check box is

The setup will verify that all system prerequisites

are met in the Proceed with Setup dialog box.
If any prerequisites are not met, they will be
displayed in this dialog box. Once verified, click
Next to continue.
In the Specify a Management server dialog

box, type the name of the previously installed
management server in the Management server
name box. Click Next to continue.
In the SQL Server instance for reporting

services dialog box, select the SQL Server
instance hosting the local SQL Server Reporting
Services and SQL Server Analysis Services from
the drop-down menu created during earlier
steps. Click Next to continue.

accounts dialog box. For each of the following
options:
Data Reader account.
If the use of a Domain Account is specified,

enter the user account information as
Once completed, click Next to continue.
The Help improve System Center 2012 Operations Manager dialog box provides
options for participating in various product
feedback mechanisms. This includes:
Operational Data Reporting (ODR).


policies. Click Next to continue.



that the Launch Microsoft Update when the
wizard closes check box is selected, then and
click Close to complete the installation.
Open the Operations Manager console from the

first management server. From this console, the
installation can be validated by noting that the
Reporting node is now visible in the console.
5.5
Design Pattern 1 Installation Add an Additional Management Server

The following steps must be completed in order to install and configure the second Operations Manager server
role detailed in Design Pattern 1.
For Design Pattern 1 deployments, perform the following steps on the second Operations Manager
management server virtual machine.
setup.

installation.

verify that the Management server and
Operations console check boxes are selected.


are met in the Proceed with Setup dialog box.
Next to continue.
In the Specify an installation option dialog

box, two installation options are provided:
Create the first Management server

in a new management group.
Add a Management server to an

existing management group.
Select Add a Management server to an

existing management group, and then click
Next to continue.
In the Configure the operational database

the provided boxes:

specify the name of the SQL Server CNO
and the database instance created for
the Operations Manager installation.

by default, may be different based on
instance)
Database name the name of the

Operations Manager database will be
discovered and available in the dropdown menu. In most cases, the default
value of OperationsManager will be
used.

accounts dialog box, for each of the following
options:
Management server action account.
System Center Configuration service

and System Center Data Access
service.
Use the same values provided in the initial

management server installation. If the use of a
Domain Account is specified, enter the user
account information as
When completed, click Next to continue.
The Help Improve System Center 2012 Operations Manager dialog box provides
feedback mechanisms. These include:

Program.
Error Reporting.

continue.

policies, and then click Next to continue.

selected, and then click Install to continue.


display the Setup is complete dialog box. Click
Close to complete the installation.
Open the Operations Manager console. From

this console, the installation can be validated by
navigating to the Administration console and
viewing the listed management server by
selecting the Device Management node and
then selecting the Management Servers node.
5.6
Post Installation Tasks

Once the installation is complete, the following tasks must be performed to complete Operations Manager and
Virtual Machine Manager integration.
5.6.1 Register the Required Service Principal Names for the Operations
Manager Management Servers
Perform the following steps on a Domain Controller in the domain where Operations Manager is
installed.
Log on to a Domain Controller with a user that
has Domain Admin privileges and run
adsiedit.msc.
Right-click the ADSI Edit node and click

Connect to on the shortcut menu.
In the Connections Settings dialog box in the

Connection Point section, select the Select a
well-known Naming Context option. Select
Default naming context from the drop-down
menu. Click OK.
Navigate to the container where the Operations

Manager management server computer objects
reside. Right-click the object and click
Properties on the shortcut menu.
In the Properties dialog box, click the Attribute

Editor tab, locate the servicePrincipalName
attribute, and then click Edit.
In the Multi-valued String Editor dialog box,

verify the following SPNs are registered:
MSOMSdkSvc/<servername>
MSOMSdkSvc/<server FQDN>
Click OK to save the changes. Repeat these steps
for each management server.
5.6.2 Deploy and Configure the Operations Manager Agent on the Virtual
Machine Manager Management Server
Perform the following steps on the Operations Manager virtual machine.
In the Operations Manager console, navigate

to the Administration workspace. Under
Actions, select Configure computers and
devices to manage.
The Computer and Device Management

Wizard will appear. In the Discovery Type
dialog box, select Windows computers from
the available options, and then click Next to
continue.
In the Auto or Advanced? dialog box, select

Automatic computer discovery, and then click
Next to continue.
In the Administrator Account dialog box,

select Other user account and provide the
credentials required to access Active Directory
and perform discovery in your environment.
Verify that the This is a local computer
account, not a domain account check box is
clear. Click Next to continue.
In the Select Objects to Manage dialog box,

review the Discovery Results and select the
VMM server. From the Management Mode
drop-down menu, select Agent and click Next
to continue.
In the Summary dialog box, accept the default

Agent installation directory as
%ProgramFiles%\System Center Operations
Manager. In the Agent Action Account section,
select the Local System option. Click Finish to
perform the agent installation.
In the Agent Management Task Status dialog

box, verify that the agent installation completes
successfully. When successful, click Close to
complete the operation.
The next step is to enable the Operations

Manager agent deployed to the Virtual Machine
Manager management server to be a proxy
agent.
to the Administration workspace, expand the
Device Management node, and then select the
Agent Managed view.
In the Agent Managed pane, select the agent

associated with the VMM Management Server,
and then click Properties in the task pane.
In the Agent Properties dialog box, click the

Security tab. Verify that the Allow this agent
to act as a proxy and discover managed
objects on other computers check box is
selected, and then click OK to save the changes.
5.6.3 Install Microsoft Report Viewer 2010 SP1 on the Virtual Machine Manager
Management Server
The Operations Manager installation also requires the Microsoft Report Viewer 2010 SP1 package be installed
prior to installation.24 Follow the provided steps to install the Microsoft Report Viewer 2010 SP1 package.
Perform the following steps on each Virtual Machine Manager virtual machine.
setup.
24



setup wizard.
When complete, click Finish to exit the

installation.
5.6.4 Install Operations Manager Console on the Virtual Machine Manager

Management Server
Perform the following steps on each Virtual Machine Manager virtual machine.

setup.

the Operations Manager console installation.

verify that the Operations console check box is

The Help Improve System Center 2012

Operations Manager dialog box provides
feedback mechanisms. These include:

Program.
Error Reporting.

continue.


that the Start the Management console when
the wizard closes check box is selected. Click
Close to complete the installation.

5.6.5 Download and Import the Required Prerequisite Management Packs in

Operations Manager
to the Administration pane and select the
Management Packs node. In the Actions pane,
click Import Management Packs.
In the Select Management Packs dialog box,

click Add, and then select Add from catalog
from the drop-down menu.
In the Select Management Packs from

Catalog dialog box, find and add the following
management packs:
Windows Server Internet Information
Services Library.

Services 2000.

Services 2003.
Windows Server 2008 Internet

Information Services 7.
SQL Server 2008 (Discovery).
SQL Server 2008 (Monitoring).
SQL Server 2008 Mirroring (Discovery).
SQL Server 2008 Mirroring (Monitoring).
SQL Server Core Library.
Windows Server 2008 R2 Best Practice

Analyzer Monitoring.
Microsoft Windows Server 2000

Operating System.
Windows Server 2003 Operating

System.
Windows Server 2008 Operating System

(Discovery).

(Monitoring).
Windows Server Operating System

Library.
Windows Server Operating System

Reports.
Windows Server Cluster Shared Volume

Monitoring.
When added, click OK to continue.
In the Select Management Packs dialog box,

click Install to import the selected management
packs.
The management packs will download and

import into Operations Manager. When
complete, verify that the imports were
successful, and then click Close to exit the
Import Management Packs wizard.
In the Operations Manager console, go to the

Administration workspace and verify the
previously selected management packs are now
installed.
5.6.6 Perform Virtual Machine Manager and Operations Manager Integration

navigate to Settings pane and select System
Center Settings. Right-click Operations
Manager Server, and then click Properties on
the shortcut menu.
The Add Operations Manager dialog box will

appear. In the Introduction dialog box, verify
the prerequisites have been met and click Next
to continue.
In the Connection to Operations Manager

dialog box, type the FQDN of the Operations
Manager server in the Server name box. Select
Use the VMM server service account. Select
the Enable Performance and Resource
Optimization (PRO) and Enable maintenance
mode integration with Operations Manager
check boxes.
In the Connection to VMM dialog box, specify

the VMM service account credentials in the User
name and Password boxes. Click Next to
continue.
In the Summary dialog box, verify the options

selected. Click Finish to begin the Operations
Manager integration process.
The Jobs pane will appear. Before moving

forward, wait for the job to complete
successfully.

navigate back to Settings, and then select
System Center Settings and double-click
Operations Manager Server. The Operations
Manager Settings dialog box will appear.
In the Details pane, click Test PRO.
As part of the test, PRO will generate a

diagnostics alert.
After a few minutes, verify that the PRO test is

successful. Navigate to the Jobs pane and verify
the PRO jobs completed successfully.
In the Management Packs dialog box, verify all

Virtual Machine Manager Management Packs
were successfully installed.
In the Configure connection to SQL Server

Analysis Services (SSAS) dialog box, provide
the following information.
Select the Enable SSAS check box. Provide the
following information in the boxes provided:
SSAS server Specify the Operations
Manager database server instance.
SSAS instance Specify the SSAS

instance name created earlier.
In the Provide credentials with administrative

rights on the SSAS instance, select Enter a
user name and password and provide the
supplied credentials for the Operations Manager
Data Reader account. Click OK to save these
settings.
On the Operations Manager console, go to
Monitoring workspace, navigate to the PRO
node, and then click PRO Object State. Verify
the VMM server is listed with a health state
other than Not Monitored.
Service Manager
The Service Manager installation process includes the following high-level steps.
4
System Center 2012

Service Manager
Installation
Installation of
System Center
2012 Service
Manager Roles
Perform
Prerequisites
Install the .NET

Framework 3.5.1
Feature on all
servers
Install SQL Server

Reporting Services
on the Data
Warehouse Server
Installation:
Management
Server
Install the Report

Viewer 2008 SP1
on the
Management and
Data Warehouse
servers
Install SharePoint
Foundation 2010
on the Self-Service
Portal Server
Pattern 1
Installation:
Add an Additional
Management
Server
Install the SQL

Server Native
Client on the
Management and
Data Warehouse
servers
Install .NET
Framework 4 2010
on the Self-Service
Portal Server
Installation:
Data Warehouse
Server
Install Analysis
Management
Objects on the
Management and
Data Warehouse
servers
Request an Install
an SSL Certificate
on the Self-Service
Portal Server
Installation:
Self-Service Portal
Server
Figure 6: Service Manager installation process
6.1
Overview
This section provides a high-level walkthrough about how to set up and complete the task sequence and scripts
for deploying Service Manager into the Private Cloud Fast Track fabric management architecture. The following
assumptions are made:
Management Server
A base virtual machine running Windows Server 2008 R2 (x64) has been provisioned for the Service
Manager management server role.
A multi-node, SQL Server 2008 R2 cluster with dedicated Service Manager instances that has been
established in previous steps for Service Manager.
o
Service Manager database instance for Service Manager management database.
The .NET Framework 3.5.1 Features are installed.
The Microsoft Report Viewer 2008 Redistributable (KB971119) is installed http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3203.
The Microsoft SQL Server 2008 R2 Native Client is installedhttp://go.microsoft.com/fwlink/?LinkID=188401&clcid=0x409.
The Microsoft SQL Server R2 Analysis Management Objects is installed http://go.microsoft.com/fwlink/?LinkID=188448&clcid=0x409.
Data Warehouse Server

A multi-node, SQL Server 2008 R2 cluster with dedicated instance that has been established in previous
steps for Service Manager.
o
SCSMAS instance for SQL Server 2008 R2 Analysis Services and SQL Server Reporting Services
databases.
SCSMDW instance for Service Manager Data Warehouse databases.
The Microsoft SQL Server 2008 R2 Native Client is installed http://go.microsoft.com/fwlink/?LinkID=188401&clcid=0x409.
The Microsoft SQL Server R2 Analysis Management Objects are installedhttp://go.microsoft.com/fwlink/?LinkID=188448&clcid=0x409.
The Microsoft SQL Server R2 Reporting Services (split configuration) is installed.
The Microsoft SQL Server R2 Management tools are installed.
Self-Service Portal Server

A four-node, SQL Server 2008 R2 cluster with dedicated instance that has been established in previous
steps for Service Manager.
o
SCSPFarm instance for Self Service Portal SharePoint Farm databases.
SharePoint Foundation 2010 is installed.
The .NET Framework 4 Redistributable is installed.
Additional Management Server for Design Pattern 1 Deployments Only

A four-node, SQL Server 2008 R2 cluster with dedicated Service Manager instances that has been
established in previous steps for Service Manager.
o
SCSMDB instance for Service Manager management database.
6.2
Prerequisites
6.2.1 Accounts
User name
Purpose
<DOMAIN>\ FT-SCSM-SVC
SCSM services account
Permissions
Add the account to the local
Administrators group on the all
SCSM servers.
Must be a local admin on all
SQL Server nodes.
<DOMAIN>\ FT-SCSM-WF
SCSM workflow account
Must have permissions to send

e-mail and must have a
mailbox on the SMTP server
(required for the E-mail
Incident feature).
Must be member of Users local
security group on all SCSM
servers.
Must be made a member of
the Service Manager
Administrators user role in
order for e-mail
SQL Server nodes.
<DOMAIN>\ FT-SCSM-SSRS
SCSM reporting account
<DOMAIN>\ FT-SCSM-OMCI
SCSM Operations
Manager CI connector

SQL Server nodes.
Must be a member of the Users
local security group on all SCSM
servers.
User name
<DOMAIN>\ FT-SCSM-ADCI
Purpose
Permissions
account
Must be an Operations Manager

Operator.
SCSM Active Directory CI

connector account
Must be a member of the

Users local security group on
the Service Manager
management server.
Must have permissions to bind
to the domain controller that
the connector will read data
from.
Needs generic read rights on
the objects that are being
synchronized into the Service
Manager database from Active
Directory.
<DOMAIN>\ FT-SCSM-OMAlert
SCSM Operations
Manager alert connector
account
Must be a member of the

Users local security group on
the Service Manager
management server.
Must be a member of FT-SCSMAdmins
DOMAIN>\ FT-SCSM-VMMCI
Virtual Machine
Manager CI connector
account
Member of the VMM Admin

domain group. The account
must also be in the Service
Manager Advanced Operator
role
DOMAIN>\ FT-SCSM-OCI
Orchestrator CI
connector
Member of SCO Operators

(Users) domain group. The
account must also be in the
Service Manager Advanced
Operator role
<DOMAIN>\ FT-SCSM-OLAP
Service Manager Analysis

Services account

SQL Server nodes.
6.2.2 Groups
Security group name
Group scope
<DOMAIN>\ FT-SCSMADMINS
Global
Members
DOMAIN\ FTSCSM-SVC
Member of
Must be added to the Service
Manager Administrators user role
and added to the Operations
Manager Administrators role in
Operations Manager and a
member of the Administrators
group on each SQL Server.
6.2.3 Add the .NET Framework 3.5.1 Features on all Server Manager Servers
The Service Manager installation requires the .NET Framework 3.5.1 Features to be enabled to support
installation. Follow the provided steps to enable the .NET Framework 3.5.1 Features.
Perform the following steps on all Service Manager virtual machines.
box only. Leave the WCF Activation check box
clear.



3.5.1 Features installed correctly. Click Close to
complete the installation of the .NET Framework
3.5.1 Features.
6.2.4 Install Microsoft Report Viewer 2008 SP1 Redistributable on the

Management and Data Warehouse Servers
The Server Manager management and Data Warehouse server installations also require the Microsoft Report
Viewer 2008 Redistributable be installed prior to installation. The following steps are provided to help install the
Microsoft Report Viewer 2008 Redistributable.
Perform the following steps on the Server Manager management and Data Warehouse servers virtual
machines.

setup.
The setup wizard will appear. Click Next to

continue.

have read and accept the license terms check
box. Click Install to begin the installation.

setup wizard.

installation.
6.2.5 Install SQL Server 2008 R2 Native Client on the on the Management and
Data Warehouse Servers
The Server Manager management and Data Warehouse server installations also require the SQL Server 2008 R2
Native Client be installed prior to installation. Follow the provided steps to install the SQL Server 2008 R2 Native
Client.
machines.
SQLNCLI.MSI and click Install on the shortcut
Note: The SQL Server Native Client installer,
1033\x64\sqlncli.msi, can be downloaded
from
aspx?id=26728.

continue.

accept the terms in the license agreement
check box. Click Next to continue.
In the Registration Information dialog box,

enter values for your organization in the Name
and Company boxes. Click Next to continue.
In the Feature Selection dialog box, verify that

the Client Components feature is selected for
In the Ready to Install the Program dialog

box, click Install to begin the installation.

setup wizard.

installation.
6.2.6 Install SQL Server 2008 R2 Analysis Management Objects on the

Management and Data Warehouse Servers
The Server Manager management and Data Warehouse server installations also require the SQL Server 2008 R2
Analysis Management Object be installed prior to installation. Follow the provided steps to install the SQL
Server 2008 R2 Analysis Management Object.
machines.
SQLSERVER2008_ASAMO10.MSI and click Run
as administrator on the shortcut menu to
begin setup.
Note: The Analysis Management Objects
installer,
1033\x64\SQLSERVER2008_ASAMO10.msi,
can be downloaded from
aspx?id=26728.
continue.

accept the terms in the license agreement
check box. Click Next to continue.
In the Registration Information dialog box,

enter values for your organization in the Name
and Company boxes. Click Next to continue.
In the Ready to Install the Program dialog

box, click Install to begin the installation.

setup wizard.

installation.
6.2.7 Install SQL Server Reporting Services (Split Configuration) on the Data
Warehouse Server
The Service Manager Data Warehouse installation requires SQL Server Reporting Services be installed to support
the Service Manager reporting features. Follow the provided steps to install SQL Server Reporting Services.
Perform the following steps on the Service Manager Data Warehouse virtual machine.


continue.

the product key option and enter the
associated product key in the provided box.

continue.

install and allow the support files to install.

continue.

Next to continue.

Reporting Services, Management Tools
Basic, and Management Tools Complete
check boxes. When all selections are made, click
Next to continue.

continue.

select the Default instance option. Keep the
default Instance ID and Instance root
directory values, and then click Next to
continue.
Note: A post-installation configuration process
will occur to configure the database within the
SCSMDW SQL Server instance.

verify that you have sufficient disk space and

the Service Accounts tab. Specify the
NETWORK SERVICE account for the SQL
Server Reporting Services service. Click Next
to continue.

dialog box, select Install, but do not configure
the report server. Note that other options
should not be available since the database
engine was not selected as a feature for


issue and rerun the validation check. Click Next
to continue.

When the installation is complete, the Complete

dialog box will appear. Click Close to complete
the installation of this SQL Server database
instance.
Verify that the Service Manager management

server installed properly by opening the console.
Microsoft SQL Server 2008 R2 folder and click
Reporting Services Configuration Manager.

Connection dialog box will appear. In the
Server Name box, specify the name of the
Service Manager server. In the Report Server
Instance box, use the default MSSQLSERVER
drop-down menu value. Click Connect.

Manager tool will appear.

Manager tool, click the Database option from
the toolbar. Within the Current Report Server
Database section, click Change Database.
The Reporting Services Configuration Wizard

will appear. In the Action section, choose the
Create a new report server database option.
In the Database Server section, specify the

following values:
Server Name specify the name of the

SQL Server cluster network name and
the database instance created for the
Service Manager installation.
Authentication Type specify Current

User Integrated Security from the
drop-down menu.
Click Test Connection to verify the credentials

and database connectivity. When verified, click
Next to continue.
In the Database section, specify the following
values:
Database Name accept the default

value of ReportServer.
Language specify the desired

language option from the drop-down
menu.
Report Server Mode select the

Native Mode option.
In the Credentials section, specify the

Authentication Type as Service Credentials
from the drop-down menu and click Next to
continue.
In the Summary section, review the selections

made. Click Next to create the SQL Server
Reporting Services database.
The Progress and Finish section will display the

progress of the database creation. Review the
report to verify successful creation, and then
click Finish.

Manager tool, the Database option will now
display the database and Report Server
Database credentials specified in the wizard.

Manager tool, click the Web Service URL
option from the toolbar. Specify the following
values:
In the Report Server Web Service

Virtual Directory section, set the
Virtual Directory value to
ReportServer in the provided box.
In the Report Server Web Service Site

Identification section, set the following
values:
o
IP Address set the All

Assigned drop-down menu
value.
TCP Port specify the desired

TCP Port (default 80).
SSL Certificate select the

available certificate or choose
the default of (Not Selected).

Web Service URL.
Manager tool, click the Report Manager URL
value:
In the Report Manager Site

Identification section, set the Virtual
Directory value to Reports in the
provided box.

Report Manager URL.
Connect to the Report Manager URL within a

web browser to verify the SQL Server Reporting
Services portal is operating properly.
Connect to the Web Service URL within a web

browser to verify the SQL Server Reporting
Services web service is operating properly.
If you wish to leave the Windows Firewall

enabled, you must first enable the following
rules in Windows Firewall:
World Wide Web Services (HTTP TrafficIn).
World Wide Web Services (HTTPS

Traffic-In).
Right-click each rule and click Enable Rule on

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

The following steps must to be completed in order to install SharePoint Foundation 2010 on the Service
Manager self-service portal server only.
Perform the following steps on the Service Manager self-service portal virtual machine.
Log on to Service Manager self-service portal
server (not a Service Manager management
server or the Data Warehouse server). Locate the
SharePoint Foundation 2010 installation file.
Right-click SharePointFoundation.exe and
click Run as administrator on the shortcut
menu to begin setup.25
25
Microsoft SharePoint Foundation 2010 - http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5970.
The SharePoint Foundation 2010 setup dialog

box will appear. In the Install section, click
Install software prerequisites.
The Microsoft SharePoint 2010 Products

Preparation Tool will open. Click Next to
continue.
In the License Terms for software products

dialog box, verify that the I accept the terms of
the License Agreement installation option
After the prerequisites install, the Installation

Complete dialog box will appear. Click Finish to
complete the installation, and then restart the
system.
After the system restart, log back on with an

account with administrative privileges. Relaunch the SharePoint Foundation 2010
installation. In the SharePoint Foundation
2010 setup dialog box, navigate to the Install
section, and click Install SharePoint
Foundation.
In the Read the Microsoft Software License

Terms dialog box, verify that the I accept the
terms of this Agreement installation option
check box is selected, and then click Continue.
In the Choose the installation you want dialog

box, click Server Farm.
In the Server Type dialog box, select the

Complete option, and then click Install Now.
After installation, the Run Configuration

Wizard dialog box will appear. Verify that the
Run the SharePoint Products Configuration
Wizard now check box is selected, and then
click Close.
The SharePoint Products Configuration

Wizard will appear. Click Next to continue with
the wizard.
A dialog box will appear that states that some

services require restart as part of the installation.
Click Yes to perform the services restart.
The Connect to a server farm dialog box will

appear. Select the Create a new server farm
option is selected, and then click Next to
continue.
In the Specify Configuration Database

Settings dialog box, specify the following
Database server specify the name of

the SQL Server CNO and the database
instance created for the Service Manager
installation.

the SharePoint database. In most cases
the default value of SharePoint_Config
should be used.
In the Specify Database Access Account

section, specify the Username
(<DOMAIN>\<USERNAME>) and associated
password for the Service Manager service
account. When complete, click Next to
continue.
In the Specify Farm Security Settings dialog
box, enter a unique passphrase in the
Passphrase box. Retype the passphrase in the
Confirm passphrase box. Click Next to
continue.
In the Configure SharePoint Central

Administration Web Application dialog box,
specify a TCP port by selecting the Specify port
number check box and providing a port
number in the supplied box.
In the Configure Security Settings section,
select the NTLM option.
When completed, click Next to continue.
The Completing the SharePoint Products

Configuration Wizard dialog box will appear
and display the selections made during the
installation wizard. Review the options selected,

performing the SharePoint configuration.
When successful, the Configuration Successful

dialog box will appear. Click Finish to complete
the configuration of SharePoint Foundation
2010.
When prompted in the Help Make SharePoint

Better page, select the appropriate option
based on your organizations policies, and then
click OK to save this setting.
In the Central Administration - Configure
your SharePoint farm page, click Start the
Wizard to begin the SharePoint configuration.
In the Service Account section, select Use

existing managed account and select the
Service Manager Service Account from the dropdown menu.
In the Services section, select the Business
Data Connectivity Services and Usage and
Health data collection check boxes.
In the Web Site configuration page, click Skip to

continue without configuring these settings.
The SharePoint farm configuration is now

complete. Click Finish to exit.
The SharePoint Central Administration portal

will open. Verify that SharePoint is operating
properly by launching the Central
Administration portal prior to proceeding to the
Service Manager self-service portal installation.
Note: The latest service pack should be applied

to SharePoint Foundation server after this
installation.26
Locate the Service Pack 1 for SharePoint
Foundation 2010 installation file, right-click the
installation file and click Run as administrator
on the shortcut menu to begin the Service Pack
setup.
The Microsoft SharePoint Foundation 2010
Service Pack 1 (SP1) wizard will appear. Verify
that the Click here to accept the Microsoft
Software License Terms check box is selected,
and then click Continue.
The installation will continue without interaction

until it completes. When prompted, click OK to
complete the installation. You must restart the
system after the service pack installation.
6.2.9 Install .NET Framework 4 on the Self-Service Portal Server

Additionally, the Service Manager self-service portal installation also requires the .NET Framework 4 package to
be installed prior to installation. Follow the provided steps to install the .NET Framework 4 on the self-service
portal.
26
Microsoft SharePoint Foundation 2010 SP1 - http://www.microsoft.com/download/en/details.aspx?id=26640.

setup.

the license terms check box. Click Install to

setup wizard.

installation.
6.2.10 Request and Install an SSL Certificate on the Self-Service Portal Server
The Service Manager self-service portal installation requires a secure socket layer (SSL) certificate in order to
enable SSL on the portal website.27 If the self-service portal is to be installed without SSL this section can be
skipped. There are several ways to request an SSL Certificate. One method, through the IIS Manager console, is
outlined below.
27
SSL Certificates for the Self-Service Portal - http://technet.microsoft.com/en-us/library/hh667343.aspx.
Log on to the Service Manager virtual machine
with a user with local admin rights. From the Start
Menu click Administrative Tools and then click
Internet Information Services (IIS) Manager.
In the Internet Information Services (IIS)

Manager console, select the server node and in
the IIS section, double-click Server Certificates.
The Server Certificates pane will expand. Under

actions, click Create Certificate Request.
The Request Certificate dialog box will appear.

In the Distinguished Name Properties dialog
box, complete the information as prompted. Note
the Common name box must equal the exact
name that the server will be accessed in the web
browser. Click Next to continue.
In the Cryptographic Service Provider

Properties dialog box, select a Cryptographic
Service Provider (CSP) that is appropriate for your
issuing certification authority (CA). In most cases,
selecting the default CSP and default bit length is
satisfactory. Click Next to continue.
In the File Name dialog box, provide a complete

path to save the certificate request file. Click
Finish to generate the certificate request.
When completed, submit the request to your
issuing CA or certificate provider of choice and
follow the next steps on installing the newly
issued certificate.
After receiving the issued certificate, open the

Internet Information Services (IIS) Manager
console and click Server Certificates once again.
From the Actions pane, click Complete
Certificate Request.
The Complete Certificate Request wizard will

appear. In the Specify Certificate Authority
Response dialog box, specify the file name and
location of the issued certificate, and supply a
friendly name for the certificate in the provided
boxes. Click OK to complete the operation.
In the Server Certificates section of the IIS

Manager, you will now see the newly created and
installed certificate.
6.3
Installation
The following steps must to be completed in order to install the Service Manager roles correctly.
Perform the following steps on all Service Manager Servers virtual machines.
Log on to each Service Manager virtual machine
on each Service Manager virtual machine:
Service Manager workflow account.
Service Manager service account.
Service Manager Admins group.

are members of the Local Users group on each
Service Manager virtual machine:
Service Manager Active Directory CI

connection account.
Service Manager Orchestrator CI

connection account.
Service Manager Operations Manager

alert connection account.
Service Manager Operations Manager CI

connection account.
Service Manager service account.
Service Manager users group.
Service Manager Virtual Machine

Manager CI connection account.
Service Manager workflow account.
Perform the following step on an Active Directory Domain Controller in the target environment.
In the domain where Service Manager will be
installed, verify that the SM Operations Manager
alert connectors and the Service Manager service
accounts are members of the SM Admins group
created earlier.
In the domain where Service Manager will be

installed, verify that the SM OLAP and the Service
Manager reporting accounts are members of the
SQL Server Admins group created earlier.
Log on to the Operations Manager server as an

Administrator. In the Operations Manager
console, navigate to Administration pane. In the
Security node under User Roles, locate the
Operations Manager Administrators role and
add the SCSM Admins group to the role. Click
OK to save the changes.
While still in the Security node under User Roles,

locate the Operations Manager Operators role
and add the SCSM OMCI user to the role. Click
OK to save the changes.
6.3.1 Installation Management Server

The following steps must to be completed in order to install the Service Manager management server role.
Perform the following steps on the first Service Manager management server virtual machine. Design
Pattern 1 deployments will provision two management servers while Design Pattern 2 deployments will
provision a single management server.
Log on to Service Manager management server
(not the Service Manager Data Warehouse
server or the self-service portal server).
From the Service Manager installation media
setup.
The Service Manager installation wizard will

begin. On the splash page, navigate to the
Install section, and then click Service Manager
management server to begin the Service
Manager server installation.
In the Product registration dialog box, provide

the following information in the provided boxes:

organization.


key for installation of Service Manager. If
no key is provided, select the Install as
an evaluation edition (180-day trial)
check box.
In the License terms section, select the I have

read, understood, and agree with the terms
of the license terms check box. When all
selections are confirmed, click Next to continue.
2012\Service Manager for the installation. Click
Next to continue.

are met in the System check results dialog box.
Next to continue.
In the Configure the Service Manager


the SQL Server CNO created for the
Service Manager installation.
SQL Server instance specify the name

of the SQL Server database instance
created for the Service Manager
installation.
Select the Create a new database option and

specify the following information in the
provided boxes:

the Service Manager database. In most
cases the default value of
ServiceManager should be used.
Size (MB) specify the initial database

size. The default value can be used for
Fast Track validation.

the database data files for the Service
Manager database. This should be crosschecked with the worksheet identified
earlier.

the database log files for the Service
Manager database. This should be crosschecked with the worksheet identified
earlier.
A warning message will appear due to the use of

the default SQL collation
(SQL_Latin1_General_CP1_CI_AS). Support for
multiple languages in Service Manager is not
possible when you are using the default
collation. If the installation requires support for
multiple languages using a different collation,
the SQL Server instance will require
reinstallation.
management group dialog box, specify a
box. This value must be unique across the
System Center 2012 products such as the Service
Manager Data Warehouse and Operations
Manager installations.
Specify the Service Manager Administrators
group in the Management group
administrators object picker section.
In the Configure the account for Service

Manager services dialog box, verify that the
Domain account option is selected and specify
the Service Manager service account in the User
name box. Enter the appropriate Password and
Domain in the provided box and drop-down
menu.
Before proceeding, click Test Credentials to
verify the credentials provided.
When successful, click Next to continue.

Manager workflow account dialog box, verify
that the Domain account option is selected and
specify the Service Manager service account in
the User name box. Enter the appropriate
Password and Domain in the provided box and
drop-down menu.
In the Help improve Microsoft System Center

2012 Service Manager dialog box, select the
option to either participate or not participate in
the CEIP by providing selected system
information to Microsoft. Click Next to
continue.
Depending on your systems configuration, the

Use Microsoft Update to help keep your
computer secure and up-to-date dialog box
may appear. Select the appropriate option to
either participate or not participate in automatic
updating. Choose to invoke checking for
updates by selecting the Initiate machine wide
Automatic Update check box. Click Next to
continue.



dialog box.
After each step shows successful installation,
select Open the Encryption Backup or Restore
Wizard after Setup closes to launch the wizard
after setup.
Click Close to complete the installation.
When the installation completes, the

Encryption Key Backup or Restore Wizard will
appear. At the Introduction dialog box, click
Next to continue.
In the Select Action dialog box, select Backup

the Encryption Key , and then click Next to
continue.
In the Specify the Location of the Backup File

dialog box, specify the desired backup file name
and path in the Path box and object picker.
In the Provide a Password dialog box, specify a

desired password in the Password box. Retype
the password in the Confirm Password box and
click Next to begin the backup process.
When complete, click Finish to exit the wizard.
Verify that the Service Manager management

server installed properly by opening the console.
Microsoft System Center 2012 node, click the
Service Manager folder, and then click Service
Manager Console.
In the Connect to Service Manager Server

dialog box, specify the Service Manager
management server name in the Server name
box and click Connect to start the console.
The Service Manager console will open. From

this console, the installation can be validated by
reviewing the configuration and proper
operation of the console.
6.3.2 Design Pattern 1 Installation Add an Additional Management Server

The following steps must to be completed in order to install the Service Manager management server role on
the additional management server.
For Pattern 1 deployments only, perform the following steps on the second Service Manager
management server virtual machine. Design Pattern 2 deployments should skip to the next section,
Installation Data Warehouse server.
Log on to the second Service Manager
management server (not the Service Manager
Data Warehouse server or the self-service portal
server).
setup.

Install section and click Service Manager
management server to begin the Service
Manager server installation.


organization.
Organization - specify the name of the


check box.

of the license terms check box. After all
Next to continue.

Next to continue.


the SQL Server cluster network name
installation.

installation.
Select the Use and existing database option

and specify the database name for the existing
Service Manager database.
reinstallation.

management group dialog box, existing values
cannot be changed for additional management
servers.

the Service Manager service account in the User
name box. Provide the appropriate Password
and Domain in the provided box and dropdown menu.

the CEIP and provide selected system
continue.
Depending on your systems configuration, in

the Use Microsoft Update to help keep your
computer secure and up-to-date dialog box,
select the appropriate option to either
participate or not participate in automatic
continue.


After the installation completes, the wizard will

dialog box.
After each step shows successful installation,
select the Open the Encryption Backup or
Restore Wizard after Setup closes to launch
the wizard after setup.
After the installation completes, the Encryption

Key Backup or Restore Wizard will appear. At
the Introduction dialog box, click Next to
continue.
In the Select Action dialog box, select the

Backup the Encryption Key option, and then


the password in the Confirm Password box,
and then click Next to begin the backup
process.
Click Finish to exit the wizard.
6.3.3 Installation Data Warehouse Server

The following steps must to be completed in order to install the Service Manager Data Warehouse server role.
Perform the following steps on the Service Manager Data Warehouse server virtual machine.
Log on to Service Manager Data Warehouse
server (not the Service Manager management
server or the self-service portal server).
setup.

Install section and click Service Manager data
warehouse management server to begin the
Service Manager server installation.


organization.


check box.

of the license terms check box. When all
Next to continue.

Next to continue.
When the Configure the data warehouse

databases dialog box launches, each
subcategory will appear with an error message
until each of the following sections are
configured:
Staging and Configuration
Repository
Data Mart

databases dialog box, supply the following
information in the provided boxes to configure
the Staging and Configuration and
Repository sections:

Service Manager installation Data
Warehouse.

installation Data Warehouse.

provided boxes:

the SM Data Warehouse database. In
most cases the default value of
DWStagingAndConfig should be used.


the database data files for the Service

the database log files for the Service

reinstallation.

databases dialog box, supply the following
the Staging and Configuration and
Repository sections:

Warehouse.


provided boxes:

the Service Manager Data Warehouse
database. In most cases the default value
of DWDataMart should be used.

Data file folder specify the same drive

letter associated above for the database
data files for the Service Manager Data
Warehouse database. This should be
cross-checked with the worksheet
identified earlier.
Log file folder Specify the same drive

log files for the Service Manager Data
Warehouse database. This should be
identified earlier.
When the Configure additional data

warehouse datamarts dialog box launches,
each subcategory will appear with an error
message until each of the following sections are
configured:
OM Data mart
CM Data mart
In the Configure additional data warehouse

datamarts dialog box, supply the following
the OM Data Mart section:

Warehouse.


provided boxes:

the Service Manager OM Data mart
of OMDWDataMart should be used.


data files for the Service Manager OM
Data mart database. This should be
identified earlier.
Log file folder specify the same drive

log files for the Service Manager OM
identified earlier.
Optionally, a CM Data mart can be created for

Configuration manager integration. To complete
this, in the Configure additional data
warehouse datamarts dialog box, supply the
following information in the provided boxes to
configure the CM Data Mart section:

Warehouse.


provided boxes:

the Service Manager CM Data mart
of CMDWDataMart should be used.


data files for the Service Manager CM
identified earlier.
Log file folder specify the same drive

log files for the Service Manager CM
identified earlier.

management group dialog box, specify a
box. This value must be unique across the
System Center 2012 products such as the Service
Manager management server and Service
Manager Operations Manager installations.
Specify the SM Administrators group in the
Management group administrators object
picker section.
In the Configure the reporting server for the

data warehouse dialog box, specify the Data
Warehouse server in the Report server box.
In the Report server instance drop-down
menu, select Default.
In the Web service URL drop-down menu,
select the default reporting server URL.

the SM service account in the User name box.
Enter the appropriate Password and Domain in
the provided box and drop-down menu.
In the Configure the reporting account dialog

box, specify the SCSM SQL Server Reporting
Services Account in the User name box. Provide
the appropriate Password and Domain in the
provided box and drop-down menu.
In the Configure Analysis Services for OLAP

cubes dialog box, select the Create a new
database option and specify the following

the SQL Server cluster CNO created for
the Service Manager installation SQL
Server Analysis Services.

installation SQL Server Analysis Services..

the SQL Server Analysis Services
of DWASDataBase should be used.
Confirm that the Change database storage

directory check box is clear and click Next to
continue.
In the Configure Analysis Services credential

dialog box, specify the SM OLAP Account in the
User name text box. Enter the appropriate
drop-down menu.

continue.

continue.


When the installation is complete, the wizard

will display the Setup completed successfully
installation.
When the installation is complete, the

Encryption Key Backup or Restore Wizard will
appear. At the Introduction dialog box, click
Next to continue.
In the Select Action dialog box, select the

Backup the Encryption Key option and click
Next to continue.


the password in the Confirm Password box,
and then click Next to begin the backup
process.
When complete, click Finish to exit the wizard.
Perform the following steps on the Service Manager management server virtual machine to register the
Service Manager Data Warehouse and enable reporting in the Service Manager instance.
Within the Service Manager Console, navigate
to the Register with Service Managers Data
Warehouse section. Click the Register with
Service manager Data Warehouse link to
enable reporting.
Note: If the console was open from the previous
installation, close and reopen it.
The Data Warehouse Registration Wizard will

launch. Click Next to begin registration.
In the Specify the data warehouse

management server name dialog box, specify
the Service Manager Data Warehouse server in
the Server name drop-down menu. Then click
Test Connection to validate connectivity
between the Service Manager management and
Data Warehouse servers. Click Next to continue.
In the Provide credentials for the data

warehouse dialog box, click Next to use the
current SM and DW service account as the Run
As account for the Data Warehouse connection.
A Credentials dialog box will appear and

prompt you for the password for the SM service
account. Provide the password, and then click
OK to continue.
The Summary dialog box will appear. Review

the information that was provided earlier, and
then click Create to begin the registration
process.
The Completion dialog box will show the

successful registration of the Data Warehouse.
Click Close to exit the wizard.
Note: The Data Warehouse registration process

can take several hours to complete. During this
time, several management packs are imported
into the Data Warehouse server and several
Data Warehouse jobs are run.
After a few minutes, the Data Warehouse

button will be added to the Service Manager
Console.
Note: This deployment and association process

can take up to two hours to complete.
The status of the management pack imports can
be checked by selecting Management Packs in
the Data Warehouse pane.
Deployment is complete when all listed
management packs show a deployment status
of Completed.
Note: This deployment and association process

can take up to two hours to complete.
In the Data Warehouse pane, select Data
Warehouse Jobs.
In the Data Warehouse Jobs pane, click
MPSyncJob.
In the MPSyncJob details pane, in the
Synchronization Job Details list, scroll to the
right to view the Status column, and then click
Status to alphabetically sort the status column.
Scroll through the Status list. The management
pack deployment process is complete when the
status for all of the management packs is
Associated or Imported. Confirm that there is
no status of either Pending Association or
Failed in the status list. In the Data Warehouse
Jobs pane, the status of the MPSyncJob will
have changed from Running to Not Started
when the registration process is complete.
6.3.4 Installation Self-Service Portal Server

The following steps must to be completed in order to install the Service Manager self-service portal server role.
Perform the following steps on the System Center Service Manager self-service portal virtual machine.
Log on to Service Manager self-service portal
server (not the Service Manager management
server or the Data Warehouse server).
setup.

Install section and click Service Manager web
portal to begin the Service Manager self-service
portal server installation.
The Service Manager Setup Wizard will open.

In the Portal Parts dialog box, select the Web
Content Server and SharePoint Web Parts
check boxes. Click Next to continue.
Note: The warning about installing both Portal
Parts on a single server can be safely ignored.
The setup wizard assumes that the SharePoint
Farm is using a local SQL Server installation
whereas the Private Cloud Fast Track solution
design uses a dedicated SQL Server instance for
the SharePoint farm drastically reducing the
load on the SharePoint Web Parts installation.

the following information in the boxes:

organization.


of the license terms check box. After all
C:\inetpub\wwwroot\System Center Service
Manager Portal for the installation. Click Next to
continue.

Next to continue.
In the Configure the Service Manager SelfService Portal name and port dialog box,
provided boxes:
Website name specify the name of

the website used for the self-service
portal. In most cases, the default name
of SCSMWebContentServer should be
used.

server. The default value is 443. In most
cases this value should be changed to
444.
In addition, select the appropriate Server

Authentication certificate from the SSL
certificate drop-down menu. The certificate CN
field must match the name of the server.
In the Select the Service Manager database
the boxes:

the SQL Server cluster CNO created for
the Service Manager installation
management server.
SQL Server instance specify the SQL

Server database instance created for the
Service Manager installation
management server.
Database specify the name of the

Service Manager database configured
earlier. In most cases the default value of
ServiceManager should be used.
In the Configure the account for the SelfService Portal dialog box, verify that the
the SM Service Account in the User name box.
Enter the appropriate Password and Domain in
the box and drop-down menu.
After the test succeeds, click Next to continue.

SharePoint Web site dialog box, provide the
following information:
In the SharePoint site section, specify
the following information in the
provided boxes:
o
Website name specify the name

of the website used for the selfservice portal. In most cases, the
default name of Service Manager
portal should be used.
Port specify the TCP port used

for the Service Manager selfservice portal server. The default
value is 443. In most cases the
default value of 443 should be
kept.
Select the appropriate server

authentication certificate from the SSL
certificate drop-down menu. This will
be the same certificate used for the
content server in the previous step.
In the SharePoint database section,

boxes:
o
Database server specify the

name of the SQL Server cluster
network name created for the
Service Manager installation
SharePoint Farm.
SQL Server instance specify the

SQL Server database instance
installation SharePoint Farm.
Database server specify the

database name for the portal. In
most cases, the default value of
SharePoint_SMPortalContent will
be used.

Manager SharePoint application pool dialog
box, specify the SM service account in the User
name box. Enter the appropriate Password and
Domain in the provided box and drop-down
menu.

continue.

continue.


When completed, the Service Manger Setup

Wizard will display the Setup completed
successfully dialog box. Click Close to finish the
installation.
Note the SMPortal link provided in the dialog
box.
From a browser, open the Service Manager selfservice portal at

https://<servername>/SMPortal.
Verify that all sections display as expected.
Orchestrator
The Orchestrator installation process includes the following high-level steps.
5
System Center 2012

Orchestrator
Installation
Perform
Prerequisites
Installation of
System Center
2012 Orchestrator
Roles
Post Installation
Configuration of
Orchestrator
Install the .NET

Framework 3.5.1
Feature
Installation:
Runbook,
Orchestration
Console, Web
Service and
Designer Server
Install Integration
Packs
Install the .NET

Framework 4
Redistributable
Pattern 1
Installation:
Add an Additional
Runbook Server
Deploy and
Configure
Integration Packs
Install Silverlight
Runtime 4
Figure 7: Orchestrator installation process
7.1
Overview
This section provides the setup procedure for Orchestrator into the Private Cloud Fast Track fabric management
architecture. The following assumptions are made:
Base virtual machines running Windows Server 2008 R2 (x64) have been provisioned.
A multi-node, SQL Server 2008 R2 cluster with dedicated instance has been established in previous
steps for Orchestrator.
The .NET Framework 4 Redistributable is installed.
7.2
Prerequisites
7.2.1 Accounts
Verify that the following security accounts have been created.
User name
Purpose
Permissions
<DOMAIN>\FT-SCO-SVC
Orchestrator service
account
This account will need:
Full admin permissions on all

target systems to be
managed
Log on As a Service rights
(User Rights)
Sysadmin on the SQL Server,
or dbo rights to the
Orchestrator database after
its created
This account will need to be a

member in the following groups:
FT-VMM-Admins
7.2.2 Groups
Security group name
Group scope
Members
<DOMAIN>\FT-SCOOperators
Global
<DOMAIN>\FT-SCOSVC
<DOMAIN>\FT-SCOAdmins
Global
<DOMAIN>\FT-SCOSVC
Member of
Local Administrators
Target Active Directory domain
BUILTIN\Distributed COM Users

The Orchestrator installation requires the .NET Framework 3.5.1 Features to be enabled to support installation.
Follow the provided steps to enable the .NET Framework 3.5.1 Features.
Perform the following steps on the Orchestrator virtual machine. For Pattern 1 perform this step on both
Orchestrator virtual machines.
box only. Leave the WCF Activation check box
clear.

box, review the choices made during the wizard,
and then click Install to add the features.

the progress of the features installation.

3.5.1 Features installed correctly. Then click
Close to complete the installation of the .NET
Framework 3.5.1 Features.

Additionally, the Orchestrator portal installation also requires the .NET Framework 4 package be installed prior
to installation. Follow the provided steps to install the .NET Framework 4 package.
setup.

the license terms check box, and then click
Install to begin the installation.

setup wizard.
After the installation has completed, click Finish

to exit the installation.
7.2.5 Install Silverlight Runtime 4

Silverlight.exe and click Run as administrator
In the Install Silverlight dialog box, click Install

now.
In the Enable Microsoft Update dialog box,

select or clear the Enable Microsoft Update
check box based on organizational preferences.
In the Installation successful dialog box, click

Close to exit the installation.
7.3
Installation Runbook, Orchestration Console, Web Service, and Designer

Server
The following steps needs to be completed in order to install the first Orchestrator Runbook Server component.
Perform the following steps on the Orchestrator virtual machine.
Log on to the Orchestrator virtual machine with
a user with local admin rights.
on the Orchestrator virtual machine:
Orchestrator Admins group.
Log on to System Center Orchestrator server.

From the System Center Orchestrator
setuporchestrator.exe and click Run as
setup.
The Orchestrator installation wizard will begin.

On the splash page, click Install to begin the
Orchestrator server installation.

box, provide the following information in the
boxes:

organization.

Product Key provide a valid product

key for installation of Orchestrator. If no
key is provided, Orchestrator will be
installed in evaluation mode.

In the Please read this License Terms dialog
box, verify that the I accept the license terms
check box is selected, and then click Next to
continue.
In the Select Features to install dialog box,

select the Management Server (default
selected), Runbook server, Orchestration
console and web service, and Runbook
Designer check boxes. Click Next to continue.
The Checking for required hardware and

software dialog box will appear to verify the
installation prerequisites. After validation is
completed, click Next to continue.
The Orchestrator setup will identify any

prerequisite software required for the
installation to complete. The Setup will install
these missing software prerequisites dialog
box will attempt to perform the installation of
missing prerequisites. When completed, click
Next to continue.
After the installation of the missing prerequisites

is completed, click Next to continue.
In the Configure the service account dialog

box, specify the Orchestrator service account in
the Username box. Provide the appropriate
drop-down menu.
Before proceeding, click Test to verify the
credentials provided.
In the Configure the database server dialog

box, enter the following information in the
boxes:
Server specify the SQL Server cluster

name and instance name created in the
steps above.

SQL Server if not the default.
In the Authentication Credentials section,

select Windows Authentication, and then click
Test Database Connection.
After the test has succeeded, click Next to
continue.
In the Configure the database dialog box in

the Database section, select New database.
Specify the default database name of
Orchestrator.
In the Configure Orchestrator users group

dialog box, select the Orchestrator users group
created earlier using the object picker by
clicking Browse and selecting the associated
group. For the Private Cloud Fast Track solution,
this is the Orchestrator operators group.
Verify that the Grant remote access to the
Runbook Designer check box is selected, and
then click Next to continue.
In the Configure the ports for the web

services dialog box, provide the following
information in the boxes:
Web service port specify the TCP port

used for the Orchestrator Web Service.
The default value of 81 is recommended.
Orchestration console port specify

the TCP port used for the Orchestrator
console port. The default value of 82 is
recommended.
After configuring the ports successfully, click

Next to continue.
In the Select the installation location dialog

box, specify a location or accept the default
location of %ProgramFiles(x86)%\Microsoft
System Center 2012\Orchestrator for the
The Help Improve Microsoft System Center

Orchestrator dialog box provides options for
participating in various product feedback
mechanisms. These include:
The Customer Experience

Improvement Program.
Error Reporting.

continue.

In the Installing features dialog box, the

installation will proceed and show progress.
The Setup completed successfully dialog box

will appear after all portions of setup complete
successfully. Verify that all check boxes are
cleared, and then click Close to finish the
installation.
After installed, verify that the Orchestrator roles

installed properly by opening the consoles. From
the Start Menu, navigate to Microsoft System
Center 2012, click the Orchestrator folder, and
then click Orchestration Console.
Validate that the Orchestration console

performs properly in Internet Explorer.

Microsoft System Center 2012, click the
Orchestrator folder, and then click Runbook
Designer.
Launch the Runbook Designer console and

verify that it performs properly.

Orchestrator folder, and then click
Deployment Manager.
Launch the Deployment Manager console and

verify that it performs properly.
Configure Windows Firewall for the first

Orchestrator Runbook Server.28
If you wish to leave Windows Firewall enabled,
you must first enable the following rules in
Windows Firewall:
Windows Management Instrumentation

(WMI-In).

(DCOM-In).

(ASync-In).
Right-click each rule, and click Enable Rule on

the shortcut menu.
28
Orchestrator guidance is provided by the following TechNet resources: Using Windows Firewall with Orchestrator http://technet.microsoft.com/en-us/library/hh912321.aspx and TCP Port Requirements http://technet.microsoft.com/en-us/library/hh420382.aspx.
In Windows Firewall, create a new Program rule

using the following program path:
%SystemRoot%\SysWOW64\orchestrato
rRemotingService.exe
Name the rule SCO Orchestrator Remoting

Service (x64).
Because the first server runs the Orchestration

console and web service, two additional ports
(TCP 81 and 82) must be opened on Windows
Firewall as well. Create two additional firewall
port rules named SCO Orchestration Console
(TCP 81) and SCO Web Service (TCP 82) for
each port and enable them.
7.4
Pattern 1 Installation Add an Additional Runbook Server

The following steps needs to be completed in order to install an additional Orchestrator Runbook Server for
Pattern 1 installations.
Perform the following steps on the second Orchestrator Runbook Server virtual machine.
Log on to the Orchestrator virtual machine with
a user with local admin rights.
on the Orchestrator virtual machine:
Orchestrator Admins group.
Log on to System Center Orchestrator server.

From the System Center Orchestrator
SetupOrchestrator.exe and click Run as
setup.
The Orchestrator installation wizard will begin.

On the splash page, click Install to begin the
Orchestrator server installation.

boxes:

organization.


key for installation of Orchestrator. If no
key is provided, Orchestrator will be
installed in evaluation mode.

In the Please read this License Terms dialog
box, verify that the I accept the license terms
check box is selected, and then click Next to
continue.

select the Management Server (default
selected) and Runbook server check boxes.
The Checking for required hardware and

software dialog box will appear to verify the
installation prerequisites. After validation
completes, click Next to continue.
The Orchestrator setup will identify any
prerequisite software required for the
installation to complete. In some cases, this
dialog box will not appear and is provided as an
example.
The Setup may install these missing software
prerequisites dialog box will attempt to
perform the installation of missing prerequisites.
When the installation has completed, click Next
to continue.
In the Configure the service account dialog
box, specify the Orchestrator service account in
the Username box. Enter the appropriate
drop-down menu.
Before proceeding, click Test to verify the
credentials provided.
continue.
In the Configure the database server dialog

boxes:
Server specify the SQL Server cluster

name and instance name created in the
steps above.

SQL Server if not the default.
In the Authentication Credentials section,

select Windows Authentication, and then click
Test Database Connection.
continue.
In the Configure the database dialog box, in
the Database section select Existing database.
Select the default database name of
Orchestrator from the drop-down menu.
In the Configure Orchestrator users group

dialog box, select the Orchestrator users group
created earlier using the object picker by
clicking Browse and selecting the associated
group. For the Private Cloud Fast Track solution,
this is the Orchestrator operators group.
Verify that the Grant remote access to the
Runbook Designer check box is selected, and
then click Next to continue.
In the Select the installation location dialog

box, specify a location or accept the default
location of %ProgramFiles(x86)%\Microsoft
System Center 2012\Orchestrator for the
The Microsoft Update dialog box provides

options for participating in automatic updates
for Orchestrator. Select the appropriate option
based on your organizations policies, and then
The Help improve Microsoft System Center

Orchestrator dialog box provides options for
participating in product feedback mechanisms.
This includes:
Error Reporting.

continue.

appear and display the selections made in the
and then click Install to continue.
In the Installing features dialog box, the

installation will proceed and show progress.
The Setup completed successfully dialog box

will appear after all portions of setup complete
successfully. Verify that all check boxes are
cleared. Click Close to finish the installation.
Configure Windows Firewall for the second

Orchestrator Runbook Server.29
If you wish to leave Windows Firewall enabled,
you must first enable the following rules in
Windows Firewall:

(WMI-In).

(DCOM-In).

(ASync-In).
Right-click each rule and click Enable Rule on

the shortcut menu.
In Windows Firewall, create a new Program rule
using the following program path:
%SystemRoot%\SysWOW64\orchestrato
rRemotingService.exe
Name the rule SCO Orchestrator Remoting

Service (x64).
29
Orchestrator guidance is provided by the following TechNet resources: Using Windows Firewall with Orchestrator http://technet.microsoft.com/en-us/library/hh912321.aspx and TCP Port Requirements http://technet.microsoft.com/en-us/library/hh420382.aspx.
7.5
Post-Installation Tasks
After the installation is complete, the installation and configuration of Orchestrator Integration Packs on the
target Runbook Servers is required.
7.5.1 Install the Virtual Machine Manager Console

Perform the following steps on the Orchestrator virtual machine. For Pattern 1 installations deploy this on
both Runbook servers.
Log on to the Orchestrator server with a
privileged user account that has Administrator
privileges. From the Virtual Machine Manager

installation.

verify that the VMM console installation option
In the Please read this notice dialog box, verify

that the I agree with the terms of this notice
In the Customer Experience Improvement

Program dialog box, click Next to continue.

continue.

%ProgramFiles%\System Center Operations
Manager 2012 for the installation. Click Next to
continue.
In the Port configuration dialog box, specify

the port used for communication with the VMM
management server in the provided box. If no
modifications were made during Virtual
Machine Management installation, the default
port is 8100. Click Next to continue.

After the installation has completed, the wizard

installation.
7.5.2 Install the Microsoft Report Viewer 2010 SP1

Additionally, the Operations Manager console installation also requires the Microsoft Report Viewer 2010 SP1
package to be installed prior to installation.30 Follow the steps to install the Report Viewer 2010 SP1 package.
Perform the following steps on each Orchestrator virtual machine. For Pattern 1 installations, deploy this
on both Runbook servers.
setup.

30


setup wizard.
After the installation has completed, click Finish

to exit the installation.
7.5.3 Install the Operations Manager Console

Perform the following steps on the Orchestrator virtual machine. For Pattern 1 installations, perform
these steps on both servers.
setup.

the Operations Manager console installation.

verify that the Operations console check box is

The Help Improve System Center 2012

Operations Manager dialog box provides
options for participating in product feedback
mechanisms. These include:

Error Reporting.

continue.


will display the Setup is complete dialog box.
Verify that the Start the Operations console
when the wizard closes check box is selected.

7.5.4 Install Integration Packs

The following steps needs to be completed in order to install the Orchestrator Integration Packs. 31
Perform the following steps on the Orchestrator Runbook Server virtual machine.
Download the System Center 2012 Integration
Packs from http://technet.microsoft.com/enus/library/hh830706.aspx32, and expand them to
a single location so that the Orchestrator
Integration Pack files are expanded.

Deployment Manager.
In the Runbook Designer console, on the

selected Runbook Server, right-click the
Integration Packs node and click Register IP
with the Orchestrator Management Server on
the shortcut menu.
31
32
System Center 2012 Orchestrator Component Add-ons and Extensions - http://www.microsoft.com/download/en/details.aspx?id=28725.
The actual download link for the integration packs installed for Private Cloud Fast Track is at the same download link listed in the footnote above
(http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=28725).
The Integration Pack Registration Wizard will

appear. Click Next to continue.
In the Select Integration Packs or Hotfixes

dialog box, click Add. Navigate to the expanded
integration packs folder created earlier, select
the following integration packs, and then click
Open:
System Center 2012 Configuration
Manager
System Center 2012 Data Protection

Manager
System Center 2012 Operations

Manager
System Center 2012 Service Manager
System Center 2012 Virtual Machine

Manager
After all integration packs are selected, click

Next to continue.
The Completing the Integration Pack Wizard

dialog box will appear with a summary of
selections. Click Finish to begin the integration
pack installation.
During installation, each integration pack will

display Microsoft Software License Terms. Click
Accept to continue with the installation.
Each integration pack will be displayed in the

Deployment Manager interface.
7.5.5 Deploy Integration Packs

The following steps needs to be completed in order to install the Orchestrator Integration Packs.33
Perform the following steps on the Orchestrator Runbook Server virtual machine.
Deployment Manager.
In the Runbook Designer console, on the

selected Runbook Server, right-click the
Integration Packs node and click Deploy IP to
Runbook Server or Runbook Designer on the
shortcut menu.
The Integration Pack Deployment Wizard will
33
System Center 2012 Orchestrator Component Add-ons and Extensions - http://www.microsoft.com/download/en/details.aspx?id=28725.
In the Deploy Integration Packs or Hotfixes

dialog box, select the check boxes of the
following integration packs:
Manager.

Manager.

Manager.
System Center 2012 Service Manager.

Manager.

In the Computer Selection Details dialog box,
type the name of the Orchestrator management
server, and then click Add. After it has been
added, click Next to continue.
In the Installation Configuration dialog box, in

the Advanced Options pane select Stop all
running Runbooks before installing the
Integration Packs or Hotfixes. Click Next to
continue.
The Completing the Integration Pack

Deployment Wizard dialog box will appear
with a summary of selections. Click Finish to
begin the integration pack installation.
During installation, each integration pack will

display Microsoft Software License Terms. Click
Accept to continue with the installation.
After the installation has completed, each

integration pack will be displayed in the
Runbook Designer interface.
To complete the configuration of the integration

packs, open the Orchestrator Runbook
Designer Console, open the Options menu,
and then click SC 2012 Virtual Machine
Manager.
In the Prerequisite Configuration dialog box,

click Add.
In the Add Configuration dialog box, complete

the required information for the Virtual Machine
Manager server as shown, and then click OK.
After returning to the Prerequisite
Configuration dialog box, click Finish to save
the changes.
While still in the Orchestrator Runbook

Designer Console, open the Options menu,
and click SC 2012 Operations Manager.
In the Microsoft System Center Operations

Manager Connections dialog box, click Add.
In the MS System Center Operations Manager

Connection Settings dialog box, complete the
required information for the Operations
Manager management server and click Test
Connection34. After connectivity is verified, click
OK. After returning to the Prerequisite
the changes.
34
The use of the Administrator account is used as an example. Use account information that is applicable to your installation.
In the Orchestrator Runbook Designer

console, open the Options menu, and click SC
2012 Service Manager.
In the Connections dialog box, click Add.
In the Connection dialog box, fill in the

required information for the Operations
Manager management server35 and click Test
Connection. After connectivity is verified, click
OK. After returning to the Prerequisite
the changes.
35
The use of the Administrator account is used as an example. Use account information that is applicable to your installation.
7.5.6 Deploy Integration Packs to the Secondary Server

The following steps needs to be completed in order to install the Orchestrator Integration Packs on the
secondary server for Pattern 1 installations.
Perform the following steps on the first Orchestrator Runbook Server virtual machine.
Deployment Manager.
Launch the Deployment Manager console,
right-click the Integration Packs node, and
click Deploy IP to Runbook Server or
Runbook Designer on the shortcut menu.
The Integration Pack Deployment Wizard will

In the Deploy Integration Packs or Hotfixes

dialog box, select the following integration
packs:
System Center Integration Pack for
Manager

Manager

Manager

System Center 2012 Service Manager

Manager

In the Computer Selection Details dialog box,
type the name of the Orchestrator management
server into the Computer box, and then click
Add. After it has been added, click Next to
continue.
In the Installation Configuration dialog box, in

the Advanced Options pane select Stop all
running Runbooks before installing the
Integration Packs or Hotfixes. Click Next to
continue.
The Completing the Integration Pack

Deployment Wizard dialog box will appear
with a summary of selections. Click Finish to
begin the integration pack installation.
During the installation, each integration pack

will display Microsoft Software License Terms.
Click Accept to continue with the installation.
App Controller
The App Controller installation process includes the following high-level steps.
6
System Center 2012

App Controller
Installation
Perform
Prerequisites
Installation of
System Center
2012 App
Controller
Install the .NET

Framework 3.5.1
Feature
Install App
Contoller
Install the .NET

Framework 4
Redistributable
Install Silverlight
Runtime 4
Request and
Install an SSL
Certificate
Installation of the
Virtual Machine
Manager Console
Figure 8: App Controller installation process
8.1
Overview
This section provides a high-level walkthrough about how to set up App Controller. The following assumptions
are made:
A base virtual machine running Windows Server 2008 R2 (x64) has been provisioned for App Controller
A SQL Server 2008 R2 cluster with dedicated instance that has been established in previous steps for
App Controller
All the System Center products have been hydrated and validated
The .NET Framework 3.5.1 Features are installed
The .NET Framework 4 Redistributable is installed
Microsoft Silverlight Runtime 4 is installed
A Trusted Server Authentication (SSL) Certificate (the CN field of the certificate must match server
name) is installed
8.2
Prerequisites
8.2.1 Accounts
User name
Purpose
Permissions
<DOMAIN>\ FT-SCAC-SVC
App controller service

account
This account will need to be a

member in the following groups:
FT-SCAC-Admins
FT-VMM-Admins
8.2.2 Groups
Group name
Purpose
<DOMAIN>\ FT-SCAC-Admins
App Controller Admin

group
Members
<DOMAIN>\ FT-SCAC-SVC
<DOMAIN>\ FT-VMM-Admins

The App Controller installation requires the .NET Framework 3.5.1 Features be enabled to support installation.
Follow the provided steps to enable the .NET Framework 3.5.1 Features.
Perform the following steps on the App Controller virtual machine.
Server Manager, click the Features node and
then click Add Features. The Add Features
Wizard will appear. In the Select Features
dialog box, select the .NET Framework 3.5.1
Features check box.
The Add role services and features required

dialog box will appear. Click Add Required Role
Services.
After returning to the Select Features dialog

box, the .NET Framework 3.5.1 Features check
box will be selected. Click Next to continue.
The Web Server (IIS) dialog box will appear,

outlining information about the dependent role
services. Click Next to continue.
The Select Role Services dialog box will appear

with default selections required by the .NET
Framework feature. To support App Controller
installation, the following additional role services
are required:
Static Content
Default Document
HTTP Errors
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
HTTP Logging
Request Monitor
Tracing
Basic Authentication
Windows Authentication
Request Filtering
Static Content Compression
IIS Management Console
After all additional role services have been

selected, click Next to continue.


the progress of the feature installation.
The Installation Results dialog box will appear.

Verify that all features and dependent role
services were installed correctly. Then click Close
to complete the installation of the .NET
Framework 3.5.1 Features.

Additionally, the App Controller installation also requires prior installation of the .NET Framework 4 package.
Follow the provided steps to install the .NET Framework 4 package.
setup.
In the Microsoft .NET Framework 4 Setup

the license terms check box. Click Install to

setup wizard.
When installation has completed, click Finish to

exit the installation.
8.2.5 Install Silverlight Runtime 4


Silverlight.exe and click Run as administrator
The Silverlight installation wizard will appear. In

the Install Silverlight dialog box, click Install
now.
In the Enable Microsoft Update dialog box,

select or clear the Enable Microsoft Update
check box based on the policies of your
organization. Click Next to begin the installation.
After installation, click Close to complete the

setup.
8.2.6 Request and Install an SSL Certificate

For IIS, there are several ways to request a SSL Certificate. One method, through the IIS Manager console, is
outlined below.

Log on to the App Controller virtual machine as
a user with local admin rights. From the Start
Menu, click Administrative Tools, and then
click Internet Information Services (IIS)
Manager.
In the Internet Information Services (IIS)
Manager console, click the server node and in
the IIS section, click Server Certificates.
The Server Certificates pane will expand. Under

actions, click Create Certificate Request.
The Request Certificate dialog box will appear.

In the Distinguished Name Properties dialog
box, complete the information as prompted.
Note that the Common name field must equal
the exact name that the server will access in a
web browser. Click Next to continue.
In the Cryptographic Service Provider

Properties dialog box, select a Cryptographic
Service Provider (CSP) that is appropriate for
your issuing CA. In most cases, selecting the
default CSP and default bit length is satisfactory.
In the File Name dialog box, provide a

complete path to save the certificate request file.
Click Finish to generate the certificate request.
When completed, submit the request to your
issuing CA or certificate provider of choice and
follow the next steps to install the newly issued
certificate.
After receiving the issued certificate, open the

Internet Information Services (IIS) Manager
console and click Server Certificates once
again. From the Actions pane, select Complete
Certificate Request.
The Complete Certificate Request wizard will
appear. In the Specify Certificate Authority
Response dialog box, specify the file name and
location of the issued certificate and supply a
friendly name for the certificate in the provided
boxes. Click OK to complete the operation.
In the Server Certificates section of the IIS

Manager, you will now see the newly created
and installed certificate.
8.2.7 Install the Virtual Machine Manager Console

The following steps needs to be completed in order to install the Virtual Machine Manager console on the
target App Controller virtual machine.

From the Virtual Machine Manager installation
media source, right-click setup.exe and click
Run as administrator on the shortcut menu to
begin setup.

installation.

verify that the VMM console installation option
In the Please read this notice dialog box, verify

that the I agree with the terms of this notice
In the Customer Experience Improvement

Program dialog box, select the option to either
participate or not participate in the CEIP and
provide selected system information to
Microsoft. Click Next to continue.

continue.

2012\Virtual Machine Manager for the
In the Port configuration dialog box, specify

the port used for communication with the
Virtual Machine Manager management server in
the provided box. If no modifications were made
during Virtual Machine Manager installation, the
default port would be 8100. Click Next to
continue.

installation.

to verify that the installation occurred properly.
Verify that the console launches and connects to
the Virtual Machine Manager instance installed.
8.3
Installation
The following steps needs to be completed in order to install App Controller.

Log on to the App Controller virtual machine
Verify the following accounts and/or groups are
members of the Local Administrators group on
the App Controller portal virtual machine:
Fast Track Operations Manager action

account.
Fast Track App Controller service

account.
Fast Track App Controller Admins

group.
Log on to System Center App controller server.

From the System Center App Controller
The App Controller Setup wizard will begin. On

the splash page, click Install to begin the App
Controller server installation.
In the Enter your product registration

information dialog box, provide a valid product
key for installation of Orchestrator. If no key is
provided, App Controller will be installed in
evaluation mode. Click Next to continue.
In the Review the software license terms

understood, and agree with the terms of the
license agreement check box is selected. Click
Next to continue.
In the Install missing software dialog box, the

wizard will detect missing roles and software,
and attempt to install missing prerequisites.
Click Install to enable missing roles and
features.
The wizard will detect missing roles and software

and attempt to install missing prerequisites.
Please be patient during this process.
In the Select the installation path dialog box,

accept the default installation location of
2012\App Controller or specify a different
location by clicking Browse. After making a
selection, click Next to continue.
In the Configure the services dialog box, verify

that the Domain account option is selected and
specify the App Controller service account in the
Domain and user name box. Provide the
associated Password in the supplied box.
In the Port box, accept the default TCP port of
18622 or change the port to meet your
organizations requirements. In most cases, the
default port selection should be kept.
In the Configure the website dialog box,

provide the following information:
Under Website, in Type: HTTPS, select

All unassigned from the IP address
drop-down menu. Set the Port value to
443.
Verify that the Use existing certificate

option is selected and select the proper
Server Authentication certificate from
the drop-down menu that installed
within the virtual machine.

Note: While not recommended, if a Server
Authentication certificate cannot be obtained
and installed on the App Controller server, you
may choose Generate self-signed certificate
to satisfy installation requirements.
In the Configure the SQL Server database

dialog box, make the following selections to
install the App Controller database in the SCO
instance (refer to the worksheet created earlier):
Server name specify the cluster

network name of the SQL Server failover
cluster hosting the instance.
Port specify the TCP port used for SQL

Server connectivity (1433 by default).
Instance name - specify the instance

name where the AppController database
will be installed to (the SCO instance).

the App Controller database. In most
cases the default value of AppController
should be used.

The Help Improve App Controller for System
Center 2012 dialog box provides options for
participating in product feedback mechanisms.
These include:

Microsoft Update.

organizations policies, and then click Install to
continue.
In the Confirm the settings dialog box, verify

the settings provided during the installation
wizard, and then click Install to begin the
installation.
The required components will install and

progress of the installation will be provided in
the wizard.
When complete, the Setup completed

successfully dialog box will appear with the
progress of each component. Verify that each
component was installed successfully. Note the
App Controller website in the provided box.
Verify that the Start the App Controller
website when Setup closes check box is
selected, and then click Finish.
The System Center 2012 App Controller

website will be launched. Because no users have
been created in Virtual Machine Manager, enter
the credentials of the administrative account
used to install Virtual Machine Manager (which
has been assigned an admin role in Virtual
Machine Manager). After entering those
credentials, click Sign In.
The App Controller portal will appear. After

validating functionality, the App Controller
installation is considered complete.
System Center Cloud Services Process Pack

The Cloud Services Process Pack installation process includes the following high-level steps.
7
System Center 2012

Cloud Services Process
Pack Installation
Perform
Prerequisites
Installation of
System Center
2012 Cloud
Services Process
Pack
Import the VMM

Discovery
Management Pack
into Service
Manager
Install Cloud
Services Process
Pack on Service
Manager
Create the
OrchestratorUsers
Group local group
on the
Orchestrator
Server
Install the Cloud

Services Runbooks
on Orchestrator
Figure 9: Cloud Services Process Pack installation process
9.1
Overview
This section provides the setup procedure for Orchestrator into the Private Cloud Fast Track fabric management
architecture. The following assumptions are made:
The System Center integration pack for System Center 2012 Service Manager needs to be imported
into Orchestrator per previous steps.
Operations Manager integration with Virtual Machine Manager should already be complete per
previous steps.
The System Center Cloud Services Process Pack is available at http://technet.microsoft.com/enus/library/hh562067.aspx. IT organizations considering IaaS will need to examine and adapt their existing tools,
processes, workflows, and automation to meet the requirements of an effective cloud services implementation.
While it is critical that the underlying components (such as self-service portal, ticketing infrastructure,
notifications, workflows, and automation) integrate well with each other and account for industry-wide
recommended practices, the work involved to implement an effective cloud service can be daunting and time
consuming.
The System Center Cloud Services Process Pack addresses these concerns by enabling IaaS while incorporating
domain expertise and recommended practices from enterprises that have successfully deployed IaaS. These
recommended practices are made available out-of-the box and are evident in all aspects of the solution.
The potential benefits offered by the System Center Cloud Services Process Pack for the enterprise include:
Deep customization and extension of the cloud services experience that is natively supported by the
System Center suite of products.
Reduced cost, effort, and time to deploy cloud services to organizations that already utilizes the System
Center platform.
The potential benefits offered by the System Center Cloud Services Process Pack for consumers of IT within the
enterprise include:
Standardized and well-defined processes for requesting and managing cloud services, including the
ability to define projects, capacity pools, and virtual machines.
Natively supported request, approval, and notification to help enable businesses to effectively manage
their own allocated infrastructure capacity pools.
The System Center Cloud Services Process Pack offers a self-service experience to facilitate private cloud
capacity requests from your business unit IT application owners and end users, including the flexibility to
request additional capacity as business demands increase.
9.2
Prerequisites
9.2.1 Import the Virtual Machine Manager Discovery Management Pack into
Service Manager
The Virtual Machine Manager Discovery Management Pack must be installed prior to the installation of CSPP.
The following steps are provided.
Perform the following steps on the Service Manager management server virtual machine.
From the Service Manager Console, click the
Administration node. In the Import
Management Packs section, click Import
additional management packs.
In the Import Management Packs dialog box,

click Add.
The following steps must be repeated for each

set of management packs, which must be
installed to remove management pack
dependencies. The required management packs
can be found in the \Setup\ManagementPacks
of the CSPP installation media.
After each set of management packs are added,
click Import to begin the process.
Install the following management packs in this
order:
1.
Data Warehouse Library
Microsoft Generic Report Library
Windows Server Operating System Library

(Discovery)
2.
3.
Services Library

Services 2000

Services 2003
Windows Server 2008 Internet Information

Services 7
SQL Server Core Library
Microsoft System Center Operations
4.
Manager Library
Image Library (System)
System Virtualization Library
SQL Server 2005 (Discovery)
SQL Server 2005 (Monitoring)
SQL Server 2008 (Discovery)

SQL Server 2008 (Monitoring)
Virtual Machine Manager Library
System Center Virtual Machine Manager
5.
2008 R2 PRO Library
Virtual Machine Manager PRO V2 Library
Follow the same steps to import the required

System Center 2012 Virtual Machine Manager
Discovery management pack.
When the import has completed, exit the wizard.
9.2.2 Create the OrchestratorUsersGroup local group on the Orchestrator

Server
Perform the following steps to avoid issues related to CSPP setup on Orchestrator.

The prerequisite checker in CSPP validates
settings in Orchestrator, but during its process, it
verifies if the logged-in user is directly a
member of a local security group called
OrchestratorUsersGroup, regardless of how
security for Orchestrator is configured. Per the
recommended configuration, this group was
changed to a domain group; however, a local
group must be created with membership
granted to the installation account to complete
setup36.
To satisfy this requirement, a local group must
be created on the Orchestrator servers where
the runbooks will be installed. In Server
Manager, navigate to the Local Users and
Groups node, right-click Groups and click New
Group on the shortcut menu.
In the New Group dialog box, provide the
Group name of OrchestratorUsersGroup, and
ensure that the membership contains the
account you are using to perform this
installation. Click Create to complete the
creation of the local group.
36
http://blogs.technet.com/b/orchestrator/archive/2012/05/10/faq-cloud-service-mp-pre-req-error-the-current-user-isnot-a-valid-system-center-orchestrator-user.aspx
9.3
Installation Cloud Services Process Pack

The following steps needs to be completed in order to install the Cloud Services Process Pack.
Perform the following steps on the Service Manager management server virtual machine.
Log on to the Service Manager management
server virtual machine with a user with local
admin rights.
Verify the account has the following rights:
A Service Manager administrator.
An administrator on the server that is

running Service Manager.
After verification, navigate to the folder where

the Cloud Services Process Pack (CSPP) was
extracted, and then click Setup.exe.
The Cloud Services Process Pack Setup
Wizard will appear. In the Install section, click
Cloud services process pack.
In the Product registration dialog box, enter


organization.


Next to continue.


dialog box.
9.4
Installation Cloud Services Runbooks

The following steps needs to be completed in order to install the Cloud Services Process Pack Orchestrator
runbooks.

Log on to the Orchestrator management server
virtual machine with a user with local admin
rights.
Verify the account has the following rights:
An administrator on the machine on

which the program is installed as well as
an Orchestrator administrator.
An administrator in the Orchestrator

database.
An administrator on VMM.
A member of the local

OrchestratorUsersGroup created in
earlier steps.
After verification, navigate to the folder where

the Cloud Services Process Pack (CSPP) was
extracted, and then click Setup.exe.
The Cloud Services Process Pack Setup
Wizard will appear. In the Install section, click
Cloud services runbooks.
In the Product registration dialog box, enter


organization.


Next to continue.


dialog box.
To verify the installation, open Runbook

Designer and validate that the SMCloudServices runbooks were added to the
Orchestrator instance.
10 Appendix A: SQL Server Cluster Named Instance Worksheet

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
SharePoint
Farm
Cluster
Service
Name
Clustered
SQL Server
Instance IP
Address
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)
SQLSCVMMDB
SQL SCACDB
SQLSCODB
SQLSCOMDB
SQLSCOMDW
SQLSCSMDB
SQLSCSMAS
SQLSCSMDW
SQLSCSPFarm
SCVMMDB
SCACDB
SCODB
SCOMDB
SCOMDW
SCSMDB
SCSMAS
SCSMDW
SCSPFarm
Host
Cluster
Public
Network
Interface
Name
Host
Cluster
Public
Network
Interface
Subnet
Mask
SQL Server
Instance
DATA
Cluster Disk
Resource
SQL Server
Instance
DATA Drive
SQL Server
Instance
Failover
Cluster
Network
Name
SQL Server
Instance
Install Drive
SQL Server
Instance
LOG Cluster
Disk
Resource
SQL Server
Instance
LOG Drive
SQL Server
Instance
Name
SQL Server
Instance
TEMPDB
Drive
11 Appendix B: Installing a Windows Deployment Services Server

The Virtual Machine Manager installation requires that the Windows Server Update Services (WSUS) 3.0 Service
Pack 2 be installed on either the Virtual Machine Manager management server or somewhere in the target
environment. This WSUS server must be a root or downstream server, not a WSUS replica server. In addition, a
Windows Deployment Services (WDS) server must exist within the target environment. The following steps are
provided for deployment of WDS:
11.1.1 Adding the Windows Deployment Services Role

The following steps are provided in the event a WDS server must be installed:
Server Manager, click the Roles node and click
Add Roles. The Add Roles Wizard will appear.
In the Select Server Roles dialog box, select the
Windows Deployment Services check box.
The Role services dialog box will appear. Select

the Deployment Server and Transport Server
check boxes. Click Next to continue.


box will appear. Verify that all dependent role
services were installed correctly. When verified,
click Close to complete the installation of
Windows Deployment Services role.
12 Appendix C: SlipSQL.PS1
To support slipstreamed installations of SQL, the following Windows PowerShell script is provided to create a
merged SQL Server source.
# Title: SQL 2008 R2 Build SlipStream Script
# Version: 1.1
$debug=1
Function Get-ValidPath ($path)
{
$isValid = $False
Do
{
$path = Read-Host "Enter the location (folder)"
$isValid = Test-Path $path
if (! $isValid ) { Write-Error $path is not a valid folder }
}
Until ($isValid)
return $path
}
Function Merge-SQLFiles ($UpdatePath, $SlipStreamTargetPath, $SlipStreamTargetFolder)
{
# Read in the update path and loop through each file.
$files = Get-ChildItem $UpdatePath
foreach ($file in $files)
{
if ($debug -eq 1){Write-Host "Extracting file $file"}
$UpdateFile = $UpdatePath + "\" + $file
$UpdateTargetPath = $SlipStreamTargetPath + "\" + $SlipStreamTargetFolder
[diagnostics.process]::start("$UpdateFile","/passive /x:$UpdateTargetPath").WaitForExit()
}
# Copy the updated setup.exe and setup.rll files into the build
write-host "Merging Setup files"
[diagnostics.process]::start("robocopy","$UpdateTargetPath $SlipStreamTargetPath setup.exe").WaitForExit()
[diagnostics.process]::start("robocopy","$UpdateTargetPath $SlipStreamTargetPath setup.rll").WaitForExit()
# Merge files from the ia64 update path with the exception of Microsoft.SQL.Chainer.PackageData.dll
write-host "Merging ia64 files"
$UpdateTargetPathPlatform = $UpdateTargetPath + "\ia64"
$SlipStreamTargetPathPlatform = $SlipStreamTargetPath + "\ia64"
[diagnostics.process]::start("robocopy","$UpdateTargetPathPlatform $SlipStreamTargetPathPlatform /XF
Microsoft.SQL.Chainer.PackageData.dll").WaitForExit()
# Merge files from the x86 update path with the exception of Microsoft.SQL.Chainer.PackageData.dll
write-host "Merging x86 files"
$UpdateTargetPathPlatform = $UpdateTargetPath + "\x86"
$SlipStreamTargetPathPlatform = $SlipStreamTargetPath + "\x86"
# Merge files from the x64 update path with the exception of Microsoft.SQL.Chainer.PackageData.dll
write-host "Merging x64 files"
$UpdateTargetPathPlatform = $UpdateTargetPath + "\x64"
$SlipStreamTargetPathPlatform = $SlipStreamTargetPath + "\x64"
}
Write-Host "`nSQL Server Slipstream Script`n" -ForeGround "yellow"
Write-Host "*********************************************************" -ForeGround "yellow"
Write-Host "* This script will merge a SQL 2008 R2 Service Pack and *" -ForeGround "yellow"
Write-Host "* Cumulative Update into a single slipstreamed build *" -ForeGround "yellow"
Write-Host "*********************************************************" -ForeGround "yellow"
Write-Host "`n"
Do {
# Prompt the user for all source paths
Write-Host "Enter the SQL RTM Source Path" -ForeGround "green"
$SQLRTMPath = Get-ValidPath $path
Write-Host "Enter the SQL Service Pack Source Path" -ForeGround "green"
$SQLPCUPath = Get-ValidPath $path
Write-Host "Enter the SQL Cumulative Update Source Path" -ForeGround "green"
$SQLCUPath = Get-ValidPath $path
if ($debug -eq 1){Write-Host "`nProvided Source Paths" }
if ($debug -eq 1){Write-Host "SQLRTMPath: $SQLRTMPath"}
if ($debug -eq 1){Write-Host "SQLPCUPath: $SQLPCUPath"}
if ($debug -eq 1){Write-Host "SQLCUPath: $SQLCUPath"}
Write-Host "`n"
Write-Host "Enter the desired SQL Slipstream Target Path" -ForeGround "green"
Write-Host "(Note this path should not previously exist)" -ForeGround "green"
$SQLSSTargetPath = Read-Host "Enter the location (folder)"
# Present a confirmation menu to the end user
Write-Host "`nConfirm Source and Target Folders"
Write-Host "----------------------------------`n"
Write-Host "SQL RTM Source Path: `t`t`t$SQLRTMPath"
Write-Host "SQL Service Pack Source Path: `t`t$SQLPCUPath"
Write-Host "SQL Cumulative Update Source Path: `t$SQLCUPath"
Write-Host "SQL Target Slipstreamed Path: `t$SQLSSTargetPath"
$settings = $values
$Confirm = 0
$ConfirmTitle = ""
$ConfirmMessage = "`nAre these values correct?"
$yes = New-Object System.Management.Automation.Host.ChoiceDescription "&Yes", "Yes"
$no = New-Object System.Management.Automation.Host.ChoiceDescription "&No", "No"
$ConfirmOptions = [System.Management.Automation.Host.ChoiceDescription[]]($yes, $no)
$ConfirmResult = $host.ui.PromptForChoice($ConfirmTitle, $ConfirmMessage, $ConfirmOptions, 0)
switch ($ConfirmResult)
{
# Set the boolean flag if the user confirms "yes" (0 = yes, 1 = no)
0 {$Confirm = 1}
1 {$Confirm = 0}
}
} Until ($Confirm -ne 0)
Write-Host "`n"
# Verify if the target path provided exist if it does, exit gracefully.

# The destination path should not since we are using Copy-Item and this cmdlet
# does not handle duplicate paths and non-existent paths in the same manner
$PathExists = Test-Path $SQLSSTargetPath
if (! $PathExists )
{
Write-Host Path does not exist, creating $SQLSSTargetPath
Write-Host "`nCopying files, please be patient..."
Copy-Item $SQLRTMPath $SQLSSTargetPath -recurse
Write-Host "Completed."
write-host "`nMerging Service Pack Files...Please Wait"
Merge-SQLFiles $SQLPCUPath $SQLSSTargetPath "PCU"
write-host "Completed Service Pack Merge"
write-host "`nMerging Cumulative Update Files...Please Wait"
Merge-SQLFiles $SQLCUPath $SQLSSTargetPath "CU"
write-host "Completed Cumulative Update Merge"
write-host "`nUpdating DefaultSetup INI Files...Please Wait"
"`rPCUSOURCE=.\PCU" | Out-File -append $SQLSSTargetPath\x86\DefaultSetup.ini
"`rPCUSOURCE=.\PCU" | Out-File -append $SQLSSTargetPath\x64\DefaultSetup.ini
"`rPCUSOURCE=.\PCU" | Out-File -append $SQLSSTargetPath\ia64\DefaultSetup.ini
"`rCUSOURCE=.\CU" | Out-File -append $SQLSSTargetPath\x86\DefaultSetup.ini
"`rCUSOURCE=.\CU" | Out-File -append $SQLSSTargetPath\x64\DefaultSetup.ini
"`rCUSOURCE=.\CU" | Out-File -append $SQLSSTargetPath\ia64\DefaultSetup.ini
write-host "Update DefaultSetup INI Files complete"
}
Else
{
Write-Host "$SQLSSTargetPath Path exists"
Write-Host "Please specify a new path for the target, exiting..."
}
Component
Servers
13 Appendix D: High-Level Fast Track SQL Server Multi-Instance Configuration

SCSM Server 1
SCSM Server 2
Management
Server
Data
Warehouse
SSRS Files
Only Install
Console
SCSM Server 3
Web Portal
WSUS/WDS
Server
Portal
SharePoint
Console
SCVMM Server
SCOM Server
SCOM Server 2
Management
Server
Management
Server
Console
Console
Reporting
Server
SSRS Files
Only Install
App Controller
Server
Portal
SSAS Install
WSUS Console
Designer
SCODB
SCSMDB
Orchestrator
ServiceManager
SCSMDW
SCSMAS
CMDWDataMart
SCSM SSAS DB
SCSPFarm
SCVMMDB
SCOMDB
SCOMDW
SCOMASRS
SCACDB
OperationsManager
OperationsManagerDW
SSAS and SSRS

Installed
Remotely on
the SCOM
Reporting
Server
AppController
Low
Low
SharePoint_Config
VirtualManagerDB
OMDWDataMart
SharePoint_Content
DBs
WSUS DB
DWDataMart
WSS DBs
ReportServer
Optional Component
Database
Instance
Names
SCO
Management
Server
Runbook
Server
ReportServerTempDB
DWStagingAndConfig
DWSRepository
ReportServer
ReportServerTempDB
LUNs
Workload
Profile
Medium
Medium
High
High
Low
Low
Medium
Medium
LUN1: Data
LUN3: Data
LUN5: Data
LUN7: Data
LUN9: Data
LUN11: Data
LUN13: Data
LUN15: Data
LUN17: Data
LUN19: Quorum
LUN2: Logs
LUN4: Logs
LUN6: Logs
LUN8: Logs
LUN10: Logs
LUN12: Logs
LUN14: Logs
LUN16: Logs
LUN18: Logs
LUN20: MSDTC
SQL Cluster
Initial Installation Recommendations (2 node cluster)

Node 1
Node 2
Node 2
Node 2
Node 1
Node 1
Node 1
Node 1
Node 1
Node 2
Node 1
Node 1
Node 3
Node 3
Node 1
Node 2
Node 1
Node 1
Node 3
Node 3
Node 1
Standard Scale Recommendations (4 node cluster)

Node 1
Node 2
Node 2
Enhanced Scale Recommendations (6 node cluster)

Node 1
Node 4
Node 2
Figure 10: High-level Fast Track SQL Server multi-instance configuration

Microsoft Private Cloud Fast Track Reference Deployment Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microsoft Private Cloud Fast Track Reference Deployment Guide PDF

Uploaded by

Copyright:

Available Formats

Microsoft Private Cloud Fast Track

Reference Deployment Guide

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

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

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

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

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

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

Overview ......................................................................................................................................................................... 129

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

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

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

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

Overview ......................................................................................................................................................................... 193

Orchestrator ......................................................................................................... 282

Overview ......................................................................................................................................................................... 282

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

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

Overview ......................................................................................................................................................................... 329

Installation ...................................................................................................................................................................... 344

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

Overview ......................................................................................................................................................................... 351

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

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

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

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

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

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

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

Private Cloud Fast Track Program Description

Using this Document

Figure 1: Fabric management infrastructure: Pattern one

Figure 2: Fabric management infrastructure: Pattern two

Fabric Management Infrastructure Host and Guest Installation

Fabric management component virtual machine

Microsoft System Center 2012 - Virtual Machine

Virtual Machine Manager management server

Microsoft System Center 2012 - Operations Manager

Operations Manager reporting server

Operations Manager (additional management server)

Microsoft System Center 2012 - Service Manager

Service Manager (additional management server)

Service Manager Data Warehouse

Service Manager self-service portal

SQL Server LUN size is dependent on Solution scale.

Fabric management component virtual machine

Orchestrator Runbook Server

Microsoft System Center 2012 - App Controller

[Optional] Microsoft Windows Server Update Services

Runbook Server, Web Service, and Designer

Table 1: Fabric management infrastructure: Pattern one

Fabric management component virtual machine

Microsoft SQL Server

Virtual Machine Manager

Operations Manager management server

Operations Manager reporting server

Service Manager Data Warehouse

Service Manager self-service portal

[Optional] Windows Server Update Services and

Table 2: Fabric management infrastructure: Pattern two

SQL Server LUN size is dependent on Solution scale.

2.1.2 Create Fabric Management Virtual Guests

The New Virtual Machine Wizard will appear.