ESG Lab Validation Performance and Cost Efficiency of Intel and Microsoft Hyperconverged Infrastructure en US

Infrastructure-as-a-Service
Product Line Architecture

Deployment Guide
Published
Dec 2013
Version 3.0
Authors
Jeff Baker, Michael Withrow, Robert Larson, Joel Yoker, Rob Willis, Yuri Diogenes
Copyright information
This document is provided "as-is". Information and views expressed in this document, including URL and other
Internet website 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.
Microsoft, Active Directory, Hyper-V, Silverlight, Windows PowerShell, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other
trademarks are property of their respective owners.
© 2013 Microsoft Corporation. All rights reserved.
2 IaaS Product Line Architecture Deployment Guide

Contents
1 Introduction .................................................................................................................................................................................. 9
1.1 Scope .................................................................................................................................................................................... 9
1.2 Microsoft Private Cloud Fast Track ........................................................................................................................... 9
2 IaaS Product Line Architecture Overview ....................................................................................................................... 10
2.1 Fabric Design Patterns Overview ............................................................................................................................ 11
2.1.1 System Center Licensing ....................................................................................................................................... 12
3 Solution Overview ................................................................................................................................................................... 14
3.1 IaaS PLA System Center Infrastructure ................................................................................................................. 14
3.1.1 Design Pattern 1: Cloud Management Infrastructure ............................................................................... 14
3.1.2 Design Pattern 2: Scale-Out Cloud Management Infrastructure .......................................................... 16
4 Fabric Management ............................................................................................................................................................... 17
4.1 Fabric Management Host and Guest Installation ............................................................................................. 17
4.1.1 Fabric Management Guest Sizing ...................................................................................................................... 17
4.1.2 Create Fabric Management Virtual Guests .................................................................................................... 18
4.1.3 Create Required User Accounts and Security Groups ............................................................................... 25
5 SQL Server 2012 Failover Cluster Installation .............................................................................................................. 28
5.1 Overview ........................................................................................................................................................................... 28
5.2 Prerequisites .................................................................................................................................................................... 30
5.2.1 Accounts ...................................................................................................................................................................... 30
5.2.2 Groups .......................................................................................................................................................................... 30
5.3 Establish the SQL Server Guest Cluster ................................................................................................................ 30
5.4 Installation ....................................................................................................................................................................... 44
5.4.1 Install the SQL Server Named Instances on the Guest Cluster (Additional Nodes) ...................... 58
5.5 Post-Installation Tasks ................................................................................................................................................ 64
5.5.1 Configure Windows Firewall Settings for SQL Server Named Instances ........................................... 64
5.5.2 Assign Preferred Owners for SQL Server Instances in Failover Cluster Manager ........................... 78
6 Virtual Machine Manager..................................................................................................................................................... 83
6.1 Overview ........................................................................................................................................................................... 84
6.2 Prerequisites .................................................................................................................................................................... 84
6.2.1 Accounts ...................................................................................................................................................................... 84
6.2.2 Groups .......................................................................................................................................................................... 85
6.2.3 Install the Windows Assessment and Deployment Kit .............................................................................. 85
6.2.4 Install the Prerequisite Windows Server Roles and Features .................................................................. 88
6.2.5 Install the Command-Line Utilities in SQL Server 2012 with SP1 ......................................................... 93
IaaS Product Line Architecture Deployment Guide 3

6.2.6 Configure Shared VHDX files ............................................................................................................................ 100
6.2.7 Configure Shared Storage .................................................................................................................................. 101
6.2.8 Create the Failover Cluster ................................................................................................................................. 104
6.2.9 Create the Virtual Machine Manager Distributed Key Management Container in Active
Directory Domain Services ................................................................................................................................................ 106
6.3 Installation ..................................................................................................................................................................... 111
6.3.1 Install the Virtual Machine Manager Failover Cluster .............................................................................. 111
6.3.2 Creating Virtual Machine Manager Library Share on a Failover Cluster .......................................... 127
7 Operations Manager ............................................................................................................................................................ 138
7.1 Overview ......................................................................................................................................................................... 138
7.2 Prerequisites .................................................................................................................................................................. 139
7.2.1 Accounts .................................................................................................................................................................... 139
7.2.2 Groups ........................................................................................................................................................................ 140
7.2.3 Add .NET Framework 3.5 ..................................................................................................................................... 140
7.2.4 Install the SQL Server Reporting Services (Split Configuration) and Analysis Services .............. 142
7.2.5 Install Microsoft Report Viewer 2012 ............................................................................................................. 162
7.2.6 Configure Operations Manager SQL Server Prerequisites .................................................................... 166
7.3 Installation ..................................................................................................................................................................... 168
7.3.1 Install the Operations Manager Management Server ............................................................................. 168
7.3.2 Install the Operations Manager Reporting Server .................................................................................... 175
7.4 Post-Installation Tasks .............................................................................................................................................. 181
7.4.1 Register the Required Service Principal Names for the Operations Manager Management
Servers 181
7.4.2 Deploy and configure the operations Manager Agent on the Virtual Machine Manager
Management Server Nodes .............................................................................................................................................. 183
7.4.3 Install Operations Manager Console on the Virtual Machine Manager Management Server 187
7.4.4 Download and Import the Required Prerequisite Management Packs in Operations Manager
191
7.4.5 Perform Virtual Machine Manager and Operations Manager Integration ..................................... 195
8 Service Manager .................................................................................................................................................................... 199
8.1 Overview ......................................................................................................................................................................... 200
8.2 Prerequisites .................................................................................................................................................................. 201
8.2.1 Accounts .................................................................................................................................................................... 201
8.2.2 Groups ........................................................................................................................................................................ 202
8.2.3 Add .NET Framework 3.5 on all Server Manager Servers ....................................................................... 203
8.2.4 Install Microsoft Report Viewer 2008 SP1 Redistributable on the Management and Data
Warehouse Servers ............................................................................................................................................................... 207

8.2.5 Install SQL Server 2012 Native Client on the on the Management and Data Warehouse
Servers 209
8.2.6 Install SQL Server 2012 SP1 Analysis Management Objects ................................................................ 211
8.2.7 Install SQL Server Reporting Services (Split Configuration) on the Data Warehouse Server .. 214
8.2.8 Install SharePoint Foundation 2010 SP1 on the Self-Service Portal Server .................................... 227
8.2.9 Install .NET Framework 4 on the Self-Service Portal Server .................................................................. 237
8.2.10 Request and Install an SSL Certificate on the Self-Service Portal Server .................................... 238
8.2.11 Configure Service Manager Environmental Prerequisites ................................................................ 242
8.3 Installation ..................................................................................................................................................................... 245
8.3.1 Install the Management Server ........................................................................................................................ 245
8.3.2 Install the Data Warehouse Server .................................................................................................................. 255
8.3.3 Install the Service Manager Self-Service Portal Server............................................................................ 274
9 Orchestrator ............................................................................................................................................................................ 283
9.1 Overview ......................................................................................................................................................................... 284
9.2 Prerequisites .................................................................................................................................................................. 284
9.2.1 Accounts .................................................................................................................................................................... 284
9.2.2 Groups ........................................................................................................................................................................ 284
9.2.3 Add .NET Framework 3.5 and .NET Framework 4.5 with HTTP Activation ...................................... 285
9.2.4 Install Silverlight ..................................................................................................................................................... 289
9.3 Installation ..................................................................................................................................................................... 289
9.3.1 Install the Runbook Server ................................................................................................................................. 289
9.4 Post-Installation Tasks .............................................................................................................................................. 301
9.4.1 Install Microsoft Report Viewer 2012 ............................................................................................................. 301
9.4.2 Install the Operations Manager Console ...................................................................................................... 305
9.4.3 Install the Virtual Machine Manager Console ............................................................................................ 309
9.4.4 Download and Register the Orchestrator Integration Packs ................................................................ 312
9.4.5 Install the Orchestrator Integration Packs.................................................................................................... 316
10 App Controller ........................................................................................................................................................................ 322
10.1 Overview ......................................................................................................................................................................... 323
10.2 Prerequisites .................................................................................................................................................................. 323
10.2.1 Accounts ............................................................................................................................................................... 323
10.2.2 Groups ................................................................................................................................................................... 323
10.2.3 Add .NET Framework 3.5................................................................................................................................ 324
10.2.4 Install Silverlight ................................................................................................................................................ 327
10.2.5 Install the Virtual Machine Manager Console ....................................................................................... 328

10.3 Installation ..................................................................................................................................................................... 331
10.3.1 Install the App Controller Portal Server ................................................................................................... 331
11 Service Management Automation (SMA) .................................................................................................................... 338
11.1 Overview ......................................................................................................................................................................... 339
11.2 Prerequisites .................................................................................................................................................................. 339
11.2.1 Add Web Server Role (IIS) ............................................................................................................................. 339
11.3 Installation ..................................................................................................................................................................... 342
11.3.1 Install the Web Service ................................................................................................................................... 342
11.3.2 Install the Runbook Worker .......................................................................................................................... 348
11.3.3 Install the Powershell Automation Module ............................................................................................ 352
12 System Center Service Provider Foundation (SPF) 2012 R2 ................................................................................. 354
12.1 Overview ......................................................................................................................................................................... 355
12.2 Prerequisites .................................................................................................................................................................. 355
12.2.1 Accounts ............................................................................................................................................................... 355
12.2.2 Groups ................................................................................................................................................................... 356
12.2.3 Add Web Server Role (IIS) ............................................................................................................................. 357
12.2.4 Install Microsoft ASP.NET Model View Control (MVC) 4 ................................................................... 361
12.2.5 Install WCF ........................................................................................................................................................... 362
12.2.6 Install the Virtual Machine Manager Console ....................................................................................... 364
12.3 Installation ..................................................................................................................................................................... 367
12.3.1 Install System Center Service Provider Foundation 2012 R2 ........................................................... 367
13 Service Reporting .................................................................................................................................................................. 373
13.1 Overview ......................................................................................................................................................................... 374
13.2 Prerequisites .................................................................................................................................................................. 374
13.2.1 Accounts ............................................................................................................................................................... 374
13.2.2 Groups ................................................................................................................................................................... 374
13.2.3 Add .NET Framework 3.5................................................................................................................................ 375
13.2.4 Install SQL Server 2012 SP1 .......................................................................................................................... 377
13.3 Installation ..................................................................................................................................................................... 384
13.3.1 Install Service Reporting ................................................................................................................................ 384
14 Windows Azure Pack (WAP) .............................................................................................................................................. 390
14.1 Overview ......................................................................................................................................................................... 390
14.2 Prerequisites .................................................................................................................................................................. 391
14.2.1 Accounts ............................................................................................................................................................... 391
14.2.2 Groups ................................................................................................................................................................... 391

14.2.3 Configure SQL Instance Permissions ......................................................................................................... 391
14.2.4 Deploy .NET 4.5 Extended with ASP.NET ................................................................................................. 394
14.2.5 Deploy IIS Recommended Configuration ............................................................................................... 397
14.3 Installation ..................................................................................................................................................................... 399
14.3.1 Install First Windows Azure Pack Server .................................................................................................. 399
14.3.2 Install Second Windows Azure Pack Server............................................................................................ 405
15 Deployment Using PowerShell Deployment Toolkit ............................................................................................... 411
15.1 Obtaining PDT Files .................................................................................................................................................... 412
15.2 Creating Source Folder ............................................................................................................................................. 414
15.3 Creating Deployment Scenario File ..................................................................................................................... 418
15.3.1 Global Variables ................................................................................................................................................. 418
15.3.2 Components ....................................................................................................................................................... 419
15.3.3 Roles ....................................................................................................................................................................... 424
15.3.4 SQL.......................................................................................................................................................................... 428
15.3.5 VMs......................................................................................................................................................................... 431
15.4 Pre-Install Scripts ........................................................................................................................................................ 435
15.4.1 Pre-Install PowerShell Scripts ....................................................................................................................... 435
15.5 PostInstaller Scripts .................................................................................................................................................... 439
15.6 VMCreator Execution enabling Pre-Install scripts .......................................................................................... 440
15.7 Installer.ps1.................................................................................................................................................................... 441
15.8 Post Deployment Actions ........................................................................................................................................ 444
15.9 Pre-Built Scenario Files ............................................................................................................................................. 444
16 Appendix A: SQL Server Cluster Named Instance Worksheet ............................................................................. 445
17 Appendix B: Example VHDX Design............................................................................................................................... 446
18 Appendix C: iSCSI Implementation Steps .................................................................................................................... 447
19 Appendix D: PDT and SQL Availability Groups .......................................................................................................... 449
20 Appendix E: PDT Scenario Files ........................................................................................................................................ 453
20.1 PLA Example One ........................................................................................................................................................ 453
20.2 PLA Example Two ........................................................................................................................................................ 460
20.3 PLA Pre-Install Scripts: DC01 .................................................................................................................................. 468
20.4 PLA Pre-Install Scripts: DB01A ............................................................................................................................... 469
20.5 PLA Pre-Install Scripts: FS01 ................................................................................................................................... 470
20.6 PLA Pre-Install Scripts: PKI01 .................................................................................................................................. 471
20.7 PLA Pre-Install Scripts: VMM01A .......................................................................................................................... 471
20.8 PLA Pre-Install Scripts: WSUS01 ............................................................................................................................ 472

21 Appendix F: Windows Azure Pack Post Deployment Actions ............................................................................. 473
21.1 VMM Configuration ................................................................................................................................................... 473
21.2 SQL Tenant Database Configuration ................................................................................................................... 473
21.3 VM Cloud Gallery Items ............................................................................................................................................ 474

1 Introduction
The goal of the Infrastructure-as-a-Service (IaaS) product line architecture (PLA) is to help organizations
develop and implement private cloud infrastructures quickly while reducing complexity and risk. The IaaS
PLA provides a reference architecture that combines Microsoft® software, consolidated guidance, and
validated configurations with partner technology such as compute, network, and storage architectures, in
addition to value-added software components.
The private cloud model provides much of the efficiency and agility of cloud computing, with the
increased control and customization that are achieved through dedicated private resources. By
implementing private cloud configurations that align to the IaaS PLA, Microsoft and its hardware partners
can help provide organizations the control and the flexibility that are required to reap the potential
benefits of the private cloud.
The IaaS PLA utilizes the core capabilities of the Windows Server® operating system, Hyper-V®, Windows
Azure and System Center to deliver a private cloud infrastructure as a service offering. These are also key
software components that are used for every reference implementation.
1.1 Scope
The scope of this document is to provide customers with the necessary guidance to deploy a Microsoft
private cloud infrastructure in accordance with the IaaS PLA patterns that are identified for use with
Windows Server 2012 R2, Windows Azure and System Center 2012 R2. This document provides specific
guidance for deploying a management architecture for an overall private cloud solution.
The following guides provide information for developing a cloud management capability using System
Center 2012 R2 based on the designs within the IaaS PLA.
1.2 Microsoft Private Cloud Fast Track

The Microsoft Private Cloud Fast Track is a joint effort between Microsoft and its hardware partners to
deliver preconfigured virtualization and private cloud solutions. The Private Cloud Fast Track focuses on
the technologies and services in Windows Server 2012 R2 in addition to investments in System
Center 2012 R2.
The validated designs in the Private Cloud Fast Track are delivering a “best-of-breed solution” from our
hardware partners that drive Microsoft technologies, investments, and best practices. The Private Cloud
Fast Track has expanded the footprint, and it enables a broader choice with different architectures.
Validated designs from our hardware partners are included with Microsoft solutions in the Private Cloud
Fast Track. Please visit the Private Cloud Fast Track website for the most up-to-date information and to
access the validated solutions.

2 IaaS Product Line Architecture Overview
Microsoft Private Cloud programs have two main solutions as shown in Figure 1. The IaaS PLA focuses on
the open solutions model to service the enterprise and hosting service provider audiences.
Open solutions
SMB solutions
From 6 to 64 hosts
From 2 to 4 hosts
Up to 8,000 server
Up to 75 server virtual machines
virtual machines
Figure 1 Branches of the Microsoft Private Cloud
Each audience should use a reference architecture that defines the requirements that are necessary to
design, build, and deliver virtualization and private cloud solutions for small and medium
implementations. Figure 2 shows an example of these reference architectures.
 From 2 to 4  From 6 to 64
compute cluster compute
nodes cluster nodes
 Dedicated or  Dedicated 2-
integrated fabric node fabric-
management management
cluster
Server infrastructure Server infrastructure
Volume1 Volume1
Volume-n Volume-n
Cluster Shared Volumes (CSV2) Cluster Shared Volumes (CSV2)
Network infrastructure Network infrastructure
Volumes Volumes
Storage infrastructure Storage infrastructure
Small configuration Medium configuration
Figure 2 Examples of Small (SMB) and Medium (Open) reference architectures

Each reference architecture in the IaaS PLA combines concise guidance with validated configurations for
the compute, network, storage, and virtualization layers. Each architecture presents multiple design
patterns to enable the architecture, and each design pattern describes the minimum requirements for
each solution.
2.1 Fabric Design Patterns Overview

As previously described, Windows Server 2012 R2 utilizes innovative hardware capabilities and enables on
commodity hardware what were once considered advanced scenarios and capabilities. These capabilities
have been summarized into initial design patterns for the IaaS PLA. Identified patterns include the
following infrastructures:
1. Software-defined infrastructure
2. Non-converged infrastructure
3. Converged infrastructure
Each design pattern in the IaaS PLA Fabric architecture guide outlines the high-level architecture, provides
an overview of the scenario, identifies technical requirements, outlines all dependencies, and provides
guidelines as to how the architectural guidance applies to each deployment pattern. Each pattern also
includes an array of Fabric constructs in the categories of compute, network, storage, and virtualization,
which comprise the pattern.
Design Pattern #1: Software-defined Infrastructure

The Software-defined infrastructure design pattern supports clustered deployments for Hyper-V in
Windows Server 2012 R2. Continuous availability and transparent failover are delivered over a Scale-Out
File Server infrastructure and SMB shares by using a converged hardware configuration and native
Windows Server 2012 R2 capabilities. The Software-defined infrastructure pattern is expected to have
three variations:
1 Variation A: SMB Direct using Shared Serial Attached SCSI (SAS) and Storage Spaces
2 Variation B: SMB Direct using Storage Area Network (SAN)
3 Variation C: SMB3-enabled storage
Design Pattern #2: Non-converged Infrastructure

The non-converged pattern for Hyper-V in Windows Server 2012 R2 uses a standard clustered
deployment with non-converged storage (traditional SAN), networking, and a compute hardware
infrastructure. Storage network and network paths are isolated by using dedicated I/O adapters. Failover
and scalability are achieved on the storage network by using multipath I/O (MPIO). The TCP/IP network
uses NIC Teaming.
Design Pattern #3: Converged Infrastructure

In this context, converged infrastructure refers to sharing network topology between network and storage
network traffic. This typically implies Ethernet network devices and network controllers with particular
features to provide segregation, quality-of-service (performance), and scalability. The result is a network
fabric with less physical complexity, greater agility, and lower costs than those that are associated with
traditional fiber-based storage networks. These patterns are illustrated in Figure 3.
Teamed network
interfaces (LBFO) Teamed network
interfaces (LBFO)
Hyper-V cluster
Hyper-V cluster
RDMA
Volume1
Volume1
Volume-n
\\cno\share-1
Volume-n
Cluster Shared Volumes (CSV2)
\\cno\share-n
Cluster Shared Volumes (CSV2)
SMB Direct shares
(SMB3 over RDMA)
RDMA Hyper-V cluster Converged-

network
architecture
iSCSI
iSCSI
FC
FC
Clustered
file servers Volumes
Volumes
Storage
Spaces
SAS
SAS
SAN-based storage SAN-based storage

Shared SAS storage
1: Software Defined Infrastructure 2: Non-Converged 3: Converged

Figure 3 Fabric design patterns
2.1.1 System Center Licensing

The IaaS Fabric Management architecture utilizes System Center 2012 R2 Datacenter edition. For more
information, refer to System Center 2012 R2 on the Microsoft website.
The packaging and licensing of System Center 2012 R2 editions have been updated to simplify purchasing
and to reduce management requirements. System Center 2012 R2 editions are differentiated only by the
number of managed operating system environments. Two managed operating system environments are
provided per the Standard edition license and an unlimited number of operating system environments are
provided for the Datacenter edition. Running instances can exist in a physical operating system
environment or a virtual operating system environment.

For more information, see the following resources on the Microsoft Download Center:
 System Center 2012 R2 Licensing Datasheet
 Microsoft Private Cloud Licensing Datasheet
 Microsoft Volume Licensing Brief: Licensing Microsoft Server Products in Virtual Environments

3 Solution Overview
3.1 IaaS PLA System Center Infrastructure
Given that there are two deployment patterns for the Windows Azure Pack, two deployment models for
the Fabric Management infrastructure are provided. The following tables summarize the Fabric
Management virtual machine requirements by the System Center component that supports the model
chosen.
3.1.1 Design Pattern 1: Cloud Management Infrastructure
Pattern 1 leverages the Windows Azure Pack Minimal Distributed Deployment pattern and is provided
below. It provides the optional capability to scale out various components of the Fabric Management
infrastructure.

Node 1 Node 2
Guest Clustering
System Center System Center
Virtual Machine Manager Virtual Machine Manager
4 CPU, 8 GB RAM minimum
Microsoft SQL Server Microsoft SQL Server

Failover Cluster Node 1 Failover Cluster Node 2
16 CPU, 16 GB RAM minimum 16 CPU, 16 GB RAM minimum
Native Application HA
System Center Operations Manager System Center Operations Manager
Management Server Management Server
System Center Orchestrator Management System Center Orchestrator

Server, Runbook Server and Web Service Runbook Server and Web Service
Active Directory Federation Services Active Directory Federation Services

Load Balanced
Windows Azure Pack (Minimal Distributed) Windows Azure Pack (Minimal Distributed)
External Tier Server Supplemental External Tier
Windows Azure Pack (Minimal Distributed) Windows Azure Pack (Minimal Distributed)
Internal Tier Server Supplemental Internal Tier
System Center
Service Provider Foundation
Host Clustering
Service Management Automation Service Reporting
System Center
System Center App Controller Operations Manager Reporting Server
System Center Service Manager System Center Service Manager

Management Server Portal
System Center Service Manager Windows Deployment Services,

Data Warehouse Windows Server Update Services
Active Directory, DNS, DHCP

(Customer-provided)
Fabric Management Failover Cluster
Figure 4 Cloud Management infrastructure

3.1.2 Design Pattern 2: Scale-Out Cloud Management Infrastructure
Pattern 2 leverages the Windows Azure Pack Scale Distributed Deployment pattern and is provided below.
It focuses on scaling out various components of the Fabric Management infrastructure to provide load
balancing and scale.
Node 1 Node 2 Node 3 Node 4
Guest Clustering
Virtual Machine Manager Virtual Machine Manager
Microsoft SQL Server Microsoft SQL Server Microsoft SQL Server Microsoft SQL Server
Failover Cluster Node 1 Failover Cluster Node 2 Failover Cluster Node 3 Failover Cluster Node 4
16 CPU, 16 GB RAM minimum 16 CPU, 16 GB RAM minimum 16 CPU, 16 GB RAM minimum
Native Application HA
System Center Operations Manager
System Center Operations Manager
Management Server
Management Server 8 CPU, 16 GB RAM minimum
System Center Orchestrator System Center Orchestrator

Management Server, Runbook Server and Web Service
Runbook Server and Web Service 4 CPU, 8 GB RAM minimum
Active Directory Federation Services Active Directory Federation Services

Load Balanced
Windows Azure Pack (Scale Distributed) System Center System Center
Windows Azure Pack (Scale
Supplemental Tenant Site Service Provider Foundation Service Provider Foundation
Distributed) Tenant Site 2 CPU, 4 GB RAM minimum
Windows Azure Pack (Scale Windows Azure Pack (Scale Distributed) System Center System Center
Distributed) Tenant Auth Site Supplemental Tenant Auth Site Service Management Automation Service Management Automation
Windows Azure Pack (Scale Windows Azure Pack (Scale Distributed)

Distributed) Tenant Public API Supplemental Tenant Public API

Distributed) Tenant API Supplemental Tenant API

Distributed) Admin API Supplemental Admin API
Host Clustering
System Center System Center Service Manager
Windows Deployment Services, Data Warehouse System Center
Windows Server Update Services Service Reporting
2 CPU, 4 GB RAM minimum 8 CPU, 16 GB RAM minimum Operations Manager Reporting
System Center Service Manager
Management Server System Center Service Manager
4 CPU, 16 GB RAM minimum Portal
Windows Azure Pack

(Scale Distributed) Admin Site System Center App Controller
Windows Azure Pack

(Scale Distributed)
Admin (Windows) Auth Site
Active Directory, DNS, DHCP

(Customer-provided)
Fabric Management Failover Cluster
Figure 5 Scale-Out Cloud Management infrastructure

4 Fabric Management
4.1 Fabric Management Host and Guest Installation
4.1.1 Fabric Management Guest Sizing
To properly size fabric management host 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-to-four node Hyper-V failover cluster.
These virtual machines serve as the basis for fabric management operations. The following table
summarizes the fabric management virtual machine requirements by the System Center component that
supports the product or operating system role.
Component Roles Virtual RAM Virtual Hard

CPU (GB) Disk (GB)
SQL Server Cluster Node 1 16 16 60
Virtual Machine Manager Management Server 4 8 60
Virtual Machine Manager Management Server 4 8 60
App Controller Server 4 8 60
Operations Manager Management Server 8 16 60
Operations Manager Reporting Server 8 16 60
Orchestrator Server (Management Server, Runbook 4 8 60
Server and Web Service)
Service Reporting Server 4 16 60
Service Provider Foundation Server 2 4 60
Service Management Automation Server 2 4 60
Service Manager Management Server 4 16 60
Service Manager Portal Server 8 16 60
Service Manager Data Warehouse Server 8 16 60
Windows Deployment Services/Windows Server Update 2 4 60
Services
Data Protection Manager Server 2 48 60
Windows Azure Pack (Minimal) — External Tier Server 4 8 60
Windows Azure Pack (Minimal) — Internal Tier Server 8 16 60
Windows Azure Pack (Minimal) — Identity (ADFS) Server 2 4 60
Totals 110 248 1140
Table 1 Component roles

Optional Scale-Out Components Virtual RAM Virtual Hard
CPU (GB) Disk (GB)
Operations Manager Management Server 8 16 60
(supplemental)
Service Manager Management Server (supplemental) 4 16 60
Orchestrator Server (Runbook Server and Web Service) 2 8 60
(supplemental)
Service Provider Foundation Server (supplemental) 2 4 60
Service Management Automation Server (supplemental) 2 4 60
Data Protection Manager Server (supplemental) 2 48 60
Windows Azure Pack (Minimal) External Tier Server 4 8 60
Windows Azure Pack (Minimal) Internal Tier Server 8 16 60
Windows Azure Pack (Minimal) Identity (ADFS) Server 2 4 60
Table 2 Optional Scale-Out Component roles
4.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 customer automated
deployment solutions or a manual build of each virtual machine. The following table lists the VMs, and
their relevant details for this reference build:
Virtual Component Virtual RAM Virtual Hard

Machine CPU (GB) Disk (GB)
SQL01 SQL cluster node 1 16 16 60
SQL02 SQL cluster node 2 16 16 60
SCVMM01 VMM cluster node 1 4 8 60
SCVMM02 VMM cluster node 2 4 8 60
SCAC01 App Controller 4 8 60
SCOM01 Operations Manager management server 8 16 60
SCOM02 Operations Manager reporting server 8 16 60
SCO01 Orchestrator management, runbook and web service 4 8 60
SCSR01 Service Reporting 4 16 60
SCSPF01 Service Provider Foundation 2 4 60
SCSMA01 Service Management Automation 2 4 60
SCSM01 Service Manager management server 4 16 60
SCSM02 Service Manager data warehouse 8 16 60
SCSM03 Service Manager self-service portal 8 16 60
WAP01 Windows Azure Pack admin API 2 4 60
WAP02 Windows Azure Pack tenant API 2 4 60

Virtual Component Virtual RAM Virtual Hard
Machine CPU (GB) Disk (GB)
WAP03 Windows Azure Pack tenant public API 2 4 60
WAP04 Windows Azure Pack management portal for admins 2 4 60
WAP05 Windows Azure Pack management portal for tenants 2 4 60
WAP06 Windows Azure Pack admin authentication site 2 4 60
WAP07 Windows Azure Pack tenant authentication site 2 4 60
ADFS01 Active Directory Federation Services 2 4 60
In addition to the VMs and components listed in the table above it is expected that a domain controller,
WSUS/WDS server and Scale-out File server or other SMB 3 storage target will be available for the
solution to leverage. Though the reference deployment leverages SMB 3, any supported shared storage
solution may be leveraged for the hosts and virtual machines. For additional guidance on these topics you
may reference the following links:
 Install a New Windows Server 2012 Active Directory Forest

 Deploy Scale-Out File Server
 Deploy Windows Server Update Services
 Windows Deployment Services Getting Started Guide
 To complete a manual build of the reference deployment VMs perform the following steps on
the first fabric management host computer in the Fabric Management Cluster.
1. Open the Failover Cluster

Manager Microsoft
Management Console (MMC)
snap-in. Navigate to the
Services and applications
node, right-click Virtual
Machines…, and then click
New Virtual Machine….

2. Select the first node of the
management cluster.
3. Click OK
4. The New Virtual Machine

Wizard appears.
5. Click Next
Note: You may select the Do not

show this page again selection
box to skip this screen in the
future.

6. On the Specify Name and
Location page, provide the
following values:
 Name: Specify the name of
the virtual machine based
on the naming
conventions of your
organization.
 Location: Specify the
location of the SMB 3
share or cluster shared
volumes (CSV) on your
fabric management host
cluster.
7. Select the Store the virtual
machine in a different
location check box. In the
8. Click Next to continue.
9. On the Specify Generation

page leave the default
Generation 1 selected.
10. Click Next to continue

11. On the Assign Memory page,
provide the following value:
 Startup memory: Specify
the amount of memory in
megabytes (MB) required
for each virtual machine.
Note: Some System Center

components will post a warning if
virtual machine memory is below
8 GB. Each virtual machine must
have at least 2 GB of startup
random access memory (RAM) if
dynamic memory is enabled.
13. On the Configure Networking

page, provide the following
value:
 Connection: Specify the
virtual switch network
connection this system
should participate in from
the available connections
in the drop-down list.

15. On the Connect Virtual Hard
Disk page, select the Create a
virtual hard disk option and
provide the following values:
 Name: Specify the name of
the virtual hard disk
(VHDX). For simplicity, this
should match the name of
the virtual machine.
 Location: Accept the
default location of the SMB
3 share or 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 at
least 60 GB).
Note: Absent any automated

deployment process for the new
virtual machines, you can use an
existing VHDX in place of the new
VHDX that is created in this step.
The VHDX must have Windows
Server 2012 R2 (or Windows
Server 2008 R2 in the case of the
Service Manager Self-service Portal
VM) installed and have been
through the Sysprep process. This
will greatly speed up the
provisioning process for the
management virtual machines.

17. On the Installation Options
page, leave the default
selection of Install an
operating system later
selected
19. The Completing the New

Virtual Machine Wizard page
will display the selections you
made throughout the wizard.
20. Click Finish to create the
virtual machine.
Note: This operation must be

completed for each fabric
management virtual machine.
21. After completion, the virtual

machines will be available for
management in the Services
and applications node of the
Failover Cluster Manager.

4.1.3 Create Required User Accounts and Security Groups
Although each System Center 2012 R2 component installation section in this document outlines the
individual accounts and groups that are 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
IaaS PLA System Center 2012 R2 installation:
Component User account Suggested name Description

System Center Component FT-SCInstall Used to install all System Center 2012 R2
installation components.
account
(optional)
SQL Server SQL Server FT-SQL-Service Used as the service account for all instances of
instance service SQL Server® used in System Center.
account
Operations Management FT-SCOM-Action Used to carry out actions on monitored
Manager server action computers across a network connection.
account
Operations System Center FT-SCOM-SVC Provides one set of credentials that is used to
Manager Operations update and read information in the
Manager operational database. Operations Manager
configuration verifies that the credentials used for the
service and data System Center Operations Manager
access service configuration service and data access service
account accounts are assigned to the sdk_user role in
the operational database.
Operations Data warehouse FT-SCOM-DW Writes data from the management server to
Manager write account the reporting data warehouse and reads data
from the operational database.
Operations Data reader FT-SCOM-DR Used to define which account credentials
Manager account Microsoft SQL Server Reporting Services uses
to run queries against the Operations
Manager reporting data warehouse.
Virtual Machine Virtual Machine FT-VMM-SVC Used to run the Virtual Machine Manager
Manager Manager service service.
account
Service Manager Service Manager FT-SCSM-SVC Becomes the operational system account. It is
services account 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
Component User account Suggested name Description
a SQL Server logon in the Service Manager
database and that this account is a member of
the Builtin\Administrators group.
Service Manager Service Manager FT-SCSM-WF Used for all workflows and is a member of the
workflow Service Manager workflows user role.
account
Service Manager Service Manager FT-SCSM-SSRS Used by SQL Server Reporting Services (SSRS)
reporting to access the DWDataMart database to get
account data for reporting. The account becomes a
member of the db_datareader and the
reportuser database roles for the
DWDataMart database.
Service Manager Microsoft SQL FT-SCSM-OLAP Used by SQL Server Analysis Services (SSAS)
Server 2008 for Service Manager reports.
Analysis Services
account for
OLAP cubes
Service Manager Operations FT-SCSM-OMAlert Used for Service Manager Operations
Manager alert Manager alert connector operations.
connector
Service Manager Operations FT-SCSM-OMCI Used for Service Manager Operations
Manager CI Manager continuous integration (CI)
connector connector operations.
Service Manager Active Directory FT-SCSM-ADCI Used for Service Manager AD DS connector
connector operations.
Service Manager Virtual Machine FT-SCSM-VMMCI Used for Service Manager Virtual Machine
Manager CI manager connector operations.
connector
Service Manager Orchestrator CI FT-SCSM-OCI Used for System Center Orchestrator
connector connector operations.
Orchestrator Orchestrator FT-SCO-SVC Used to run the Orchestrator management
services account service, the Orchestrator runbook service, and
the Orchestrator runbook server monitor
service.
App Controller App Controller FT-SCAC-SVC Used to run all App Controller services.
services account
Service Provider Service Provider FT-SPF-SVC Used to run all SPF services.
Foundation (SPF) Foundation
service account
Windows Azure Windows Azure FT-WAP-SVC Used to run all WAP services.
Pack (WAP) Pack service
account
Table 2 Components and suggested user accounts

The following security groups are required in Active Directory for the System Center 2012 R2 installation:
Component Group Name Group notes

System System Center FT-SC-Admins Members are full administrators on all System
Center 2012 Administrators Center components.
SQL Server SQL Server FT-SQL-Admin Members are system administrators on all SQL
Administrators Server instances and local administrators on
all SQL Server nodes.
Operations Operations Manager FT-SCOM-Admins Members are administrators for the
Manager Administrators Operations Manager installation and hold the
Administrators role in Operations Manager.
Virtual Virtual Machine FT-SCVMM- Members are administrators for the Virtual
Machine Manager Admins Machine Manager installation and hold the
Manager Administrators Administrators role in Virtual Machine
Manager.
Virtual Virtual Machine FT-SCVMM- Members are delegated administrators for the
Machine Manager Delegated FabricAdmins Virtual Machine Manager installation and hold
Manager Administrators the Fabric Administrators role in Virtual
Machine Manager.
Virtual Virtual Machine FT-SCVMM- Members are Read-only administrators for the
Machine Manager Read Only ROAdmins Virtual Machine Manager installation and hold
Manager Admins the Read-only Administrators role in Virtual
Machine Manager.
Virtual Virtual Machine FT-SCVMM- Members are administrators for Virtual
Machine Manager Tenant TenantAdmins Machine Manager Self-Service users and hold
Manager Administrators the Tenant Administrators role in Virtual
Machine Manager.
Virtual Virtual Machine FT-VMM- Members are self-service users in the Virtual
Machine Manager Self-Service AppAdmins Machine Manager and hold the Application
Manager users Administrators role in Virtual Machine
Manager.
Orchestrator Orchestrator FT-SCO-Admins Members are administrators for the
Administrators Orchestrator installation.
Orchestrator Orchestrator FT-SCO-Operators Members gain access to Orchestrator through
Operators membership in the Orchestrator Operators
group. Any user account added to this group
is granted permission to use the Runbook
Designer and Deployment Manager tools.
Service Service Manager FT-SCSM-Admins Members are added to the Service Manager
Manager Admins Administrators user role and the Data
Warehouse Administrators user role.
Table 3 Components and names

5 SQL Server 2012 Failover Cluster
Installation
The SQL Server 2012 SP1 failover cluster installation process includes the high-level steps shown in Figure
5:
Install the SQL Add additional

SQL Server 2012 SP1 Perform Named Instances SQL Nodes for
Installation Prerequisites on Node 1 of the each named
Guest Cluster instance
Establish the
Guest Cluster
Figure 5 SQL Server 2012 failover cluster installation steps
5.1 Overview
There is a decision in the SQL Server architecture that must occur prior to deployment. There are multiple
valid SQL Server deployment scenarios, as follows.
 Architecture
o Physical servers
o Virtual machines
 Storage
o Shared VHDX
o iSCSI
o Fibre Channel
From these choices described, the standard IaaS PLA architecture recommends a minimum two-node
virtualized SQL Server guest cluster that is scaled accordingly for your deployment. The subsequent
sections of this document contain guidance for deploying a two-node cluster.
A high-level walkthrough on how to install SQL Server 2012 SP1 is provided below. The following
assumptions are made prior to installation:

 Two to four base virtual machines running Windows Server 2012 R2 have been provisioned for
SQL Server.
 17 Shared VHDX LUNs have been assigned to the virtual machine guests.
o One LUN for quorum (1 GB)
o Two LUNs for each fabric management component database (16 LUNs for all
components)
As discussed in the Infrastructure-as-a-Service Fabric Management Architecture Guide, virtual machines

running SQL Server are 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 is installed on the hosting System Center component server (for
example, the Operations Manager reporting server). However, this installation is “Files only,” and the SQL
Server Reporting Services configuration configures remote Reporting Services databases that are 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 Instance Components Collation Storage
Management Name Requirements
Component (Suggested)
Virtual Machine SCVMMDB Database Engine Latin1_General_100_CI_AS 2 LUNs
Manager
Windows Server
Update Services
Operations SCOMDB Database Engine, Latin1_General_100_CI_AS 2 LUNs
Manager Full-Text Search
Operations SCOMDW Database Engine, Latin1_General_100_CI_AS 2 LUNs
Manager Full-Text Search
Data Warehouse
Service Manager SCSMDB Database Engine, Latin1_General_100_CI_AS 2 LUNs
Full-Text Search
Service Manager SCSMDW Database Engine, Latin1_General_100_CI_AS 2 LUNs
Data Warehouse Full-Text Search
Service Manager SCSMAS Analysis Services Latin1_General_100_CI_AS 2 LUNs
Data Warehouse
Service Manager SCDB Database Engine Latin1_General_100_CI_AS 2 LUNs
Web Parts and
Portal
(SharePoint
Foundation)
Orchestrator
App Controller
Service Provider
Foundation

Services
Management
Automation
Windows Azure WAPDB Database Engine Latin1_General_100_CI_AS 2 LUNs
Pack
Table 4 Database instances and requirements
5.2 Prerequisites
The following environment prerequisites must be met before proceeding with installation.
5.2.1 Accounts
Verify that the following accounts have been created:
User name Purpose Permissions

<DOMAIN>\FT-SQL-SVC SQL Server service account Needs full administrator
permissions on all target SQL Server
systems and serves as the service
account for all instances. This
account must also be added to the
FT-SQL-Admins group and be a
sysadmin in all instances.
Table 5 SQL Server service account
5.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.
Table 6 Security group
5.3 Establish the SQL Server Guest Cluster

This section assumes that storage with the Shared VHDX is available and the customer is implementing a
SQL Server guest cluster. The following steps create the SQL Server guest cluster.
Notes
 The SQL Server guest cluster can also use Fibre Channel storage for clustering the virtual Fibre
Channel adapter, or iSCSI LUNs for Hyper-V in Windows Server 2012 R2.
 Although SMB shares can be used for SQL Server failover clusters, SQL Server Analysis Services is
a requirement for the IaaS PLA design, and it is not compatible with SMB shares.

The first step in installing SQL Server is to create the guest cluster by using Shared VHDX. To do this,
access to Shared VHDXs is required to allow each guest virtual machine in the cluster to access shared
storage. Prior to completing the following steps, the SMB 3.0 share should be provisioned and presented
to the nodes, but not yet made online, initialized, or formatted. The required storage for the IaaS PLA is as
follows:
 One VHDX for quorum (1 GB)

 Two VHDXs for each fabric management component instance (16 VHDXs for all products)
During the provisioning process, two to four virtual machines were built to the specifications outlined in
the Infrastructure-as-a-Service Fabric Management Architecture Guide to support SQL Server operations
for fabric management. After they are created, the Shared VHDXs 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.
1. Log on to the first node in the

SQL Server cluster as a user
with local Administrator rights.
2. Verify that the following
accounts and/or groups are
members of the local
Administrators group on the
first and second SQL Server
nodes:
 SQL Server service account
 SQL Server Admins group
 Virtual Machine Manager
computer accounts
 Service Manager OLAP
account
 Service Manager SSRS
account
 Service Manager workflow
account
 Service Manager service
account
 Operations Manager
action account
service account
 Perform the following steps on a Fabric Management cluster Hyper-V Host.

3. Open up Failover Cluster
Manager, click on Roles, right-
click on SQL01, select Settings.
4. Select SCSI Controller, click

Hard Drive, and click Add.
5. Select Virtual Hard Disk, and

click New.

6. On the Before You Begin page,
select Next.
7. On the Choose Disk Format

page, select Next.
8. On the Choose Disk Type page,

select Next.

9. On the Specify Name and
Location page, specify the
following:
Name: See Chart in Appendix
D:
Location: Location of SMB 3.0
Share where VHDXs will reside
Click Next.
10. On Configure Disk page,

specify the following:
Size: See Chart in Appendix D:
Click Next.
11. Click Finish.

12. Expand the newly added Hard
Drive, select Advanced
Features, and check Enable
virtual hard disk sharing.
13. Repeat steps 4-12 for each disk

represented in Appendix D:
14. Once all the disks have been

added, select Ok.

15. Open Settings for SQL02
16. Select SCSI Controller, select

Hard Drive, and click Add.
17. Select Virtual Hard Disk, and

select Browse.

18. Select the VHDX file, and select
Open.
19. Expand the newly added Hard

Drive, select Advanced
Features, and check Enable
virtual hard disk sharing.
20. Repeat for each VHDX in

Appendix D:
21. Click Ok.

22. Once all the disks have been
added, select Ok.
 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.
23. Within Computer

Management, navigate to the
Storage node and click Disk
Management. The iSCSI
LUNs should be visible, and
they should appear offline.
24. Right-click each disk and click

Online in the context menu.
This step must be completed
for each attached VHDX.
Note: Perform this action on
the first node of the SQL
cluster.

25. When each disk is online,
right-click the first disk and
click Initialize Disk in the
context menu.
Note: Perform this action on
the first node of the SQL
cluster.
26. The Initialize Disk page

appears. Verify that each
VHDX 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.
27. After they are initialized, on

the first node, right-click each
disk, and click New Simple
Volume… in the context
menu.
28. When the New Simple

Volume Wizard appears, click
Next to continue.

29. In the Specify Volume Size
text box, specify the
maximum disk space value in
the Simple volume size
in MB text box. Click Next to
continue.
30. In the Assign Drive Letter or

Path text box, select Assign
the following drive letter,
and specify a path in the text
box. Click Next to continue.
31. On the Format Partition

page, select Format this
volume with the following
settings. In the File system
drop-down list, select NTFS.
In the Allocation unit size
drop-down list, select
Default. Optionally, type a
descriptive label in the
Volume Label text box. Verify
that the Perform a quick
format check box is selected,
and click Next to format the
partition.

32. When the Completing the
New Simple Volume Wizard
page appears, click Finish to
complete the operation, and
then repeat the steps for each
disk.
Organizations should configure the interfaces according to their specific deployment characteristics. If
separate physical networks are used for VHDXs and inter-cluster private communications (also known as
heartbeat), you should reconnect the virtual network adapters appropriately.
When these steps are 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 and they need be identified.
Important: The installation of a SQL Server cluster creates computer accounts in AD DS, called cluster
name objects, for each instance in the cluster. By default, these objects are created in the default
Computers container of the target Active Directory domain. The account that is used to perform the
installation of the SQL Server cluster requires rights in AD DS to create the associated cluster name
objects for each SQL Server instance. This occurs as a standard part of the SQL Server installation process.
There are several approaches to mitigate this process, including using a higher privileged account for
installation, delegating rights in AD DS for the account that is 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 Failover Cluster Step-by-
Step Guide: Configuring Accounts in Active Directory.
 Perform the following steps on the first fabric management SQL Server node virtual machine with an
account that has local Administrator rights and permissions in AD DS to create the SQL Server CNOs.

1. Open an elevated Windows
PowerShell prompt within each guest
virtual machine (Node 1, Node 2, and
additional nodes such as Node 3 and
Node 4, if desired).
Note: The Failover Clustering feature
can be installed from an elevated
Windows PowerShell® prompt by
using the following command:
Add-WindowsFeature –Name
Failover-Clustering –
IncludeManagementTools
2. 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:
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 in Step 3.
Note: The validation stage of the
cluster creation can take up to an
hour to complete.
3. Navigate to %TEMP% and review the
Failover Cluster Validation Report
for errors and warnings. Perform any
required remediation and perform the
cluster tests described in Step 2 as
required.

4. The next step is to create the cluster.
From the same elevated Windows
PowerShell prompt, run the following
command to create the cluster:
New-Cluster -Node <Node1>, <Node2>,
<Node3>, <Node4> -Name
<ClusterName> -StaticAddress
<ClusterIPAddress>
If successful, the cluster name will be

displayed as output when the process
is complete.
Note: If you are using Dynamic Host

Configuration Protocol (DHCP) for the
cluster nodes, the –StaticAddress
parameter should not be used.
5. After the cluster creation is complete,

verify that the correct LUN was
assigned as the quorum disk. If the
incorrect disk was assigned, the
correct assignment can be made by
running the following Windows
PowerShell command:
Set-ClusterQuorum -
NodeAndDiskMajority
<ClusterQuorumDisk>
Note: For a three-node initial cluster

installation, this command is not
applicable.
6. Verify that all cluster networks are

assigned properly. Take care to
document which cluster network
names are assigned to public and
private network interfaces.

7. 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.
8. Note that as an optional step, cluster

disks can be renamed and provided
with more friendly versions to keep
track of which cluster disks are
associated with each System Center
SQL Instance.
5.4 Installation
Prior to installing 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 table provides an example.
Component Service Service Service App Virtual Operations Operations Windows

Manager Manager Manager Controller, Machine Manager Manager Azure Pack
management data analysis Orchestrat Manager data
server warehouse server or, SMA, warehouse
server SPF,
Microsoft
SharePoint
Services
farm, and
WSUS
SQL Server SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW WAPDB
Instance
Name
SQL Server SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW WAPDB
Instance

Component Service Service Service App Virtual Operations Operations Windows
Manager Manager Manager Controller, Machine Manager Manager Azure Pack
management data analysis Orchestrat Manager data
server warehouse server or, SMA, warehouse
server SPF,
Microsoft
SharePoint
Services
farm, and
WSUS
Failover
Cluster
Network
Name
SQL Server Cluster Disk 2 Cluster Disk Cluster Disk Cluster Disk Cluster Disk Cluster Disk Cluster Disk Cluster Disk
Instance 4 6 8 10 12 14 16
DATA
Cluster Disk
Resource
SQL Server Cluster Disk 3 Cluster Disk Cluster Cluster Disk Cluster Disk Cluster Disk Cluster Disk Cluster Disk
Instance 5 Disk 7 9 11 13 15 17
LOG Cluster
Disk
Resource
SQL Server E: G: I: K: M: O: Q: S:
Instance
Install Drive
SQL Server E: G: I: K: M: O: Q: S:
Instance
DATA Drive
SQL Server F: H: J: L: N: P: R: T:
Instance
LOG Drive
SQL Server F: H: J: L: N: P: R: T:
Instance
TEMPDB
Drive
Cluster SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server
Service (SCSMDB) (SCSMDW) (SCSMAS) (SCDB) (SCVMMDB (SCOMDB) (SCOMDW) (WAPDB)
Name )
Clustered 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
SQL Server
Instance IP
Address
Host Cluster 255.255.255.0 255.255.255 255.255.255 255.255.255 255.255.255 255.255.255 255.255.255 255.255.255
Public .0 .0 .0 .0 .0 .0 .0
Network
Interface
Subnet
Mask
Host Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster Cluster
Public Network 2 Network 2 Network 2 Network 2 Network 2 Network 2 Network 2 Network 2
Network
Interface
Name
SQL Server 10436 10437 10440 10433 10438 10434 10435 10439
Instance
Listening
TCP/IP Port
SQL Server Node2, Node4 Node2, Node2, Node1, Node1, Node3, Node3, Node1,
Instance Node4 Node4 Node4 Node4 Node4 Node4 Node3
Preferred
Owners
Table 7 Example System Center component database worksheet

The template provided in Appendix A of this document can help you capture this information for the
installation process. After you gather the necessary information, use the following steps to perform
installation.
Note: At this point during the installation, the first node of the SQL Server cluster must have ownership of
the LUNs.
 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.
1. The IaaS PLA installation requires

separate instances for each System
Center product. The instances
associated with these products are:
 SCSMDB (Service Manager database)
 SCSMDW (Service Manager data

warehouse)
 SCSMAS (Service Manager SQL

Analysis Services)
 SCDB (Shared App Controller,

Orchestrator, Service Provider
Foundation, Services Management
Automation, Service Manager self-
service portal, Microsoft
SharePoint® Foundation 2010
services, and WSUS database)
 SCVMMDB (Virtual Machine

Manager database and optional
WSUS database)
 SCOMDB (Operations Manager

database)
 SCOMDW (Operations Manager data

warehouse)
 WAPDB (Shared Windows Azure

Pack)
For multi-instance failover clusters,

installation of SQL Server 2012 SP1
must be performed once for each
instance. As such, these steps must
be performed for each instance
sequentially.

2. From the SQL Server 2012 SP1
installation media source, right-click
setup.exe and click Run as
administrator to begin setup. The
SQL Server Installation Center will
appear. Click Installation in the left
pane.
3. Click New SQL Server failover

cluster installation.
4. The SQL Server 2012 Setup Wizard

will appear. On the Setup Support
Rules page, 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.
5. If the View detailed report link is

selected, the following report is
available.

6. On the Product Key page, select the
Enter the product key option and
enter the associated product key in
the provided text box. Click Next to
continue.
Note: If you do not have a product

key, select the Specify a free edition
option, and then click Evaluation
from the drop-down list for a 180-
day evaluation period.
7. On the License Terms page, select

the I accept the license terms check
box. Select or clear the Send feature
usage data to Microsoft check box,
based on your organization’s
policies, and click Next to continue.
8. On the Product Updates page,

select the Include SQL Server
product updates check box, and
click Next to continue.

9. On the Install Setup Files page, click
Install Setup Files and allow the files
to install.
10. On the Setup Support Rules page,

verify that each rule shows a Passed
status. If any rule requires attention,
remediate the issue and rerun the
validation check. Note: Common
issues include MSDTC, MSCS, and
Windows Firewall warnings. The use
of MSDTC is not required for the
System Center 2012 R2 environment.
Click Next to continue.
11. On the Setup Role page, select SQL

Server Feature Installation, and

12. On the Feature Selection page, Database Engine Services (all instances except SCSMAS):
features for the various instances will
be selected.
Note: Not all features are supported
for failover cluster installations, so
the features for the IaaS PLA are
limited to the features in the
following list.
SQL Server with failover clusters
requires the selection of the SQL
Server Replication check box and
Full-Text Search check box with
every instance. The following
additional selections are required for
each instance:
 SCDB
o Database Engine Services
 SCOMDB
o Database Engine Services Analysis Services (SCSMAS instance only):
 SCOMDW
 SCSMAS
o Analysis Services
 SCSMDB
 SCSMDW
 SCVMMDB
 WAPDB
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.

13. On the Feature Rules page, click
Next to continue. Show details and
View detailed report can be viewed
if required.
14. On the Instance Configuration

page, make the following selections
(refer to the worksheet that you
created earlier):
 SQL Server Network Name –
Specify the cluster network name
of the failover cluster instance
being installed.
15. Select the Named instance option.
In the provided text 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.

17. On the Disk Space Requirements
page, verify that you have sufficient
disk space, and click Next to
continue.
18. On the Cluster Resource Group

page, in the SQL Server cluster
resource group name drop-down
list, accept the default value of SQL
Server (<InstanceName>). Click
Next to continue.
19. On the Cluster Disk Selection page,

refer to the worksheet that you
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.
Note: Cluster disks can be renamed
in Failover Cluster Manager to
friendly names as illustrated in this
dialog box.

20. On the Cluster Network
Configuration page, refer to the
worksheet that you created earlier to
assign the correct IP address for each
instance. Clear the DHCP check box
if you are using static addressing,
and enter the IP address in the
Address field text box.
22. On the Server Configuration page,

click the Service Accounts tab.
Specify the SQL Server Service
Account and an associated password
for the SQL Server Agent and SQL
Server Database Engine services.
Note: The SQL Server Service
Account will also be used for the SQL
Server Analysis Services service for
instances where these feature are
selected.

23. On the same Server Configuration
page, click the Collation tab. In the
Database Engine field set the value
to Latin1_General_100_CI_AS for all
instances, and click Next to continue.
24. On the Database Engine

Configuration page, click the
Account Provisioning tab. In the
Authentication Mode section, select
the Windows authentication mode
option. In the Specify SQL Server
administrators section, click the
Add Current User button to add the
current installation user. Click the
Add… button to select the previously
created SQL Server Admins group
and the SQL service account from the
object picker. You can also add any
application specific service accounts
and groups at this point or add them
later.
25. For the WAPDB instance you must
select Mixed Mode and supply a
password.

26. On the same Database Engine
Configuration page, 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 enter the proper
drive letter in the Data root
directory text 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 text 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,
Note: It may be necessary to relocate
the Temp DB files to a dedicated
LUN if performance is not adequate
using the two primary SQL LUNs.
27. In instances that contain Analysis
Services, on the Analysis Services
Configuration page, click the Server
Configuration tab. In the Specify
which users have administrative
permissions for Analysis Services
section, click Add Current User to
add the current installation user.
Click Add… to select the following
groups:
Service Manager instance:
 SQL Server Service account
 SM Admins group
 SM OLAP account

28. On the Analysis Services
Configuration page , click the Data
Directories tab, and use the
following configuration
Set the Data directory, and Temp
directory to the cluster disk that is
configured for the database files.
Set the Log file directory and the
Backup directory to the cluster disk
that is configured for the log files.
Do not change the folder structure
unless your organization has specific
standards for this.
29. On the Error Reporting page, select

or clear the Send Windows and SQL
Server Error Reports to Microsoft
or your corporate report server
check box, based on your
organization’s policies, and click
Next to continue.
30. On the Cluster Installation Rules

page, 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.

31. On the Ready to Install page, verify
all of the settings that were entered
during the setup process, and click
Install to begin the installation of the
SQL Server instance.
32. On the Installation Progress page,

the installation progress will be
displayed.
33. When the installation is complete,

the Complete page will appear. Click
Close.

34. Repeat these steps for each
associated SQL Server instance that is
required for the IaaS PLA fabric
management installation (eight
instances total).
35. Verify the installation by inspecting

the instances in Failover Cluster
Manager and in SQL Server 2012
Management Studio prior to moving
to the next step of installation.
5.4.1 Install the SQL Server Named Instances on the Guest Cluster (Additional Nodes)
After the creation of all required SQL Server instances on Node 1 is complete, additional nodes (Node 2 is
required and additional nodes are optional) can be added to each instance of the cluster. Follow these
steps to begin the installation of additional nodes of the cluster.
 Perform the following steps on each additional fabric management SQL Server node virtual
machine.

installation media source, right-
click setup.exe and click Run as
SQL Server Installation Center
will appear.

2. From the SQL Server Installation
Center, click the Add node to a
SQL Server failover cluster link.

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

5. On the Install Setup Files page,

click Install, and allow the support
files to install.

verify that each rule shows a
rerun the validation check.
Note: Common issues include
MSDTC, MSCS, and Windows
Firewall warnings. The use of
MSDTC is not required for the
System Center 2012 R2
environment.
7. On the Product Key page, select

the Enter the product key option
and enter the associated product
key in the provided text box. Click
Next to continue.

key, select the Specify a free
edition option, and select
Evaluation from the drop-down
list for a 180-day evaluation period.

the I accept the license terms
check box. Select or clear the Send
feature usage data to Microsoft,
policies, and click Next to
continue.

9. On the Cluster Node
Configuration page, select the
desired instance name from the
SQL Server instance name drop-
down list. Each instance will be
listed along with the nodes that are
currently assigned to each
instance. Click Next to continue.
10. On the Cluster Network

Configuration page, the network
configuration values are displayed
and set based on the existing
failover cluster instance values
from the first node. They cannot be
modified. Click Next to continue.
11. On the Service Accounts page,

specify the SQL Server Service
Account and an associated
password for the SQL Server
Agent and SQL Server Database
Engine services. Click Next to
continue.
Note: For the SCSMAS instance
only, an additional password must
be supplied for the SQL Server
Analysis Services service account.

12. On the Error Reporting page,
select or clear the Send Windows
and SQL Server Error Reports to
Microsoft or your corporate
report server check box, based on
your organization’s policies, and
13. On the Add Node Rules page,

rerun the validation check. Click
Next to continue.
14. On the Ready to Add Node page,

verify that all of the settings were
entered during the setup process,
and click Install to begin the
installation of the second SQL
Server node for the selected
instance.

15. The Add Node Progress screen
will display real-time progress for
the operation.

the Complete page will appear.
Click Close to complete the
installation of this SQL Server
database instance.
Repeat these steps for each

associated SQL Server instance that
is required for IaaS PLA fabric
management installation (seven
instances total).
17. Verify the installation by inspecting
the instances in Failover Cluster
Manager and in SQL Server 2012
Management Studio prior to
moving to the next step of
installation.

18. Once complete, install the latest
cumulative update for SQL Server
2012 SP1. Note that at the time of
writing, Cumulative Update 7
contains a compatibility update1 for
Windows Server 2012 R2 and
Windows 8.1 clients. Integration
with initial install can be achieved
using the following command line
during setup:
\Setup.exe /Action=Install
/UpdateSource=[PATH]
5.5 Post-Installation Tasks

When the installation is complete, the following tasks must be performed to complete the installation of
SQL Server.
5.5.1 Configure Windows Firewall Settings for SQL Server Named Instances
To support the multi-instance cluster, you must configure each SQL Server instance to use a specific
TCP/IP port for the database engine or analysis services. The default instance of the database engine uses
port 1433, and named instances use dynamic ports. To configure the firewall rules to allow access to each
named instance, static listening ports must be assigned.
Use the following procedure to configure the TCP/IP port. For more information, see Configure a Server to
Listen on a Specific TCP Port (SQL Server Configuration Manager) 2.
1
You cannot open the SQL Server Analysis Services properties dialog box in Windows 8.1 - http://support.microsoft.com/kb/2889492
2
Additional information for configuring the Windows Firewall to support SQL Server can be found at
http://technet.microsoft.com/library/cc646023.aspx and http://technet.microsoft.com/library/ms174937.aspx.

 Perform the following steps on each fabric management SQL Server node virtual machine.
1. Open an administrative Command

Prompt by searching for and selecting
CMD.EXE, then right-click and select
Run as Administrator. Within the
command prompt type the following
command:
netstat –b
The existing dynamic ports used by the
SQLSERVER.EXE sessions will appear.
2. On the first SQL Server node, open SQL

Configuration Manager.
3. In the SQL Server Configuration

Manager console pane, expand the SQL
Server Network Configuration node
and then click Protocols for the
<instance name>. Double-click TCP/IP
from the available protocol names to
observe its properties.

4. On the TCP/IP Properties page, click
the IP Addresses tab. Several IP
addresses appear in the format IP1, IP2,
up to IPAll. Each address will include
several values:
 Active - Indicates that the IP
address is active on the computer.
Not available for IPAll.
 Enabled - If the Listen All property
in TCP/IP Properties (on the
Protocol tab) is set to No, this
property indicates whether SQL
Server is listening on the IP address.
If the Listen All property in TCP/IP
Properties (on the Protocol tab) is
set to Yes, the property is
disregarded. Not available for IPAll.
 IP Address - View or change the IP
address used by this connection.
Lists the IP address that is used by
the computer and the IP loopback
address, 127.0.0.1. Not available for
IPAll. The IP address can be in IPv4
or IPv6 format.
 TCP Dynamic Ports - Blank if
dynamic ports are not enabled. To
use dynamic ports, set to 0. For
IPAll, displays the port number of
the dynamic port used.
 TCP Port - View or change the port
on which SQL Server listens. By
default, the default instance of
Database Engine listens on port
1433.
SQL Server Database Engine can listen
on multiple ports on the same IP
address. List the ports separated by
commas in the format 1433, 1500, 1501.
This field is limited to 2047 characters.
To configure a single IP address to listen
on multiple ports, the Listen All
parameter must also be set to No in the
TCP/IP Properties on the Protocols
tab.
For more information see How to: Configure the
Database Engine to Listen on Multiple TCP Ports.

5. Within the dialog box, browse to each IP
address section for the instance, and
delete the numerical value (0) from the
TCP Dynamic Ports field.
6. Scroll down to the IPAll section, and

delete the existing dynamic port value
from TCP Dynamic Ports property.
Assign a static port value under TCP
Port that is appropriate for the instance.
For this example, port 10437 was
specified. Click Apply to save the
changes.

7. A warning message will appear stating
that the settings will not take effect until
the SQL Server service has been
restarted for that instance.
8. Repeat these steps to set a static port SQL Instance Listening Port
for each database service instance. SCDB 10433
Reference the SQL Server settings table SCOMDB 10434
at the beginning of this section for the SCOMDW 10435
default values that are used in this
SCSMDB 10436
guide.
SCSMDW 10437
9. When all of the database instances are
SCVMMDB 10438
configured, close SQL Server
Configuration Manager and continue WAPDB 10439
to the next steps to change the SSAS SCSMAS 10440
instance listening port.
10. Open SQL Server Management Studio.
11. On the Connect to Server page, input

the connection values for the SSAS
instance.
Connect to connect to the instance.
NOTE: The default value is

SCSMAS\SCSMAS and needs to be
changed to SCSMAS

12. When you are connected to the instance
in SQL Management Studio, right-click
the SSAS instance and click Properties.
13. On the Analysis Server Properties

page, click the General tab, and in the
Name column, click Port. By default the
value will be set to “0” (zero) to specify a
dynamic port.

14. On the same page, in the Value column,
specify an appropriate static port value,
then click OK to save the changes.
15. A message will appear outlining that a

restart is required. Click OK and close
SQL Management Studio.
16. Open Failover Cluster Manager and

expand the Roles node.
17. To apply the new port settings, in

Failover Cluster Manager, select each
SQL Server instance (this must be
repeated per instance). In the Action
pane, select Stop Role to stop the
service for each instance. Restart each
instance by selecting Start Role from
the Action pane. Close the Failover
Cluster Manager console.

18. To verify that the port settings are
properly assigned, open Task Manager
and click the Services tab. Review the
list of services and note the PID
numbers for each of the SQL Services.
19. Open an administrative Command

Prompt by searching for and selecting
CMD.EXE, then right-click and select
Run as Administrator. Within the
command prompt, type the following
command: netstat –ano to export the
output to a CSV file.
20. Import the CSV file into Excel to then

format the data into a spreadsheet.
Locate the PIDs you documented from
the Task Manager previously. Then filter
on the state column to identify the
listening and blank values.
The resulting table should confirm that
all of the SQL instances are listening on
only the static ports assigned previously.
In addition to the static ports for each
instance, the 2382 TCP/UDP and 1434
TCP/UDP ports for the SQL Server
Browser are also listed. You must open
them in the firewall settings to support
the Analysis and Database Engine
instances.

21. When completed, configure the
Windows Firewall rule for the SQL Server
Browser. To perform this action, on each
node in the Windows Failover Cluster
that will host SQL Server instances, open
the Windows Firewall with Advanced
Security MMC console.
22. In the Windows Firewall with

Advanced Security MMC console, click
the Inbound Rules node, and click New
Rule… in the Action pane.
23. In the New Inbound Rule Wizard, on the

Rule Type page, select the Port button,
and click Next to continue.
24. On the Protocol and Ports page, select

the UDP button. Select the Specific
local ports button and type 1434 in the
text box. This enables access to the SQL
Server Browser for Database Engine
instances. Click Next to continue.

25. On the Action page, select the Allow
the connection button, and click Next
to continue.
26. On the Profile page, leave the Domain,

Private, and Public check boxes
selected, and click Next to continue.
Note: Allowing the Private and Public
network types enables this rule to
support other scenarios such as the SQL
Server AlwaysOn Multisite Failover
Cluster Instance for database availability
groups when replication may take place
on a network other than the domain
network.

27. Specify a name for the new rule, such as
SQL Server Browser Service for
Database Engine, and click Finish.
28. Note the new rule listed in under

Inbound Rules. Click New Rule again
from the Action pane to create the SQL
Browser Service for Analysis Server
rule.

the TCP and the Specific local ports
buttons. In the Specific local ports text
box, type 2382 to enable access to the
SQL Server Browser for the Analysis
Server instance.

30. Note the additional new rule listed in
the Inbound Rules pane.
31. Next, create and configure the inbound
Windows Firewall rule for each SQL
Server instance. In the same window,
click New Rule in the Action pane to
create the firewall rule for the first
named instance.
32. In the New Inbound Rule Wizard, on the

Rule Type page, select the Port button,

the TCP button. Select the Specific
local ports button and type the specific
local TCP/IP port to enable access to the
first named SQL Server instance. In this
example, to enable access to the SQL
Server instance, SCDB, the port specified
is 10433.

34. On the Action page, select the Allow
the connection button and click Next
to continue.
35. On the Profile page, leave the Domain,

Private, and Public check boxes
Note: Allowing the Private and Public
network types enables this rule to
support other scenarios such as the SQL
Server AlwaysOn Multisite Failover
Cluster Instance for database availability
groups when replication may take place
on a network other than the domain
network.

36. Specify a name for the new rule, such as
SQL Server Named Instance SCDB,
and click Finish.
37. Create an additional rule for each SQL

Server instance. This screenshot
provides an example for how the rule
set for the SQL Server architecture and
instances would be configured.
38. Alternatively, firewall rules can be New-NetFirewallRule -DisplayName "SQL Server Browser
created through Windows PowerShell Service for Database Engine" -LocalPort 1434 -Protocol
on the local server as shown in this UDP -Action Allow
example. Be sure to replace the port
number value with the correct value for
your environment.

39. These commands provide an example $RemoteSession = New-CimSession –ComputerName
for using Windows PowerShell to create SQL02
rules on remote nodes. New-NetFirewallRule -DisplayName "SQL Server Browser
Service for Database Engine" -LocalPort 1434 -Protocol
UDP -Action Allow –CimSession $RemoteSession
New-NetFirewallRule -DisplayName "SQL Server Browser
Service for Analysis Server" -LocalPort 2382 -Protocol
TCP -Action Allow –CimSession $RemoteSession
New-NetFirewallRule -DisplayName "SQL Server Named
Instance SCDB" -LocalPort 10433 -Protocol TCP -Action
Allow –CimSession $RemoteSession
Instance SCVMMDB" -LocalPort 10434 -Protocol TCP -
Action Allow –CimSession $RemoteSession
Instance SCOMDB" -LocalPort 10435 -Protocol TCP -
Instance SCOMDW" -LocalPort 10436 -Protocol TCP -
Instance SCSMDB" -LocalPort 10437 -Protocol TCP -
Instance SCSMDW" -LocalPort 10438 -Protocol TCP -
Instance WAPDB" -LocalPort 10439 -Protocol TCP -
Instance SCSMAS" -LocalPort 10440 -Protocol TCP -
5.5.2 Assign Preferred Owners for SQL Server Instances in Failover Cluster Manager
To support the proper distribution of SQL Server instances across the multi-instance SQL Server cluster,
you must configure failover clustering in Windows to assign preferred owners for each SQL Server
instance. The following steps are provided to assist with this configuration. Note that this change is only
applicable to SQL Server installations which use three or more nodes. The following section is provided as
an example and all installed SQL named instances would need to have similar configuration changes as
outlined. Refer to the planning table to determine appropriate node placement for each named instance.
If the SQL Server installation contains only two nodes, this section is not applicable.

 Perform the following steps on one fabric management SQL Server node virtual machine.
1. On any SQL Server cluster node, open

Failover Cluster Manager and
expand the Roles node.
2. During the installation of SQL Server,

all instances were installed on the first
failover cluster node and then added
to each additional node. By default
every failover cluster node is now a
Possible Owner and a Preferred
Owner of every SQL Server instance.
3. To better control failover behavior
and distribution of the instances, the
Preferred Owners list must be
modified and the owner node must be SQL Instance Preferred Owners
assigned by failing over the SQL
SCDB Node1, Node4
Server instance to that node. To start
this process, you need the list that you SCVMMDB Node1, Node4
created previously. WAPDB Node1, Node4
4. To perform this configuration, select SCOMDB Node2, Node4
the first SQL Server instance under the SCOMDW Node2, Node4
Roles node, then click the Any Node SCSMAS Node2, Node4
link next to Preferred Owners. SCSMDB Node3, Node4
SCSMDW Node3, Node4

5. On the SQL Server Properties page,
click the General tab, and select the
two preferred nodes for the instance.
The order will be automatically
adjusted when the process is
completed.
6. On the SQL Server Properties page,

click the Failover tab. In the Failback
section, select the Allow failback and
Immediately buttons. Click OK to
save the changes.

Note: The value for the Preferred
Owners link now displays a value of
User Settings.
7. Repeat this process for each SQL
Server instance.
8. After all instances have been

configured correctly for Preferred
Owners, you must initiate a planned
failover to balance the SQL Server
instances across nodes.
9. In Failover Cluster Manager, select
the roles for each of the SQL Server
instances that should not run on
Node1 (In this example, these are:
SCOMDB, SCOMDW, SCSMDB,
SCSMDW, SCSMAS). Right-click the
selection of SQL Server instances, click
Move, and then click Best Possible
Node.

10. When the moves are complete, all
instances should be distributed across
Node1, Node2, and Node 3. Node4 is
reserved as the passive node.
Note: With all nodes configured as
Possible Owners, failover to nodes
not listed as a Preferred Owner can
still occur when the preferred owners
are not available. However, with
failback enabled, the SQL Server
instances should always be reassigned
on their preferred node when
availability returns. This configuration
supports a primary dedicated passive
node plus two additional active or
passive nodes in the case of a failure
of two nodes. It is important to note
that failback only applies to automatic
failover events and not to user
initiated moves.

6 Virtual Machine Manager
The installation process for System Center 2012 R2 Virtual Machine Manager includes the high-level steps
shown in Figure 6:
Installation of
Perform System Center
Virtual Machine
Prerequisites 2012 R2 Virtual
Manager Installation
Machine Manager
Install the
Windows Install the Virtual
Assessment and Configure Shared
Machine Manager
Deployment Kit Storage
Failover Cluster
(ADK)
Install the Pre- Creating Virtual

requisite Windows Configure Failover Machine Manager
Server Roles and Clustering Library Share on a
Features Failover Cluster
Create the VMM

Install the SQL Distributed Key
Server 2012 SP1 Management
Command Line Container in
Utilities Active Directory
Configure iSCSI
Connections and
MPIO
Figure 6 System Center 2012 R2 Virtual Machine Manager installation process

6.1 Overview
This section provides a high-level walkthrough for deploying Virtual Machine Manager into the IaaS PLA
fabric management architecture. The following assumptions are made prior to the installation:
 Two base virtual machines running Windows Server 2012 R2 have been provisioned and
configured as a Windows Failover Cluster, which includes:
o The selected operating system installation type must be Full Installation.
o At least two shared storage LUNs or one shared storage LUN and a file share witness disk.
o A dedicated virtual network adapter for cluster communication.
o At least one dedicated virtual network adapter for iSCSI communications (if using iSCSI).
 The target virtual machines must have the Windows Assessment and Deployment Kit (ADK) for
Windows 8 and Windows Server 2012 R2 installed.
 The target virtual machine must have the Windows Server Update Services (WSUS) 4.0 console
installed (available in Windows Server 2012 R2).
o Virtual Machine Manager can use a WSUS root server or a downstream WSUS server.
Virtual Machine Manager does not support using a WSUS replica server. The WSUS server
can be dedicated to Virtual Machine Manager or it can be a WSUS server that is already in
use.
 A Microsoft SQL Server instance dedicated to Virtual Machine Manager as outlined in previous
steps must be available.
o The Virtual Machine Manager SQL Server instance must be case-insensitive (this is the
default in SQL Server 2012).
o The SQL Server name must not exceed 15 characters.
o 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 distributed key management container in
AD DS, or this container must already exist prior to running the Virtual Machine Manager setup.
6.2 Prerequisites
The following environment prerequisites must be met before proceeding.
6.2.1 Accounts
Verify that the following service accounts have been created:

<DOMAIN>\FT-VMM-SVC Virtual Machine Manager This account needs full
Service Account administrator permissions on the
Virtual Machine Manager server
virtual machine and runs the Virtual

Machine Manager service.
Table 8 Accounts
6.2.2 Groups
Verify that the following security groups are created:

<DOMAIN>\FT-SCVMM-Admins Global FT-VMM-SVC
<DOMAIN>\FT-SCVMM-FabricAdmins Global Virtual Machine Manager delegated
administrators
<DOMAIN>\FT-SCVMM-ROAdmins Global Virtual Machine Manager Read-only
administrators
<DOMAIN>\FT-SCVMM-TenantAdmins Global Virtual Machine Manager tenant
administrators who manage self-
service users
<DOMAIN>\FT-VMM-AppAdmins Global Virtual Machine Manager self-service
users
Table 9 Accounts
For more information, see Creating User Roles in VMM on Microsoft TechNet.
6.2.3 Install the Windows Assessment and Deployment Kit

The Virtual Machine Manager installation requires that the Windows Assessment and Deployment Kit
(ADK) is installed on the Virtual Machine Manager management server. To download this kit, see Windows
Assessment and Deployment Kit for Windows 8 in the Microsoft Download Center.
During installation, only the Deployment Tools and the Windows Pre-installation Environment features will
be selected. This installation also assumes the Virtual Machine Manager servers have Internet access. If that
is not the case, an offline installation can be performed. For more information for this installation option
and complete installation details, see Installing the Windows ADK.

The following steps outline how to install the Windows ADK on the Virtual Machine Manager
management server.
 Perform the following steps on both Virtual Machine Manager virtual machines.
1. From the Windows ADK installation

media source, right-click
adksetup.exe and select Run as
administrator to begin setup. If
prompted by User Account Control,
click Yes to allow the installation to
make changes to the computer.
2. The Assessment and Deployment Kit

Wizard appears On the Specify
Location page, accept the default
folder location of
%ProgramFiles%\Windows Kits\8.1\,
3. On the Join the Customer

Experience Improvement Program
(CEIP) page, choose to participate or
to not participate by providing
selected system information. Click
Next to continue.

4. On the License Agreement page,
click Accept to continue.
5. On the Select the features you

want to install page, select the
following option check boxes:
 Deployment Tools
 Windows Preinstallation
Environment (Windows PE)
6. Ensure all other option check boxes
are cleared. Click Install to begin the
installation.
7. After the installation is complete,

clear the Launch the Getting
Started Guide check box, and click
Close.

6.2.4 Install the Prerequisite Windows Server Roles and Features
The Virtual Machine Manager installation requires the WSUS Administration Tools to be installed on the
Virtual Machine Manager management servers. In addition, the MPIO and Failover Clustering Features
must be installed. Follow the steps below to install the pre-requisite roles and features on the Virtual
Machine Manager management servers.
 Perform the following steps on each Virtual Machine Manager virtual machine.
1. Open Server Manager and

navigate to the Dashboard node. In
the main pane, under Configure
this local server, click Add roles
and features.
2. The Add Roles and Features Wizard

appears. On the Before You Begin
page, click Next to continue.

3. On the Select Installation Type
page, you are presented with two
options:
 Role-based or feature-based
installation. This is a traditional
installation of roles and features
to enable discrete functionality
on the operating system.
 Remote Desktop Services
installation. This installs a
predetermined combination of
roles, features, and
configurations to support a
Remote Desktop (Session
Virtualization) or VDI scenario.
4. Select the Role-based or feature-
based installation button, and click
Next to continue.

5. On the Select destination server
page, you are presented with two
options:
 Select a server from the server
pool. This option allows you to
select a server from the
managed pool of systems
defined within Server Manager.
 Select a virtual hard disk. This
option allows for roles to be
installed to staged VHD files for
offline servicing purposes.
6. For this installation, select the
Select a server from the server
pool button, select the local server,
Note: Although many servers may
be presented in the Select a server
from the server pool option, only
one can be selected at a time for
role and feature installation
operations. To enable installations
across multiple hosts, the
configuration can be saved at the
end of the wizard and applied to
multiple systems by using the Server
Manager module for Windows
PowerShell.
7. On the Select Server Roles page,
do not make any additional
selections, and click Next to
continue.

8. On the Features page, select
Failover Clustering.
9. The Add features that are

required for Failover Clustering?
page appears. Select the Include
management tools (if applicable)
check box, then click the Add
Features button.

10. Next select the Multipath I/O
feature.
11. Next expand Remote Server

Administration Tools, then expand
Role Administration Tools, and
select the Windows Server Update
Services Tools features. Click Next
to continue.
12. On the Confirm installation

selections page, verify that the
Multipath I/O, Windows Server
Update Services Tools, and Failover
Clustering features are selected.
Ensure that Restart each
destination server automatically if
required is selected. This is
especially important for remote role
and feature installation. Click Install
to begin installation.
Note: The Export Configuration
Settings option is available as a link
on this page to export the options
selected to XML. When exported,
they can be used in conjunction
with the Server Manager module for
Windows PowerShell to automate
the installation of roles and features.

13. The Installation Progress page will
show the progress of the feature
installation. Click Close when the
installation process completes.
Note: Although this installation was

performed interactively, the installation
of roles and features can be automated
by using the Server Manager module for
Windows PowerShell.
6.2.5 Install the Command-Line Utilities in SQL Server 2012 with SP1
The Virtual Machine Manager installation requires that the command-line utilities and management tools
in SQL Server 2012 with SP1 are installed on the Virtual Machine Manager management server. Use the
following procedure to install the command-line utilities and management tools on the Virtual Machine
Manager management server.
1. From the SQL Server 2012 with

SP1 installation media source,
right-click setup.exe, and
select Run as administrator to
begin setup.

2. The SQL Server Installation
Center appears. In the left
pane, click Installation.
3. Click the New SQL Server

stand-alone installation or
add features to an existing
installation link.

4. The SQL Server 2012 Setup
Wizard appears. On the Setup
Support Rules page, verify
that each rule shows a Passed
status. If any rule requires
attention, remediate the issue
and rerun the validation check.
5. On the Product Key page,

select the Enter the product
key option and type the
associated product key in the
text 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 list for a 180-day
evaluation period.

6. On the License Terms page,
select the I accept the license
terms check box. Select or
clear the Send feature usage
data to Microsoft, based on
your organization’s policies,

leave the Include SQL Server
product updates, selection
selected, and click Next.
8. On the Install Setup Files

page, the update and
installation process will be
displayed.

9. On the Setup Support Rules
page, 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.
10. On the Setup Role page,

select the SQL Server Feature
Installation option, and click
Next to continue.

11. On the Feature Selection
page, select the Client Tools
Connectivity, Management
Tools – Basic and
Management Tools –
Complete check boxes, then
12. On the Installation Rules

page, 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.
13. On the Disk Space

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

14. on the Error Reporting page,
select or clear the Send
Windows and SQL Server
Error Reports to Microsoft or
your corporate report server
organization’s policies, and
15. On the Installation

Configuration Rules page,
Passed status. If any rule
requires attention, remediate
the issue and rerun the
validation check. Click Next to
continue.

16. On the Ready to Install page,
verify all of the settings that
were entered during the setup
process, and click Install to
begin the installation of the
17. When the installation

completes, the Complete page
will appear. Click Close to
complete the installation of
command-line tools in SQL
Server.
6.2.6 Configure Shared VHDX files

The Virtual Machine Manager Failover cluster installation requires a quorum model. That model can be a
disk witness or a file share witness. If a disk witness is selected for the quorum model, you need to
connect both Virtual Machine Manager management servers to shared storage. If a file share witness will
be used, you can skip this section.
This section assumes Shared VHDX files are in use. If using iSCSI LUNs, the iSCSI Initiator must be
configured on each virtual machine in SQL Server. If virtual Fibre Channel is used or if the cluster quorum
model is file share witness, you can skip this section.

6.2.7 Configure Shared Storage
If the quorum model used is file share witness, you can safely skip this section.
 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.
1. Within Server Manager, navigate

to the Storage node and expand
the Disk Management snap-in.
The LUN should be visible in the
snap-in, but should appear offline.
2. Right-click the disk and select

Online. Perform this action on a
single node of the cluster.
3. When the disk is online, right-click

and select Initialize Disk. Perform
this action on the first node of the
cluster.
4. The Initialize Disk page appears.

In the Select disks section, verify
that the check box is selected.
Verify that the MBR (Master Boot
Record) option is selected, and
click OK to initialize the disk.

5. After they are initialized, on the
first node, right-click the disk and
click New Simple Volume…
6. The New Simple Volume Wizard

appears. Click Next to continue.
7. On the Specify Volume Size page,

specify the maximum disk space
value in the Simple volume size
in MB text box. Click Next to
continue.

8. On the Assign Drive Letter or
Path page, select the Assign the
following drive letter option.
9. On the Format Partition page,

select the Format this volume
with the following settings
option. In the File system drop-
down list, click NTFS. In the
Allocation unit size drop-down
list, click Default. Optionally, type a
descriptive label in the Volume
label text box, for example,
“WitnessDisk.” Verify that the
Perform a quick format check
box is selected, and click Next to
format the partition.
10. When the Completing the New

Simple Volume Wizard page
appears, click Finish to complete
the operation.

6.2.8 Create the Failover Cluster
During the provisioning process, two virtual machines were built to the specifications outlined in the IaaS
PLA Fabric Management Architecture Guide to support a high availability Virtual Machine Manager for
fabric management. After the shared storage was created, it was configured within each virtual machine
to make them accessible to each candidate cluster node.
 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.
1. From an elevated command prompt in

Windows PowerShell, on the first SQL
Server node, run the following
commands to test the cluster
configuration:
Import-Module FailoverClusters
Test-Cluster <Node1>, <Node2>
If successful the Test-Cluster cmdlet

will display a validation report.
Note: Depending on the configuration,
the validation stage of the cluster
creation can take up to an hour to
complete.
2. Navigate to %TEMP% and review the

Failover Cluster Validation Report for
errors and warnings. Perform any
required remediation and run the
previous cluster test as required.

New-Cluster -Name SCVMMCLUSTER01 -Node
3. From the same elevated command
SCVMM01,SCVMM02 -StaticAddress 192.168.1.45
prompt in Windows PowerShell, run
the following command to create the
cluster:
New-Cluster -Node <Node1>, <Node2>
-Name <ClusterName> -StaticAddress
<ClusterIPAddress>
If successful, the cluster name will be

displayed as output when the process
is complete.
Note: If you are using DHCP for the
cluster nodes, do not use the
–StaticAddress parameter.
4. When the cluster creation is complete,
verify that the correct LUN was
assigned as the quorum disk. If the
incorrect disk was assigned, the correct
assignment can be made running the
following Windows PowerShell cmdlet:
Set-ClusterQuorum -NodeAndDiskMajority
<ClusterQuorumDisk>
5. Open Failover Cluster Manager.

6. In the Failover Cluster Manager
console, expand the Networks node.
Verify that all the cluster networks are
assigned properly. Take care to
document which cluster network name
is assigned to the public and private
network interfaces.
7. Close Failover Cluster Manager.
Note: The cluster networks can be

renamed to specify the network
connection.
6.2.9 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.
For more information, see Configuring Distributed Key Management in VMM.
Note: If Virtual Machine Manager will be deployed by using an account with rights to create containers in
AD DS, you can skip this step.
Use the following procedure to create an AD DS container to house the distributed key information. These
instructions assume that a domain controller running Windows Server 2008 R2 is in use. Similar steps
would be followed for other versions of Active Directory, including versions in Windows Server 2008,
Windows Server 2012, and Windows Server 2012 R2.

 Perform the following steps on a domain controller in the domain where Virtual Machine Manager
is to be installed.
1. Log on to a domain controller

with a user that has Domain
Admin privileges, and run
adsiedit.msc.
2. Right-click the ADSI Edit node,

and click Connect to…
3. 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 list,
and click OK.

4. On the ADSI Edit page, click
Default naming context
[<computer fully qualified domain
name>], expand <distinguished
name of domain>, right-click the
root node. Click New, and then
click Object…
5. On the Create Object page, click

container, and then click Next.
6. In the Value text box, type

VMMDKM, and then click Next.

7. Click Finish to create the
container object.
8. Within ADSI Edit, right-click the

new CN=VMMDKM object, and
then click Properties.

9. On the VMMDKM Properties
page, click the Security tab. Click
Add to add the VMM Service
account and VMM Admins group.
Grant the security principles Full
Control permissions.
10. Click OK three times and close

ADSI Edit.

6.3 Installation
6.3.1 Install the Virtual Machine Manager Failover Cluster
 Perform the following steps on the first Virtual Machine Manager virtual machine.
1. Log on to Virtual Machine Manager

virtual machine as a user with local
Administrator rights.
Verify that the following accounts or
groups are members of the local
Administrators group on the Virtual
Machine Manager virtual machine:
 Orchestrator service account
 Operations Manager action
account
Admins group
service account
2. From the Virtual Machine Manager

select Yes to allow the installation to

3. The Virtual Machine Manager
installation wizard will appear. Click
Install to begin the Virtual Machine
Manager server installation.
4. Attempting to select any feature will

cause a Microsoft System Center VMM
Setup message to appear.
5. Click Yes to switch to the high
availability Virtual Machine Manager
Setup Wizard.

6. On the Select features to install page,
verify that the VMM management
server installation option check box is
selected. When it is selected, the VMM
console installation option check box
is selected by default. Click Next to
continue.
7. On the Product registration

information page, type the following
information in the provided text boxes:
 Name – Specify the name of the
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.
9. On the Please read this license

agreement page, verify that the I have
read, understood and agree with the
terms of the license agreement
installation option check box is
selected and click Next to continue.

10. On the Join the Customer Experience
Improvement Program (CEIP) page,
select the option to participate or not
participate in the CEIP by providing
selected system information to
Microsoft. Click Next to continue.
11. On the Microsoft Update page, select

the option to allow or not allow Virtual
Machine Manager to use Microsoft
Update to check for and perform
Automatic Updates based on your
organization’s policies. Click Next to
continue.
12. On the Select installation location

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

Note: The Virtual Machine Manager Setup
Wizard automatically checks for
prerequisites. If for any reason a
prerequisite is not met, the setup UI will
notify you of the discrepancy. This
screenshot provides an example of a
discrepancy warning.
If the system passes the prerequisite check,
no screen will be displayed and the Setup
Wizard will proceed to the Database
configuration page.
13. On the Database configuration page,

type the following information in the
provided text boxes:
 Server name – Specify the name of
the SQL Server cluster created in
the steps above.
 Port - Specify the TCP port used
for the SQL Server, as configured in
the steps above.
14. Verify that the Use the following
credentials check box is clear. In the
Instance name drop-down list, select
the Virtual Machine Manager database
instance deployed earlier in the SQL
Server cluster.
15. In the Select an existing database or
create a new database option, select
New database, and accept the default
database name of VirtualManagerDB.

17. On the Cluster Configuration page, in
the Name field, provide a name for the
Virtual Machine Manager cluster
service.
If the cluster node you are installing is

configured with static IP addresses, you
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.
18. On the Configure service account

and distributed key management
page, in the Virtual Machine Manager
Service account section, select
Domain account. Enter the following
 User name and domain – Specify
the Virtual Machine Manager
service account identified in the
previous section in the following
format:
<DOMAIN>\<USERNAME>.
 Password – Specify the password
for the Virtual Machine Manager
service account identified earlier.
19. In the Distributed Key Management
section, select the Store my keys in
Active Directory check box. In the
provided text box, type the
distinguished name (DN) location
created earlier within Active Directory:
cn=VMMDKM,DC=domain,…

21. On the Port configuration page,
accept the default values in the
 Communication with the VMM
console: 8100
 Communication to agents on
hosts and library servers: 5985
 File transfers to agents on hosts
and library servers: 443
 Communication with Windows
Deployment Services: 8102
Preinstallation Environment
(Windows PE) agents: 8101
PE agent for time
synchronization: 8103
23. On the Library configuration page, no

options are available for a high
availability installation. The Library
must be configured separately and it
should point to a high availability file
share. Click Next to continue.

24. The Installation summary page will
appear and display the selections you
made in the Setup Wizard. Review the
options selected and click Install to
continue.
25. The wizard will display the progress

while installing features.
26. When the installation completes, the x

wizard will display the Setup
completed successfully page. Click
Close to complete the installation.

open the Virtual Machine Manager
console to verify that it installed
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 opens and
connects to the Virtual Machine
Manager instance installed.

 Perform the following steps on the second Virtual Machine Manager virtual machine.
1. Log on to the second Virtual

Machine Manager virtual machine as
a user with local Administrator rights.
Administrators group on the Virtual
Machine Manager virtual machine:
account
Admins group
service account
2. From the Virtual Machine Manager

setup.exe and select Run as
select Yes to allow the installation to
3. The Virtual Machine Manager

installation wizard will begin. Click
Install to begin the Virtual Machine
Manager server installation.

4. Attempting to select any feature will
cause the Microsoft System Center
VMM Setup message to appear.
5. Click Yes to switch to the high
availability 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.
6. On the Select features to install

page, verify that the VMM
management server installation
option check box is selected. When it
is selected, the Virtual Machine
Manager console installation option
check box is selected by default. Click
Next to continue.

information page, type the
following information in the provided
text boxes:
 Organization – Specify the name
Virtual Machine Manager. If no
key is provided, Virtual Machine
evaluation mode.
9. On the Please read this license

agreement page, verify that the I
have read, understood and agree
with the terms of the license
agreement check box is selected,
10. On the Join the Customer

Experience Improvement Program
(CEIP) page, select the option to
participate or not participate in the
CEIP by providing selected system
information to Microsoft. Click Next
to continue.

11. On the Microsoft Update page,
select the option to allow or not
allow Virtual Machine Manager to
use Microsoft Update to check for
and perform Automatic Updates,
policies. Click Next to continue.
12. On the Installation location page,

specify a location or accept the
default location of
Center 2012 R2\Virtual Machine
Manager for the installation. Click
Next to continue.
Note: The Setup Wizard automatically

checks for prerequisites. If for any reason
a prerequisite is not met, the setup UI will
notify you of the discrepancy. This
screenshot provides an example of a
discrepancy warning.
If the system passes the prerequisite
check, no screen will be displayed and
the Setup Wizard will proceed to the
Database configuration page.

13. On the Database configuration
page, all options are unavailable
when adding an additional node to
an existing Virtual Machine Manager
cluster.
15. On the Configure service account

and distributed key management
page, when deploying additional
nodes to a Virtual Machine Manager
cluster, all fields other than
Password are unavailable.
 Password – Specify the
password for the Virtual Machine
Manager service account
identified earlier.
17. On the Port configuration page,

when deploying additional nodes to
a Virtual Machine Manager cluster,
all fields are unavailable.

19. On the Library configuration page,
no options are available for a high
availability installation. The Library
must be configured separately and
should point to a high availability file
share. Click Next to continue.

appear and display the selections
you made during the Setup Wizard.
Review the options selected and click
Install to continue.


22. When the installation completes, the
wizard will display the Setup
completed successfully page. Click
Close to complete the installation.
23. When complete, open 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 opens
and connects to the Virtual
Machine Manager instance
installed.

24. In the Virtual Machine Manager
Console, select Fabric node, then
select Servers, and then select
Infrastructure, and then select VMM
Server.
 In the Role column, verify that
both cluster nodes are listed as
VMM Servers.
 In the Agent Status column,
verify that both nodes are listed
as Responding.
6.3.2 Creating Virtual Machine Manager Library Share on a Failover Cluster

In a high availability 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 on the Virtual Machine Manager cluster or its nodes.
In addition, creating a high availability Virtual Machine Manager Library is a recommended practice given
that the Virtual Machine Manager servers are high availability servers.
The Private Cloud IaaS PLA physical architecture makes no recommendations for where the Virtual
Machine Manager Library resides, other than that it should have the same high availability as other
aspects of the installation. Although any file server cluster will suffice, this document details the steps
required to host the Virtual Machine Manager Library on the SQL Server Cluster created in earlier portions
of this document as an example.
 Perform the following steps on each SQL Server virtual machine.
1. Open a Windows PowerShell session

as an administrator.

2. Run the following command once for
each SQL Server cluster node, and
change the ComputerName value
each time to that of a different SQL
Server cluster node.
Add-WindowsFeature -Name FS-FileServer
–ComputerName “SQL01”
3. Add an additional Shared VHDX, iSCSI

or Fibre Channel 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.
1. Within Failover Cluster Manager,

right-click Services and applications
and select Configure Role…
2. The High Availability Wizard

page, click Next to begin the wizard.

3. On the Select Role page, from the
available services and applications,
click File Server, and click Next to
continue.
4. On the File Server Type page, select

the File Server for general use
button, and click Next to continue.
5. On the Client Access Point page,

type a unique name for the clustered
file server in the Name text box.
Additionally, for static IP
configurations, select the appropriate
network and assign a unique IP
address to the service. Click Next to
continue.

6. On the Select Storage page, from the
available storage, select the cluster
disk that will be used for the Virtual
Machine Manager Library, and click
Next to continue.
7. On the Confirmation page, verify the

options selected, and click Next to
continue.
8. When complete, the Summary page

will show a report of the actions taken
by the wizard. Verify success, and click
Finish to complete the wizard.

Note: The high availability file server is
available as a service in Failover Cluster
Manager.
9. Within Failover Cluster Manager,

right-click the newly created file
server, and click Add File Share.
10. The New Share Wizard appears. On

the Select Profile page, select SMB
Share – Quick, and click Next to
continue.

11. On the Shared the server and path
for this share page, in the Server
pane, select the File Server cluster role
object name created earlier. In the
Share location pane, select the Select
by volume button and click Next to
continue.
12. On the Share Name page, type

“VMMLibrary” in the Share name
field, and then click Next to continue.
13. On the Other Settings page, select

only the Enable continuous
availability option, and then click
Next.

14. On the Permissions page, click
Customize Permissions…
15. Click the Permissions tab, and then

click Add. Add the following accounts
with NTFS Full Control permissions:
 VMM service account
 VMM Admins group
 Both VMM computer accounts
 VMM cluster name object
computer account
 VMM VCO computer account
16. Click OK to save the changes, and
click Next to continue the wizard.
17. On the Confirmation page, review

the settings, and then click Create.

18. On the Results page, verify that the
shared folder was provisioned
properly, and click Close.
 Perform the following steps on the Virtual Machine Manager virtual machine.

console, click the Library node. Click
the Home tab, and then click Add
Library Server from the ribbon.

2. The Add Library Server Wizard
appears. On the Enter Credentials
page, select the Enter a user name
and password option. In the User
name and Password text boxes, type
credentials that have administrative
rights over each of the target servers
where the new highly-available Virtual
Machine Manager Library share will
reside. Click Next to continue.
3. On the Select Library Servers page,

in the Domain text box, specify the
FQDN of the target domain. In the
Computer name text box, type the
name of the newly created highly-
available File Server cluster name
object, and click Add.
4. The cluster object will appear In the

Specified Servers pane. Click Next to
continue.

5. On the Add Library Shares page,
select the check box associated with
the VMMLibrary share created earlier.
Verify that the Add Default
Resources check box is selected, and
6. Review the Summary page, and click

Add Library Servers to continue.
7. The Jobs page will appear showing

the progress of the Add Library Server
action. Verify that all steps have
completed.

console, click Fabric Resources, and
then click Library Servers in the left
pane. Verify that all cluster nodes are
listed with the cluster object name
and that all servers are listed as
Responding under Agent Status.

console, click Library Servers in the
left pane, and verify that all of the
correct objects are created. When they
are verified, exit the console.

7 Operations Manager
The Operations Manager installation process includes the high-level steps shown in Figure 7.
3
Installation of
System Center Post Installation
Perform 2012 R2 Configuration of
Operations Manager
Prerequisites Operations Operations
Installation
Manager Database Manager
and Server Roles
Install the .NET Installation: Register the

Framework 3.5 Management Required Service
Feature Server Principal Names
Download and
Install SQL Server Deploy and
Import the
Reporting Services Installation: Configure the OM
Prerequisite
and Analysis Reporting Server Agent on VMM
Management
Services Servers
Packs in OM
(Optional) Install SQL

Install the Report
Install the Report Add an Additional Analysis
Viewer 2012 on
Viewer 2012 Management Management
the VMM Servers
Server Objects
Install the
Perform Virtual
Operations
Configure SQL Machine Manager
Manager Console
Server Prerequites and Operations
on the VMM
Manager
Management
Integration
Servers
Figure 7 Examples of reference architectures
7.1 Overview
This section provides a high-level walkthrough for deploying Operations Manager into the fabric
management architecture. The following assumptions are made:
 A base virtual machine running Windows Server 2012 R2 has been provisioned for Operations
Manager.
 A SQL Server 2012 SP1 cluster with dedicated instances has been established in previous steps.
o The default SQL Server collation settings are SQL_Latin1_General_CP1_CI_AS.
o SQL Server full text search is required.

 The installation will follow a remote SQL Server configuration with multiple SQL Server instances:
o SQL Server Reporting Services and SQL Server Analysis Services are installed in one SQL
instance locally on the Operations Manager reporting server. The reporting services
databases will run on the remote Operations Manager data warehouse SQL FCI and the
Analysis Services data will reside locally on the Operations manager reporting server.
o The Operations Manager databases on will run on a separate SQL Server instance in the
Fabric Management SQL Server cluster.
7.2 Prerequisites
7.2.1 Accounts
Verify that the following domain accounts have been created:

<DOMAIN>\FT-SCOM- System Center Configuration Domain account with local
SVC service and System Center Administrator permissions on all
Data Access service account Operations Manager management
(sdk_user role) servers and all SQL Server nodes, in
addition to System Admin rights on
all Operations Manager SQL Server
instances.
<DOMAIN>\FT-SCOM- Operations Manager action This account needs full Administrator
Action account permissions on all target systems
that will be managed by using the
action account.
<DOMAIN>\FT-SCOM-DR Operations Manager data Domain account with local
reader account Administrator permissions on all
Operations Manager management
servers and all SQL Server nodes.
<DOMAIN>\FT-SCOM- Operations Manager, data Domain account with local
DW warehouse write account Administrator permissions on all
servers and all SQL Server nodes.
Table 10 Account
Note: Specific requirements for Operations Manager are outlined in the Before You Begin section of
Deploying System Center 2012 R2 - Operations Manager in the TechNet Library.

7.2.2 Groups
Verify that the following security groups have been created.

<DOMAIN>\FT-SCOM- Global <DOMAIN>\FT-SCOM-Action
ADMINS <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-SCOM- Global Operations Manager Operators privileged
Operators admin accounts
<DOMAIN>\FT-SCOM- Global Operations Manager Advanced Operators
AdvOperators privileged admin accounts
Table 111 Groups
7.2.3 Add .NET Framework 3.5
The Operations Manager installation requires that .NET Framework 3.5 is enabled to support installation.
Use the following procedure to enable .NET Framework 3.5.
 Perform the following steps on all Operations Manager virtual machines.

this local server, select Add roles
and features.

2. The Add Roles and Features
Wizard appears. On the Before You
Begin page, click Server Selection
in the left pane. (Do not click Next.)

page, select the Select a server
from the server pool button, select
the local server and then click
Features in the left pane. (Do not
click Next.)
4. On the Select Features page, in the

Features pane. Select the .NET
Framework 3.5 Features and .NET
Framework 3.5 (includes .NET 2.0
and 3.0) check boxes only. Leave all
other check boxes clear. Click Next
to continue.

selections page, verify that.NET
Framework 3.5 Features is listed.
Ensure that the Restart each
required is not selected. Click Install
Note: The Export configuration
settings option is available as a link
they can be used in conjunction with
the Server Manager module for

Windows PowerShell.
7.2.4 Install the SQL Server Reporting Services (Split Configuration) and Analysis
Services
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 following procedure to install SQL Server Reporting Services and SQL
Server Analysis Services to support the Operations Manager reporting features.

 Perform the following steps on only the Operations Manager reporting server virtual machine.
1. Log on to the Operations Manager

reporting server virtual machine as a
user with local Admin rights.
Operations Manager reporting server
virtual machine:
account
 Operations Manager Admins
group
 Operations configuration
service and data access
service account
2. From the SQL Server 2012 installation

media source, right-click setup.exe
and select Run as administrator to
begin setup.

3. The SQL Server Installation Center
will appear. Click Installation in the
left pane.

Center, click the New SQL Server
stand-alone installation or add
features to an existing installation
link.


6. Note: If the View detailed report
link is selected, the following report
is available.

Enter the product key option, and
type the associated product key in
continue.

option, and select Evaluation from
the drop-down list for a 180-day
evaluation period.


10. On the Install Setup Files page, click

Install and allow the support files to
install.

validation check. Note: Common
issues include MSDTC, MSCS, and
Windows Firewall warnings. The use
of MSDTC is not required for the
System Center 2012 R2 environment.

12. On the Setup Role page, select the
SQL Server Feature Installation
13. On the Feature Selection page,

select the following check boxes:
 Analysis Services
 Reporting Services - Native
 Management Tools – Basic
 Management Tools – Complete
When all selections are made, click
Next to continue.

14. On the Installation Rules page,
continue.

page, select the Named instance
option. In the provided text box,
specify the name of the instance
being installed.
 Instance ID – Select the Named
instance option and specify
SCOMASRS in the provided text
box. Verify that the Instance ID is
listed as SCOMASRS in the
associated text box. Keep the
default Instance root directory
value, and then click Next to
continue.
Server.
Note: A post-installation
configuration process will occur to
configure the reporting server
database to leverage the Operations
Manager data warehouse SQL Server
instance database engine.

continue.

click the Service Accounts tab. For
SQL Server Reporting Services, in
the Account Name drop-down list,
select the NETWORK SERVICE
account. Click Next to continue. For
SQL Server Analysis Service
account name and password values,
provide the domain SQL service
account used previously for the SQL
Failover Cluster instances. For this
example the account is Contoso\FT-
SQL-SVC. Click Next.

Configuration page, add the
necessary accounts to the
administrative users list. Click Next.
For the reference architecture

deployment the accounts are:
 FT-SQL-Admins
 FT-SQL-SVC
 FT-VMM-SVC
 FT-SCOM-Action
 FT-SCOM-Admins
 FT-SCOM-DR
 FT-SCOM-DW

19. On the Reporting Services
Install only option.
Note: Other options should not be
available because the database
engine was not selected as a feature
for installation. Click Next to
continue.

Next to continue.
21. On the Installation Configuration


23. When complete, the Complete page

will appear. Click Close to complete
the installation of this SQL Server
database instance.
24. Browse to the folder where the latest

Cumulative Update for SQL Server
2012 SP1. Right click on the
extracted executable and select Run
as administrator from the menu.

25. On the SQL Server 2012 update
page, review the rules report and
then click Next.

27. On the Select Features page,

confirm that all features are selected
and then click Next.

28. On the Check Files In Use page, click
Next.
29. On the Ready to update page, click

Update.
30. The Update Progress page will

display until installation completes.

31. When the update is complete click
Close.
32. Open SQL Server Management

Studio and connect to Analysis
Services at
ServerName\InstanceName.

33. By default, named instances will use
dynamic ports. For better
compatibility with firewalls, the
instance port should be set to static.
To do so, right-click the SQL Server
Analysis Services instance and click
Properties.
34. On the Properties page, click the

General tab. Scroll down to the Port
value in the Name column. Click the
value and change the value of 0
(zero) to 2383 or a port value of your
choice. Click OK to continue.
35. When prompted by the Restart

Required message, click OK.

36. Within SQL Server Management
Studio, in Object Explorer, right-
click the SSAS instance, and click
Restart.
37. On the confirmation screen, click Yes.

Close SQL Server Management
Studio.
38. By default, the Windows Firewall will

not allow traffic for SQL Server
services or for the SSRS Web Service.
You need to create firewall
exceptions if the Windows Firewall is
enabled.
To do so, open an administrative
session of Windows PowerShell.

39. Run the following commands to
create the needed firewall rules:
New-NetFirewallRule -DisplayName "SQL
Analysis Services Browser Service" -
Protocol TCP -LocalPort 2382
Analysis Services SCOMASRS Instance" -
Protocol TCP -LocalPort 2383
Reporting Services" -Protocol TCP -
LocalPort 80
Adjust the display names and ports
based on organizational
requirements.
40. Open the Windows Firewall with

Advanced Security MMC console to
verify the results. When verified,
close the MMC console.
41. To verify that SQL Server Reporting

Services installed properly, on the
Start menu, click the Reporting
Services Configuration Manager
tile.
42. The Reporting Services

Configuration Connection page will
appear.
 In the Server Name text box,
specify the name of the
Operations Manager server.
 In the Report Server Instance
text box, select the default value
SCOMASRS from the drop-down
list.
Click Connect.

Configuration Manager will appear.
44. Click Database in the left pane, and

then in the Current Report Server
Database section, click the Change
Database button.
45. The Reporting Services Database

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

46. In the Database Server section,
specify the following values:
 Server Name – Specify the name
of the remote SQL Server
failover cluster name and the
database instance name
created for the Operations
Manager installation. For the
reference architecture
deployment the name is
SCOMDW\SCOMDW
 Authentication Type – Specify
Current User – Integrated
Security from the drop-down
list.
47. Click the Test Connection button to
verify the credentials and database
connectivity. When verified, click
Next to continue.
48. 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 list.
 Report Server Mode – Select
the Native option.

50. In the Credentials section, for
Authentication Type, select Service
Credentials from the drop-down list.
The User name value should show
NT Authority\Network Service.
51. In the Summary section, review the

selections that you made, and click
Next to create the SQL Server
Reporting Services database on the
remote SQL Server cluster instance
supporting the Operations Manager
Data Warehouse.
52. The Progress and Finish section will

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

53. In Reporting Services
Configuration Manager, the
Database option will now display the
database and report server database
credentials that you specified in the
wizard.

Configuration Manager, click Web
Service URL in the left pane. Specify
the following values:
 In the Report Server Web
Service Virtual Directory
section, set the Virtual Directory
value to
ReportServer_SCOMASRS in
the provided text box. This
default value must be used for
VMM and SCOM integration to
function properly.
Service Site Identification
section, set the following values:
o IP Address – Select All
Assigned from the drop-
down list.
o TCP Port – Specify the
desired TCP Port (the
default is 80).
o SSL Certificate – Select
the available certificate
or choose the default of
(Not Selected).
55. Click the Apply button to save the
settings and create the Web Service
URL.

Configuration Manager, click
Report Manager URL in the left
pane. Specify the following value:
 In the Report Manager Site
Identification section, set the
Virtual Directory value to
Reports_SCOMASRS in the
provided text box. This default
value must be used for VMM
and SCOM integration to
function properly.
57. Click the Apply button to save the
settings and create the Report
Manager URL.
Note: To test the URL directory from the Operations Manager server, Internet Explorer Enhanced
Security Configuration (ESC) needs to be temporarily disabled.
58. Connect to the Report Manager URL

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

within a web browser to verify the
SQL Server Reporting Services web
service is operating properly.
60. Close the Reporting Server

7.2.5 Install Microsoft Report Viewer 2012
The Operations Manager installation requires that Microsoft Report Viewer 2012 is installed prior to
installing Operations Manager. Use the following procedure to install Microsoft Report Viewer 2012.
 Perform the following steps on the Operations Manager management server virtual machine.

1. From the installation media source,
double-click SQLSysClrTypes.msi to
begin setup.
2. On the Welcome to the

Installation… page click Next.

select the I accept the license terms
check box and click Next to continue.

4. On the Ready to Install the Program
page click Install.
5. On the Completing the Microsoft

System…Installation page click
Finish.

right-click ReportViewer.exe and
select Run as administrator to begin
setup.

7. On the Microsoft Report Viewer 2012
Runtime setup wizard Welcome to
the Installation… page click Next.

select the I accept the license terms
check box and click Next to continue.

page click Install.

Report Viewer 2012 Runtime
Installation page click Finish.
7.2.6 Configure Operations Manager SQL Server Prerequisites
The following prerequisite steps must be completed prior to the installation of Operations Manager roles.
Note: Specific requirements for Operations Manager are outlined in the Before You Begin section of
Deploying System Center 2012 R2 - Operations Manager in the TechNet Library.
 Perform the following steps on the Operations Manager management server virtual machines.
1. Log on to the Operations Manager

virtual machine as a user with local
Admin rights.
Operations Manager virtual machine:
account
 Operations Manager Admins
group
 Operations configuration
service and data access
service account
 VMM service account

 Perform the following step on an Active Directory domain controller in the target environment.
1. In the domain where Operations

Manager will be installed, verify that
the Operations Manager computer
account and the groups outlined in
the previous table are members of
the SCOM Admins group that you
created earlier.
 Perform the following steps on the primary SQL Server cluster node.
1. Using Administrative credentials, log

on to the first SQL Server and open
SQL Server 2012 Management
Studio. Connect to the Operations
Manager SQL Server instance by
using the values specified earlier.
Expand Security, right-click Logins,
and click New Login…
2. In the Login – New dialog box, select
the Operations Manager Admins
group created earlier as the new
Login name.

3. While still in the Login – New dialog
box, click the Server Roles page.
Select the sysadmin role, and click
OK to create and add this login to
the sysadmin role of the instance.
7.3 Installation
7.3.1 Install the Operations Manager Management Server
The following steps must be completed to install and configure the Operations Manager database and
server roles.
 Perform the following steps on the first Operations Manager management server virtual machine.
1. From the Operations Manager

setup.exe, and select Run as
administrator to begin setup.

2. The Operations Manager Setup
Wizard will appear. Select the
Download the latest updates…
option and then Click Install to begin
the Operations Manager management
server installation.

page, verify that the Management
server and Operations console check
boxes are selected. Click Next to
continue.

default location of
%ProgramFiles%\System
Center 2012\Operations Manager for
the installation. Click Next to
continue.

5. The wizard will verify that all system
prerequisites are met. If any
prerequisites are not met, they will be
displayed on the Proceed with Setup
page. After you verify that the
prerequisites are met, click Next to
continue.
6. On the Specify an installation option

page, select the Create the first
Management server in a new
management group option, and type
a unique name in the Management
group name text box. Note that this
name must be unique across System
Center products.
7. On the Please read the license terms

page, verify that the I have read,
understood and agree with the
terms of the license agreement

8. On the Configure the operational
database page, specify the following
information in the provided text
boxes:
 Server name and instance name
– Specify the name of the SQL
Server cluster network name
(cluster name object) and the
database instance created for the
Operations Manager installation.
 SQL Server port – Specify the TCP
port used for SQL Server
connectivity. Port 1433 is the
default; however, this may be
different based on instance
requirements outlined earlier. As
long as the browser service is
enabled the correct port will be
detected even if 1433 is selected
as the port value for setup.
Alternatively you may simply
provide the correct port
assignment. For the reference
deployment the correct static port
is 10434.
 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.3 The
following values can be used as a
general guideline:
o Up to 500 agents: 12 GB
 Data file folder – Specify the
drive letter associated in the SQL
3 For general guidance for database sizing, see System Center 2012 - Operations Manager Component Add – On.

Server cluster data files for the
Operations Manager database.
This should be detected by the
setup process however it should
be cross-checked with the
worksheet identified earlier.
 Log file folder – Specify the drive
letter associated in the SQL Server
cluster for the log files for the
Operations Manager database.
This should be detected by the
setup process however it should
10. On the Configure the Data

warehouse database page, specify
the following information in the
 Server name and instance name
– Specify the name of the SQL
Server cluster network name
(cluster name object) and the
Operations Manager installation.
 SQL Server port – Specify the TCP
port used for SQL Server
connectivity. Port 1433 is the
default; however, this may be
different based on instance
requirements outlined earlier. As
long as the browser service is
enabled the correct port will be
detected even if 1433 is selected
as the port value for setup.
Alternatively you may simply
provide the correct port
assignment. For the reference
deployment the correct static port
is 10435.

data warehouse database. In most
cases the default value of
OperationsManagerDW should be
used.
 Database size (MB) – Specify the
initial database size. The following
values can be used as a general
guideline:
o Up to 1000
agents: 720 GB
 Data file folder – specify the drive
letter associated in the SQL
Service cluster for the log files for
the Operations Manager data
warehouse database. This should
 Log file folder – Specify the drive
letter associated in the SQL Server
cluster for the log files for the
Operations Manager data
warehouse database. This should
12. On the Configure Operations

Manager accounts page, for each of
the following accounts, specify the
appropriate Domain Account name
and password:
 Management server action
account (reference deployment:
FT-SCOM-Action)
 System Center Configuration
service and System Center Data
Access service (reference
deployment: FT-SCOM-SVC)
 Data reader account (reference
deployment: FT-SCOM-DR)
 Data writer account (reference

deployment: FT-SCOM-DW)
Domain Accounts are specified as

<DOMAIN>\<USERNAME.
13. When completed, click Next to
continue.
14. The Help Improve System

Center 2012 - Operations Manager
page provides options for
participating in various product
feedback mechanisms. These include:
 Customer Experience
Improvement Program
 Error Reporting
15. Select the appropriate option based
on your organization’s policies, and
16. The Installation Summary page will

made during the Setup Wizard. Review
the options selected, and click Install
to continue.
Note: Ensure that you set the
database sizes appropriately for your
particular deployment. Both databases
will be fully allocated at deployment
time as operations manager databases
are note set to auto grow by default.


wizard will display the Setup is
complete page. Verify that the Start
the Operations console when the
wizard closes check box is selected,
and click Close to complete the
installation.
19. The Operations Manager console will

open. Validate the installation by
reviewing the configuration and
ensure that the console operates
properly.
7.3.2 Install the Operations Manager Reporting Server

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

click setup.exe and select Run as
2. The Operations Manager

installation wizard will begin. Click
Install to begin the Operations
Manager management server
installation.

page, verify that the Reporting
server check box is selected. Click
Next to continue.
4. On the Select installation

location page, specify a location
or accept the default location of
%ProgramFiles%\System
Center 2012\Operations Manager
for the installation. Click Next to
continue.
5. The wizard will verify that all

system prerequisites are met. If
any prerequisites are not met,
they will be displayed on the
Proceed with Setup page. After
you verify that the prerequisites
are met, click Next to continue.

6. On the Please read the license
terms page, select the I have
read, understood and agree
with the license terms check box,
7. On the Specify a Management

server page, type the name of the
previously installed management
server in the Management server
name text box. Click Next to
continue.
8. On the SQL Server instance for

reporting services page, select
the SQL Server instance that hosts
the local SQL Server Reporting
Services and SQL Server Analysis
Services from the drop-down list
created earlier. Click Next to
continue.

9. On the Configure Operations
Manager accounts page, specify
whether the following account is a
Local System or Domain
Account by using the available
options:
 Data reader account
If the use of a Domain Account is

specified, enter the user account
information as
<DOMAIN>\<USERNAME>, and
enter the appropriate password.
11. The Help Improve Operations

Manager 2012 page provides
options for participating in various
product feedback mechanisms.
This includes:
 Operational Data Reporting
(ODR)
12. Select the appropriate option
policies, and click Next to
continue.
13. On the Microsoft Update page,

select the appropriate update
setting for your organization and
click Next.

14. The Installation Summary page
will appear and display the
selections made during the
installation wizard. Review the
options selected, and click Install
to continue.
15. The wizard will display the

progress while installing features.
16. When the installation completes,

the wizard will display the Setup
is complete page. Verify that the
Launch Microsoft Update when
the wizard closes check box is
selected, and click Close to
complete the installation.

17. 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.
After the installation is complete, the following tasks must be performed to complete Operations
Manager and Virtual Machine Manager integration.
7.4.1 Register the Required Service Principal Names for the Operations Manager
Management Servers
The following steps must be performed on a domain controller or on one of the Operations Manager
servers by using a domain admin account or an account with permissions to create service principal
names.
 Perform the following steps on a domain controller in the domain where Operations Manager is
installed.
1. The Operations Manager Health Service

service principal names should be set
automatically by the management
server’s computer account. To confirm
that the service principal names are set
correctly, open an administrative
command prompt and run the following
command:
SETSPN –L <DOMAIN>\<SERVERNAME>
Where <DOMAIN> is the Active
Directory domain name where the
Operations Manager management server

is installed and <SERVERNAME> is the
management server.
2. The Data Access Service account runs

under a domain user account context,
and it is not able to create the
appropriate service principal names in
Active Directory. The following command
must be run from a domain admin
account or from an account with
delegated permissions to user objects.
To set the service principal name, run the
following commands from an administrative
command prompt:
SETSPN.exe –A
MSOMSdkSvc/<ManagementServerFQDN>
<domain>\<SDKServiceAccount>
SETSPN.exe –A
MSOMSdkSvc/<ManagementServerNetBIOS
> <domain>\<SDKServiceAccount>
Where <ManagementServerFQDN> is the
management server and
<SDKServiceAccount> is the name of the
Operations Manager service account.
If there is more than one management server
being deployed, these commands must be
run for each management server.
3. When complete, the service principal
name s can be confirmed with the
following command:
SETSPN –L
<DOMAIN>\<SDKServiceAccount>

7.4.2 Deploy and configure the operations Manager Agent on the Virtual Machine
Manager Management Server Nodes
 Perform the following steps on the Operations Manager management server virtual machine.
1. From the Operations Console

Monitoring or Administration view,
select the Configure computers and
devices to manage task item link.
2. The Computer and Device Management

Wizard will appear. On the Discovery
Type page, select Windows computers
from the available options, and click
Next to continue.

3. On the Auto or Advanced? page, select
the Advanced discovery option, and
4. On the Discovery Method page, under

Browse for, or type-in computer
names, input the names of both Virtual
Machine Manager servers. Click Next to
continue.

5. On the Administrator Account page, If
the account your logged in with is a local
administrator on the VMM server then
leave the default selection in place, if not
then select the Other user account
option, and provide the credentials that
are 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, and click
Discover to continue.
6. On the Select Objects to Manage page,

review the Discovery Results. In the
Select the devices you want to manage
dialog box, select the Virtual Machine
Manager server. From the Management
Mode drop-down list, select Agent, and

7. On the Summary page, 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.
8. On the Agent Management Task Status

page, verify that the agent installation
completes successfully, and then click
Close to complete the operation.
9. The next step is to enable the Operations

Manager agent that is deployed on the
Virtual Machine Manager management
server to be a proxy agent.
10. In the Operations Manager console,
navigate to the Administration
workspace, expand the Device
Management node, and select the
Agent Managed view.
Note: It can take a few minutes for the
Health State to transition from Not
Monitored to Healthy.

11. In the Agent Managed pane, select the
agent that is associated with the Virtual
Machine Manager management server,
and click Properties in the task pane.
12. On the Agent Properties page, 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, then click OK to
save the changes. Repeat this process for
each Virtual Machine Manager agent-
managed system.
Note: Once hosts are brought in VMM to
be managed they must also have the
SCOM agent installed for VMM to and
SCOM integration to continue
functioning properly.
7.4.3 Install Operations Manager Console on the Virtual Machine Manager

Management Server


2. The Operations Manager installation
wizard will begin. Click Install to begin
the Operations Manager console
installation.

verify that the Operations console
check box is selected. Click Next to
continue.

default location of
%ProgramFiles%\System Center 2012
R2\Operations Manager for the
installation. Click Next to continue.

continue.

license terms check box is selected, and

Manager page provides options for
 Customer Experience Improvement
Program
 Error Reporting
8. Select the appropriate option based on
your organization’s policies, and click
Next to continue.

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

while performing the installation.
11. After the installation completes, the

complete page. Verify that the start the
Management console when the
wizard closes check box is selected, and
click Close to complete the installation.

reviewing the configuration and ensure
that the console operates properly.
7.4.4 Download and Import the Required Prerequisite Management Packs in

Operations Manager
 Perform the following steps on the Operations Manager virtual machine.

navigate to the Administration pane
and click the Management Packs node.
In the Actions pane, click Import
Management Packs…

2. On the Select Management Packs page,
click the Add button, and click Add from
catalog… in the drop-down list.

3. On the Select Management Packs from
Catalog page, find and add the following
management packs (in this order):
 Windows Server Internet Information
Services Library
 Windows Server Internet Information
Services 2003
 Windows Server 2008 Internet
Information Services 7
 Windows Server 2008 Operating System
(Discovery)
 Windows Server Operating System
Library
 SQL Server Core Library
4. After they are added, click OK to
continue.
Note that additional management packs may

be required to satisfy dependencies or
monitoring requirements for the target
infrastructure.

5. On the Select Management Packs page,
click Install to import the selected
management packs.
6. The management packs will download

into Operations Manager. When
complete, verify that the imports were
successful, and click Close to exit the
Import Management Packs Wizard.

navigate to the Administration
workspace and verify that the previously
selected management packs are installed.

7.4.5 Perform Virtual Machine Manager and Operations Manager Integration
After all prerequisite configurations and installations are performed, the integration of Virtual Machine
Manager and Operations Manager can be completed.
 Perform the following steps on the Virtual Machine Manager virtual machine.
1. In the Virtual Machine Manager console,

navigate to Settings pane, and select
System Center Settings. Right-click
Operations Manager Server, and select
Properties.
2. The Add Operations Manager Wizard

will appear. On the Introduction page,
verify that the prerequisites have been
met, and click Next to continue.
3. On the Connection to Operations

Manager page:
 Type the FQDN of the Operations
Manager server in the Server name
text box.
 Select Use the VMM server service
account.
 Select Enable Performance and
Resource Optimization (PRO).
 Select Enable maintenance mode
integration with Operations
Manager.

4. On the Connection to VMM page, specify
the Virtual Machine Manager service
account credentials in the User name and
Password text boxes, and click Next to
continue.
5. On the Summary page, verify the options

selected, and click Finish to begin the
Operations Manager integration process.
6. The Jobs pane will appear. Before moving

forward, wait for the job to complete
successfully.

7. In the Virtual Machine Manager console,
navigate back to Settings. Click System
Center Settings, and double-click
Operations Manager Server. The
Operations Manager Settings page will
appear.
In the Details pane, click the Test PRO
button.
8. As part of the test, the PRO page appears

and displays a diagnostics alert.
9. After a few minutes it will be possible to

determine that the PRO test completed by
navigating to the Jobs pane and verify
that the PRO jobs completed successfully.
10. On the Management Packs page, verify

that all Virtual Machine Manager
Management Packs were successfully
installed.

11. On the Configure connection to SQL
Server Analysis Services (SSAS) page,
provide the following information.
Select the Enable SSAS check box.
Provide the following information in the
text boxes provided:
 SSAS server – Specify the
Operations Manager database
server instance.
 SSAS Instance – Specify the SSAS
instance name that you created
earlier.
 Port – Leave the default value of
0.
12. In the Provide credentials with
administrative rights on the SSAS
instance section, select the Enter a user
name and password option, and provide
the supplied credentials for the
Operations Manager data reader account.
Click OK to save these settings.

navigate to the Monitoring workspace,
right-click the PRO node and click PRO
Object State. Verify that the Virtual
Machine Manager is listed with a health
state other than Not Monitored.

8 Service Manager
The Service Manager installation process includes the high-level steps shown in Figure 8.
Installation of
Service Manager
Prerequisites 2012 R2 Service
Installation
Manager Roles
Install the .NET Install SQL Server

Install the
Framework 3.5.1 Reporting Services
Management
Feature on all on the Data
Server
servers Warehouse Server
Install the Report

Install SharePoint
Viewer 2012 on
Foundation 2010 Add an Additional
the Management
SP1 on the Self- Management
and Data
Service Portal Server
Warehouse
Server
servers
Install the SQL

Server Native Install .NET
Client on the Framework 4 on Install the Data
Management and the Self-Service Warehouse Server
Data Warehouse Portal Server
servers
Install Analysis
Management Request an Install
Install the Self-
Objects on the an SSL Certificate
Service Portal
Management and on the Self-Service
Server
Data Warehouse Portal Server
servers
Figure 8 Service Manager installation process

8.1 Overview
This section provides a high-level walkthrough for deploying Service Manager into the fabric
management architecture. The following requirements are necessary to deploy the management, data
warehouse, and self-service portal servers:
Management server
 A base virtual machine running Windows Server 2012 R2 has been provisioned for the Service
Manager management server role
 A multi-node, SQL Server 2012 SP1 cluster with dedicated Service Manager instances has been
established in previous steps for Service Manager
o SCSMDB - instance for Service Manager management database.
 .NET Framework 3.5 SP1 is installed
 Microsoft Report Viewer 2008 Service Pack 1 Redistributable is installed
To install, see article 971119 in the Microsoft Knowledge Base
 Microsoft SQL Server 2012 Native Client is installed:
To install, see SQL Server 2012 Native Client
 The Microsoft SQL Server 2012 Analysis Management Objects are installed:
To install, see SQL Server Analysis Management Objects
Data warehouse server
 A base virtual machine running Windows Server 2012 R2 has been provisioned for the Service
Manager management server role
 A multi-node, SQL Server 2012 SP1 cluster with a dedicated instance has been established in
previous steps for Service Manager, which includes:
o SCSMAS – instance for SQL Server 2012 SP1 Analysis Services and SQL Server Reporting
Services databases
o SCSMDW – instance for Service Manager data warehouse databases
To download, see SQL Server 2012 Native Client
 Microsoft SQL Server 2012 Analysis Management Objects are installed:
To install, see SQL Server Analysis Management Objects.
 Microsoft SQL Server 2012 Reporting Services (split configuration) is installed
 Microsoft SQL Server 2012 management tools are installed

Self-service portal server
 A base virtual machine running Windows Server 2008 R2 (x64) has been provisioned for the
Service Manager management server role
 A multinode, SQL Server 2012 SP1 cluster with a dedicated instance has been established in
previous steps for Service Manager
To download, see SQL Server 2012 Native Client
 Microsoft SQL Server 2012 Analysis Management Objects are installed:
To install, see SQL Server Analysis Management Objects
 SharePoint Foundation 2010 Service Pack 1 is installed
 The .NET Framework 4 Redistributable
8.2 Prerequisites
8.2.1 Accounts

<DOMAIN>\ FT-SCSM-SVC SCSM services account  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 email
and must have a mailbox on the SMTP
server (required for the Email Incident
feature)
 Must be member of local Users security
group on all SCSM servers
 Must be a member of the Service
Manager Administrators user role for
email
 Must be a local Admin on all SQL Server
nodes
<DOMAIN>\ FT-SCSM-SSRS SCSM reporting account  Must be a local Admin on all SQL Server

nodes
<DOMAIN>\ FT-SCSM-OMCI SCSM Operations Manager CI  Must be a member of the local Users
connector account security group on all SCSM servers.
 Must be an Operations Manager
operator
<DOMAIN>\ FT-SCSM-ADCI SCSM Active Directory CI  Must be a member of the local Users
connector account 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 to
the Service Manager database from
Active Directory
<DOMAIN>\ FT-SCSM- SCSM Operations Manager  Must be a member of the local Users
OMAlert alert connector account security group on the Service
Manager management server
 Must be a member of FT-SCSM-Admins
DOMAIN>\ FT-SCSM-VMMCI Virtual Machine Manager CI  Must be a member of the VMM Admin
connector account domain group and be in the Service
Manager Advanced Operator role
DOMAIN>\ FT-SCSM-OCI Orchestrator CI connector  Must be a member of SCO Operators

(Users) domain group and be in the
Service Manager Advanced Operator
role
<DOMAIN>\ FT-SCSM-OLAP Service Manager Analysis  Must be a local Admin on all SQL Server
Services account nodes
Table 12 Accounts
8.2.2 Groups
Security group name Group scope Members Member of

<DOMAIN>\ FT-SCSM- Global DOMAIN\ FT-  Must be added to the Service
ADMINS SCSM-SVC Manager Administrators user role,
added to the Operations
Manager Administrators role in
Operations Manager, and be a
member of the Administrators

group on each SQL Server
Table 13 Groups
8.2.3 Add .NET Framework 3.5 on all Server Manager Servers

The Service Manager installation requires that .NET Framework 3.5 be enabled to support installation. Use
the following procedure to enable.NET Framework 3.5.
 Perform the following steps on the Service Manager management server and the data warehouse
virtual machines.

this local server, click Add roles
and features.

will appear. On the Before You
in the left pane to continue.

the local server, and then, click
Features in the left pane to
continue.
4. To add .NET Framework 3.5, On the

Select Features page, in the
Features pane, select the .NET
to continue.

required is not selected. Click
Install to begin installation.
Settings option is available as a link
they can be used in conjunction
If the server does not have Internet
access, an alternate source path can
be specified by clicking the Specify
an alternate source path link.

For servers without Internet access, or if
the .NET Framework 3.5 source files
already exist on the network, an
alternate source location be specified
here for the installation.


 Perform the following steps on the Service Manager Self-Service Portal virtual machine running
Windows Server 2008 R2.
1. To add .NET Framework 3.5.1, from

Server Manager, click the Features
node, and then click Add Features.
The Add Features Wizard will appear.
On the Select Features page, select
.NET Framework 3.5.1 Features,
and then select the .NET Framework
3.5.1 check box only. Leave WCF
Activation check box clear.
2. On the Confirm Installation

Selections page, review the choices
that you made during the wizard,
and click Install to add the feature.

installation.

4. When complete, the Installation
Results page will appear. Verify that
the .NET 3.5.1 Feature installed
correctly. When verified, click Close
to complete the installation of.NET
Framework 3.5.1.
8.2.4 Install Microsoft Report Viewer 2008 SP1 Redistributable on the Management
and Data Warehouse Servers
The Server Manager management server and the data warehouse server installations also require the
Microsoft Report Viewer 2008 SP1 Redistributable. Use the following procedure to install the Microsoft
Report Viewer 2008 SP1 Redistributable.
 Perform the following steps on the Server Manager management server and on data warehouse
server virtual machines.
1. From the installation media, right-

click ReportViewer.exe and click
Run as administrator to begin
setup.
Note: You can find the Report
Viewer 2008 SP1 Redistributable as
follows:
 In the Prerequisites folder of the
Service Manager 2012 R2
installation media
 In the Microsoft Download
Center: Report Viewer
Redistributable 2008 Service
Pack 1 GDIPLUS.DLL Security
Update

2. The Setup Wizard will appear. Click
Next to continue.

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

4. When the setup is complete, click
Finish.
8.2.5 Install SQL Server 2012 Native Client on the on the Management and Data
Warehouse Servers
The Server Manager management server and data warehouse server installations also require that SQL
Server 2012 Native Client is installed prior to installation. Use the following procedure to install SQL
Server 2012 Native Client.
 Perform the following steps on the Server Manager management server and on the data
warehouse server virtual machines.

right-click SQLNCLI.MSI and select
Install to begin setup.
Note: Download SQL Server 2012
SP1 Native Client installer,
1033\x64\sqlncli.msi, from the
Microsoft Download Center:
Microsoft SQL Server 2012 SP1
Feature Pack.

2. The setup wizard will appear. Click
Next to continue.

the I accept the terms in the license
agreement check box. Click Next to
continue.

verify that Client Components is
selected for installation. Click Next to
continue.

5. On the Ready to Install the
Program page, click Install to begin
the installation.
6. When complete, click Finish.
8.2.6 Install SQL Server 2012 SP1 Analysis Management Objects

The Server Manager management server and data warehouse server installations also requires SQL
Server 2012 SP1 Analysis Management Objects. Use the following procedure to install the SQL
Server 2012 SP1 Analysis Management Objects.

 Perform the following steps on the Server Manager management server and on the data
warehouse server virtual machines.

Analysis Management Objects
installation media source, double-
click SQL_AS_AMO.MSI to begin
setup.
Note: Download the SQL
Server 2012 SP1 Analysis
Management Objects installer,
SQL_AS_AMO.MSI, from the
Microsoft Download Center:
Microsoft SQL Server 2012 SP1
Feature Pack.
2. The Setup Wizard will appear. On the

Welcome page, click Next to
continue.

review the license agreement, and
select the I accept the terms in the
license agreement button. Click
Next to continue.

4. On the Ready to Install the
Program page, click Install to begin
the installation.
5. The installation process may take

several minutes to complete. The
progress is displayed in the status
bar.
6. On the Completing the SQL

Server 2012 Analysis Management
Objects installation page, click
Finish.

8.2.7 Install SQL Server Reporting Services (Split Configuration) on the Data
Warehouse Server
The Service Manager data warehouse installation requires that SQL Server Reporting Services is installed
to support the Service Manager reporting features. Use the following procedure to install SQL Server
Reporting Services.
 Perform the following steps on the Service Manager data warehouse virtual machine.
1. From the SQL Server 2012

2. The SQL Server Installation Center

will appear. Select the Installation
menu option.

Center, click the New SQL Server
features to an existing installation
link.

5. If you click the View detailed

report link, the following report is
available.
6. On the Product Key page, select

the Enter the product key option
and type the associated product key
in the provided text box. Click Next
to continue.

key, select the Specify a free
edition option, and select
Evaluation from the drop-down list
for a 180-day evaluation period.

the I accept the license terms
check box. Select or clear the Send
feature usage data to Microsoft
organization’s policies and click
Next to continue.

9. On the Install Setup Files page,

click Install and allow the support
files to install.

validation check.
Note: Common issues include

MSDTC, MSCS, and Windows
Firewall warnings. The use of
MSDTC is not required for the
environment. Click Next to
continue.
11. On the Setup Role page, select the

SQL Server Feature Installation

 Reporting Services - Native
 Management Tools – Basic
 Management Tools –
Complete
When all selections are made, click
Next to continue.

continue.

page, select the Default instance
option, and accept the default
options for Instance ID and
Instance root directory values.
Note: A post-installation
configuration process will occur to
configure the reporting server
database within the Service
Manager data warehouse SQL
Server instance.

disk space and click Next to
continue.

select the Service Accounts tab. In
the Account Name drop-down list,
specify the NETWORK SERVICE
account for the SQL Server
Reporting Services service. Click
Next to continue.

17. On the Reporting Services
Install only option. Note that other
options should not be available
because the database engine was
not selected as a feature for
18. On the Error Reporting page,

select or clear the Send Windows
and SQL Server Error Reports to
Microsoft or your corporate
report server check box, based on
your organization’s policies and


Install to begin the installation of
the SQL Server instance.
21. When the Complete page appears,

click Close to complete the
installation of this SQL Server
database instance.
22. By default, Windows Firewall does

not allow traffic for SQL Server
services or for the SSRS Web
Service. Firewall exceptions need to
be created if the Windows Firewall is
enabled.
To create exceptions, open an
administrative session of Windows
PowerShell.

23. Run the following commands to
create the needed firewall rules:
New-NetFirewallRule -DisplayName
"SQL Reporting Services" -Protocol TCP
-LocalPort 80
Adjust the display names and ports
based on organizational
requirements.
24. Open the Windows Firewall with
Advanced Security MMC console
to verify the results. When verified,
close the MMC console.
25. Verify that SQL Server Reporting

Services installed properly by
opening the console: on the Start
screen, click the Reporting Services
Configuration Manager tile.

Configuration Connection page
will appear. In the Server Name text
box, specify the name of the Service
Manager server. In the Report
Server Instance text box, use the
default MSSQLSERVER value from
the drop-down list. Click Connect.

Configuration Manager will
appear.

Configuration Manager, click the
Database option in the left pane. In
the Current Report Server
Database section, click the Change
Database button.
29. The Reporting Services Database

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

30. In the Database Server section,
specify the following values:
 Server Name – Specify the
name of the SQL Server Cluster
SCSMDW instance cluster name
object and the database
instance created for the Service
Manager data warehouse
installation.
Current User – Integrated
Security from the drop-down
list.
31. Click the Test Connection button to
verify the credentials and database
connectivity. When verified, click
Next to continue.
32. 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 list.
 Report Server Mode – Select
the Native Mode option.
34. In the Credentials section, specify

the Authentication Type as
Service Credentials from the drop-
down list, and click Next to
continue.

35. In the Summary section, review the
selections made, and click Next to
create the SQL Server Reporting
Services database.
36. The Progress and Finish section

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

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

Web Service URL option from the
toolbar. Specify the following
values:
Service Virtual Directory
section, set the Virtual
Directory value to
ReportServer in the provided
text box.
Service Site Identification
section, set the following values:
o IP Address – Select All
Assigned in the drop-
down list.
o TCP Port – Specify the
desired TCP port
(default is 80).
o SSL Certificate – Select
the available certificate
or choose the default
(Not Selected).
39. Click Apply to save the settings and
create the Web Service URL.

Report Manager URL option in the
toolbar. Specify the following value:
 In the Report Manager Site
Identification section, keep the
default Virtual Directory value,
Reports, in the provided text
box.
41. Click Apply to save the setting and
create the Report Manager URL.

42. Connect to the Report Manager URL
from a web browser to verify that
the SQL Server Reporting Services
portal is operating properly.
43. Connect to the Web Service URL

from a web browser to verify that
the SQL Server Reporting Services
web service is operating properly.
Note: To test the URL directory
from the Service Manager server,
Internet Explorer Enhanced Security
Configuration needs to be
temporarily disabled.
44. Close the Reporting Server
8.2.8 Install SharePoint Foundation 2010 SP1 on the Self-Service Portal Server
SharePoint Foundation 2010 Service Pack 1 (SP1) must be installed to configure SharePoint with the SQL
Server 2012 SP1 installation. Use the following procedure to install SharePoint Foundation 2010 SP1 on
the Service Manager self-service portal server only.
 Perform the following steps on the Service Manager self-service portal virtual machine.
1. Log on to the 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 to begin setup.

2. The SharePoint Foundation 2010
setup page will appear. In the Install
section, click Install software
prerequisites.
3. The Microsoft SharePoint 2010

Products Preparation Tool will open.
4. On the License Terms for software

products page, verify that the I
accept the terms of the License
Agreement installation option check
continue.

5. After the prerequisites install, the
Installation Complete page will
appear. Click Finish to complete the
installation, and then restart the
system.
6. After the system restart, log on with

an account with administrative
privileges, and open the SharePoint
Foundation 2010 setup page. In the
Install section, click Install
SharePoint Foundation.
7. On the Read the Microsoft Software

License Terms page, verify that the I
accept the terms of this Agreement
selected, and click Continue.

8. On the Choose the installation you
want page, click the Server Farm
button.
9. On the Server Type page, select the

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

Configuration Wizard will appear.
Verify that the Run the SharePoint
Products Configuration Wizard now
check box is not selected, and click
Close.
Important: SharePoint Foundation
Server 2010 SP1 must be installed
prior to running the Configuration
Wizard.

Note: SharePoint Foundation 2010
SP1 must be applied to the SharePoint
Foundation server.4
11. Right-click the SharePoint
Foundation 2010 Service Pack 1
installation file, and select Run as
administrator to begin the Service
Pack setup.
12. The Microsoft SharePoint

Foundation 2010 Service Pack 1 (SP1)
Wizard will appear. Verify that the
Click here to accept the Microsoft
Software License Terms installation
option check box is selected, and click
Continue.
13. 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.
14. From the Start menu, expand

Microsoft SharePoint 2010
Products, and click SharePoint 2010
Products Configuration Wizard.
4 Service Pack 1 for SharePoint Foundation 2010 (KB2460058)

15. The SharePoint Products
Configuration Wizard will appear.
16. A message will appear that states

some services require a restart as part
of the installation. Click Yes to restart
the services.
17. On Connect to a server farm page,

select Create a new server farm, and

18. On the Specify Configuration
Database Settings page, specify the
text boxes:
 Database server – Specify the
name of the SQL Server cluster
name object and the database
Manager installation.
name of the SharePoint database.
In most cases, use the default
value of SharePoint_Config.
19. In the Specify Database Access
Account section, specify the
Username in the form
(<DOMAIN>\<USERNAME>) and an
associated password for the Service
Manager service account. Click Next
to continue.
20. On the Specify Farm Security

Settings page, enter a unique
passphrase in the Passphrase text
box. Retype the passphrase in the
Confirm passphrase text box, and

21. On the Configure SharePoint
Central Administration Web
Application page, click the Specify
port number check box, and
providing a port number in the
provided text box.
22. In the Configure Security Settings
section, select the NTLM option.
24. The Completing the SharePoint

Products Configuration Wizard will
made during the installation wizard.
Review the selections and click Next
to continue.

while performing the SharePoint
configuration.
26. When the Configuration Successful

page appears, click Finish to complete
the configuration of SharePoint
Foundation 2010 Service Pack 1.
27. When prompted in the Help Make

SharePoint Better page, select the
appropriate option based on your
organization’s policies, and click OK to
save this setting.
28. On the Central Administration -

Configure your SharePoint farm
page, click the Start the Wizard
button to begin the SharePoint
configuration.

29. In the Service Account section, select
Use existing managed account, and
select the SQL Service account from
the drop-down list.
30. In the Services section, select the
Business Data Connectivity Services
and Usage and Health data
collection check boxes.
32. On the website configuration page,

click the Skip button to continue
without configuring these settings.
33. The SharePoint farm configuration is

now complete. Click the Finish button
to exit the wizard.
34. The SharePoint Central

Administration portal will open.
Verify that SharePoint is operating
properly by opening the Central
Administration portal prior to
proceeding to the Service Manager
self-service portal installation.

8.2.9 Install .NET Framework 4 on the Self-Service Portal Server
Additionally, the Service Manager self-service portal installation requires that the .NET Framework 4
package is installed. Use the following procedure to install .NET Framework 4 on the self-service portal.

right-click
dotNetFx40_Full_x86_x64.exe and
select Run as administrator to
begin setup.
2. On the Microsoft .NET Framework

4 Setup page, select the I have read
and accept the license terms check
box, and click Install to begin the
installation.

3. The wizard will display the
installation progress.

click Finish.
8.2.10 Request and Install an SSL Certificate on the Self-Service Portal Server
Additionally, the Service Manager self-service portal installation requires a secure socket layer (SSL)
certificate to enable SSL on the portal website. If you are installing the self-service portal without SSL, you
can skip this section. There are several ways to request an SSL certificate. The following procedure
describes how to request the certificate through the IIS Manager console.

1. Log on to the Service Manager self-

service virtual machine as a user with
local Admin rights. From the Start
menu, click Administrative Tools,
and then click Internet Information
Services (IIS) Manager.
2. In the Internet Information

Services (IIS) Manager console, click
the server node, and in the IIS
section, double-click Server
Certificates.
3. The Server Certificates pane will

expand. In the Actions pane, click
Create Certificate Request…
4. The Request Certificate Wizard will

appear. On the Distinguished Name
Properties page, complete the
information as prompted.
Note: The Common Name field
must equal the exact name of the
server as it will be accessed from the
web browser. Click Next to continue.

5. On the Cryptographic Service
Provider Properties page, 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.
6. On the File Name page, provide a

complete path to save the certificate
request file. Click Finish to generate
the certificate request.
When complete, submit the request

to your issuing CA or a certificate
provider of choice.
7. When you receive the issued

certificate, open the Internet
Information Services (IIS) Manager
console, and select Server
Certificates. In the Actions pane,
click Complete Certificate
Request…

8. The Complete Certificate Request
Wizard will appear. On the Specify
Certificate Authority Response
page, specify the file name and
location of the issued certificate and
supply a friendly name for the
certificate in the provided text boxes.
Click OK to complete the operation.
9. In the Server Certificates section of

the IIS Manager, you will now see the
newly created and installed
certificate.

8.2.11 Configure Service Manager Environmental Prerequisites
Complete the following procedures to install the Service Manager roles correctly.
 Perform the following steps on all Service Manager Servers virtual machines.
1. Log on to each Service Manager virtual

machine as a user with local Admin rights.
Verify that the following accounts or groups
are members of the local Administrators
group on each Service Manager virtual
machine:
 Operations Manager action account
 Service Manager workflow account
 Service Manager service account
 Service Manager Admins group
2. On the self-service portal server, also add the
following account:

3. Verify that the following accounts or groups
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.
1. In the domain where Service Manager will be

installed, verify that the Service Manager
Operations Manager alert connectors and
the Service Manager service accounts are
members of the Service Manager Admins
group that you created earlier.

2. In the domain where Service Manager will be
installed, verify that the FT-SCSM-OLAP and
the Service Manager reporting accounts are
members of the SQL Server Admins group
that you created earlier.
 Perform the following steps on the Operations Manager virtual machine.
1. Log on to the Operations Manager server as

an Administrator. In the Operations
Manager console, navigate to
Administration pane, and click the Security
node. Under User Role name, click
Operations Manager Administrators, and
add SCSM Admins. Click OK to save the
changes.

2. While still in the Security node under User
Roles, click Operations Manager Operators,
and add SCSM OMCI. Click OK to save the
changes.
8.3 Installation
8.3.1 Install the Management Server

Complete the following procedure to install the Service Manager management server role.
 Perform the following steps on the first Service Manager management server virtual machine.
1. Log on to the Service Manager

management server (not the Service
Manager data warehouse server or
the self-service portal server).
2. From the Service Manager

3. The Service Manager Setup Wizard
will appear. In the Install section,
click Service Manager
management server to begin the
installation.
4. On the Product registration page,

enter the following information in
the provided text boxes:
primary user or responsible
party within your organization.
 Organization – Specify the
name of the licensed
organization.
Service Manager. If no key is
provided, select the Install as
an evaluation edition (180-
day trial) check box.
5. 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.

default location of
Center 2012 R2\Service Manager for
continue.
7. On the System check results page,

the wizard will verify that all system
prerequisites are not met, they will
be displayed on this page. When
verified, click Next to continue.

8. On the Configure the Service
Manager database page, specify
name object created for the
Service Manager installation.
 SQL Server instance – Specify
the name of the SQL Server
database instance created for
the Service Manager
installation.
9. Select the Create a new database
option, and specify the following
boxes:
name of the Service Manager
database. In most cases, use the
default value ServiceManager.
 Size (MB) – Specify the initial
database size. The default value
can be used.
For more information, see
Planning for Performance and
Scalability in System Center
2012 - Service Manager.
drive letter associated in the
SQL Server cluster data files for
the Service Manager database.
Cross-check this with the
worksheet created earlier.
 Log file folder – Specify the
SQL Server cluster for the log
files for the Service Manager
database. Cross-check this with
the worksheet created earlier.

Manager management group
page, specify a unique name in the
Management group name text
box. This value must be unique
across the System Center 2012 R2
products, such as the Service
Manager data warehouse and
Operations Manager installations.
12. In the Management group
administrators text box, specify the
Service Manager Administrators
group.
14. On the Configure the account for

Service Manager services page:
 Verify that the Domain account
option is selected.
 In the User name text box,
specify the Service Manager
service account.
 In the Password text box, type
an appropriate password.
 In the Domain text box, select a
domain from the drop-down
list.
15. Before proceeding, click the Test
Credentials button to verify the
credentials provided.
16. When successful, click Next to
continue.

Service Manager workflow
account page:
 Verify that the Domain account
option is selected.
 In the User name text box,
specify the Service Manager
service account.
 In the Password text box, type
an appropriate password.
 In the Domain text box, select a
domain from the drop-down
list.
continue.
20. On the Help improve Microsoft

System Center 2012 R2 Service
Manager page, select the option to
CEIP by providing selected system
information to Microsoft. Click Next
to continue.

21. Depending on your system’s
configuration, the Use Microsoft
Update to help keep your
computer secure and up-to-date
page may appear.
 Select the appropriate option to
participate or not participate in
automatic updating.
 Select the Initiate machine
wide Automatic Update check
box.

made during the Setup Wizard.
Review the options selected, and
click Install to continue.


completed successfully page.
25. When all steps show successful
installation, ensure that the Open
the Encryption Backup or Restore
Wizard after Setup closes check
box is selected to open the wizard
after setup.
26. Click Close to complete the
installation.

the Encryption Key Backup or
Restore Wizard will appear. On the
Introduction page, click Next to
continue.

28. On the Select Action page, select
the Backup the Encryption Key
option, and click Next to continue.
29. On the Specify the Location of the

Backup File page, in the Path text
box select the desired backup file
name and path. Click Next to
continue.

30. On the Provide a Password page,
type a desired password in the
Password text box. Re-type the
password in the Confirm Password
text box, and click Next to begin
the backup process.
31. Click Finish to exit the wizard.
32. When installed, verify that the

Service Manager management
server installed properly by opening
the console: on the Start screen,
click the Service Manager Console
tile.

33. On the Connect to Service
Manager Server page, type the
server name in the Server name
text box, and click Connect to start
the console.
34. The Service Manager Console will

reviewing the configuration and
ensure that the console operates
properly.
8.3.2 Install the Data Warehouse Server

The following steps must to be completed to install the Service Manager data warehouse server role.
 Perform the following steps on the Service Manager data warehouse server virtual machine.
1. Log on to Service Manager data

warehouse server (not the Service
Manager management server or
the self-service portal server).

click Service Manager data
warehouse management server
to begin the Service Manager

 Name – Specify the name of
the primary user or responsible
 Organization - Specify the
organization.
Service Manager. If no key is
provided, select the Install as
an evaluation edition (180-
day trial) check box.
to continue.

default location of
Center 2012 R2\Service Manager
for the installation. Click Next to
continue.

prerequisites are met on the
System check results page. If any
8. On the Configure the data

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

warehouse databases page,
supply the following information in
the provided text boxes to
configure the Staging and
Configuration and Repository
sections:
name object that was created
for the Service Manager
installation data warehouse.
database instance that was
created for the Service
Manager installation data
warehouse.
option and specify the following
boxes:
name of the Server Manager
data warehouse database. In
most cases, use the default
value of DWStagingAndConfig
for the Staging and
Configuration section, and use
DWRepository for the
Repository section.
database size.
SQL Server cluster for the
database data files for the
Service Manager data
warehouse. This should be
cross-checked with the
worksheet identified earlier. Set
the correct value in the
Staging and Configuration
and the Repository sections.
258 IaaSLog
Product Line Architecture
file folder – Specify Deployment
the Guide
SQL Server cluster for the
database log files for the
warehouse databases page,
configure the Staging and
sections:
Service Manager installation
data warehouse. (This should
be the same name that you
used earlier for the Staging
and Configuration and
Repository sections).
the Service Manager
(This should be the same name
that you used earlier for the
and Repository sections).
boxes:
data warehouse. In most cases,
use the default value of
DWDataMart.
database size.
same drive letter that you used
earlier for the database data
data warehouse. This should be
cross-checked with the
(This should be the same name IaaS Product Line Architecture Deployment Guide 259
you used earlier for the
and Repository sections.)
15. On the Configure additional data
warehouse datamarts page, each
subcategory will appear with an
error message until each of the
following sections are configured:
 OM Data mart
 CM Data mart

16. On the Configure additional data
warehouse datamarts page,
configure the OM Data Mart
section:
be the same name you used
earlier for the Staging and
sections.)
the Service Manager
boxes:
OM Data mart database. In
value of OMDWDataMart.
database size.
same drive letter you used
OM Data mart database. This
should be cross-checked with
the worksheet identified earlier.
you used earlier for the IaaS Product Line Architecture Deployment Guide 261
19. A CM Data mart is created for
Configuration Manager integration.
To complete this, on the Configure
additional data warehouse
datamarts page, supply the
following information in the
provided text boxes to configure
the CM Data Mart section:
be the same name you used
earlier for the Staging and
sections.)
the Service Manager
boxes:
CM Data mart database. In
value of CMDWDataMart.
database size.
 Data file folder – specify the
same drive letter you used
CM Data mart database. This
should be cross-checked with
the worksheet identified earlier.
262 IaaS(This should
Product Linebe the sameDeployment
Architecture name Guide
warehouse management group
page, specify a unique name in the
Management group name text
box. This value must be unique
across the System Center 2012 R2
products such as the Service
Manager management server and
Service Manager Operations
Manager installations.
23. In the Management group
administrators section, select the
SM Administrators group from the
drop-down list.
25. On the Configure the reporting

server for the data warehouse
page, specify the data warehouse
server in the Report server text
box.
26. In the Report server instance
drop-down list, select Default.
27. In the Web service URL drop-
down list, select the default
reporting server URL.

Service Manager services page:
 Verify that the Domain
account option is selected.
 Specify the Server Manager
service account in the User
name text box.
 Type the appropriate Password
in the provided text box.
 Select the appropriate Domain
from the drop-down list.
continue.
32. On the Configure the reporting

account page:
 Specify the SCSM SQL Server
Reporting Services Account in
the User name text box.
continue.

35. On the Configure Analysis
Services for OLAP cubes page,
select the Create a new database
boxes:
SQL Server Analysis Services.
the Service Manager
installation SQL Server Analysis
Services.
name of the SQL Server
Analysis Services database. In
value of DWASDataBase.
36. Confirm that the Change database
storage directory check box is
clear, and click Next to continue.
37. On the Configure Analysis

Services Credential page:
 Specify the SM OLAP Account
in the User name text box.
continue.

Manager page, select the option to
CEIP and provide selected system
information to Microsoft. Click
Next to continue.

page may appear. Select the
appropriate option to participate or
not participate in automatic
updating. Choose to invoke
checking for updates by selecting
the Initiate machine wide
Automatic Update check box.

42. The Installation summary page
selections made during the Setup
Wizard. Review the options
selected, and click Install to
continue.

completed successfully page.
45. Ensure the Open the Encryption
Backup or Restore Wizard after
Setup closes check box is selected
to open the wizard after setup.
installation.

the Encryption Key Backup or
Restore Wizard will appear. On the
Introduction page, click Next to
continue.
48. On the Select Action page, select

the Backup the Encryption Key
option, and click Next to continue.

49. On the Specify the Location of
the Backup File page, in the Path
text box, select the desired backup
file name and path from the drop-
down list. Click Next to continue.
50. On the Provide a Password page,

type a desired password in the
Password text box. Retype the
password in the Confirm
Password text box, and click Next
to begin the backup process.

51. 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.
1. Log on to the Service Manager

management server by using an
account with Administrator
permissions. From the Windows
Start screen, click the Service
Manager Console tile.
2. In the Service Manager Console,

click the Administration node, and
in the Register with Service
Manager’s Data Warehouse
section, click Register with Service
manager data warehouse to
enable reporting.
Note: If the console was opened
from the previous installation, close
it and re-open the console.

3. The Data Warehouse Registration
Wizard will appear. Click Next to
begin registration.
4. On the Specify the data

warehouse management server
name page, select the Service
Manager data warehouse server
FQDN from the Server name drop-
down list.
5. Click the Test Connection button
to validate connectivity between
the Service Manager management
server and the data warehouse
server. Click Next to continue.
6. On the Provide credentials for the

data warehouse page, in the Run
As account section, click New…
and select the current SM and DW
service account for the data
warehouse connection.

7. A Credentials page will appear and
prompt you for the password for
the SM service account. When
provided, click OK to continue.
8. The Summary page will appear.

Review the information that was
provided earlier, and click Create to
begin the registration process.
9. The Completion page 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, and several data
warehouse jobs run.

10. After a few minutes the Data
Warehouse button will be added
to the Service Manager Console.
Note: This deployment and the

association process can take up to two
hours to complete.
11. To check the status of the
management pack imports, in the
Data Warehouse pane, click
Management Packs.
12. Deployment is complete when all
listed management packs show a
deployment status of Completed.

Note: This deployment and the
association process can take up to two
hours to complete.
13. In the Data Warehouse pane, click
Data Warehouse Jobs.
14. In the Data Warehouse Jobs pane,
click MPSyncJob.
15. In the MPSyncJob section, 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.
16. 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
Pending Association or Failed in
the status list. In the Data
Warehouse Jobs pane, the status
of the MPSyncJob will change
from Running to Not Started
when the registration process is
complete.
8.3.3 Install the Service Manager Self-Service Portal Server

The following steps must to be completed 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.
1. Log on to Service Manager self-
service portal server (not the
server or the data warehouse
server).

click Service Manager web portal
to begin the Service Manager self-
service portal server installation.
4. On the Portal Parts page, select

the Web Content Server and
SharePoint Web Parts check
boxes, and click Next to continue.
Note: The warning about installing

both Portal Parts on a single server
can be safely ignored.

 Name – Specify the name of
the primary user or responsible
 Organization – Specify the
organization.
to continue.

default location of
C:\inetpub\wwwroot\System Center
Service Manager Portal for the
8. On the System check results page,

the wizard will verify that all system

Manager Self-Service Portal
name and port page, specify the
following information in the
 Website name – Specify the
name of the website used for
the self-service portal. In most
cases, use the default name of
SCSMWebContentServer.
 Port – Specify the TCP port
used for the Service Manager
self-service portal server. The
default value is 443. In most
cases this value should be
changed to 444.
10. Select the appropriate Server
Authentication certificate from the
SSL certificate drop-down list. The
certificate CN field must match the
name of the server.
12. On the Select the Service

Manager database page, specify
cluster name object created for
the Service Manager
management server.
the SQL Server database
Manager management server.
 Database – Specify the name
of the Service Manager
database configured earlier. In
value of ServiceManager.

the Self-Service Portal page:
 Verify that the Domain
account option is selected, and
 Specify the SM Service Account
continue.

Manager SharePoint Web site
page, provide the following
information:
 In the SharePoint site section,
specify the following
information in the provided
text boxes:
Website name – Specify the name
of the website used for the self-
service portal. In most cases, use
the default name of Service
Manager Portal.
Port – Specify the TCP port used
for the Service Manager self-
service portal server. The default
value is 443. In most cases, keep
the default value of 443.
 Select the appropriate server
authentication certificate from
the SSL certificate drop-down
list. This will be the same
certificate used for the content
server in the previous step.
 In the SharePoint database
section, specify the following
information in the provided
text boxes:
Database server – Specify the
network name created for the
SharePoint farm.
SQL Server instance – Specify the
SQL Server database instance
created for the Service Manager
installation SharePoint farm.
Database server – Specify the
database name for the portal. In
most cases, use the default value
of SharePoint_SMPortalContent.

Service Manager SharePoint
application pool page:
 Specify the SM service account
continue.

System Center 2012 page, select
the option to participate or not
participate in the CEIP and provide
Microsoft. Click Next to continue.

page may appear. Select the
appropriate option to participate or
not participate in automatic
updating. Choose to invoke
checking for updates by selecting
the Initiate machine wide
Automatic Update check box.

24. The Installation summary page
selections made during the Setup
Wizard. Review the options
selected and click Install to
continue.

26. When completed, the Service

Manger Setup Wizard will display
the Setup completed successfully
page. Click Close to finish the
installation.
Note the SMPortal link provided on

the page.

27. From a system with Silverlight®
installed, open the Service Manager
self-service portal from Microsoft
Internet Explorer at
https://<servername>/SMPortal.
Verify that the page loads
completely and that all sections
display as expected.

9 Orchestrator
The Orchestrator installation process includes the high-level steps shown in Figure 9:
Installation of
System Center 2012 R2 Post Installation
Orchestrator Configuration of
Prerequisites 2012 R2
Installation Orchestrator
Orchestrator Roles
Installation:
Runbook,
Install the .NET Install the Virtual
Orchestration
Framework 3.5 Machine Manager
Console, Web
Feature Console
Service and
Designer Server
Install the
Install Silverlight Add an Additional
Microsoft Report
Runtime Runbook Server
Viewer 2010 SP1
Install the
Operations
Manager Console
Install Integration
Packs
Deploy and
Configure
Integration Packs
Figure 9 Orchestrator installation steps

9.1 Overview
This section provides the procedure to set up Orchestrator in the fabric management architecture. The
following requirements are necessary for the setup:
 Base virtual machines running Windows Server 2012 R2 have been provisioned.
 A multinode, SQL Server 2012 SP1 cluster with a dedicated instance has been established for
Orchestrator in previous steps.
 .NET Framework 3.5 is required
9.2 Prerequisites
9.2.1 Accounts

<DOMAIN>\FT-SCO-SVC Orchestrator service This account needs:
account
 Full Administrator 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
 Member of FT-SCVMM-Admins
Table 14 Accounts
9.2.2 Groups

<DOMAIN>\FT-SCO- Global
Operators
<DOMAIN>\FT-SCO- Global <DOMAIN>\FT-SCO-SVC  Local Administrators
Admins  Target Active Directory domain
BUILTIN\Distributed COM
Users
Table 15 Groups

9.2.3 Add .NET Framework 3.5 and .NET Framework 4.5 with HTTP Activation
The Orchestrator installation requires that .NET Framework 3.5 and HTTP Activation for .NET 4.5 are
enabled. Use the following procedure to enable these features.
 Perform the following steps on the Orchestrator virtual machine.
1. Open Server Manager and navigate to the

Dashboard node. In the main pane, under
Configure this local server, click Add roles
and features from the available options.
2. The Add Roles and Features Wizard will

appear. On the Before You Begin page, click
Server Selection in the left pane.
3. On the Select destination server page,

select the Select a server from the server
pool button, select the local server, and then
click Features in the left pane to continue.

4. To add .NET Framework 3.5, on the Select
Features page in the Features pane, expand
and select the .NET Framework 3.5
Features and .NET Framework 3.5
(includes .NET 2.0 and 3.0) check boxes
only. Leave all other check boxes clear.
5. Expand .NET Framework 4.5 Features item

and then expand the WCF item. Select HTTP
Activation and then select Add Features on
the Add features that are required for
HTTP activation window.
6. The following items should now show as

enabled for the .NET Framework features:
a. the .NET Framework 3.5 Features
i. .NET Framework 3.5
(includes .NET 2.0 and 3.0)
b. .NET Framework 4.5 Features
i. .NET Framework 4.5
ii. ASP.NET 4.5
iii. WCF Services
1. HTTP Activation
2. TCP Port Sharing

8. On the Web Server Role (IIS) page click
Next to continue.
9. On the Select role services page, confirm

that only Web Server, Common HTTP
Features and Default Document are
selected and then click Next.

10. On the Confirm installation selections
page, verify that.NET Framework 3.5
Features and .NET Framework 4.5 Features
are listed. Ensure that the Restart each
required is not selected. Click Install to
begin installation.
Note: The Export Configuration Settings
option is available as a link on this page to
export the options selected to XML. When
exported, they can be used in conjunction
Windows PowerShell to automate the
installation of roles and features.
If the server does not have Internet access,
an alternate source path can be specified by
clicking the Specify an alternate source
path link. For servers without Internet access
or if the .NET Framework 3.5 source files
already exist on the network, an alternate
source location be specified here for the
installation
11. The Installation Progress page will show the

progress of the feature installation. Click
Close when the installation process
completes.
Note: Although this installation was performed

interactively, the installation of roles and features
can be automated by using the Server Manager
module for Windows PowerShell.

9.2.4 Install Silverlight

right-click Silverlight.exe and select
2. On the Install Silverlight page, click

Install now.
3. On the Enable Microsoft Update

page, select or clear the Enable
Microsoft Update check box based on
organizational preferences, and click
Next to continue.
4. On the Installation Successful page,

click Close.
9.3 Installation
9.3.1 Install the Runbook Server
Complete the following steps to install the all Orchestrator components.

1. Log on to the Orchestrator virtual
machine as a user with local Admin
rights.
groups are members of the Local
Orchestrator virtual machine:
 Orchestrator Admins group
account
2. Log on to System Center Orchestrator

server. From the System Center
Orchestrator installation media source,
right-click setuporchestrator.exe and
select Run as administrator to begin
setup.
3. The Orchestrator Setup Wizard will

appear. Click Install to begin the
Orchestrator server installation.

information page, enter the following
 Organization – Specify the name
 Product Key – Provide a valid
Orchestrator. If no key is provided,
Orchestrator will be installed in
evaluation mode.
6. On the Please read this License Terms

page, verify that the I accept the
license terms installation option check
continue.
7. On the Select Features to install page,

 Management Server (default
selected)
 Runbook server
 Orchestration console and web
service
 Runbook Designer

9. The Checking for required hardware
and software page will appear to verify
the installation prerequisites. When
validation completes, click Next to
continue.

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

11. When the installation of the missing
prerequisites is completed, click Next
to continue.
12. On the Configure the service account

page:
 Specify the Orchestrator service
account in the Username text box.
 Type the appropriate Password in
the provided text box.
button to verify the credentials
provided.
continue.

15. On the Configure the database server
page, enter the following information in
 Server – Specify the SQL Server
cluster name and instance name
created earlier. For the reference
deployment the server and instance
value is SCDB\SCDB.
 Port – Specify the TCP port used
for the SQL Server, if not the
default. For the reference
deployment the SCDB instance port
is 10433.
16. In the Authentication Credentials
section, select the Windows
Authentication option, and click the
Test Database Connection button.
continue.
18. On the Configure the database page

in the Database section, select the
New Database option. Type the default
database name of Orchestrator.

20. On the Configure Orchestrator users
group page, select the Orchestrator
users group created earlier from the
drop-down list. For this installation, this
is the domain Orchestrator operators
group outlined at the beginning of this
section.
21. Verify that the Grant remote access to
the Runbook Designer check box is
22. On the Configure the ports for the

web services page, enter the following
 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.
continue.
24. On the Select the installation location

default location of
%ProgramFiles(x86)%\Microsoft System
Center 2012 R2\Orchestrator for the

25. The Help Improve Microsoft System
Center Orchestrator page provides
options for participating in various
product feedback mechanisms. These
include:
 Customer Experience
Improvement Program (CEIP)
 Error Reporting
26. Select the appropriate option based on
Next to continue.

display the selections made during the
Setup Wizard. Review the options
selected, and click Install to continue.
28. The Installing features page will show

the installation progress.

29. The Setup completed successfully
page will appear when all portions of
the setup complete successfully. Verify
that all check boxes are cleared, and
click Close to finish the installation.
30. Verify that the Orchestrator roles

installed properly by opening the
consoles: on the Start screen, click the
Orchestration Console tile.
Note: To run the Orchestration Console

on the Orchestrator server, Internet
Explorer Enhanced Security must be
disabled or configured to function with
the console.
31. Validate that the Orchestration
console performs properly in Internet
Explorer.
32. On the Start Menu, click the Runbook

Designer tile.

33. Open the Runbook Designer console,
and verify that it performs properly.
34. On the Start Menu, click the

Deployment Manager tile.
35. Open the Deployment Manager

console, and verify that it performs
properly.

36. On the Start Screen, click the Windows
Firewall tile. Configure Windows
Firewall for the first Orchestrator
runbook server.5
If you want to leave Windows Firewall
enabled, you must first enable the
following rules in Windows Firewall:
 Windows Management
Instrumentation (WMI-In)
Instrumentation (DCOM-In)
Instrumentation (ASync-In)
37. Right-click each rule and click Enable
Rule.
38. Alternatively, the followingWindows

PowerShell commands can be run to
create the firewall rules:
Enable-NetFirewallRule -DisplayName
"Windows Management Instrumentation
(WMI-In)"
(DCOM-In)"
(ASync-In)"
5 Orchestrator guidance is provided by the following TechNet resources: Using Windows Firewall with Orchestrator and TCP Port Requirements.

39. In Windows Firewall, create a new
Program rule. Select the following path
from The program path drop-down
list:
 %SystemRoot%\SysWOW64\orches
tratorRemotingService.exe
40. Name the rule SCO – Orchestrator
Remoting Service (x64) and click
Next.
Alternatively, run the following

Windows PowerShell command:
New-NetFirewallRule -DisplayName "SCO –
Orchestrator Remoting Service (x64)" -
Program
C:\Windows\SysWOW64\OrchestratorRemo
tingService.exe
41. In Windows Firewall, create a new

Program rule. Select the following path
from The program path drop-down
list:
 %Program Files (x86)%\Microsoft
System Center 2012
R2\Orchestrator\Management
Server\ManagementService.exe
42. Name the rule SCO – Orchestrator
Management Service (x64) and click
Next.

Windows PowerShell command:
New-NetFirewallRule -DisplayName "SCO –
Orchestrator Management Service (x64)" -
Program “C:\Program Files (x86)\Microsoft
System Center 2012
R2\Orchestrator\Management
Server\ManagementService.exe”

43. Since the first server runs the
Orchestration console and web service,
two additional ports (TCP 81 and 82)
must be opened in Windows Firewall.
Follow the preceding step to create and
enable two additional firewall Program
rules and name them as follows:
 SCO – Orchestration Console
(TCP 81)
 SCO – Web Service (TCP 82)

Windows PowerShell commands:
New-NetFirewallRule -DisplayName "SCO -
Orchestration Console (TCP-In 81)"
New-NetFirewallRule -DisplayName "SCO -
Web Service (TCP-In 82)"
44. Restart the Orchestrator server.

After the installation is complete, install and configure Orchestrator Integration Packs on the target
runbook servers.
9.4.1 Install Microsoft Report Viewer 2012

Additionally, Orchestrator requires the Operations Manager console, but prior to installing it, you must
install the Microsoft Report Viewer 2012 package.
Use the following procedure to install the Microsoft Report Viewer 2012 package.

double-click SQLSysClrTypes.msi to
begin setup.

2. On the Welcome to the Installation…
page click Next.
3. On the License Agreement page, select

box and click Next to continue.

page click Install.

System…Installation page click Finish.

right-click ReportViewer.exe and select
7. On the Microsoft Report Viewer 2012

Runtime setup wizard Welcome to the
Installation… page click Next.

8. On the License Agreement page, select
box and click Next to continue.

page click Install.

Report Viewer 2012 Runtime
Installation page click Finish.

9.4.2 Install the Operations Manager Console

2. The Operations Manager installation

wizard will begin. Click Install to begin
the Operations Manager console
installation.

verify that the Operations console
check box is selected. Click Next to
continue.

default location of
C:\ProgramFiles\System Center 2012
R2\Operations Manager for the

continue.

license terms check box is selected, and

Manager page provides options for
Program
 Error Reporting
Select the appropriate option based on

Next to continue.

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

while performing the installation.
9. After the installation completes, the

complete page. Verify that the start the
Management console when the
wizard closes check box is selected, and
click Close to complete the installation.

reviewing the configuration and ensure
that the console operates properly.
9.4.3 Install the Virtual Machine Manager Console
 Perform the following steps on the Orchestrator virtual machines.
1. Log on to the Orchestrator server as a user

with Administrator privileges. From the
Virtual Machine Manager installation media
source, right-click setup.exe and select Run
as administrator to begin setup.

2. The Virtual Machine Manager Setup Wizard
will appear. Click Install to begin the Virtual
Machine Manager server installation.
3. On the Select features to install page, verify

that the VMM console installation option
check box is selected. Click Next to continue.
4. On the Please read this license agreement

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

5. On the Customer Experience Improvement
Program page, click Next to continue.
6. Depending on the current configuration of

the server, the Microsoft Update page may
appear. Select the option to allow or not
allow Virtual Machine Manager to use
Microsoft Update to check for and perform
Automatic Updates, based on your
continue.
7. On the Select installation location page,

specify a location or accept the default
location of C:\Program Files\Microsoft
System Center 2012 R2\Virtual Machine
Manager for the installation. Click Next to
continue.

8. On the Port Configuration page, specify the
port used for communication with the VMM
management server in the provided text box.
If no modifications were made during Virtual
Machine Management installation, the
default port would be 8100. Click Next to
continue.
9. The Installation summary page will appear

and display the selections made during the
Setup Wizard. Review the options selected,
and click Install to continue.
10. When the installation completes, the wizard

will display the Setup completed
successfully page. Click Close to complete
the installation.
9.4.4 Download and Register the Orchestrator Integration Packs

Complete the following steps to register the Orchestrator Integration Packs.
 Perform the following steps on the Orchestrator runbook server virtual machine.

1. Download the System Center 2012 R2 –
Orchestrator Component Add-ons and
Extensions from the Microsoft
Download Center.
2. Expand the Orchestrator Integration
Pack files.
3. On the Start screen, click the

4. 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…
5. The Integration Pack Registration

continue.

6. On the Select Integration Packs or
Hotfixes page, click Add. Navigate to
the expanded integration packs folder
created earlier. Select the following
integration packs from the File name
drop-down list, and 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
7. When all the integration packs are open,


8. The Completing the Integration Pack
Wizard page will appear with a
summary of selections. Verify the
selections, and click Finish to begin the
integration pack installation.
9. During the installation, each integration

pack will display Microsoft Software
License Terms. Click Accept to continue
with the installation.
10. When complete, each integration pack

will be displayed in the Orchestrator
Deployment Manager interface.

9.4.5 Install the Orchestrator Integration Packs
Complete the following steps to install the Orchestrator Integration Packs.
 Perform the following steps on the Orchestrator runbook server virtual machine.
1. On the Start screen, click the

2. In the Runbook Designer console on

the selected runbook server, right-click
the Integration Packs node and select
Deploy IP to Runbook Server or
Runbook Designer…
3. The Integration Pack Deployment

continue.

4. On the Deploy Integration Packs or
Hotfixes page, select the check boxes
for the following integration packs:
 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
6. On the Computer Selection Details

page, type the name of the Orchestrator
management server and click Add.
When it is added, click Next to
continue.

page, in the Advanced Options section,
select Stop all running Runbooks
before installing the Integration
Packs or Hotfixes. Click Next to
continue.

8. The Completing the Integration Pack
Deployment Wizard will appear with a
summary of selections. Click Finish to
begin the integration pack installation.
9. During the installation each integration

pack will display Microsoft Software
License Terms. Click Accept to continue
with the installation.
10. On the Start screen, click the Runbook

Designer tile.
11. Verify that each integration pack is

displayed in the Runbook Designer
interface.

12. To complete the configuration of the
integration packs, open the
Orchestrator Runbook Designer
Console, click the Options menu, and
click SC 2012 Virtual Machine
Manager.
13. On the Prerequisite Configuration

page, click Add.
14. On the Add Configuration page, fill in

the required information for the Virtual
Machine Manager server and click OK.
page, click Finish to save the changes.

16. While still in the Orchestrator Runbook
Designer Console, click the Options
menu, and click SC 2012 Operations
Manager.
17. On the Microsoft System Center

Operations Manager Connections
page, click Add.
18. On the MS System Center Operations

Manager Connection Settings page,
fill in the required information for the
server, and click Test Connection6.
19. When connectivity is verified, click OK.
6 The use of the Administrator account is used as an example. Use account information that is applicable to your installation.

21. In the Orchestrator Runbook Designer
console, click the Options menu, and
click SC 2012 Service Manager.
22. On the Connections page, click Add.
23. On the Connection page, fill in the

required information for the Operations
Manager management server,7 and click
Test Connection.
24. When connectivity is verified, click OK.
7 The use of the Administrator account is used as an example. Use account information that is applicable to your installation.

10 App Controller
The App Controller installation process includes the high-level steps shown in Figure 10:
Installation of
App Controller
Prerequisites 2012 R2 App
Installation
Controller
Install the .NET

Install App
Framework 3.5
Contoller
Feature
Install Silverlight
Runtime
Request and
Install an SSL
Certificate
Installation of the
Virtual Machine
Manager Console
Figure 10 App Controller installation process

10.1 Overview
This section provides a high-level walkthrough for how to set up App Controller. The following
requirements are necessary for the setup:
 A base virtual machine running Windows Server 2012 R2 has been provisioned for App Controller.
 A SQL Server 2012 SP1 cluster with dedicated instance has been established in previous steps for
App Controller.
 The System Center Virtual Machine Manager console is installed.
 .NET Framework 3.5 is installed.
 Microsoft Silverlight Runtime is installed.
 A Trusted Server Authentication (SSL) Certificate (the CN field of the certificate must match the
server name) is installed.
10.2 Prerequisites
10.2.1 Accounts

<DOMAIN>\ FT-SCAC-SVC App controller service This account needs to be a member
account in the following groups:
 FT-SCAC-Admins
 FT-SCVMM-Admins
Table 16 Accounts
10.2.2 Groups
Group name Purpose Members

<DOMAIN>\ FT-SCAC-Admins App Controller Admin <DOMAIN>\ FT-SCAC-SVC
group <DOMAIN>\ FT-SCVMM-Admins
Table 17 Accounts

The App Controller installation requires that .NET Framework 3.5 is enabled to support installation. Use
the following procedure to enable.NET Framework 3.5.
 Perform the following steps on the App Controller virtual machine.
1. Open Server Manager and navigate to

the Dashboard. In the main pane,
under Configure this local server,
click Add roles and features.
2. The Add Roles and Features Wizard will

appear. On the Before You Begin
page, click Server Selection in the left
pane to continue.

page, select the Select a server from
the server pool button, select the local
server, and then click Features in the
left pane to continue.
4. To add .NET Framework 3.5, on the

Select Features page, in the Features
pane select the .NET Framework 3.5
Features and .NET Framework 3.5
(includes .NET 2.0 and 3.0) check
boxes only. Leave all other check boxes
clear. Click Next to continue.

Settings option is available as a link on
this page to export the options
selected to XML. When exported, they
can be used in conjunction with the
Server Manager module for Windows
PowerShell to automate the installation
of roles and features.
If the server does not have Internet
access, an alternate source path can be
specified by clicking the Specify an
alternate source path link.
For servers without Internet access or if the
.NET Framework 3.5 source files already
exist on the network, an alternate source
location be specified here for the
installation.


performed interactively, the installation of
roles and features can be automated by
using the Server Manager module for
Windows PowerShell.

10.2.4 Install Silverlight

right-click Silverlight.exe and select
2. On the Install Silverlight page, click

Install now.
3. On the Enable Microsoft Update

page, select or clear the Enable
Microsoft Update check box, based
on organizational preferences, and click
Next to continue.
4. On the Installation Successful page,

click Close.

Complete the following steps install the Virtual Machine Manager console on the target App Controller
virtual machines.
 Perform the following steps on the App Controller virtual machines.
1. Log on to the App Controller server as a user

with Administrator privileges. From the
Virtual Machine Manager installation media
source, right-click setup.exe and select Run
as administrator to begin setup.



continue.


appear.Select the option to allow or not
continue.

continue.

continue.


the installation.
10.3 Installation
10.3.1 Install the App Controller Portal Server

Complete the following steps to install the App Controller portal server.
1. Log on to the App Controller virtual machine

as a user with local Admin rights.
Verify the following accounts or groups are

members of the local Administrators group
on the App Controller portal virtual machine:
 Operations Manager action account
 App Controller service account
 App Controller Admins group

2. Log on to the System Center App Controller
server. From the System Center App
Controller installation media source, right-
3. The App Controller Setup Wizard will appear.

Click Install to begin the App Controller
4. On the Enter your product registration

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

this license agreement installation option
continue.

6. On the Install missing software page, the
wizard will detect missing roles and software
and attempt installation of missing
prerequisites. Click Install to enable missing
roles and features.
7. The wizard will display the progress while

installing features.
8. On the Select the installation path page,

accept the default installation location of
Center 2012\App Controller, or click the
Browse button to specify a different location.
After making a selection, click Next to
continue.

9. On the Configure the services page, verify
that the Domain account option is selected,
and specify the App Controller service
account in the Domain and user name text
box. Provide the associated Password in the
supplied text box.
10. In the Port text box, accept the default TCP
port of 18622, or change the port to meet
your organization’s requirements. In most
cases, keep the default port selection.
12. On the Configure the website page, provide

the following information:
 In the Type: HTTPS, in the IP address
text box, select All unassigned from the
drop-down list. Set the Port value to
443.
 Verify that the Use existing certificate
option is selected, and select the proper
Server Authentication certificate that
installed within the virtual machine from
the drop-down list.
Note: Although not recommended, if a Server

Authentication certificate cannot be obtained
and installed on the App Controller server, you
may choose the Generate self-signed
certificate option to satisfy installation
requirements.

14. On the Configure the SQL Server database
page, 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. For the
reference installation the server name is
SCDB.
 Port – Specify the TCP port used for SQL
Server connectivity. . For the reference
installation the port value is 10433.
 Instance name - Specify the instance
name where the AppController database
will be installed (the SCDB instance). . For
the reference installation the instance
name is SCDB.
 Database name – Specify the name of
the App Controller database. In most
cases, use the default value of
AppController.
16. The Help Improve App Controller for

System Center 2012 page provides options
for participating in various product feedback
mechanisms. These include:
Program (CEIP)
 Microsoft Update
17. Select the appropriate options, based on
your organization’s policies, and click Next
to continue.

18. On the Confirm the settings page, verify the
settings provided during the Setup Wizard,
and click Install to begin the installation.
19. The wizard will display the progress while

installing features
20. When complete, the Setup completed

successfully page will appear with progress
of each component. Verify that each
component installed successfully. Note the
App Controller website in the provided text
box.
21. Verify that the Start the App Controller
website when Setup closes check box is
selected, and click Finish.

22. The System Center 2012 App Controller
website will appear. Because no users have
been created in SCVMM, enter in the
administrative account used to install Virtual
Machine Manager (which has been assigned
an admin role in SCVMM).Click Sign in.
23. The App Controller portal will appear. After

validating functionality, the App Controller
installation is considered complete.

11 Service Management Automation (SMA)
The Service Management Automation installation process includes the high-level steps shown in Figure
11:
Installation of
Service Management
Perform Service
Autiomation
Prerequisites Management
Installation
Automation
Add the Web Install the Web

Server Role (IIS) Service
Install the
Runbook Worker
Install the
Powershell
Automation
Module
Figure 11 Service Management Automation installation steps

11.1 Overview
Service Management Automation is a set of tools that is integrated as the Automation extension in
Windows Azure Pack for Windows Server. IT pros and IT developers can use Automation to construct, run,
and manage runbooks to integrate, orchestrate, and automate IT business processes. Automation
runbooks run on the Windows PowerShell workflow engine.
11.2 Prerequisites
11.2.1 Add Web Server Role (IIS)

The Service Management Automation installation requires the Web Server Role and several additional role
features. Use the following procedure to add this role and features to the server.
 Perform the following steps on the Service Management Automation server virtual machine.

the Dashboard node. In the main pane,
under Configure this local server, select
Add roles and features.

appears. On the Before You Begin page,
click Server Selection in the left pane.
(Do not click Next.)
3. On the Select destination server page,

select the Select a server from the
server pool button, select the local
server and then click Features in the left
pane. (Do not click Next.)
4. On the Select Server roles page, select

the Web Server (IIS) role and click Next
to continue.

5. In the Select features section, expand
.NET Framework 4.5 Features item and
then expand the WCF Services item.
Select HTTP Activation and click next to
continue.
6. On the Web Server Role (IIS) page click

Next to continue.
7. On the Select role services page, expand

Security and select the Request
Filtering, Basic Authentication, URL
Authorization and Windows
Authentication checkboxes and then
click Next.

page, verify that the previously selected
roles and features are listed. Ensure that
the Restart each destination server
automatically if required is selected.
Click Install to begin installation.
9. The Installation Progress page will show

the progress of the feature installation.
Click Close when the installation process
completes.
11.3 Installation
11.3.1 Install the Web Service
Complete the following steps to install the Web Service.
1. From the System Center

Orchestrator installation media
source, right-click
setupOrchestrator.exe and select

appear. Under Automation click Web
Service to begin the SMA Web
Service installation Wizard.
3. The Service Management Automation

Wizard will appear. Click Install to
begin the SMA Web Service
installation.

boxes:
evaluation mode.
6. On the License Terms page, verify

that the I have read, understood and
agree with the terms of this license
agreement installation option check
continue.

7. On the Prerequisites page, the wizard
will verify that all system prerequisites
are met. If any prerequisites are not
met, they will be displayed on the
continue.
8. On the Configure the database

server page, specify the following
boxes:
 Server – Specify the name of the
shared System Center SQL
instance.
 Port Number – Specify number
of the SCDB port recorded earlier
in the installation
name of the database. In most
cases, use the default value.
9. Under Authentication Credentials
select Windows Authentication.

11. On the Configure the web service
page, specify the following accounts
in the Domain Security groups or
users with access box:
 SMA Admins Group
 SMA Service Account
12. In the Application pool credentials
section, specify the SMA Service
Account and password
14. On the Configure the web service

page, specify the following
boxes:
 Port Number – Accept the
default of 9090.
15. Under Server Certificate select Use
existing certificate and select the
installed certificate. Note: While a
self-signed certificate can be used, it is
recommended in production
scenarios to use a valid certificate
issued from a trusted certification
authority.
17. On the Specify a location for the

web service files page, accept the
default path, click Next to continue.

Management Automation page,
Microsoft.
19. Under the Microsoft Update portion
of the page. Select the appropriate
option to participate or not participate
in automatic updating.

Review the options selected, and click

wizard will display the Finished page.

installation.

11.3.2 Install the Runbook Worker

source, right-click

appear. Under Automation click
Runbook Worker to begin the SMA
Runbook Worker installation Wizard.
3. The Service Management Automation

begin the SMA Runbook Worker
installation.

4. The On the Product registration
boxes:
evaluation mode.

continue.

continue.

boxes:
Service Reporting Server.
in the installation
11. On the Configure the service

account page, specify the following
boxes:
 Service account credentials –
Specify the SMA Service account.

runbook worker files page, accept
the default path, click Next to
continue.

Management Automation page,
Microsoft.



installation.
11.3.3 Install the Powershell Automation Module


source, right-click

appear. Under Automation click
Powershell Module to begin the
SMA Powershell Module installation.

3. The Install will run silently to install
the Powershell Module.

12 System Center Service Provider
Foundation (SPF) 2012 R2
The System Center Service Provider Foundation (SPF) 2012 R2 installation process includes the high-level
steps shown in Figure 12:
8
Installation of
System Center Service System Center
Perform
Provider Foundation Service Provider
Prerequisites
2012 R2 Installation Foundation 2012
R2
Install IIS Install SPF
Install ASP.NET
Model View
Control (MVC) 4
Install WCF
Install the Virtual

Machine Manager
Console
Figure 12 System Center Service Provider Foundation installation steps

12.1 Overview
Service providers can use Service Provider Foundation technology to offer infrastructure as a service (IaaS)
to their clients. If a service provider has a front-end portal for clients to interact with, Service Provider
Foundation makes it possible for the clients to access the resources on their hosting provider’s system
without making changes to the portal.
This section provides a high-level walkthrough for how to set up Service Provider Foundation. The
following requirements are necessary for the setup:
 A base virtual machine running Windows Server 2012 R2 has been provisioned for Service
Provider Foundation.
Service Provider Foundation.
12.2 Prerequisites
12.2.1 Accounts

<DOMAIN>\ FT-SPF-SVC Service Provider This domain account needs to be a
Foundation service member in the following groups:
account. Account used to
 FT-VMM-Admins
run the SPF service, the
 FT-SPF-Admins
identity for the four SPF IIS
application pools and the  FT-SPF-Provider
account used for VMM  FT-SPF-VMM
access and integration.  FT-SPF-Usage
 <SPF Server>\Administrators
 <SPF Server>\SPF_Admin
 <SPF Server>\SPF_Provider
 <SPF Server>\SPF_Usage
 <SPF Server>\SPF_VMM
<SPF Server>\Local-SPF-SVC Service Provider This local account needs to be a

Foundation local account member in the following groups:
used as the integration
 <SPF Server>\Administrators

account for Windows  <SPF Server>\SPF_Admin
Azure Pack.  <SPF Server>\SPF_Provider
 <SPF Server>\SPF_Usage
 <SPF Server>\SPF_VMM
Table 18 Accounts
12.2.2 Groups

<DOMAIN>\ FT-SPF-Admins Service Provider Admin <DOMAIN>\ FT-SPF-SVC
domain group used to
provide domain accounts
admin rights to all SPF
components and web
services.
<DOMAIN>\ FT-SPF-Provider Service Provider domain Appropriate domain accounts to be
group used to provide delegated permissions to services.
domain accounts access to
the SPF Provider web
service.
<DOMAIN>\ FT-SPF-VMM Service Provider domain Appropriate domain accounts to be
the SPF VMM web service.
<DOMAIN>\ FT-SPF-Usage Service Provider domain Appropriate domain accounts to be
the SPF Usage web service.
<SPF Server>\SPF_Admin Local group created by SPF This local group should contain the
setup process to provide following members:
access to the Admin web
 <SPF Server>\Local-SPF-SVC
service. Domain groups
 <DOMAIN>\FT-SPF-Admins
and accounts must be
added after setup
completes.
<SPF Server>\SPF_Provider Local group created by SPF  <SPF Server>\Local-SPF-SVC
setup process to provide  <DOMAIN>\FT-SPF-Admins
 <DOMAIN>\ FT-SPF-Provider
added after setup
completes.
<SPF Server>\SPF_VMM Local group created by SPF  <SPF Server>\Local-SPF-SVC

service. Domain groups  <DOMAIN>\ FT-SPF-VMM
added after setup
completes.
<SPF Server>\SPF_Usage Local group created by SPF  <SPF Server>\Local-SPF-SVC
 <DOMAIN>\ FT-SPF-Usage
added after setup
completes.
Table 19 Accounts
12.2.3 Add Web Server Role (IIS)

The Service Provider Foundation installation requires the Web Server Role and several additional role
features. Use the following procedure to add this role and features to the server.
 Perform the following steps on the Service Provider Foundation server virtual machine.

the Dashboard node. In the main pane,
under Configure this local server,
select Add roles and features.

page, click Server Selection in the left
pane. (Do not click Next.)

page, select the Select a server from
the server pool button, select the local
server and then click Features in the
left pane. (Do not click Next.)

Framework 3.5 (includes .NET 2.0 and
3.0) check boxes only. Leave all other
check boxes clear. Click Next to
continue.

page, verify that.NET Framework 3.5
Features is listed. Ensure that the
Restart each destination server
automatically if required is not
selected. Click Install to begin
installation.
4. Note: The Export configuration
settings option is available as a link on
this page to export the options selected
to XML. When exported, they can be
used in conjunction with the Server
Manager module for Windows
PowerShell to automate the installation
of roles and features.
5. On the Select role services page,

expand Security and select the
following services and then click Next.
 Web Server
o Common HTTP Features
 Default Document
 Directory Browsing
 HTTP Errors
 Static Content
o Health and Diagnostics
 HTTP Logging
o Performance
 Static Content
Compression
o Security
 Request Filtering
 Basic Authentication
 Windows
Authentication
o Application Development
o Management Tools
 IIS Management
Console
 IIS Management Scripts
and Tools
 Management Service

page, verify that the previously selected
roles and features are listed. Ensure that
the Restart each destination server
automatically if required is selected.
Click Install to begin installation.


12.2.4 Install Microsoft ASP.NET Model View Control (MVC) 4
1. In the Setup Window, select Install.
2. The Setup Progress page will launch and

show the progress of the installation.

3. On the Setup Successful page, select
Close.
12.2.5 Install WCF
1. In the Setup Window, select Install.

2. The Setup Progress page will launch and
show the progress of the installation.
3. On the Setup Successful page, select

Close.

Complete the following steps to install the Virtual Machine Manager console on the target Service
Provider Foundation virtual machine.
 Perform the following steps on the Service Provider Foundation virtual machine.
1. Log on to the Service Provider Foundation

server as a user with Administrator privileges.
From the Virtual Machine Manager
setup.exe and select Run as administrator
to begin setup.



continue.


appear. Select the option to allow or not
continue.

continue.

continue.


the installation.
12.3 Installation
12.3.1 Install System Center Service Provider Foundation 2012 R2

Complete the following steps to install Service Provider Foundation 2012 R2.

source, right-click

appear. Under Standalone
Installations click Service Provider
Foundation to begin the SPF
installation Wizard.

3. The Service Provider Foundation
begin the Service Provider Foundation
installation.

continue.

continue.

boxes:
shared System Center SQL
instance.
in the installation

SPF files page, specify the following
boxes:
 Install in folder – Accept the
default of C:\inetpub.
 Website name – Accept the
default name of SPF
 Port Number – Accept the
default of 8090.
10. Under Server Certificate select Use
existing certificate and select the
installed certificate. Note: While a
self-signed certificate can be used, it is
recommended in production
scenarios to use a valid certificate
issued from a trusted certification
authority.

12. On the Configure the Admin web
service page, specify the following
accounts in the Domain Security
groups or users with access box:
 Administrator
 SPF Admins group
section, specify the SPF Service
15. On the Configure the Provider web

 Administrator
 SPF Provider group
18. On the Configure the VMM web

 Administrator
 SPF VMM group

21. On the Configure the Usage web
 Administrator
 SPF Usage group

Provider Foundation page, select the
in the CEIP by providing selected
system information to Microsoft.



installation.

13 Service Reporting
The Service Reporting installation process includes the high-level steps shown in Figure 11:
Installation of
System Center 2012 R2 Perform System Center
Service Reporting Prerequisites 2012 R2 Service
Reporting
Install the .NET

Install Service
Framework 3.5
Reporting
Feature
Install SQL 2012

SP1
Install SQL Server

Analysis
Management
Objects
Figure 12 Service Reporting installation steps

13.1 Overview
Service Reporting in System Center 2012 R2 enables administrators at IT hosting providers to view tenant
consumption of virtual machines, resources (computation, network, and storage), and operating system
inventory in their infrastructure.
This section provides a high-level walkthrough for how to set up Service Reporting. The following
requirements are necessary for the setup:
 A base virtual machine running Windows Server 2012 R2 has been provisioned for Service
Reporting.
App Controller.
 .NET Framework 3.5 is installed.
 Microsoft Silverlight Runtime is installed.
13.2 Prerequisites
13.2.1 Accounts
No specific service accounts are required for this component
13.2.2 Groups
No specific groups are required for this component.

The Reporting Services installation requires that .NET Framework 3.5 is enabled to support installation.
Use the following procedure to enable .NET Framework 3.5.
 Perform the following steps on Service Reporting virtual machine.

this local server, select Add roles
and features.
10. The Add Roles and Features

Wizard appears. On the Before You
in the left pane. (Do not click Next.)

the local server and then click
Features in the left pane. (Do not
click Next.)

to continue.

Note: The Export configuration
settings option is available as a link
they can be used in conjunction with
the Server Manager module for


Windows PowerShell.
13.2.4 Install SQL Server 2012 SP1
 Perform the following steps on the Server Reporting server virtual machine.

SQL Server Installation Center will
appear. Click Installation in the left
pane. Then click New SQL Server
features to an existing installation.

2. The Setup Support Rules Wizard will
appear. Click Ok to continue.

Enter the product key option and
enter the associated product key in
continue.

option, and then click Evaluation
from the drop-down list for a 180-
day evaluation period.


6. The Setup Support Rules Wizard will

appear. Click Ok to continue.
7. On the Setup Role page, select SQL

Server Feature Installation, and

make the following selections:
o Analysis Services
o Integration Services
o Management Tools-Basic
o Management Tools-
Complete
9. When all selections are made, click
Next to continue.

continue.
11. On the Instance Configuration ,

select the Named instance option. In
the provided text box, specify the
instance name being installed:
 Instance ID – Specify the
instance name being installed.
Verify that it matches the Named
instance value.
Server.

continue.

click the Service Accounts tab.
Specify the SQL Server Service
Account and an associated password
for the SQL Server Agent, SQL
Server Database Engine, SQL
Server Analysis Services and SQL
Server Integration Services 11.0
services.
Note: For the SQL Server Agent set

the Startup Type to Automatic.
15. On the Database Engine

Configuration tab. In the
Authentication Mode section, select
the Windows authentication mode
option. In the Specify SQL Server
administrators section, click the
Add… button to add SQL Server
Service Account.

Configuration tab. In the Specify
which users have administrative
permissions for Analysis Services
section, click Add… to add the SQL
Service Service account.

Next to continue.


21. On the Installation Progress page,
the installation progress will be
displayed.

the Complete page will appear. Click
Close.

13.3 Installation
13.3.1 Install Service Reporting
Complete the following steps to install Service Reporting.
 Perform the following steps on the Service Reporting server virtual machine.
1. Log on to the Service Reporting virtual

machine as a user with local Admin
rights.
Verify the following accounts or

Administrators group on the App
Controller portal virtual machine:
 SQL service account
 SQL Admins group

source, right-click

appear. Under Standalone Installation
click Service Reporting to begin the
Service Reporting server installation
Wizard.
4. The Service Reporting Setup Wizard

will appear. Click Install to begin the
Service Reporting server installation.

continue.

continue.

default location of
Center 2012 R2\Service Reporting for
continue.

8. On the Configure Service Reporting
Data Warehouse page, specify the
text boxes:
name of the Service Reporting
Server.
 SQL Server instance – Specify the
name of the SQL Server database
Reporting installation.
boxes:
 ETLRepository DB – Specify the
name of the ETL Repository
default value.
 Staging DB – Specify the name of
the Staging database. In most
 Data Warehouse DB – Specify
the name of the Data Warehouse
default value.

11. On the Configure Analysis Server
page, specify the following
boxes:
name of the Service Reporting
Server.
 SQL Server instance – Specify the
name of the SQL Server database
Reporting installation.
boxes:
 Analysis DB – Specify the name
of the Analysis database. In most

System Center Service Reporting
page, select the option to participate
or not participate in the CEIP by
providing selected system information
to Microsoft.


19. Check the Initiate machine wide
Automatic Update box.
installation.

14 Windows Azure Pack (WAP)
The Windows Azure Pack installation process includes the high-level steps shown in Figure 13:
Installation of
Windows Azure Pack Perform
Windows Azure
2012 R2 Installation Prerequisites
Pack 2012 R2
Configure SQL Install the First

Instance Windows Azure
Permissions Pack Server
Deploy .NET 4.5 Install the Second

Extended with Windows Azure
ASP.NET Pack Server
Deploy IIS
Recommended
Configfuration
Figure 13 Windows Azure Pack 2012 R2 installation steps
14.1 Overview
Windows Azure Pack for Windows Server is a collection of Windows Azure technologies, available to
Microsoft customers at no additional cost for installation into your data center. It runs on top of Windows

Server 2012 R2 and System Center 2012 R2 and, through the use of the Windows Azure technologies,
enables you to offer a rich, self-service, multi-tenant cloud, consistent with the public Windows Azure
experience.
14.2 Prerequisites
14.2.1 Accounts

<DOMAIN>\ FT-WAP-SVC Windows Azure Pack  N/A
service account. Account
used to run Web Sites and
Portal services.
Table 20 Accounts
14.2.2 Groups
No specific groups are required for this component.
14.2.3 Configure SQL Instance Permissions
 Perform the following steps on the SQL Cluster virtual machine.
1. Open SQL Server Management Studio

2. On the Connect to Server page, input
the connection values for the WAPDB
instance. Select Connect to connect to
the instance.
3. Right-click on the WAPDB instance, and

select Properties.

4. In the Server Properties Window, select
Security.
5. Ensure that SQL Server and Windows
Authentication mode is selected.
6. Click Ok.
7. Expand Security, and the Logins.

8. Right-click on the sa account and select
Properties.

9. In the Login Properties Window, select
Status on the left-hand side.
10. Under Login, ensure Enabled is selected.
11. Click Ok.
14.2.4 Deploy .NET 4.5 Extended with ASP.NET
 Perform the following steps on both Windows Azure Pack server virtual machines.
1. Open up Internet Explorer and navigate

to -
http://www.microsoft.com/web/downloa
ds/platform.aspx
2. Click Free Download.
3. When the “Do you want to run or save”
Windows pops up, click Run.

4. In Web Platform Installer 4.6, select
Products, then in the search bar type
.NET 4.5 Extended with ASP.NET, click
Enter.
5. Click Add.
6. Click Install.

7. On the Prerequisites page, select I
Accept.
8. On the Install page, monitor the

Installation progress.
9. On the Finish page, verify everything

installed correctly, then click Finish.

14.2.5 Deploy IIS Recommended Configuration
 Perform the following steps on both Windows Azure Pack server virtual machines.

Products, then select IIS
Recommended Configuration, click
Add.
2. Click Install.
3. On the Prerequisites screen, click I

Accept.
1. On the Use Microsoft Update to help

keep your computer secure and up to
date page, select the appropriate option
to participate or not participate in
automatic updating.
2. Click Continue.



14.3 Installation
14.3.1 Install First Windows Azure Pack Server

Complete the following steps to install Windows Azure Pack.
 Perform the following steps on the first Windows Azure Pack server virtual machine.

Products, then select Add for each of
the following:
o Windows Azure Pack:
Tenant API
Admin Site
Admin API
Admin Authentication Site
2. Click Install.

Accept.

date page, select the appropriate
4. Click Continue.


5. On the Configure Screen, click
Continue.
6. In Internet Explorer, select Continue

to this website (not recommended).

boxes:
of the Windows Azure Database
Instance.
SQL Server Authentication.
 Database Server Admin
Username – Specify the Windows
Azure Pack Database Instance sa
account.
Password – Specify the Windows
password.
8. Under Configuration store, specify
and confirm a PassPhrase.
9. Click the Arrow to continue.
10. On the Customer Experience

Improvement Program Page, select
Microsoft.

12. On the Ready to configure page,
verify the features.
13. Click the Check box to continue.
14. On the Features Configured Page,

verify the application installed
correctly.
15. Select the Check box to continue.
16. On the popup select Yes.

14.3.2 Install Second Windows Azure Pack Server

Complete the following steps to install Windows Azure Pack Site.
 Perform the following steps on the second Windows Azure Pack server virtual machine.

Products, then select Add for each of
the following:
Tenant Public API
Tenant Site
Tenant Authentication Site
2. Click Install.

Accept.

date page, select the appropriate
6. Click Continue.


8. On the Configure Screen, click
Continue.
9. In Internet Explorer, select Continue

to this website (not recommended).

boxes:
of the Windows Azure Database
Instance.
SQL Server Authentication.
Username – Specify the Windows
account.
Password – Specify the Windows
password.
11. Under Configuration store, specify
and confirm a PassPhrase.
13. On the Customer Experience

Improvement Program Page, select
Microsoft.

15. On the Ready to configure page,
verify the features.
16. Click the Check box to continue
17. On the Features Configured Page,

verify the application installed
correctly.
18. Select the Check box to continue.
19. On the popup select Yes.


15 Deployment Using PowerShell
Deployment Toolkit
The IaaS PLA Deployment Guide provides guidance on how to perform an interactive deployment of the
prescribed architecture. While performing an interactive deployment is required in many deployment
scenarios, having a fully automated approach to deploying the IaaS PLA Architecture would save many
hours of work and make the deployment a reproducible action.
The PowerShell Deployment Toolkit (PDT) provides the framework to automate the deployment of the
IaaS PLA Architecture. The toolkit consists of a set of PowerShell scripts and configuration files that used
together can automate the collection of installation prerequisite files, creation of virtual machines
(including OS and domain join), advanced configuration of the virtual machines, installation of the System
Center and other software components, and integration between components.
PDT supports different deployment modes based on the configuration of the files or the way PDT tools
are leveraged.
 GreenField - Creates a new forest and installs the scenario into that forest
 Integration - Creates VMs and install the scenario into an existing forest
 Pre-Existing - Uses pre-existing servers (Virtual or physical) and installs the scenario into an existing
forest
 Intelligent Restart - Validates existing deployed scenario and adds only what is missing
Greenfield is used for most lab and POC deployments or for a customer that wants to start from scratch.
Integration is the typical deployment mode where the customer already has an existing active directory
and other established services and PDT should be run to leverage those services. Pre-Existing mode
supports an environment where the virtual machines or physical servers have already been deployed and
joined to the domain and PDT just needs to configure the machines and then perform the installation.
Intelligent restart deployment mode allows you to add roles/features to a previous deployment, or allows
you to fix a failed deployment scenario and rerun the deployment. In this mode, PDT verifies all existing
deployed components/roles and skips them if already complete.
Only the greenfield deployment mode requires a <DOMAIN> section exist in the variable.xml. This
requires that the information on the forest that will be created and the VM that will be used as the
domain controller for the forest.
PDT consists of the following base tools:
 Workflow.xml – defines all possible deployment building blocks and default settings
 Downloader.ps1 – downloads prerequisites from the Internet
 VMCreator.ps1 – Creates Virtual machines
 Installer.ps1 – Installs roles and components on the virtual machines or physical servers
 Variable.xml – Defines the deployment scenario and settings
Optionally you can also have a per VM scripts that are run prior to the Installer.ps1 script. These are used
to perform machine configuration and special actions like building clusters.
Workflow versus Variable
Workflow defines all the possible variables that are required and specifies default values. Unless a
variable in workflow.xml is tagged with Required =True, it does not have to be placed in the
variable.xml unless the default values in workflow are not acceptable. You can specify all variables
in variable.xml and they override the default workflow.xml values. The PDT code loads all values
from Workflow.xml, then loads all values from variable.xml, overwriting any default values from
workflow.xml.
To use PDT the following minimum steps are required:
 Run the Downloader.ps1 script to download all the prerequisites from the Internet into a Source
folder (this only has to be done once to generate the source folder)
 Add the customers System Center and Windows source files to the source folder
 Edit the variable.xml to match the deployment scenario and specify information like product keys
 Modify the optional per-VM scripts depending on the deployment scenario requirements
 Run the VMCreator.ps1 script to create all the required virtual machines
 Run the Installer.ps1 script to install all the of the roles and components
The following sections will describe each of these steps and provide insight into how the PDT engine
works. The steps will use an example variable.xml file for the IaaS PLA architecture.
15.1 Obtaining PDT Files

PDT is published on the TechNet Gallery and freely downloadable from
http://gallery.technet.microsoft.com/
 Perform the following steps on a machine with Internet access.
1. To download the PDT installation files,

open
http://gallery.technet.microsoft.com/
2. Search for “PDT”

3. Sort by Release Date to find the latest
version of PowerShell Deployment
Toolkit
4. Download the latest version of the

PowerShell Deployment Toolkit and
expand the files to C:\PDT-PLA

15.2 Creating Source Folder
Perform the following steps to create the source folder that is required to perform a PDT installation. This
involves running the downloader.ps1 to get the prerequisites and then coping System Center and
Windows source.
 Perform the following steps on a machine with Internet Access and PDT installed in C:\PDT-PLA.
1. Open an administrative PowerShell

Prompt with Administrator
permissions by Right-clicking the
PowerShell taskbar icon and selecting
“Run As Administrator”
2. Change the current directory to the

location where you extracted the files
(e.g. - C:\PDT-PLA)

Execute the Downloader.ps1 script
(.\Downloader.ps1). The variable.xml
will be referenced for a global variable
called DOWNLOAD for the path to
store the downloads
Optional Syntax:
.\Downloader.ps1 –
deploymentonly
Only downloads the prerequisites for
the defined variable.xml deployment
scenario
.\Downloader.ps1 –Path
C:\<Downloadfolder>
Specifies the path to variable and
workflow files (default is local path)
3. The files will be downloaded and

placed in the folder specified by the
DOWNLOAD value in the
variable.xml. In this example
C:\PDTDOWNLOAD
4. Once the download is complete the

remaining Windows and System
Center source files must be copied.
In the C:\PDTDOWNLOAD folder

create a directory called
WindowsServer2012 and copy the
contents of a Windows Server 2012
ISO to that folder
5. In the C:\PDTDOWNLOAD folder

create a directory called
WindowsServer2012R2 and copy the
contents of a Windows Server 2012 R2
ISO to that folder

6. In the
C:\PDTDOWNLOAD\SystemCenter2
012R2 folder create a directory called
AppController and copy the contents
of a App Controller 2012 R2 ISO to
that folder
7. In the
VirtualMachineManager and copy
the contents of a Virtual Machine
Manager 2012 R2 ISO to that folder
8. In the
ServiceManager and copy the
contents of a Service Manager 2012
R2 ISO to that folder

9. In the
OperationsManager.en and copy the
contents of an Operations Manager
2012 R2 ISO to that folder
10. In the
Orchestrator and copy the contents
of an Orchestrator 2012 R2 ISO to that
folder

11. Optional: SQL 2012 supports the
ability to automatically integrate
updates into the deployment. If you
want the current Cumulative Update
to be part of the deployment, you
need to download the update and
extract it to
C:\Installer\SQLServer2012.en\Upd
ates folder
15.3 Creating Deployment Scenario File

In order to deploy the IaaS PLA Architecture using PDT, you must modify the sample Variable.xml file
based on the scenario that is being deployed.
The Variable.xml file is broken down into five major sections
 Global Variables
 Components
 Roles
 SQL
 VMs
The following sections explains the different sections and items that would need to be modified per
customer scenario.
15.3.1 Global Variables
The top of the variable.xml file has a section for global variables
<Variable Name="RegisteredUser" Value="Microsoft Corporation" />

<Variable Name="RegisteredOrganization" Value="Microsoft Corporation" />
<Variable Name="InstallerServiceAccount" Value="CONTOSO\Installer" />
<Variable Name="InstallerServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SourcePath" Value="$SystemDrive\InstallerRTM" />
<Variable Name="Download" Value="C:\PDTDownload" />
<Variable Name="SystemCenter2012R2ProductKey" Value="*****-*****-*****-*****-*****"
/>
<Variable Name="SystemCenter2012ProductKey" Value="*****-*****-*****-*****-*****" />

Each of these variables have values that must be specified
 InstallerServiceAccount – the Account that will be used by PDT to perform the installation. This
account must have local admin rights on each VM. By default during a greenfield deployment, this
account is created in the domain for you. In all other deployment modes, this account must be pre-
created before the installer.ps1 is run.
 InstallerServiceAccountPassword – this is the clear text password for the installation account.
 SourcePath – This is the folder that the source files will be copied from during deployment
 Download – This is the folder that downloader.ps1 will use to store the download files.
 SystemCenter2012Productkey – This is the customer product key
 SystemCenter2012R2Productkey – This is the customer product key
Typically the SourcePath and Download variables are the same.
15.3.2 Components
The <Components> section defines the input variables that will be used during the role installation. Each
component in the Components section is framed by a <Component> section. The variables for that
component are specified within that section.
To understand what component variables are required for a role, you can go to the WORKFLOW.XML file
in the <Components> section to see all the defined possible variables. Only those with the designator
Required=”True” are required to be specified in the variable.xml, assuming the defaults values in the
workflow.xml are acceptable values.
For example, in the workflow.xml file for the System Center 2012 R2 Virtual Machine Manager role, the
following variables are defined in the component section
<Component Name="System Center 2012 R2 Virtual Machine Manager">

<Variable Name="SystemCenter2012R2VirtualMachineManagerAdminGroup" Value="" Principal="True" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerProgramFiles" Value="$SystemDrive\Program
Files\Microsoft System Center 2012 R2\Virtual Machine Manager" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerDatabase" Value="VirtualManagerDB" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerIndigoTcpPort" Value="8100" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerWSManTcpPort" Value="5985" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerBitsTcpPort" Value="443" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerIndigoNETTCPPort" Value="8102" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerIndigoHTTPSPort" Value="8101" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerIndigoHTTPPort" Value="8103" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerLibraryPath" Value="$SystemDrive\ProgramData\Virtual
Machine Manager Library Files" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerServiceAccount" Value="$InstallerServiceAccount" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerServiceAccountPassword"
Value="$InstallerServiceAccountPassword" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerVmmServerName" Value="" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerTopContainerName" Value="" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerVMMStaticIPAddress" Value="" />
</Component>

As you can see, there are no variables that have a Required=True designation, so if all the default values
are acceptable, there is no requirement for a VMM 2012 R2 component section in the variable.xml. In the
provided example scenario files, the default values are not acceptable for some variables, so they are
specified in the variable.xml

<Variable Name="SystemCenter2012R2VirtualMachineManagerAdminGroup" Value="CONTOSO\VMM Admins" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerServiceAccount" Value="CONTOSO\VMM-SVC" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerTopContainerName" Value="CN=VMMDKM,DC=CONTOSO,DC=COM"
/>
<Variable Name="SystemCenter2012R2VirtualMachineManagerVmmServerName" Value="VMM01.CONTOSO.com" />
<Variable Name="SystemCenter2012R2VirtualMachineManagerVMMStaticIPAddress" Value="192.168.1.102" />
</Component>
The last three variables are only required for a scenario where VMM is being deployed in HA mode. The
TopContainerName is the container in AD that will be created or must exist for Distributed Key
Management to be installed and configured. The ServerName is the cluster group name for the HA install,
and the StaticIPAddress is the IP address of the cluster resource.
The variable.xml file has many variables that have values that must be modified for the customer
environment.
 the NetBIOS or FQDN domain name (i.e. CONTOSO or Contoso.com)

 IP addresses – the IP address of the Cluster name, IP addresses for SQL clusters
 Service Accounts – CONTOSO\SCO-SVC
 Admin Groups – CONTOSO\SCO Admins
 Service Account Passwords – “P@ssw0rd”
 Path – C:\Websites
Component Editing
Component sections can be part of the variable.xml file even if there is no corresponding role that
is being deployed. This minimizes the editing required in the case that a role is not needed for a
current deployment scenario.
If the variable.xml file does not have a <component> section for a role that you would like to deploy, then
you can get the potential component variables by opening the workflow.xml file, search for the
<Components> section, finding the associated component, then copying that component section to the
variable.xml. The section copied from the workflow will require slight editing.
As an example, let’s say you want to deploy Configuration Manager 2012 R2, but you do not have the
component section in the variable.xml. You copy that component section from workflow and paste it in
the variable.xml
<Component Name="System Center 2012 R2 Configuration Manager">

<Variable Name="SystemCenter2012R2ConfigurationManagerAdminGroup" Value="" Principal="True" />
<Variable Name="SystemCenter2012R2ConfigurationManagerInstallDir" Value="$SystemDrive\Program
Files\Microsoft System Center 2012 R2\Configuration Manager" />
<Variable Name="SystemCenter2012R2ConfigurationManagerConsoleTargetDir" Value="$SystemDrive\Program Files
(x86)\Microsoft Configuration Manager\AdminConsole" />
<Variable Name="SystemCenter2012R2ConfigurationManagerDatabase" Value="" Required="True" />
<Variable Name="SystemCenter2012R2ConfigurationManagerSiteCode" Value="" Required="True" />
<Variable Name="SystemCenter2012R2ConfigurationManagerSite" Value="" Required="True" />
</Component>

This component section needs to have some text removed, and then values need to be specified. The text
that needs to be removed is highlighted in yellow. Notice the multiple values that have Required=True
specified and are required to exist in the variable.xml. If you remove the text that does not belong and
add the values that are blank, you get something like.

<Variable Name="SystemCenter2012R2ConfigurationManagerAdminGroup" Value="Contoso\CM-Admins" />
<Variable Name="SystemCenter2012R2ConfigurationManagerInstallDir" Value="$SystemDrive\Program
Files\Microsoft System Center 2012 R2\Configuration Manager" />
<Variable Name="SystemCenter2012R2ConfigurationManagerConsoleTargetDir" Value="$SystemDrive\Program Files
(x86)\Microsoft Configuration Manager\AdminConsole" />
<Variable Name="SystemCenter2012R2ConfigurationManagerDatabase" Value="SCCMDB" />
<Variable Name="SystemCenter2012R2ConfigurationManagerSiteCode" Value="CM-S01" />
<Variable Name="SystemCenter2012R2ConfigurationManagerSite" Value="CORP" />
</Component>
Duplicate Variable Values
The scripts load the values from the workflow.xml first, then overwrite them with the values
specified in the variable.xml. There is no issue with having the same values in the workflow and
the variable, since the end result will be the same.
15.3.2.1 Virtual Machine Manager 2012 R2 Component

The following is a sample component section for Virtual Machine Manager 2012 R2

<Variable Name="SystemCenter2012R2VirtualMachineManagerTopContainerName" Value="CN=VMMDKM,DC=CONTOSO,DC=COM"
/>
</Component>
Cluster specific variables
The last three variables in the component section above only apply to the creation and
configuration of a VMM HA clustered installation.
15.3.2.2 Orchestrator 2012 R2 Component

The following is a sample component section for Orchestrator 2012 R2
<Component Name="System Center 2012 R2 Orchestrator">

<Variable Name="SystemCenter2012R2OrchestratorAdminGroup" Value="CONTOSO\SCO Admins" />
<Variable Name="SystemCenter2012R2OrchestratorServiceAccount" Value="CONTOSO\SCO-SVC" />
<Variable Name="SystemCenter2012R2OrchestratorServiceAccountPassword" Value="P@ssw0rd" />
</Component>
15.3.2.3 App Controller 2012 R2 Component

The following is a sample component section for App Controller 2012 R2
<Component Name="System Center 2012 R2 App Controller">

<Variable Name="SystemCenter2012R2AppControllerAdminGroup" Value="CONTOSO\SCAC Admins"/>
<Variable Name="SystemCenter2012R2AppControllerServiceAccount" Value="CONTOSO\SCAC-SVC" />
<Variable Name="SystemCenter2012R2AppControllerServiceAccountPassword" Value="P@ssw0rd" />
</Component>

15.3.2.4 Operation Manager 2012 R2 Component
The following is a sample component section for Operations Manager 2012 R2
<Component Name="System Center 2012 R2 Operations Manager">

<Variable Name="SystemCenter2012R2OperationsManagerAdminGroup" Value="CONTOSO\SCOM Admins"/>
<Variable Name="SystemCenter2012R2OperationsManagerManagementGroupName" Value="SCOM_Contoso"/>
<Variable Name="SystemCenter2012R2OperationsManagerActionServiceAccount" Value="CONTOSO\SCOM-ACTION"/>
<Variable Name="SystemCenter2012R2OperationsManagerActionServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2OperationsManagerDASServiceAccount" Value="CONTOSO\SCOM-SVC"/>
<Variable Name="SystemCenter2012R2OperationsManagerDASServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2OperationsManagerDataReaderServiceAccount" Value="CONTOSO\SCOM-DR"/>
<Variable Name="SystemCenter2012R2OperationsManagerDataReaderServiceAccountPassword" Value="P@ssw0rd"/>
<Variable Name="SystemCenter2012R2OperationsManagerDataWriterServiceAccount" Value="CONTOSO\SCOM-DW"/>
<Variable Name="SystemCenter2012R2OperationsManagerDataWriterServiceAccountPassword" Value="P@ssw0rd"/>
</Component>
15.3.2.5 Service Manager 2012 R2 Component

The following is a sample component section for Service Manager 2012 R2
<Component Name="System Center 2012 R2 Service Manager">

<Variable Name="SystemCenter2012R2ServiceManagerAdminRoleGroup" Value="CONTOSO\SCSM Admins"/>
<Variable Name="SystemCenter2012R2ServiceManagerServicesServiceAccount" Value="CONTOSO\SCSM-SVC" />
<Variable Name="SystemCenter2012R2ServiceManagerServicesServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceManagerWorkflowServiceAccount" Value="CONTOSO\SCSM-WF" />
<Variable Name="SystemCenter2012R2ServiceManagerWorkflowServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceManagerReportingServiceAccount" Value="CONTOSO\SCSM-SSRS" />
<Variable Name="SystemCenter2012R2ServiceManagerReportingServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceManagerAnalysisServiceAccount" Value="CONTOSO\SCSM-OLAP" />
<Variable Name="SystemCenter2012R2ServiceManagerAnalysisServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceManagerPortalServiceAccount" Value="CONTOSO\SCSM-Portal" />
<Variable Name="SystemCenter2012R2ServiceManagerPortalServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceManagerManagementGroupName" Value="SM_Contoso"/>
<Variable Name="SystemCenter2012R2ServiceManagerDatawarehouseManagementGroupName" Value="DW_Contoso"/>
<Variable Name="SystemCenter2012R2ServiceManagerPortalUsers" Value="CONTOSO\Domain Users"/>
</Component>
15.3.2.6 Service Provider Foundation 2012 R2 Component

The following is a sample component section for Service Provider Foundation 2012 R2
<Component Name="System Center 2012 R2 Service Provider Foundation">

<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCVMMServiceAccount" Value="CONTOSO\SPF-SVC" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCVMMServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationVMMSecurityGroupUsers" Value="CONTOSO\SPF Admins"
/>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCAdminServiceAccount" Value="CONTOSO\SPF-SVC" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCAdminServiceAccountPassword" Value="P@ssw0rd"
/>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationAdminSecurityGroupUsers" Value="CONTOSO\SPF
Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccount" Value="CONTOSO\SPF-SVC"
/>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccountPassword"
Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationProviderSecurityGroupUsers" Value="CONTOSO\SPF
Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCUsageServiceAccount" Value="CONTOSO\SPF-SVC" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCUsageServiceAccountPassword" Value="P@ssw0rd"
/>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationUsageSecurityGroupUsers" Value="CONTOSO\SPF
Admins" />
</Component>
15.3.2.7 Service Management Automation 2012 R2 Component

The following is a sample component section for Service Management Automation 2012 R2
<Component Name="System Center 2012 R2 Service Management Automation">

<Variable Name="SystemCenter2012R2ServiceManagementAutomationAdminGroup" Value="CONTOSO\SMA-Admins" />
<Variable Name="SystemCenter2012R2ServiceManagementAutomationServiceAccount" Value="CONTOSO\SMA-SVC" />
<Variable Name="SystemCenter2012R2ServiceManagementAutomationServiceAccountPassword" Value="P@ssw0rd" />
</Component>

Naming restrictions
SMA does not support blanks in the Admin Group variable.
15.3.2.8 Service Reporting 2012 R2 Component

The following is a sample component section for Service Reporting 2012 R2
<Component Name="System Center 2012 R2 Service Reporting">

<Variable Name="SystemCenter2012R2ServiceReportingRunAsAccount" Value="Contoso\SR-SVC" />
<Variable Name="SystemCenter2012R2ServiceReportingInstallFolder" Value="$SystemDrive\Program Files\Microsoft
System Center 2012 R2\Service Reporting" />
<Variable Name="SystemCenter2012R2ServiceReportingRepositoryDatabaseName" Value="UsageETLRepositoryDB" />
<Variable Name="SystemCenter2012R2ServiceReportingStagingDatabaseName" Value="UsageStagingDB" />
<Variable Name="SystemCenter2012R2ServiceReportingDWDatabaseName" Value="UsageDatawarehouseDB" />
<Variable Name="SystemCenter2012R2ServiceReportingAnalysisDatabaseName" Value="UsageAnalysisDB" />
</Component>
15.3.2.9 Windows Azure Pack Component

The following is a sample component section for Windows Azure Pack
<Component Name="Windows Azure Pack 2013">

<Variable Name="WindowsAzurePack2013AdminGroup" Value="CONTOSO\WAP Admins" />
<Variable Name="WindowsAzurePack2013ConfigStorePassphrase" Value="P@ssw0rd" />
</Component>
15.3.2.10 Windows Azure Pack WebSites Component

The following is a sample component section for Windows Azure Pack WebSites
<Component Name="Windows Azure Pack 2013 Websites">

<Variable Name="WindowsAzurePack2013WebsitesControllerServerName" Value="SitesCN01.Contoso.com" />
<Variable Name="WindowsAzurePack2013WebsitesOfflineSourceDir"
Value="$TempPath\Installer\$WindowsAzurePack2013WebsitesOfflineSource\Offline_Feeds" />
<Variable Name="WindowsAzurePack2013WebsitesOfflineHostFeedDir" Value="$SystemDrive\Hosted_Feeds" />
<Variable Name="WindowsAzurePack2013WebsitesVMServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesVMServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesCloudServiceAccount" Value="Contoso\cloudadmin" />
<Variable Name="WindowsAzurePack2013WebsitesCloudServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesDbPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesDnsSuffix" Value="websites.Contoso.com"/>
<Variable Name="WindowsAzurePack2013WebsitesDBServer" Value="SitesDB01" />
<Variable Name="WindowsAzurePack2013WebsitesFileServer" Value="SitesFS01"/>
<Variable Name="WindowsAzurePack2013WebsitesFileServerType" Value="WindowsSingle" />
<Variable Name="WindowsAzurePack2013WebsitesSQLAdmin" Value="sa" />
<Variable Name="WindowsAzurePack2013WebsitesCTLServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesCTLServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesMGMTServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesMGMTServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesFSServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesFSServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesWWServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesWWServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesFEServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesFEServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesPBServiceAccount" Value="Contoso\WAPWEB-SVC" />
<Variable Name="WindowsAzurePack2013WebsitesPBServiceAccountPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesFileShareOwnerUser" Value="Contoso\FileShareOwner" />
<Variable Name="WindowsAzurePack2013WebsitesFileShareOwnerPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesFileShareUserName" Value="Contoso\FileShareUser" />
<Variable Name="WindowsAzurePack2013WebsitesFileShareUserPassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesCertStoreUserName" Value="Contoso\CertStoreUser" />
<Variable Name="WindowsAzurePack2013WebsitesCertStorePassword" Value="Pass@word1" />
<Variable Name="WindowsAzurePack2013WebsitesContentSharePath"
Value="\\$WindowsAzurePack2013WebsitesFileServer\WebSites" />
<Variable Name="WindowsAzurePack2013WebsitesContentShareLocalPath" Value="C:\WebSites" />
<Variable Name="WindowsAzurePack2013WebsitesCertSharePath"
Value="\\$WindowsAzurePack2013WebsitesFileServer\Certificates" />
<Variable Name="WindowsAzurePack2013WebsitesCertShareLocalPath" Value="C:\Certificates" />
<Variable Name="WindowsAzurePack2013WebsitesOfflineFeedServer" Value="SitesOffline.Contoso.com" />

<Variable Name="WindowsAzurePack2013WebsitesCustomFeed"
Value="http://$WindowsAzurePack2013WebsitesOfflineFeedServer/BootStrapperFeed/feeds/latest/BootstrapperEntries
.xml" />
</Component>
Syncing Variable Values
The values for variable values for the DNSSuffix, FileShare and CertStore accounts/groups must be
syncd between the Component section and the section in DC01.PS1 preinstall script that actually
creates the values.
15.3.3 Roles
The <Roles> section defines System Center, SQL tools, Windows Azure Pack roles or any other defined
role that exists in the workflow.xml that will be deployed as part of a scenario.
Roles defines every installable component for an installation. For example, a Virtual Machine Manager
deployment consists of a management server, a database server, a console server, and in a High
Availability deployment scenario, the cluster nodes.
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server" Server="SCVMMDB.CONTOSO.com"
Instance="SCVMMDB" SQLCluster="True" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Management Server" Server="VMM01.CONTOSO.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Console" Server="RD01.contoso.com"/>
Alternative HA roles
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Active Management Server"
Server="VMM01A.CONTOSO.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Passive Management Server"
Server="VMM01B.CONTOSO.com" />
You can see the syntax of a role statement includes
 Role Name
 Server the role is deployed
 Instance name of the database if the role is for a database (MSSQLSERVER or a named instance)
 Optionally the specification that the SQL instance is actually clustered
You can deploy each role component on a separate server or combined on a single server (assuming the
product supports the consolidated scenario). So if you wanted to deploy
Cluster or not to cluster roles
In the example above, you would either specify the single management server for a non-HA
deployment, or the alternative lines for the two cluster servers in an HA scenario, but not both.
Note that the actual creation of the cluster is not a native feature of PDT role installation. The
cluster has to be built prior to running the Installer.ps1 script. One way of accomplishing that is to
use the per VM pre-installer script.

Cluster or not to cluster SQL
In the example above, the Database Server specifies a named instance SCVMMDB and specifies
that the instance should be clustered.
If you did not want to cluster SQL, the role line would look like
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server"

Server="VMM01.CONTOSO.com" Instance="SCVMMDB" />
The Server name can specify the VMM management server for a local SQL install or a remote
non-clustered SQL server.
Preexisting SQL Server Instances
Some corporate environments highly restrict who can install and access SQL servers and SQL
instances. To support the installation using a preexisting SQL server and instance, PDT has an
option called EXISTING=TRUE than can be used on roles that require SQL instanced to be
specified. Note that there is no validation when you use this option. The installer account needs
appropriate SQL permissions, the collation needs to be correct, correct SQL features need to be
installed prior to attempting the PDT installation. The Installer account does not need Windows
admin permissions in this instance since it never does anything to that server. To use the option
the Role line looks like
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server"
Server="VMMDB.contoso.com" Instance="VMMDB" Existing="True"/>
If the sample variable.xml does not have a role that you want to deploy, you can obtain the Role format
and role component names from workflow.xml. To find a role in the workflow.xml, search for <Roles> and
then find the role that needs to be added. The roles for a System Center component are normally
grouped together.
<Role Name="System Center 2012 R2 Configuration Manager Database Server" Component="System Center 2012 R2
Configuration Manager" SQL="True">
<Role Name="System Center 2012 R2 Configuration Manager Provider Server" Component="System Center 2012 R2
Configuration Manager">
<Role Name="System Center 2012 R2 Configuration Manager Site Server" Component="System Center 2012 R2
<Role Name="System Center 2012 R2 Configuration Manager Console" Component="System Center 2012 R2
To use the role line from the workflow you will need to edit it to conform to the role syntax. The examples
above have the sections highlighted that need to be edited or removed. Every <role> line will need to
have the Component= specification removed and replaced with a Server= value added that specifies the
server the role should be installed on. Lines that have SQL=TRUE require the specification of SQL Instance
in the <role> line. That can be just an Instance= or the additional SQLCluster=”true” if you are clustering
the SQL instance for this role.
<Role Name="System Center 2012 R2 Configuration Manager Database Server" Server="CM01.contoso.com"

Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Configuration Manager Provider Server" Server="CM01.contoso.com" />
<Role Name="System Center 2012 R2 Configuration Manager Site Server" Server="CSSS01.contoso.com" />
<Role Name="System Center 2012 R2 Configuration Manager Console" Server="CM01.contoso.com" />

XML Formatting
Note that when you copy the <ROLE> section from the workflow.xml that it does not have the
closing XML tag /> at the end of the line, be sure to add that tag to prevent XML formatting
issues.
15.3.3.1 Orchestrator 2012 R2 Roles

The following is a sample roles for Orchestrator 2012 R2. In this example, the database instance is a
clustered shared instance named SCDB
<Role Name="System Center 2012 R2 Orchestrator Database Server" Server="SCDB.contoso.com" Instance="SCDB"

SQLCluster="True" />
<Role Name="System Center 2012 R2 Orchestrator Management Server" Server="OR01.contoso.com"/>
<Role Name="System Center 2012 R2 Orchestrator Primary Runbook Server" Server="OR01.contoso.com"/>
<Role Name="System Center 2012 R2 Orchestrator Web Components Server" Server="OR01.contoso.com"/>
<Role Name="System Center 2012 R2 Orchestrator Runbook Designer" Server="RD01.contoso.com"/>
15.3.3.2 App Controller 2012 R2 Roles

The following is a sample role section for App Controller 2012 R2
<Role Name="System Center 2012 R2 App Controller Database Server" Server="SCDB.contoso.com" Instance="SCDB"
<Role Name="System Center 2012 R2 App Controller Server" Server="AC01.contoso.com"/>
<Role Name="System Center 2012 R2 App Controller Console" Server="AC01.contoso.com"/>
15.3.3.3 Operation Manager 2012 R2 Roles

The following is a sample role section for Operations Manager 2012 R2
<Role Name="System Center 2012 R2 Operations Manager Database Server" Server="SCOMDB.CONTOSO.com"

Instance="SCOMDB" SQLCluster="True" />
<Role Name="System Center 2012 R2 Operations Manager Datawarehouse Server" Server="SCOMDW.contoso.com"
Instance="SCOMDW" SQLCluster="True" />
<Role Name="System Center 2012 R2 Operations Manager Reporting Server" Server="OMRP01.contoso.com"
<Role Name="System Center 2012 R2 Operations Manager Management Server" Server="OM01.contoso.com"/>
<Role Name="System Center 2012 R2 Operations Manager Web Console Server" Server="OM01.contoso.com"/>
<Role Name="System Center 2012 R2 Operations Manager Console" Server="RD01.contoso.com"/>
<Role Name="SQL Server 2012 Management Tools" Server="OMRP01.Contoso.com” />
Reporting Server
Note that the Operations Manager Reporting Server requires a local SQL install on the server,
therefore the Instance=”SMSQLSERVER” is specified for that role.

15.3.3.4 Service Manager 2012 R2 Roles
The following is a sample role section for Service Manager 2012 R2
<Role Name="System Center 2012 R2 Service Manager Database Server" Server="SCSMDB.contoso.com"

Instance="SCSMDB" SQLCluster="True" />
<Role Name="System Center 2012 R2 Service Manager Datawarehouse Server" Server="SCSMDW.contoso.com"
Instance="SCSMDW" SQLCluster="True" />
<Role Name="System Center 2012 R2 Service Manager Analysis Server" Server="SCSMAS.contoso.com"
Instance="SCSMAS" SQLCluster="True" />
<Role Name="System Center 2012 R2 Service Manager Reporting Server" Server="SM02.contoso.com"
<Role Name="System Center 2012 R2 Service Manager Management Server" Server="SM01.contoso.com"/>
<Role Name="System Center 2012 R2 Service Manager Web Content Server" Server="SM01.contoso.com"/>
<Role Name="System Center 2012 R2 Service Manager Datawarehouse Management Server" Server="SM02.contoso.com"/>
<Role Name="System Center 2012 R2 Service Manager SharePoint Web Parts Server" Server="SM03.contoso.com"/>
<Role Name="System Center 2012 R2 Service Manager Console" Server="RD01.contoso.com"/>
15.3.3.5 Service Provider Foundation 2012 R2 Roles

The following is a sample role section for Service Provider Foundation 2012 R2
<Role Name="System Center 2012 R2 Service Provider Foundation Database Server" Server="SCDB.CONTOSO.com"
Instance="SCDB" SQLCluster="True" />
<Role Name="System Center 2012 R2 Service Provider Foundation Server" Server="SPF01.CONTOSO.com" />
15.3.3.6 Service Management Automation 2012 R2 Roles

The following is a sample role section for Service Management Automation 2012 R2
<Role Name="System Center 2012 R2 Service Management Automation Database Server" Server="SCDB.CONTOSO.com"
Instance="SCDB" SQLCluster="True" />
<Role Name="System Center 2012 R2 Service Management Automation Web Service Server" Server="SMA01.CONTOSO.com"
/>
15.3.3.7 Service Reporting 2012 R2 Component

The following is a sample component section for Service Reporting 2012 R2

<Variable Name="SystemCenter2012R2ServiceReportingInstallFolder" Value="$SystemDrive\Program Files\Microsoft
System Center 2012 R2\Service Reporting" />
</Component>
15.3.3.8 Windows Azure Pack 2013 Roles

The following is a sample role section for Windows Azure Pack 2013.
This is the role example for a Distributed deployment pattern of Windows Azure Pack
<Role Name="Windows Azure Pack 2013 Database Server" Server="WAPDB.CONTOSO.com" Instance="WAPDB"

<Role Name="Windows Azure Pack 2013 Admin API Server" Server="WAPADMINAPI.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Admin Authentication Site Server" Server="WAPADMINAuth.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Admin Site Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 SQL Server Extension Server" Server="WAPADMINAPI.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 MySQL Extension Server" Server="WAPADMINAPI.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant API Server" Server="WAPTENANTAPI.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant Public API Server" Server="WAPTENPubAPI.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant Authentication Site Server" Server="WAPTENAuth.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant Site Server" Server="WAPTENANT.CONTOSO.com" />

This is the role example for deploying the Minimal (2 server) deployment pattern of Windows Azure Pack
<Role Name="Windows Azure Pack 2013 Database Server" Server="WAPDB.CONTOSO.com" Instance="WAPDB"
<Role Name="Windows Azure Pack 2013 Admin API Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Admin Authentication Site Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 SQL Server Extension Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 MySQL Extension Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant API Server" Server="WAPADMIN.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant Public API Server" Server="WAPTENANT.CONTOSO.com" />
<Role Name="Windows Azure Pack 2013 Tenant Authentication Site Server" Server="WAPTENANT.CONTOSO.com" />
15.3.3.9 Windows Azure Pack WebSites Roles

The following is a sample role section for Windows Azure Pack WebSites
<Role Name="Windows Azure Pack 2013 Websites Database Server" Server="SitesDB01.Contoso.com"

<Role Name="Windows Azure Pack 2013 Websites Offline Feed Server" Server="SitesOffline.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites Controller" Server="SitesCN01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites Management Server" Server="SitesMN01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites FrontEnd Server" Server="SitesFE01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites Publisher Server" Server="SitesPB01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites Reserved WebWorker Server" Server="SitesWWR01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites Shared WebWorker Server" Server="SitesWWS01.Contoso.com" />
<Role Name="Windows Azure Pack 2013 Websites File Server" Server="SitesFS01.Contoso.com" />
<Role Name="SQL Server 2012 Management Tools" Server="SitesDB01.Contoso.com" />
Websites Role Limitations
Windows Azure Pack 2013 Websites requires that each role be placed on a separate server.
Offline Feed Server
To facilitate the ability to install WAP Websites at customers with no Internet access, the
installation of WAP Websites is always done using an offline approach. This requires that an
offline version of the installation feed is made available prior to installing any of the Websites
roles. This is the purpose of the Offline Feed Server.
15.3.4 SQL
The <SQL> section defines SQL deployment configuration that will be deployed as part of a scenario. This
includes the definition of clustered and standalone instances of SQL. For every <role> definition that
references a SQL instance, a corresponding SQL instance or clustered instance definition must exist in the
SQL section.

Clustered SQL instances have sections defined by the <Cluster> tag. The following example defines a
clustered SQL instance for the VMM database server role definition.
<Cluster Cluster="SCVMMDB.contoso.com" Version="SQL Server 2012">

<Variable Name="SQLAdmins" Value="CONTOSO\SQL Admins" />
<Variable Name="SQLAgtServiceAccount" Value="CONTOSO\SQL-SVC" />
<Variable Name="SQLAgtServiceAccountPassword" Value="Pass@word1" />
<Variable Name="SQLServiceAccount" Value="CONTOSO\SQL-SVC" />
<Variable Name="SQLServiceAccountPassword" Value="Pass@word1" />
<Variable Name="SQLInstallSQLDataDir" Value="E:\SQL\SCVMMDB" />
<Variable Name="SQLUserDBDir" Value="E:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="F:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="E:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="F:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLClusterIPAddress" Value="192.168.1.104" />
<Variable Name="SQLClusterNetwork" Value="Cluster Network 1" />
<Variable Name="SQLClusterIPSubnet" Value="255.255.255.0" />
<Variable Name="SQLClusterDisks">
<Value>`"E-Drive`" `"F-Drive`" </Value>
</Variable>
<Node Server="DB01A.contoso.com" Preferred="1"></Node>
<Node Server="DB01B.contoso.com"></Node>
</Cluster>
Cluster= value corresponds to the Server value from the role definition
Version= value defines the version of SQL to install
Variables define the information for Groups, service accounts, service account passwords, and storage
locations for databases and log files. In addition, Cluster resource settings are defined for IP address,
network name, subnet masks, Cluster resource disk names that map to the drive letters defined for the
database and log directories, and the nodes of the cluster.
Storage Choices
SQL Guest Clusters can utilize SMB shares, SharedVHDX, or iSCSI LUNS for the storage of the
database and log files. The SQLClusteredDisks variable is only required for SharedVHDX and iSCSI
LUN approaches.
SMB UNC approach is the easiest to configure because you do not have any additional setup
other than the remote share. Paths are specified using \\FS01\SQL\SCVMMDB notation
ShareVHDX requires knowledge of the cluster resource disk name so that the SQLClusterDisk
section can reference the clustered disks that correspond to the drive letters specified for the
database and log storage locations.
SQL Clusters
A SQL cluster can have two or more nodes in the cluster. Specifying the nodes and the node
preference is required for a clustered SQL install. Adding an additional node only requires an
addition <node> in the <Cluster> section.
Cluster Resources
Cluster resources such as cluster IP addresses, must be validated manually in the variable file to
ensure that no conflicts occur.

Data Disks and Clusters
Leveraging the SharedVHDX capability requires no page file or addition non-shared data disks are
added to a cluster nodes to ensure the proper mapping of storage to the cluster.
Standalone SQL instances. The following example defines a standalone SQL instance for the WAP
Websites database server role definition.
<Instance Server="SitesDB01.Contoso.com" Instance="MSSQLSERVER" Version="SQL Server 2012">

<Variable Name="SQLAdmins" Value="Contoso\SQL Admins" />
<Variable Name="SQLInstallSQLDataDir" Value="E:\Program Files\Microsoft SQL Server" />
<Variable Name="SQLUserDBDir" Value="E:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLUserDBLogDir" Value="F:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data"
/>
<Variable Name="SQLTempDBDir" Value="G:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLTempDBLogDir" Value="G:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data"
/>
<Variable Name="SQLAgtServiceAccount" Value="Contoso\SQL-SVC" />
<Variable Name="SQLServiceAccount" Value="Contoso\SQL-SVC" />
</Instance>
Server = value corresponds to the Server value from the role definition for a standalone SQL server
Instance = value defines the default or named database instance to create
Version= value defines the version of SQL to install
Variables define the information for Admins, service accounts, service account passwords, and storage
locations for databases and log files.
Data Drives
The VM definition for a standalone SQL server must specify the number of data disks to ensure all
the corresponding drive letters are available. Assuming a single C: drive, a standalone SQL server
that stores database and logs on D:, E:, F: and G: requires 2 data disks to be specified in the VM
definition.
It is possible for a single standalone or cluster SQL server to contain multiple instances. To accomplish this
separate instance sections must exist in the <SQL> section that contains the same Server name, but a
different instance name. For example, to have a difference instance installed on the SitesDB01 server
called TESTINSTANCE, the additional section would look like
<Instance Server="SitesDB01.Contoso.com" Instance="TESTINSTANCE" Version="SQL Server 2012">

<Variable Name="SQLInstallSQLDataDir" Value="E:\Program Files\Microsoft SQL Server" />
<Variable Name="SQLUserDBDir" Value="E:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLUserDBLogDir" Value="F:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data"
/>
<Variable Name="SQLTempDBDir" Value="G:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLTempDBLogDir" Value="G:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data"
/>
</Instance>
The actual Instance name ($Instance) is used in the path for storing the files.

15.3.5 VMs
The <VMs> section defines the number and configuration of the virtual machines that will be deployed as
part of a scenario when you run the VMCreator tool.
The VMs section is broken down into different major subsections.
 <COUNT> defines the total number of VMs to create

 <Domain> Specifies to create a new domain using the first VM in the list and use this information as
the domain information
 <Default> The default settings for ever VM created. They can be overridden at a per VM level
 <VM> These are the definition for each VM to create
15.3.5.1 <COUNT>
The <COUNT> section defines the number of virtual machines that will be created as part of a scenario
when you run the VMCreator tool.
<Count>36</Count>
The COUNT value should correspond to the number of <VM> sections defined later in the <VMs>
section. If the COUNT value is less than the number of <VM> sections, then it will fail validation. If the
COUNT value is more than the number of <VM> sections, then once the last defined VM section has been
created, then additional VMs will be created using the <VMName><PREFIX> value in the <Default>
section.
15.3.5.2 <DOMAIN>
The <DOMAIN> section defines the domain information that will be used to create a new DC for a new
domain. It specifies the NAME of the new domain, and defines the OUs that will be created to store the
service accounts and groups that are pulled from the variable.xml and workflow.xml files. Any
deployment scenario component section or SQL section that defines variable that contains a
ServiceAccount, AdminGroup will be parsed and automatically create the account and group in the new
domain.
<Domain>
<Name>CONTOSO.com</Name>
<ServiceAccountOU>Services.HQ</ServiceAccountOU>
<GroupOU>Groups.HQ</GroupOU>
</Domain>
If the <DOMAIN> section is specified in the variable.xml, then the first <VM> defined will be used to
create the new DC for the new forest. Specifying the <DOMAIN> section is enabling the greenfield
scenario for PDT.

15.3.5.3 <DEFAULT>
The <DEFAULT> section defines the default VM settings that will be used when creating VMs using
VMCreator. Any of these values can be overridden in a <VM> section to specify different values.
<Default>
<Host>Localhost</Host>
<VMFolder>E:\PLAVMs</VMFolder>
<VHDFolder>E:\PLAVMs</VHDFolder>
<SHAREDVHDXFolder>C:\ClusterStorage\Volume1\SharedVHDX</SHAREDVHDXFolder>
<VMName>
<Prefix>WS12R2D</Prefix>
<Sequence>1</Sequence>
</VMName>
<Processor>2</Processor>
<Memory>
<Startup>1024</Startup>
<Minimum>512</Minimum>
<Maximum>2048</Maximum>
<Buffer>20</Buffer>
</Memory>
<NetworkAdapter>
<VirtualSwitch>INSIDE</VirtualSwitch>
<IP>
<Prefix>192.168.1.</Prefix>
<Mask>24</Mask>
<Gateway>192.168.1.1</Gateway>
<DNS>192.168.1.4</DNS>
</IP>
</NetworkAdapter>
<OSDisk>
<Parent>C:\VHDs\Win2012r2RTM.vhdx</Parent>
<Type>Differencing</Type>
</OSDisk>
<DataDisks>
<Count>1</Count>
<Format>VHDX</Format>
<Size>100</Size>
</DataDisks>
<DVD>False</DVD>
<AutoStart>
<Action>Nothing</Action>
<Delay>0</Delay>
</AutoStart>
<JoinDomain>
<Domain>contoso.com</Domain>
<Credentials>
<Password>P@ssw0rd</Password>
<Username>Administrator</Username>
</Credentials>
<OrganizationalUnit>Servers.HQ</OrganizationalUnit>
</JoinDomain>
<AdministratorPassword>P@ssw0rd</AdministratorPassword>
</Default>
Variable Description
HOST Hyper-V host that the VMs will be created on.
VMFOLDER Default folder for VM configuration files
VHDFOLDER Default folder for VHD/VHDX files
SHAREDVHDXFOLDER Default folder for SharedVHDX files for guest clusters (must be on a
drive that has the svhdxflt filter driver attached)
VMNAME <PREFIX> - prefix for all VM names that have no <VM> section

<SEQUENCE> - Starting value to append for unique name generation
PROCESSOR Number of processors the VM should have
MEMORY Memory configuration for the VM
NETWORKADAPTER <SWITCH> - virtual switch on the Hyper-V server to attach the vNIC
<IP><PREFIX> - Static IP address that will be the starting prefix for VM
assignment
<IP><SEQUENCE> The last octet of the IPaddress used as the starting
point
<IP><MASK> - subnet mask
<IP><GATEWAY> - gateway
<IP><DNS> - DNS server value (Can specify multiple DNS entries)
OSDISK <PARENT> - VHD/VHDX to use for all VM creation actions
<TYPE> - DIFFERENCING if using Differencing disks, COPY if not using
differencing disks
DATADISKS Optional – allows you to specify additional data disks to be attached to
the VM
<COUNT> - number of data disks to attach
<FORMAT> - VHD/VHDX
<SIZE> - size in GB
DVD Specifies if a virtual DVD should be attached to the VM
AUTOSTART <ACTION> - Specifies the action the virtual machine is to take upon
start. Allowed values are Nothing, StartIfRunning, and Start.
<DELAY> - delay in seconds that the VM will wait before starting
JOINDOMAIN <DOMAIN> - domain to join the VM to
<CREDENTIALS> the credentials to use to join the VMs to the domain
<ORGANIZATIONALUNIT> - the OU to place the computer accounts
ADMINISTRATORPASSWORD The password to set the local admin account to.
15.3.5.4 <VM>
The <VM> section defines the VM and any settings that should be overridden for the VM when creating
VMs using VMCreator. Each <VM> section requires only one value <VMNAME> be specified to define the
VM name in the admin GUI and the actual name of the VM within the OS.
The following is an example section from the IaaS PLA variable.xml file sample.
 The first VM section for DC01 is specifying a DC for a greenfield deployment.

 The second VM section for RD01 is not overriding any of the default VM settings from the
<DEFAULT> section.
 The third VM section for FS01 specifies an additional 200 GB data disk be attached the VM when
created. The FS01 also specifies the IP Address for this VM. You can specify the MASK, Gateway, and
DNS values or accept the values from the Default section.
 The forth VM section for DB01A is for a one node of a SQL cluster. It overrides the default memory
assignment, it also specifies that SharedVHDX data disks need to be attached to the VM. The
ShareDataDisk section requires the <COUNT> number of disks to attach, the <PREFIX> that is used to
name the datadisk, the disk format VHDX, and the size of the datadisk 20GB.

SharedVHDX Data Disks
Note that every node of a cluster must have the same SharedDataDisk section specified. So you
can see that the fifth VM section for DB01B has the same section defined. This tells VMCreator to
create and attach the SharedVHDX data disks to both nodes of the cluster. The PREFIX value must
be unique between clusters.
<VM Count="1">
<VMName>DC01</VMName>
</VM>
<VM Count="2">
<VMName>RD01</VMName>
</VM>
<VM Count="3">
<VMName>FS01</VMName>
<DataDisks>
<Count>1</Count>
<Size>200</Size>
</DataDisks>
<NetworkAdapter>
<IP>
<Address>192.168.1.199</Address>
<Mask>24</Mask>
<DNS>192.168.1.4</DNS>
</IP>
</VM>
<VM Count="4">
<VMName>DB01A</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Prefix>Instance</Prefix>
<Size>20</Size>
</SharedDataDisks>
</VM>
<VM Count="5">
<VMName>DB01B</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Size>20</Size>
</SharedDataDisks>
</VM>

15.4 Pre-Install Scripts
PDT supports the ability for a VM to execute a PowerShell script prior to Installer.pS1 executing. This is a
function of the VMCreator script. To enable this capability, two actions must be taken
1) The PowerShell script for the VM must be created and placed in a specific folder location.
2) When VMCreator is executed, the path to the folder location must be specified.
15.4.1 Pre-Install PowerShell Scripts
Preinstall PowerShell scripts are injected into the VMs C:\Temp folder and executed as a run once action
once the VM has joined the domain and rebooted. The script is run in the context of the Installer service
account.
There is no real limitation to what can be executed in the preinstaller script except that is cannot have any
dependency on an installation that the Installer.ps1 script will execute after all VM preinstaller scripts are
complete.
Some example preinstaller scripts will be shown from the IaaS PLA deployment scenarios. The complete
scripts can be obtained in Appendix E.
15.4.1.1 DC01 Preinstall script
DC01 is created in a greenfield deployment scenario. A DC01 preinstall script can be useful to accomplish
things like creating cluster accounts, additional OUs, loading additional roles like DHCP, or creating DNS
records.
In the sample below, the following actions are being completed once the DC01 has installed Active
Directory Domain Services:
 Log the script execution to the local drive for later troubleshooting
 Import the AD PowerShell module
 Create the DKM container in AD to support a VMM HA installation
 Create Cluster accounts that are needed for guest clustering in this scenario
 Copy the CMTrace tool from the C:\Temp folder
 Create Users, Groups, and a DNS subdomain records that are required for a WAP Websites
deployment
###################################
# DC01 Preinstall Script
###################################
# Function to read registry values

function Get-RegValue ($Server,$Value) {
try {$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $Server)} catch {$reg =
$null}
If ($reg -ne $Null) {
$regKey= $reg.OpenSubKey("SOFTWARE\\Microsoft\\Virtual Machine\\Auto")

If ($regKey -ne $Null) {
If ($regkey.GetValue($Value) -eq 1) {
return $True
} Else {
return $False
}
}
}
}
# Log the script to the local C:\temp folder
start-transcript -path C:\Temp\DC-Configure.txt -noclobber
# Import AD module
While (!(Test-Path "AD:\")) {
If (Get-Module ActiveDirectory) {Remove-Module ActiveDirectory;Start-Sleep 1}
Import-Module ActiveDirectory -ErrorAction SilentlyContinue
}
###################################
# Create VMM DKM container
###################################
Write-Host "Create AD container for VMM"
New-ADObject -Name 'VMMDKM' -Type Container -Path 'DC=contoso,DC=com' -ErrorAction SilentlyContinue
$VMMSA = (Get-ADUser -Identity 'vmm-SVC').SID
$acl = Get-Acl -Path "AD:CN=VMMDKM,DC=contoso,DC=com"
$nullGuid = New-Object Guid 00000000-0000-0000-0000-000000000000
$ace = New-Object System.DirectoryServices.ActiveDirectoryAccessRule
$VMMSA,"GenericAll","Allow","All",$nullGuid
$acl.AddAccessRule($ace)
Set-Acl -Path "AD:CN=VMMDKM,DC=contoso,DC=com" -AclObject $acl
###################################
# Create cluster computer accounts
###################################
New-ADOrganizationalUnit -Name "Clusters" -Path "OU=HQ,DC=contoso,DC=com" -ProtectedFromAccidentalDeletion

$true
Function New-ADClusterComputerObject ($Cluster,$ClusterGroups,$ClusterOU) {

Write-Host "Creating computer object $Cluster"
New-ADComputer -Name $Cluster -Path $ClusterOU
$ClusterSID = $null
While ($ClusterSID -eq $null) {Try {$ClusterSID = (Get-ADComputer -Identity "$Cluster").SID} Catch {Start-
Sleep 1}}
$ClusterGroups | ForEach-Object {
Write-Host "Creating computer object $_"
New-ADComputer -Name "$_" -Path $ClusterOU
$acl = $null
While ($acl -eq $null) {try {$acl = Get-ACL -Path "AD:CN=$_,$ClusterOU" -ErrorAction SilentlyContinue}
catch {Start-Sleep 1}}
$ace = New-Object System.DirectoryServices.ActiveDirectoryAccessRule
$ClusterSID,"GenericAll","Allow","All",$nullGuid
Set-Acl -Path "AD:CN=$_,$ClusterOU" -AclObject $acl
}
Disable-ADAccount -Identity "$Cluster$"
}
New-ADClusterComputerObject -Cluster "CLDB01" -ClusterGroups

@("SCVMMDB","SCDB","SCSMDB","SCSMDW","SCSMAS","SCOMDB","SCOMDW","WAPDB") -ClusterOU
"OU=Clusters,OU=HQ,DC=contoso,DC=com"
New-ADClusterComputerObject -Cluster "CLVMM01" -ClusterGroups @("VMM01") -ClusterOU
"OU=Clusters,OU=HQ,DC=contoso,DC=com"
###################################
# Copy CMTrace for troubleshooting
###################################
New-Item -Path "C:\" -Name "CMTrace" -ItemType Directory
Copy-Item -Path "C:\Temp\CMTrace.exe" -Destination "C:\CMTrace"
###################################
# Section for WAP Websites
###################################
Write-Host "Creating File and Cert Groups"
New-ADGroup -Name "FileShareOwners" -SamAccountName FileShareOwners -GroupCategory Security -GroupScope Global
-DisplayName "FileShareOwners" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
New-ADGroup -Name "FileShareUsers" -SamAccountName FileShareUsers -GroupCategory Security -GroupScope Global -
DisplayName "FileShareUsers" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
New-ADGroup -Name "CertStoreFSUsers" -SamAccountName CertStoreFSUsers -GroupCategory Security -GroupScope
Global -DisplayName "CertStoreFSUsers" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
Write-Host "Creating File and Cert Users"

New-ADUser -SamAccountName FileShareUser -Name "FileShareUser" -AccountPassword (ConvertTo-SecureString -
AsPlainText "Pass@word1" -Force) -Enabled $true -Path 'OU=Services,OU=HQ,DC=CONTOSO,DC=com'
New-ADUser -SamAccountName FileShareOwner -Name "FileShareOwner" -AccountPassword (ConvertTo-SecureString -
New-ADUser -SamAccountName CertStoreUser -Name "CertStoreUser" -AccountPassword (ConvertTo-SecureString -

Write-Host "Add Users to the Groups"
Add-ADGroupMember -Identity FileShareOwners -Member FileShareOwner
Add-ADGroupMember -Identity FileShareUsers -Member FileShareUser
Add-ADGroupMember -Identity CertStoreFSUsers -Member CertStoreUser
Write-Host "Create SubDomain"

Add-DnsServerResourceRecordCName -Name "*.websites" -HostNameAlias "sitesfe01.Contoso.com" -ZoneName
"Contoso.com"
Add-DnsServerResourceRecordCName -Name "*.scm.websites" -HostNameAlias "sitesfe01.Contoso.com" -ZoneName
"Contoso.com"
Add-DnsServerResourceRecordCName -Name "ftp.websites" -HostNameAlias "sitespb01.Contoso.com" -ZoneName
"Contoso.com"
Add-DnsServerResourceRecordCName -Name "publish.websites" -HostNameAlias "sitespb01.Contoso.com" -ZoneName
"Contoso.com"
Copying other files with Preinstall scripts
In addition to copying the preinstall scripts to the C:\Temp folder of the VM, any other files that
are placed in the Preinstall script folder will also be copied to the C:\Temp folder. If you want
those files to existing post the PDT installation, you must add code to the preinstall script to copy
the files to a different directory.
For example, since the DC01 VM is where the Installer,ps1 script is executed from and the output
is in a log format used by Configuration Manager, using the CMTrace.exe is a good way to view
the Installer logs stored in %localappdata%\Installer folder.
You can place the CMTrace.exe in the DC01 preinstall folder and use the following PowerShell to
copy the tool to the C:\CMTRACE folder.
Editing PreInstall Scripts
In the DC01 sample preinstall script, there are values that are deployment specific and must be
modified prior to running the PDT deployment. When using prebuilt IaaS PLA scenario files that
you verify the variable.xml and the preinstall scripts have been modified based on the customer
specific scenario.
15.4.1.2 DB01A Preinstall script
DB01A is the first of a two node database cluster node for the IaaS PLA deployment scenario.
In the sample below, the following actions are being completed once the DB01A has joined the domain:
 Log the script execution to the local drive for later troubleshooting
 Define the other nodes for the cluster and wait for them to come online
 Install Failover Clustering on all cluster nodes
 Create the two node cluster for DB01A and DB01B with no storage

 Add the Shared VHDX data disks to the cluster in order and name the cluster resources with their
drive letters as the storage is added
 Set the Quorum disk to the first SharedVHDX that was created to be the Witness disk
 Clean up the C:\Temp folder
###################################
# DB01A Preinstall script
###################################

try {$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $Server)} catch {$reg =
$null}
return $True
} Else {
return $False
}
}
}
}
start-transcript -path C:\Temp\DBCLuster.txt -noclobber
###################################
# Define the Cluster nodes that are being created other than this node
###################################
$Nodes = @("DB01B")
# Wait for cluster nodes
$Nodes | Sort-Object -Unique | ForEach-Object {

Write-Host "Waiting for $_"
While (!(Get-RegValue -Server $_ -Value $_)) {Start-Sleep 1}
Write-Host "Waiting for $_ DNS"
While (!(Resolve-DNSName -Name "$_.$Domain" -ErrorAction SilentlyContinue)) {
Invoke-Command -ComputerName $_ -ScriptBlock {ipconfig.exe /registerdns | Out-Null}
Start-Sleep 15
}
}
###################################
# Install failover clustering on All nodes
###################################
$Nodes = @("DB01A","DB01B")
$Jobs = @()
Write-Host "Installing failover clustering"
$Nodes | ForEach-Object {
$Jobs += Start-Job -Name $_ -ScriptBlock {
$Computer = $args[0]
Invoke-Command -ComputerName $Computer -ScriptBlock {
Install-WindowsFeature Failover-Clustering -ComputerName $Computer -IncludeManagementTools
} -ArgumentList @($Computer)
} -ArgumentList @($_)
}
$Jobs | ForEach-Object {
While ((Get-Job -Id $_.Id).State -eq "Running") {Start-Sleep 1}
}
# Create cluster
Install-WindowsFeature -Name RSAT-Clustering-PowerShell

Write-Host "Creating cluster CLDB01"
New-Cluster -Name "CLDB01" -Node $Nodes -StaticAddress 192.168.1.103 -nostorage
# Assumption: There are no Pagefile disk or additional non-shared data disks connected to the nodes
$NumberOfSharedVHDX = 17
for ($i=1; $i -le $NumberOfSharedVHDX; $i++) {
$Drive = get-disk -Number $i | Get-partition
(Get-ClusterAvailableDisk | ?{ $_.Number -eq $i} | Add-ClusterDisk).Name = $Drive.DriveLetter + "-
Drive"
Write-Host "Adding Drive $Drive.DriveLetter-Drive"
}
Set-ClusterQuorum -NodeAndDiskMajority "D-Drive"
# Cleanup
Get-ChildItem -Path 'C:\Temp' -Recurse | Where-Object {$_.Name -ne "Setup.bat"} | ForEach-Object
{$_.Attributes = 'Normal'}
Get-ChildItem -Path 'C:\Temp' -Recurse -Hidden | Where-Object {$_.Name -ne "Setup.bat"} | ForEach-Object
{$_.Attributes = 'Normal'}
Get-ChildItem -Path 'C:\Temp' | Where-Object {($_.Name -ne "Setup.bat") -and ($_.Name -ne "DBCLuster.txt")} |
Remove-Item -Recurse

SharedVHDX Data Disks
A Two node SQL cluster can use multiple methods of storage for the clustered database and log
files. If the two node cluster is using SMB versus SharedVHDX, then the section of code that
attaches the SharedVHDX would not be needed because the SharedVHDX data drives would not
be specified in the variable.xml <VM> section and the <SQL> <CLUSTER> section would have
specified UNC paths for the database and log paths. See Appendix E for a variable.xml with UNC
paths.
SETUP.BAT
At the end of the DB01A.PS1 pre-install script is a section with three lines entitled “Cleanup”. The
last line basically deleted everything in the C:\Temp folder except the Setup.bat that PDT
generated and placed there. Setup.bat actually does some tracking and at the end of a successful
deployment, writes a registry value that the Installer script looks for to verify that the server
installation as completed successfully. If Setup.bat does not run writes the registry value, Installer
will hang waiting on the VM.
15.5 PostInstaller Scripts

In addition to the ability to run pre-install scripts on a per VM basis, PDT supports the ability to run a
single PostInstaller.ps1 script when being used for greenfield deployments (from the domain controller).
The PostInstaller.ps1 script must exist on the VM that is the first VM built as the DC. In the examples
included in the IaaS PLA Deployment guide, the first VM is DC01.
Create a PostInstaller.ps1 script and place it in the DC01 preinstall directory. After a successful deployment
scenario is complete, PDT Installer will automatically launch the PostInstaller.ps1 script on the DC01
VM. The fact that the PowerShell is running on the DC01, any actions that need to be performed on VMs
other than DC01 will require the use of PowerShell remoting.
As an example, when we create a clustered VMM installation, we create a remote library share on the FS01
server. That share needs to be registered on the VMM server. The following PowerShell could be run
manually on the VMM server after installation, or we can convert it to using PowerShell remoting and run
it as part of the PostInstaller.ps1 script.
Here is the PowerShell script if we wanted to run it on the VMM server:
#
# Add a Library Server and Share to the VMM installation
#
# Get the Credentials
$pwd = "Pass@word1" | ConvertTo-SecureString -asPlainText -Force
$Creds = New-Object System.Management.Automation.PSCredential("contoso\Administrator", $pwd)
# Create the Library Server and Share
{$vmmServer = Get-SCVMMServer -ComputerName "VMM01.Contoso.com"
Add-SCLibraryServer -ComputerName "FS01.Contoso.com" -Credential $Creds -vmmserver $vmmServer -
RunAsynchronously
Add-SCLibraryShare -Description "Remote Library Share" –SharePath
"\\FS01.contoso.com\MSSCVMMLibrary"

Here is what the script looks like converted to PowerShell remoting code:
#
# Add a Library Server and Share to the VMM installation via PS Remoting
#
$s = New-PSSession -ComputerName VMM01.contoso.com

Invoke-command -session $s {$pwd = "P@ssw0rd" | ConvertTo-SecureString -AsPlainText -Force}
Invoke-command -session $s {$Creds = New-Object
System.Management.Automation.PSCredential("Contoso\Administrator", $pwd)}
Invoke-command -session $s {import-module "VirtualMachineManager"}
Invoke-command -session $s {$vmmServer = Get-SCVMMServer -computername "VMM01.contoso.com"}
Invoke-command -session $s {Add-SClibraryserver -computername "FS01.contoso.com" -credential
$Creds -vmmserver $vmmServer}
Invoke-command -session $s {Add-SClibrarySHare -Description "Remote Library Share" -Sharepath
\\FS01.Contoso.com\MSSCVMMLibrary -AddDefaultResources}
Note
The Sleep command is to give VMM the time to recognize the new library server before you attempt to add a
share to it. You could also write logic using the Get-SCLibraryServer to wait for the existence of the library server.
15.6 VMCreator Execution enabling Pre-Install scripts

VMCreator is the first deployment script that is executed to create any VMs defined in the deployment
scenario. VMCreator execution requires that the PDT source folder has been created and all product
source files have been added. In addition, the Variable.xml edits to support the desired deployment
scenario must be complete.
VMcreator supports the following command line options:
 SETUP – specifies the root folder to the preinstall scripts

 PATH - Specifies the path that should VMCreator should read .xml input files
 SKIPVALIDATION – specifies whether validation should be skipped, Default is FALSE, TRUE skips
validation
In order to leverage pre-install scripts, VMCreator must be executed using the –SETUP command line
option.
.\VMCreator.ps1 –setup <path to pre-install script folders>
Typically you would create the folders under the PDT source folder. So if the PDT source folder is C:\PDT-
PLA and you had preinstall scripts for DC01, DB01A, and VMM01A, the structure would look like
C:\PDT-PLA\
\DC01
\DB01A
\VMM01A
Within each of the VM folders, the preinstall scripts would be placed.

C:\PDT-PLA\
\DC01\
\DC01.ps1
\DB01A\
\DB01A.ps1
\VMM01A\
\VMM01A.ps1
Then the execution command line would be
.\VMCreator.ps1 –setup C:\PDT-PLA
If the <DOMAIN> section has been specified in the variable.xml file, the executing VMCreator.ps1, will
copy all the required files into the DC VM and automatically execute Installer.ps1 as part of the process. If
the <DOMAIN> section is not specified in variable.xml, then once VMCreator.ps1 is complete, Installer.ps1
must be executed manually.
15.7 Installer.ps1
PDT Installer.ps1 script performs the actual <role> installations as defined in the variable.xml. As
mentioned above, Installer.ps1 can be executed automatically in a greenfield deployment scenario or can
be execute manually in a non-greenfield deployment scenario.
Installer.ps1 supports the following command line options (none are mandatory):
 ValidateOnly – specifies whether the installer should just validate the installation attempt versus
actually deploy, Default is FALSE, TRUE does validation only
 PATH - Specifies the path that should VMCreator should read .xml input files
 VALIDATESET – specifies the scope of validation, ALL, LOCAL, ActiveDirectory, REMOTE
Typically Installer.ps1 is run with no options. This starts the validation of the variable.xml, the deployment
scenario, the SQL configuration, the role dependencies, the media source folder, and many other items
including is all the specified servers can be contacted.

Once validation is complete, the installation will start. Installer provides an active status screen that shows
the different roles being installed and the status of each installation.

The status screen is color coded.
 White lines indicate that an installation action is currently active

 Yellow lines indicate that the installation action is currently waiting on a dependency
 Green lines indicate a successful installation
 Red lines indicate an installation failure
During the execution of Installer.ps1, log files are created for each server that roles are being installed on
and those logs are also rolled up into a single installation log. The logs are created on the machine that is
executing Installer.ps1. All logs are placed in the %localappdata%\installer folder. In addition each server
has logs that are created for each application installed. Those local server logs are place in the C:\Temp
folder in a subfolder named with a GUID.
Reading Log Files
It is highly recommended to use the CMTrace.exe tool from Configuration Manager 2012 R2
Tools to read the PDT log files.
15.8 Post Deployment Actions

PDT does a great job of installing all the roles and the integrations between the products. For example
when PDT completes the installation of System Center it will have installed all the defined roles and any
integration between them like Service Manager connectors and registering VMM in the WAP portal. There
are actions that PDT does not complete that will need to leverage the PLA deployment guide
documentation or other documentation:
 Orchestrator Integration pack connectors

 VMM Cloud for Windows Azure Pack
 SQL Database Tenant Servers
 Windows Azure Pack Websites REST API
 Import Windows Azure Pack Gallery Items
Refer to Appendix F: for more information and sample code on automating some of these actions.
15.9 Pre-Built Scenario Files

To facilitate creating deployment scenario files, Appendix E has a set of example Variable.XML files as well
as supporting Pre-install script examples.

16 Appendix A: SQL Server Cluster Named
Instance Worksheet
Prior to installing the SQL Server cluster, it is recommended that information be compiled to provide a
point of reference for the information that is required during the setup steps. The following template is
provided for that purpose.
Component Service Service Service App Virtual Operation Operations

Manager Manager Manager Controller, Machine s Manager
manageme Data analysis Orchestrator Manager Manager Data
nt server Warehouse server , Microsoft Warehouse
server SharePoint
services
Farm and
WSUS
SQL Server Instance SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW
Name
SQL Server Instance SCSMDB SCSMDW SCSMAS SCDB SCVMMDB SCOMDB SCOMDW
Failover Cluster Network
Name
SQL Server Instance
DATA Cluster Disk
Resource
SQL Server Instance LOG
Cluster Disk Resource
SQL Server Instance
Install Drive
SQL Server Instance
DATA Drive
SQL Server Instance LOG
Drive
SQL Server Instance
TEMPDB Drive
Cluster Service Name SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server
(SCSMDB) (SCSMDW) (SCSMAS) (SCDB) (SCVMMDB) (SCOMDB) (SCOMDW)
Clustered SQL Server
Instance IP Address
Host Cluster Public
Network Interface
Subnet Mask
Host Cluster Public
Network Interface Name
SQL Server Instance
Listening TCP/IP Port
SQL Server Instance Node2, Node2, Node2, Node1, Node1, Node3, Node3,
Preferred Owners Node4 Node4 Node4 Node4 Node4 Node4 Node4
Table 21 Component template

17 Appendix B: Example VHDX Design
VHDX Component(s) Instance Purpose Size
Name
VHDX 1 Service Manager Management SCSMDB Instance Database 145 GB
VHDX 2 Service Manager Management SCSMDB Instance Logs 70 GB
VHDX 3 Service Manager Data Warehouse SCSMDW Instance Database 1 TB
VHDX 4 Service Manager Data Warehouse SCSMDW Instance Logs 500 GB
VHDX 5 Service Manager Analysis Service SCSMAS Analysis Services 8 GB

VHDX 6 Service Manager Analysis Service SCSMAS Analysis Logs 4 GB
VHDX 7 Service Manager SharePoint Farm SCDB Instance Database 10 GB

Orchestrator
App Controller
Service Management Automation
VHDX 8 Service Manager SharePoint Farm SCDB Instance Logs 5 GB
Orchestrator
App Controller
Service Management Automation
VHDX 9 Virtual Machine Manager SCVMMDB Instance Database 6 GB
Windows Server Update Services
VHDX 10 Virtual Machine Manager SCVMMDB Instance Logs 3 GB
Windows Server Update Services
VHDX 11 Operations Manager SCOMDB Instance Database 130 GB
VHDX 12 Operations Manager SCOMDB Instance Logs 65 GB
VHDX 13 Operations Manager Data SCOMDW Instance Database 1 TB

Warehouse
VHDX 14 Operations Manager Data SCOMDW Instance Logs 500 GB
Warehouse
VHDX 15 Windows Azure Pack WAPDB Instance Database
VHDX 16 Windows Azure Pack WAPDB Instance Logs
VHDX 17 N/A N/A SQL Server Failover 1 GB

Cluster Disk Witness
N/A Service Reporting SCRSDWAS Instance Database, 100 GB
Integration Services
Analysis Services
N/A Service Reporting SCRSDWAS Instance Logs 50 GB

18 Appendix C: iSCSI Implementation Steps
1. To attach the guest cluster to
the iSCSI LUNs, the iSCSI
Initiator must be configured on
each SQL Server virtual
machine. On the Start screen,
click the iSCSI Initiator tile.
Note: Non-Microsoft Storage
Area Network (SAN)
connectivity software can be
used in place of the Microsoft
iSCSI Initiator. If a non-
Microsoft solution is used, skip
the steps that relate to
configuring the Microsoft iSCSI
Initiator.
2. When the iSCSI Initiator
Properties page appears, click
the Targets tab. In the Target
text box, supply the IP address
or fully qualified domain name
(FQDN) of the iSCSI Target
Server, and click the Quick
Connect button to establish
connectivity.

3. The Quick Connect page
provides a list of discovered
targets. When the Progress
report section shows Login
Succeeded, click Done.
4. On the iSCSI Initiator

Properties page, click the
Volumes and Devices tab. In
some cases, you may need to
click the Auto Configure
button to establish
connectivity with the LUNs that
are available to the initiator.
5. Click OK to close the iSCSI

Initiator Properties page.

19 Appendix D: PDT and SQL Availability
Groups
By default PDT does not support SQL 2012 Availability groups since Availability Groups requires actions
on the role to configure it to use availability groups. It is possible to take a multiple pass approach using
PDT to create the SQL cluster, manually performing some actions between PDT runs, and then configuring
the Availability Group in the end. This will require a different variable.xml file for each pass. It also requires
to leverage a feature to tell PDT that the database already exists in the second PDT pass.
As an example, we will use Virtual Machine Manager 2012 R2 installed to use a remote clustered SQL
2012 Availability group. The process would consist of the following high level steps
1. Create your VMs using VMCreator.ps1, creating the two node cluster using the –setup option. (like
shown in the Pre-Install scripts section)
2. For the first pass of Installer.ps1 – install standalone SQL instances, not clustered
instances. Variable.xml would look something like…
<Roles>
<Role Name="SQL Server 2012 Database Server" Server="DB01A.contoso.local" Instance="MSSQLSERVER" />
<Role Name="SQL Server 2012 Database Server" Server="DB01B.contoso.local" Instance="MSSQLSERVER" />
</Roles>
<SQL>
<Instance Server="DB01A.contoso.local" Instance="MSSQLSERVER" Version="SQL Server 2012">

</Instance>
<Instance Server="DB01B.contoso.local" Instance="MSSQLSERVER" Version="SQL Server 2012">

</Instance>
</SQL>
3. After the first pass of DPT completes, you will need to create the Availability Group and the Listener.
The following script is an example of creating an availability group and listener.
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") |
Out-Null
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoExtended") |
Out-Null
Import-Module "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules\SQLPS" –

DisableNameChecking
$SqlServerPrimName = "DB01A"
$SqlServerSecName = "DB01B"
$SqlAgName = "AG01"
$AgListenerName = "AG01"
$AgListenerPort = 1433
$HadrEndpointName = "HardEndpoint"
$HadrEndpointPort = 5022
Enable-SqlAlwaysOn -Path SQLSERVER:\SQL\$SqlServerPrimName\Default -Force
Enable-SqlAlwaysOn -Path SQLSERVER:\SQL\$SqlServerSecName\Default -Force
$SqlServerPrim = New-Object Microsoft.SqlServer.Management.Smo.Server($SqlServerPrimName)
$SqlServerSec = New-Object Microsoft.SqlServer.Management.Smo.Server($SqlServerSecName)
try {
# create the endpoint if it doesn't exist on the primary replica
$EndpointPrim = $SqlServerPrim.Endpoints |
Where-Object {$_.EndpointType -eq
[Microsoft.SqlServer.Management.Smo.EndpointType]::DatabaseMirroring}
if(!$EndpointPrim) {
$EndpointPrim = New-Object Microsoft.SqlServer.Management.Smo.Endpoint($SqlServerPrim,
$HadrEndpointName)

$EndpointPrim.EndpointType = [Microsoft.SqlServer.Management.Smo.EndpointType]::DatabaseMirroring
$EndpointPrim.ProtocolType = [Microsoft.SqlServer.Management.Smo.ProtocolType]::Tcp
$EndpointPrim.Protocol.Tcp.ListenerPort = $HadrEndpointPort
$EndpointPrim.Payload.DatabaseMirroring.ServerMirroringRole =
[Microsoft.SqlServer.Management.Smo.ServerMirroringRole]::All
$EndpointPrim.Payload.DatabaseMirroring.EndpointEncryption =
[Microsoft.SqlServer.Management.Smo.EndpointEncryption]::Required
$EndpointPrim.Payload.DatabaseMirroring.EndpointEncryptionAlgorithm =
[Microsoft.SqlServer.Management.Smo.EndpointEncryptionAlgorithm]::Aes
$EndpointPrim.Create()
$EndpointPrim.Start()
}
# create the endpoint if it doesn't exist on the secondary replica

$EndpointSec = $SqlServerSec.Endpoints |
Where-Object {$_.EndpointType -eq
[Microsoft.SqlServer.Management.Smo.EndpointType]::DatabaseMirroring}
if(!$EndpointSec) {
$EndpointSec = New-Object Microsoft.SqlServer.Management.Smo.Endpoint($SqlServerSec,
$HadrEndpointName)
$EndpointSec.EndpointType = [Microsoft.SqlServer.Management.Smo.EndpointType]::DatabaseMirroring
$EndpointSec.ProtocolType = [Microsoft.SqlServer.Management.Smo.ProtocolType]::Tcp
$EndpointSec.Protocol.Tcp.ListenerPort = $HadrEndpointPort
$EndpointSec.Payload.DatabaseMirroring.ServerMirroringRole =
[Microsoft.SqlServer.Management.Smo.ServerMirroringRole]::All
$EndpointSec.Payload.DatabaseMirroring.EndpointEncryption =
[Microsoft.SqlServer.Management.Smo.EndpointEncryption]::Required
$EndpointSec.Payload.DatabaseMirroring.EndpointEncryptionAlgorithm =
[Microsoft.SqlServer.Management.Smo.EndpointEncryptionAlgorithm]::Aes
$EndpointSec.Create()
$EndpointSec.Start()
}
$AvailabilityGroup = New-Object Microsoft.SqlServer.Management.Smo.AvailabilityGroup($SqlServerPrim,

$SqlAgName)
# create the primary replica object

$PrimaryReplica = New-Object Microsoft.SqlServer.Management.Smo.AvailabilityReplica($AvailabilityGroup,
$SqlServerPrimName)
$PrimaryReplica.EndpointUrl = "TCP://$($SqlServerPrim.NetName):$($EndpointPrim.Protocol.Tcp.ListenerPort)"
$PrimaryReplica.FailoverMode =
[Microsoft.SqlServer.Management.Smo.AvailabilityReplicaFailoverMode]::Automatic
$PrimaryReplica.AvailabilityMode =
[Microsoft.SqlServer.Management.Smo.AvailabilityReplicaAvailabilityMode]::SynchronousCommit
$AvailabilityGroup.AvailabilityReplicas.Add($PrimaryReplica)
# create the secondary replica object

$SecondaryReplica = New-Object Microsoft.SqlServer.Management.Smo.AvailabilityReplica($AvailabilityGroup,
$SqlServerSecName)
$SecondaryReplica.EndpointUrl = "TCP://$($SqlServerSec.NetName):$($EndpointSec.Protocol.Tcp.ListenerPort)"
$SecondaryReplica.FailoverMode =
[Microsoft.SqlServer.Management.Smo.AvailabilityReplicaFailoverMode]::Automatic
$SecondaryReplica.AvailabilityMode =
[Microsoft.SqlServer.Management.Smo.AvailabilityReplicaAvailabilityMode]::SynchronousCommit
$AvailabilityGroup.AvailabilityReplicas.Add($SecondaryReplica)
# create the listener object

$AgListener = New-Object Microsoft.SqlServer.Management.Smo.AvailabilityGroupListener($AvailabilityGroup,
$AgListenerName)
$AgListenerIp = New-Object
Microsoft.SqlServer.Management.Smo.AvailabilityGroupListenerIPAddress($AgListener)
$AgListener.PortNumber = $AgListenerPort
$AgListenerIp.IsDHCP = $true
$AgListener.AvailabilityGroupListenerIPAddresses.Add($AgListenerIp)
$AvailabilityGroup.AvailabilityGroupListeners.Add($AgListener)
# create the availability group

$SqlServerPrim.AvailabilityGroups.Add($AvailabilityGroup)
$AvailabilityGroup.Create()
# on the secondary replica, join the replica to the AG, and join the database to the AG
$SqlServerSec.JoinAvailabilityGroup($SqlAgName)
}
catch {
Write-Error $_.Exception
}
4. Now you would need to create a new Variable.xml that would be used to run another pass of
Installer.ps1. The Variable.xml would look something like the following. Note the use of the
Existing=”True” statement in the VMM database server role. That tells PDT that the database server is
already installed, and just to create the VMM database on the existing server. The permissions for that
server must match what is specified in the variable.xml file.

<Roles>
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server" Server="AG01.contoso.local"
Instance="MSSQLSERVER" Existing="True"></Role>
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Active Management Server"
Server="VMM01A.CONTOSO.local" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Passive Management Server"
Server="VMM01B.CONTOSO.local" />
</Roles>
<SQL>
<Instance Server="AG01.contoso.local" Instance="MSSQLSERVER" Version="SQL Server 2012">

</Instance>
</SQL>
5. After the second pass of Installer.ps1 is complete, then you would just need to add the newly created
VMM database to the Availability group.

20 Appendix E: PDT Scenario Files
This appendix contains some sample PDT scenario files as well as pre-install scripts
20.1 PLA Example One

In this example VARIABLE.XML file, the following is being deployed:
 DC01 – New domain controller for CONTOSO.COM

 DB01A/B – Two node Database Guest cluster using SharedVHDX for database and log storage
 VMM01A/B – Two node HA install of VMM
 FS01 – File server for VMM Library share
 RD01 – Remote admin console
 AC01 – App Controller
 OR01 – Orchestrator
 OM01 – Operations Manager
 OMRP01 – Operations Manager Reporting Server
 SM01 – Service Manager Management server
 SM02 – Service Manager DataWarehouse Management server
 SM03 – Web Parts and Portal server
 SPF01 – Service Provider Foundation server
 SMA01 – Service Management Automation server
 SR01 – Service Reporting Server
 WAP – Distributed deployment
 WAP Websites – Distributed deployment
 SQLCloud – WAP tenant database server
 PKI01 – PKI server for Contoso.com
 WSUS01 – WSUS server for Contoso.com
<?xml version="1.0" encoding="utf-8"?>

<Installer version="2.0">
<Variable Name="Download" Value="C:\InstallerRTM" />
<Variable Name="SystemCenter2012R2ProductKey" Value="*****-*****-*****-*****-*****" />
<Components>
<Variable Name="SystemCenter2012R2VirtualMachineManagerTopContainerName" Value="CN=VMMDKM,DC=CONTOSO,DC=COM" />
</Component>
</Component>
</Component>

</Component>
<Variable Name="SystemCenter2012R2ConfigurationManagerAdminGroup" Value="CONTOSO\SCCM Admins"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerDatabase" Value="CM_HQ1"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerSiteCode" Value="HQ1"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerSite" Value="Contoso"/>
</Component>
</Component>
<Component Name="System Center 2012 R2 Data Protection Manager">
<Variable Name="SystemCenter2012R2DataProtectionManagerAdminGroup" Value="CONTOSO\DPM Admins"/>
</Component>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationVMMSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCAdminServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationAdminSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccount" Value="CONTOSO\SPF-SVC" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationProviderSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCUsageServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationUsageSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
</Component>
</Component>
</Component>
<Variable Name="SystemCenter2012R2ServiceReportingInstallFolder" Value="$SystemDrive\Program Files\Microsoft System Center
2012 R2\Service Reporting" />
</Component>
<Variable Name="WindowsAzurePack2013WebsitesVMServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesDnsSuffix" Value="Contoso.com"/>
<Variable Name="WindowsAzurePack2013WebsitesCTLServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesMGMTServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesFSServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesWWServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesFEServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesPBServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesContentSharePath" Value="\\$WindowsAzurePack2013WebsitesFileServer\WebSites" />
<Variable Name="WindowsAzurePack2013WebsitesCertSharePath" Value="\\$WindowsAzurePack2013WebsitesFileServer\Certificates"
/>
Value="http://$WindowsAzurePack2013WebsitesOfflineFeedServer/BootStrapperFeed/feeds/latest/BootstrapperEntries.xml" />

</Component>
</Components>
<Roles>
<!—Databases ->
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server" Server="SCVMMDB.CONTOSO.com" Instance="SCVMMDB"
<Role Name="System Center 2012 R2 Orchestrator Database Server" Server="SCDB.contoso.com" Instance="SCDB" SQLCluster="True"
/>
<Role Name="System Center 2012 R2 Operations Manager Database Server" Server="SCOMDB.CONTOSO.com" Instance="SCOMDB"
<Role Name="System Center 2012 R2 App Controller Database Server" Server="SCDB.contoso.com" Instance="SCDB" SQLCluster="True"
/>
<Role Name="System Center 2012 R2 Operations Manager Datawarehouse Server" Server="SCOMDW.contoso.com" Instance="SCOMDW"
<Role Name="System Center 2012 R2 Operations Manager Reporting Server" Server="OMRP01.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Manager Database Server" Server="SCSMDB.contoso.com" Instance="SCSMDB"
<Role Name="System Center 2012 R2 Service Manager Datawarehouse Server" Server="SCSMDW.contoso.com" Instance="SCSMDW"
<Role Name="System Center 2012 R2 Service Manager Analysis Server" Server="SCSMAS.contoso.com" Instance="SCSMAS"
<Role Name="System Center 2012 R2 Service Manager Reporting Server" Server="SM02.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Provider Foundation Database Server" Server="SCDB.CONTOSO.com" Instance="SCDB"
<Role Name="System Center 2012 R2 Service Management Automation Database Server" Server="SCDB.CONTOSO.com" Instance="SCDB"
<Role Name="Windows Azure Pack 2013 Database Server" Server="WAPDB.CONTOSO.com" Instance="WAPDB" SQLCluster="True" />
<Role Name="Windows Azure Pack 2013 Websites Database Server" Server="SitesDB01.Contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Reporting Datawarehouse Server" Server="SR01.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Reporting Analysis Server" Server="SR01.contoso.com" Instance="MSSQLSERVER" />
<!—Roles ->
<Role Name="System Center 2012 R2 Service Reporting Server" Server="SR01.contoso.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Active Management Server" Server="VMM01A.CONTOSO.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Passive Management Server" Server="VMM01B.CONTOSO.com" />
<Role Name="System Center 2012 R2 Service Management Automation Web Service Server" Server="SMA01.CONTOSO.com" />
<!—Management Tools ->
<Role Name="SQL Server 2012 Management Tools" Server="OMRP01.Contoso.com" />
<Role Name="SQL Server 2012 Management Tools" Server="RD01.contoso.com"/>
</Roles>
<SQL>
<Variable Name="SQLInstallSQLDataDir" Value="E:\SQL\SCVMMDB" />
<Variable Name="SQLUserDBDir" Value="E:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="F:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="E:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="F:\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Value>`"E-Drive`" `"F-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="SCDB.contoso.com" Version="SQL Server 2012" Port="50001">
<Variable Name="SQLInstallSQLDataDir" Value="G:\SQL\SCDB" />
<Variable Name="SQLUserDBDir" Value="G:\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="H:\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="G:\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="H:\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />

<Value>`"G-Drive`" `"H-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="SCSMDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="I:\SQL\SCSMDB" />
<Variable Name="SQLUserDBDir" Value="I:\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="J:\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="I:\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="J:\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Value>`"I-Drive`" `"J-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="SCSMDW.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="K:\SQL\SCSMDW" />
<Variable Name="SQLUserDBDir" Value="K:\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="L:\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="K:\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="L:\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLASDataDir" Value="K:\SQL\SCSMDW\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="L:\SQL\SCSMDW\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="K:\SQL\SCSMDW\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="K:\SQL\SCSMDW\MSAS11.$Instance\OLAP\Temp" />
<Variable Name="SQLASServiceAccount" Value="CONTOSO\SQL-SVC" />
<Variable Name="SQLASServiceAccountPassword" Value="Pass@word1" />
<Value>`"K-Drive`" `"L-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="SCSMAS.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="M:\SQL\SCSMAS" />
<Variable Name="SQLUserDBDir" Value="M:\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="N:\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="M:\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="N:\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLASDataDir" Value="M:\SQL\SCSMAS\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="N:\SQL\SCSMAS\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="M:\SQL\SCSMAS\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="M:\SQL\SCSMAS\MSAS11.$Instance\OLAP\Temp" />
<Value>`"M-Drive`" `"N-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="WAPDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="O:\SQL\WAPDB" />
<Variable Name="SQLUserDBDir" Value="O:\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="P:\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="O:\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="P:\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Value>`"O-Drive`" `"P-Drive`" </Value>
</Variable>
</Cluster>
<Cluster Cluster="SCOMDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="Q:\SQL\SCOMDB" />
<Variable Name="SQLUserDBDir" Value="Q:\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="R:\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />

<Variable Name="SQLTempDBDir" Value="Q:\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="R:\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Value>`"Q-Drive`" `"R-Drive`" </Value>
</Variable>
<Node Server="DB01B.contoso.com" Preferred="1"></Node>
<Node Server="DB01A.contoso.com"></Node>
</Cluster>
<Cluster Cluster="SCOMDW.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="S:\SQL\SCOMDW" />
<Variable Name="SQLUserDBDir" Value="S:\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="T:\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="S:\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="T:\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLASDataDir" Value="S:\SQL\SCOMDW\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="T:\SQL\SCOMDW\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="S:\SQL\SCOMDW\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="S:\SQL\SCOMDW\MSAS11.$Instance\OLAP\Temp" />
<Value>`"S-Drive`" `"T-Drive`" </Value>
</Variable>
</Cluster>
<Instance Server="OMRP01.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
</Instance>
<Instance Server="SQLCLOUD.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="D:\Program Files\Microsoft SQL Server" />
<Variable Name="SQLUserDBDir" Value="D:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLUserDBLogDir" Value="E:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLTempDBDir" Value="F:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
<Variable Name="SQLTempDBLogDir" Value="F:\Program Files\Microsoft SQL Server\MSSQL11.$Instance\MSSQL\Data" />
</Instance>
</Instance>
<Instance Server="SR01.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
</Instance>
</SQL>
<VMs>
<Count>36</Count>
<Domain>
</Domain>
<Default>
<SharedVHDXFolder>E:\SHAREDVHDX</SharedVHDXFolder>
<VMName>
</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
<NetworkAdapter>
<IP>
<Mask>24</Mask>

<DNS>192.168.1.4</DNS>
</IP>
</NetworkAdapter>
<OSDisk>
</OSDisk>
<DVD>False</DVD>
<AutoStart>
<Delay>0</Delay>
</AutoStart>
<JoinDomain>
<Credentials>
</Credentials>
</JoinDomain>
</Default>
<VM Count="1">
</VM>
<VM Count="2">
</VM>
<VM Count="3">
<DataDisks>
<Count>1</Count>
<Size>200</Size>
</DataDisks>
</VM>
<VM Count="4">
<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Size>20</Size>
</SharedDataDisks>
</VM>
<VM Count="5">
<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Size>20</Size>
</SharedDataDisks>
</VM>
<VM Count="6">
<VMName>VMM01A</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="7">
<VMName>VMM01B</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="8">
<VMName>SPF01</VMName>
</VM>
<VM Count="9">
<VMName>SMA01</VMName>
</VM>
<VM Count="10">
<VMName>WAPADMINAUTH</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="11">
<VMName>WAPADMINAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>

</VM>
<VM Count="12">
<VMName>WAPTENANTAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="13">
<VMName>WAPTenPubAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="14">
<VMName>WAPTENAUTH</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="15">
<VMName>WAPADMIN</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="16">
<VMName>WAPTENANT</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="17">
<VMName>OR01</VMName>
</VM>
<VM Count="18">
<VMName>OM01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="19">
<VMName>SM01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="20">
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="21">
<NetworkAdapter>
<Identifier>Local Area Connection</Identifier>
</NetworkAdapter>
<OSDisk>
<Parent>C:\VHDs\Win2008r2.vhdx</Parent>
</OSDisk>
</VM>
<VM Count="22">
<VMName>OMRP01</VMName>
</VM>
<VM Count="23">
<VMName>SQLCLOUD</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>1000</Size>
</DataDisks>
</VM>
<VM Count="24">
<VMName>PKI01</VMName>
</VM>
<VM Count="25">

<VMName>WSUS01</VMName>
<DataDisks>
<Count>1</Count>
<Size>100</Size>
</DataDisks>
</VM>
<VM Count="26">
<VMName>SitesCN01</VMName>
</VM>
<VM Count="27">
<VMName>SitesMN01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="28">
<VMName>SitesFE01</VMName>
</VM>
<VM Count="29">
<VMName>SitesPB01</VMName>
</VM>
<VM Count="30">
<VMName>SitesWWS01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="31">
<VMName>SitesWWR01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="32">
<VMName>SitesFS01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
<DataDisks>
<Count>1</Count>
<Size>100</Size>
</DataDisks>
</VM>
<VM Count="33">
<VMName>SitesOffline</VMName>
</VM>
<VM Count="34">
<VMName>SitesDB01</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>100</Size>
</DataDisks>
</VM>
<VM Count="35">
<VMName>AC01</VMName>
</VM>
<VM Count="36">
<VMName>SR01</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>100</Size>
</DataDisks>
</VM>
</VMs>
</Installer>
20.2 PLA Example Two

In this example VARIABLE.XML file, the following is being deployed:

 DC01 – New domain controller for CONTOSO.COM
 DB01A/B – Two node Database Guest cluster using SMB3.0 for database and log storage
 VMM01A/B – Two node HA install of VMM
 FS01 – File server for Database storage and VMM Library share
 RD01 – Remote admin console
 AC01 – App Controller
 OR01 – Orchestrator
 OM01 – Operations Manager
 OMRP01 – Operations Manager Reporting Server
 SM01 – Service Manager Management server
 SM02 – Service Manager DataWarehouse Management server
 SM03 – Web Parts and Portal server
 SPF01 – Service Provider Foundation server
 SMA01 – Service Management Automation server
 SR01 – Service Reporting Server
 WAP – Distributed deployment
 WAP Websites – Distributed deployment
 SQLCloud – WAP tenant database server
 PKI01 – PKI server for Contoso.com
 WSUS01 – WSUS server for Contoso.com
<?xml version="1.0" encoding="utf-8"?>

<Installer version="2.0">
<Variable Name="Download" Value="C:\InstallerRTM" />
<Variable Name="SystemCenter2012R2ProductKey" Value="*****-*****-*****-*****-*****" />
<Components>
<Variable Name="SystemCenter2012R2VirtualMachineManagerTopContainerName" Value="CN=VMMDKM,DC=CONTOSO,DC=COM" />
</Component>
</Component>
</Component>
</Component>
<Variable Name="SystemCenter2012R2ConfigurationManagerAdminGroup" Value="CONTOSO\SCCM Admins"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerDatabase" Value="CM_HQ1"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerSiteCode" Value="HQ1"/>
<Variable Name="SystemCenter2012R2ConfigurationManagerSite" Value="Contoso"/>
</Component>

</Component>
<Component Name="System Center 2012 R2 Data Protection Manager">
<Variable Name="SystemCenter2012R2DataProtectionManagerAdminGroup" Value="CONTOSO\DPM Admins"/>
</Component>
<Variable Name="SystemCenter2012R2ServiceProviderFoundationVMMSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCAdminServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationAdminSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccount" Value="CONTOSO\SPF-SVC" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCProviderServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationProviderSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationSCUsageServiceAccountPassword" Value="P@ssw0rd" />
<Variable Name="SystemCenter2012R2ServiceProviderFoundationUsageSecurityGroupUsers" Value="CONTOSO\SPF Admins" />
</Component>
</Component>
</Component>
<Variable Name="SystemCenter2012R2ServiceReportingInstallFolder" Value="$SystemDrive\Program Files\Microsoft System Center
2012 R2\Service Reporting" />
</Component>
<Variable Name="WindowsAzurePack2013WebsitesVMServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesDnsSuffix" Value="Contoso.com"/>
<Variable Name="WindowsAzurePack2013WebsitesCTLServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesMGMTServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesFSServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesWWServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesFEServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesPBServiceAccount" Value="Contoso\administrator" />
<Variable Name="WindowsAzurePack2013WebsitesContentSharePath" Value="\\$WindowsAzurePack2013WebsitesFileServer\WebSites" />
<Variable Name="WindowsAzurePack2013WebsitesCertSharePath" Value="\\$WindowsAzurePack2013WebsitesFileServer\Certificates"
/>
Value="http://$WindowsAzurePack2013WebsitesOfflineFeedServer/BootStrapperFeed/feeds/latest/BootstrapperEntries.xml" />
</Component>
</Components>
<Roles>
<Role Name="System Center 2012 R2 Virtual Machine Manager Database Server" Server="SCVMMDB.CONTOSO.com" Instance="SCVMMDB"
<Role Name="System Center 2012 R2 Orchestrator Database Server" Server="SCDB.contoso.com" Instance="SCDB" SQLCluster="True"
/>
<Role Name="System Center 2012 R2 Operations Manager Database Server" Server="SCOMDB.CONTOSO.com" Instance="SCOMDB"
<Role Name="System Center 2012 R2 App Controller Database Server" Server="SCDB.contoso.com" Instance="SCDB" SQLCluster="True"
/>
<Role Name="System Center 2012 R2 Operations Manager Datawarehouse Server" Server="SCOMDW.contoso.com" Instance="SCOMDW"
<Role Name="System Center 2012 R2 Operations Manager Reporting Server" Server="OMRP01.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Manager Database Server" Server="SCSMDB.contoso.com" Instance="SCSMDB"
<Role Name="System Center 2012 R2 Service Manager Datawarehouse Server" Server="SCSMDW.contoso.com" Instance="SCSMDW"
<Role Name="System Center 2012 R2 Service Manager Analysis Server" Server="SCSMAS.contoso.com" Instance="SCSMAS"
<Role Name="System Center 2012 R2 Service Manager Reporting Server" Server="SM02.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Provider Foundation Database Server" Server="SCDB.CONTOSO.com" Instance="SCDB"
<Role Name="System Center 2012 R2 Service Management Automation Database Server" Server="SCDB.CONTOSO.com" Instance="SCDB"
<Role Name="Windows Azure Pack 2013 Database Server" Server="WAPDB.CONTOSO.com" Instance="WAPDB" SQLCluster="True" />

<Role Name="Windows Azure Pack 2013 Websites Database Server" Server="SitesDB01.Contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Reporting Datawarehouse Server" Server="SR01.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Reporting Analysis Server" Server="SR01.contoso.com" Instance="MSSQLSERVER" />
<Role Name="System Center 2012 R2 Service Reporting Server" Server="SR01.contoso.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Active Management Server" Server="VMM01A.CONTOSO.com" />
<Role Name="System Center 2012 R2 Virtual Machine Manager Cluster Passive Management Server" Server="VMM01B.CONTOSO.com" />
<Role Name="System Center 2012 R2 Service Management Automation Web Service Server" Server="SMA01.CONTOSO.com" />
<Role Name="SQL Server 2012 Management Tools" Server="OMRP01.Contoso.com" />
<Role Name="SQL Server 2012 Management Tools" Server="RD01.contoso.com"/>
</Roles>
<SQL>
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCVMMDB" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCVMMDB\MSSQL11.$Instance\MSSQL\DATA" />
</Cluster>
<Cluster Cluster="SCDB.contoso.com" Version="SQL Server 2012" Port="50001">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCDB" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCDB\MSSQL11.$Instance\MSSQL\DATA" />
</Cluster>
<Cluster Cluster="SCSMDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCSMDB" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCSMDB\MSSQL11.$Instance\MSSQL\DATA" />
</Cluster>
<Cluster Cluster="SCSMDW.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCSMDW" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCSMDW\MSSQL11.$Instance\MSSQL\DATA" />

<Variable Name="SQLASDataDir" Value="\\FS01\SQL\SCSMDW\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="\\FS01\SQL\SCSMDW\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="\\FS01\SQL\SCSMDW\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="\\FS01\SQL\SCSMDW\MSAS11.$Instance\OLAP\Temp" />
</Cluster>
<Cluster Cluster="SCSMAS.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCSMAS" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCSMAS\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLASDataDir" Value="\\FS01\SQL\SCSMAS\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="\\FS01\SQL\SCSMAS\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="\\FS01\SQL\SCSMAS\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="\\FS01\SQL\SCSMAS\MSAS11.$Instance\OLAP\Temp" />
</Cluster>
<Cluster Cluster="WAPDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\WAPDB" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\WAPDB\MSSQL11.$Instance\MSSQL\DATA" />
</Cluster>
<Cluster Cluster="SCOMDB.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCOMDB" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCOMDB\MSSQL11.$Instance\MSSQL\DATA" />
</Cluster>
<Cluster Cluster="SCOMDW.contoso.com" Version="SQL Server 2012">
<Variable Name="SQLInstallSQLDataDir" Value="\\FS01\SQL\SCOMDW" />
<Variable Name="SQLUserDBDir" Value="\\FS01\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLUserDBLogDir" Value="\\FS01\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBDir" Value="\\FS01\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLTempDBLogDir" Value="\\FS01\SQL\SCOMDW\MSSQL11.$Instance\MSSQL\DATA" />
<Variable Name="SQLASDataDir" Value="\\FS01\SQL\SCOMDW\MSAS11.$Instance\OLAP\Data" />
<Variable Name="SQLASLogDir" Value="\\FS01\SQL\SCOMDW\MSAS11.$Instance\OLAP\Log" />
<Variable Name="SQLASBackupDir" Value="\\FS01\SQL\SCOMDW\MSAS11.$Instance\OLAP\Backup" />
<Variable Name="SQLASTempDir" Value="\\FS01\SQL\SCOMDW\MSAS11.$Instance\OLAP\Temp" />
</Cluster>
<Instance Server="OMRP01.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
</Instance>
<Instance Server="SQLCLOUD.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
</Instance>

</Instance>
<Instance Server="SR01.CONTOSO.com" Instance="MSSQLSERVER" Version="SQL Server 2012">
</Instance>
</SQL>
<VMs>
<Count>17</Count>
<Domain>
</Domain>
<Default>
<SharedVHDXFolder>E:\SHAREDVHDX</SharedVHDXFolder>
<VMName>
</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
<NetworkAdapter>
<IP>
<Mask>24</Mask>
<DNS>192.168.1.4</DNS>
</IP>
</NetworkAdapter>
<OSDisk>
</OSDisk>
<DVD>False</DVD>
<AutoStart>
<Delay>0</Delay>
</AutoStart>
<JoinDomain>
<Credentials>
</Credentials>
</JoinDomain>
</Default>
<VM Count="1">
</VM>
<VM Count="2">
</VM>
<VM Count="3">
<DataDisks>
<Count>1</Count>
<Size>200</Size>
</DataDisks>
</VM>
<VM Count="4">
<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Size>20</Size>
</SharedDataDisks>
</VM>
<VM Count="5">

<Memory>
<Buffer>5</Buffer>
</Memory>
<SharedDataDisks>
<Count>17</Count>
<Size>20</Size>
</SharedDataDisks>
</VM>
<VM Count="6">
<VMName>VMM01A</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="7">
<VMName>VMM01B</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="8">
<VMName>SPF01</VMName>
</VM>
<VM Count="9">
<VMName>SMA01</VMName>
</VM>
<VM Count="10">
<VMName>WAPADMINAUTH</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="11">
<VMName>WAPADMINAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="12">
<VMName>WAPTENANTAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="13">
<VMName>WAPTenPubAPI</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="14">
<VMName>WAPTENAUTH</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="15">
<VMName>WAPADMIN</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="16">
<VMName>WAPTENANT</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
</VM>
<VM Count="17">
<VMName>OR01</VMName>
</VM>
<VM Count="11">
<VMName>OM01</VMName>
<Memory>

<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="12">
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="13">
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="14">
<NetworkAdapter>
<Identifier>Local Area Connection</Identifier>
</NetworkAdapter>
<OSDisk>
<Parent>C:\VHDs\Win2008r2.vhdx</Parent>
</OSDisk>
</VM>
<VM Count="15">
<VMName>OMRP01</VMName>
</VM>
<VM Count="16">
<VMName>SQLCLOUD</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>1000</Size>
</DataDisks>
</VM>
<VM Count="24">
<VMName>PKI01</VMName>
</VM>
<VM Count="25">
<VMName>WSUS01</VMName>
<DataDisks>
<Count>1</Count>
<Size>100</Size>
</DataDisks>
</VM>
<VM Count="26">
<VMName>SitesCN01</VMName>
</VM>
<VM Count="27">
<VMName>SitesMN01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="28">
<VMName>SitesFE01</VMName>
</VM>
<VM Count="29">
<VMName>SitesPB01</VMName>
</VM>
<VM Count="30">
<VMName>SitesWWS01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="31">
<VMName>SitesWWR01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
</VM>
<VM Count="32">
<VMName>SitesFS01</VMName>
<Memory>
<Buffer>20</Buffer>
</Memory>
<DataDisks>
<Count>1</Count>

<Size>100</Size>
</DataDisks>
</VM>
<VM Count="33">
<VMName>SitesOffline</VMName>
</VM>
<VM Count="34">
<VMName>SitesDB01</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>100</Size>
</DataDisks>
</VM>
<VM Count="35">
<VMName>AC01</VMName>
</VM>
<VM Count="17">
<VMName>SR01</VMName>
<Memory>
<Buffer>5</Buffer>
</Memory>
<DataDisks>
<Count>3</Count>
<Size>100</Size>
</DataDisks>
</VM>
</VMs>
</Installer>
20.3 PLA Pre-Install Scripts: DC01

In this example DC01.ps1 pre-install script file, additional setup actions are taken:
 Create the DKM container in AD for an HA install of VMM

 Create some cluster AD accounts in AD
 Copy the CMTrace tool from the C:\Temp directory
 Create prerequisites for WAP Websites installation

try {$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $Server)} catch {$reg = $null}
return $True
} Else {
return $False
}
}
}
}
start-transcript -path C:\Temp\DC-Configure.txt -noclobber
# Import AD module
While (!(Test-Path "AD:\")) {

If (Get-Module ActiveDirectory) {Remove-Module ActiveDirectory;Start-Sleep 1}
Import-Module ActiveDirectory -ErrorAction SilentlyContinue
}
###################################
# Create VMM DKM container
###################################
Write-Host "Create AD container for VMM"
New-ADObject -Name 'VMMDKM' -Type Container -Path 'DC=contoso,DC=com' -ErrorAction SilentlyContinue
$VMMSA = (Get-ADUser -Identity 'vmm-SVC').SID
$acl = Get-Acl -Path "AD:CN=VMMDKM,DC=contoso,DC=com"
$ace = New-Object System.DirectoryServices.ActiveDirectoryAccessRule $VMMSA,"GenericAll","Allow","All",$nullGuid
Set-Acl -Path "AD:CN=VMMDKM,DC=contoso,DC=com" -AclObject $acl
###################################
# Create cluster computer accounts
###################################
New-ADOrganizationalUnit -Name "Clusters" -Path "OU=HQ,DC=contoso,DC=com" -ProtectedFromAccidentalDeletion $true

Function New-ADClusterComputerObject ($Cluster,$ClusterGroups,$ClusterOU) {
Write-Host "Creating computer object $Cluster"
New-ADComputer -Name $Cluster -Path $ClusterOU

$ClusterSID = $null
While ($ClusterSID -eq $null) {Try {$ClusterSID = (Get-ADComputer -Identity "$Cluster").SID} Catch {Start-Sleep 1}}
$ClusterGroups | ForEach-Object {
Write-Host "Creating computer object $_"
New-ADComputer -Name "$_" -Path $ClusterOU
$acl = $null
While ($acl -eq $null) {try {$acl = Get-ACL -Path "AD:CN=$_,$ClusterOU" -ErrorAction SilentlyContinue} catch {Start-Sleep
1}}
$ace = New-Object System.DirectoryServices.ActiveDirectoryAccessRule $ClusterSID,"GenericAll","Allow","All",$nullGuid
Set-Acl -Path "AD:CN=$_,$ClusterOU" -AclObject $acl
}
Disable-ADAccount -Identity "$Cluster$"
}
New-ADClusterComputerObject -Cluster "CLDB01" -ClusterGroups

@("SCVMMDB","SCDB","SCSMDB","SCSMDW","SCSMAS","SCOMDB","SCOMDW","WAPDB") -ClusterOU "OU=Clusters,OU=HQ,DC=contoso,DC=com"
New-ADClusterComputerObject -Cluster "CLVMM01" -ClusterGroups @("VMM01") -ClusterOU "OU=Clusters,OU=HQ,DC=contoso,DC=com"
###################################
# Copy CMTrace for troubleshooting
###################################
###################################
# Section for WAP Websites
###################################
Write-Host "Creating File and Cert Groups"
New-ADGroup -Name "FileShareOwners" -SamAccountName FileShareOwners -GroupCategory Security -GroupScope Global -DisplayName
"FileShareOwners" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
New-ADGroup -Name "FileShareUsers" -SamAccountName FileShareUsers -GroupCategory Security -GroupScope Global -DisplayName
"FileShareUsers" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
New-ADGroup -Name "CertStoreFSUsers" -SamAccountName CertStoreFSUsers -GroupCategory Security -GroupScope Global -DisplayName
"CertStoreFSUsers" -Path "OU=Groups,OU=HQ,DC=CONTOSO,DC=com"
Write-Host "Creating File and Cert Users"

New-ADUser -SamAccountName FileShareUser -Name "FileShareUser" -AccountPassword (ConvertTo-SecureString -AsPlainText "Pass@word1"
-Force) -Enabled $true -Path 'OU=Services,OU=HQ,DC=CONTOSO,DC=com'
New-ADUser -SamAccountName FileShareOwner -Name "FileShareOwner" -AccountPassword (ConvertTo-SecureString -AsPlainText
"Pass@word1" -Force) -Enabled $true -Path 'OU=Services,OU=HQ,DC=CONTOSO,DC=com'
New-ADUser -SamAccountName CertStoreUser -Name "CertStoreUser" -AccountPassword (ConvertTo-SecureString -AsPlainText "Pass@word1"
-Force) -Enabled $true -Path 'OU=Services,OU=HQ,DC=CONTOSO,DC=com'
Write-Host "Add Users to the Groups"

Add-ADGroupMember -Identity FileShareOwners -Member FileShareOwner
Add-ADGroupMember -Identity FileShareUsers -Member FileShareUser
Add-ADGroupMember -Identity CertStoreFSUsers -Member CertStoreUser
Write-Host "Create SubDomain"

Add-DnsServerResourceRecordCName -Name "*.websites" -HostNameAlias "sitesfe01.Contoso.com" -ZoneName "Contoso.com"
Add-DnsServerResourceRecordCName -Name "*.scm.websites" -HostNameAlias "sitesfe01.Contoso.com" -ZoneName "Contoso.com"
Add-DnsServerResourceRecordCName -Name "ftp.websites" -HostNameAlias "sitespb01.Contoso.com" -ZoneName "Contoso.com"
Add-DnsServerResourceRecordCName -Name "publish.websites" -HostNameAlias "sitespb01.Contoso.com" -ZoneName "Contoso.com"
20.4 PLA Pre-Install Scripts: DB01A

In this example DB01A.ps1 pre-install script file, the following actions are taken:
 Wait for the database cluster nodes to be joined to the domain

 Create the database cluster
 Attach the sharedvhdx data disks to the cluster
 Move the log
 Clean up the installation files

return $True
} Else {
return $False
}
}
}
}
start-transcript -path C:\Temp\DBCLuster.txt -noclobber
###################################
# Define the Cluster nodes that are being created other than this node
###################################
$Nodes = @("DB01B")


Start-Sleep 15
}
}
###################################
# Install failover clustering on All nodes
###################################
$Nodes = @("DB01A","DB01B")
$Jobs = @()
Install-WindowsFeature Failover-Clustering -ComputerName $Computer -IncludeManagementTools
}
}
# Create cluster

Write-Host "Creating cluster CLDB01"
New-Cluster -Name "CLDB01" -Node $Nodes -StaticAddress 192.168.1.103 -nostorage
# Assumption: There are no Pagefile disk or additional non-shared data disks connected to the nodes
$NumberOfSharedVHDX = 17
for ($i=1; $i -le $NumberOfSharedVHDX; $i++) {
$Drive = get-disk -Number $i | Get-partition
(Get-ClusterAvailableDisk | ?{ $_.Number -eq $i} | Add-ClusterDisk).Name = $Drive.DriveLetter + "-Drive"
Write-Host "Adding Drive $Drive.DriveLetter-Drive"
}
Set-ClusterQuorum -NodeAndDiskMajority "D-Drive"
###################################
# Copy Log for troubleshooting
###################################
New-Item -Path "C:\" -Name "Logs" -ItemType Directory
Copy-Item -Path "C:\Temp\DBCluster.txt" -Destination "C:\Logs"
# Cleanup
Get-ChildItem -Path 'C:\Temp' -Recurse | Where-Object {$_.Name -ne "Setup.bat"} | ForEach-Object {$_.Attributes = 'Normal'}
Get-ChildItem -Path 'C:\Temp' -Recurse -Hidden | Where-Object {$_.Name -ne "Setup.bat"} | ForEach-Object {$_.Attributes =
'Normal'}
Get-ChildItem -Path 'C:\Temp' | Where-Object {$_.Name -ne "Setup.bat"} | Remove-Item -Recurse
20.5 PLA Pre-Install Scripts: FS01

In this example FS01.ps1 pre-install script file is performing the following actions:
 Create a share for SMB based SQL database storage

 Create a share for the VMM Library
 Clean up the installation files
###################################
# Setup file server
###################################
###################################
# Create Share for SQL Server SMB Storage
###################################
start-transcript -path C:\Temp\FS01.txt -noclobber
Write-Host "Creating file share SQL"

New-Item -Path "E:\" -Name "SQL" -ItemType Directory
New-SmbShare -Name "SQL" -Path "E:\SQL" -CachingMode None -FullAccess "Everyone"
$acl = Get-Acl "E:\SQL"
$acl.SetAccessRuleProtection($true, $true)
$ace = New-Object System.Security.AccessControl.FileSystemAccessRule("Contoso\SQL-
SVC",“FullControl","ContainerInherit,ObjectInherit","None","Allow")
Set-ACL "E:\SQL" $acl
###################################
# Create Share for VMM Library
###################################

Write-Host "Creating file share VMMLibrary"
New-Item -Path "E:\" -Name "VMMLibrary" -ItemType Directory
New-SmbShare -Name "VMMLibrary" -Path "E:\VMMLibrary" -CachingMode None -FullAccess "Everyone"
$acl = Get-Acl "E:\VMMLibrary"
$acl.SetAccessRuleProtection($true, $true)
$ace = New-Object System.Security.AccessControl.FileSystemAccessRule("Contoso\VMM
Admins",“FullControl","ContainerInherit,ObjectInherit","None","Allow")
Set-Acl "E:\VMMLibrary" $acl
# Cleanup
'Normal'}
20.6 PLA Pre-Install Scripts: PKI01

In this example PKI01.ps1 pre-install script file is performing the following actions:
 Ensure that PowerShell execution policy is correct

 Add the AD Certificate Service feature to the server
 Install Certificate services as an Enterprise root CA
###################################
# Setup PKI server
###################################
If ((Get-ExecutionPolicy) -eq 'Restricted') {Set-ExecutionPolicy RemoteSigned -Force}
Add-WindowsFeature ADCS-Cert-Authority -IncludeManagementTools

Install-ADCSCertificationAuthority -CAType EnterpriseRootCA -force
20.7 PLA Pre-Install Scripts: VMM01A

In this example VMM01A.ps1 pre-install script file is performing the following actions:
 Wait for VMM cluster nodes to join the domain

 Install Failover Clustering
 Create the VMM Cluster
 Clean up installation files
###################################
# Setup VMM Cluster
###################################
return $True
} Else {
return $False
}
}
}
}
start-transcript -path C:\Temp\VMMCLuster.txt -noclobber
$Nodes = @("VMM01B")

Start-Sleep 15
}
}
# Install failover clustering on nodes
$Nodes = @("VMM01A","VMM01B")

$Jobs = @()
Install-WindowsFeature Failover-Clustering -ComputerName $Computer
}
}
# Create cluster

Write-Host "Creating cluster CLVMM01"
New-Cluster -Name "CLVMM01" -Node $Nodes -StaticAddress 192.168.1.181 -NoStorage
Stop-transcript
# Cleanup
'Normal'}
20.8 PLA Pre-Install Scripts: WSUS01

In this example WSUS01.ps1 pre-install script file is performing the following actions:
 Set the PowerShell Execution policy

 Install the WSUS feature
 Configure the WSUS feature
###################################
# Setup WSUS Server
###################################
$WSUS2012R2ContentFolder="WSUS"
$WSUS2012R2ContentDrive="E:"
$WSUS2012R2SyncFrom="SyncFromMU"
If ((Get-ExecutionPolicy) -eq 'Restricted') {Set-ExecutionPolicy RemoteSigned -Force}
Install-WindowsFeature -Name UpdateServices -IncludeManagementTools
New-Item -Path $WSUS2012R2ContentDrive -Name $WSUS2012R2ContentFolder -ItemType Directory
CD "C:\Program Files\Update Services\Tools"
.\wsusutil.exe postinstall CONTENT_DIR="$WSUS2012R2ContentDrive\$WSUS2012R2ContentFolder"
$wsus = Get-WSUSServer
$wsusConfig = $wsus.GetConfiguration()
Set-WsusServerSynchronization –syncfromMU
$wsusConfig.AllUpdateLanguagesEnabled = $false
$wsusConfig.SetEnabledUpdateLanguages('en')
$wsusConfig.Save()

21 Appendix F: Windows Azure Pack Post
Deployment Actions
The following information outline the additional actions that must be completed to obtain a working WAP
infrastructure with the optional services. The guidance in this appendix carries the assumption that the
WAP infrastructure deployment has been automated using PDT and prebuilt scenarios as outlined in this
guide.
21.1 VMM Configuration

Once the installation has been completed with PDT, VMM has been installed and integrated with
Operations Manager and registered in the WAP portal. The following actions must still be completed:
 Creation of one or more VMM clouds

o A cloud is required for targeting VM deployments
 Registering of a VMM Library Server and Share (Assumes an HA install of VMM)
o VMM HA install requires a Library Server and Library share must be created on a file server
separate from the VMM cluster. It is also recommended to use a ScaleOut File Server to host
the share.
 Creation of the Logical Networks
o Logical networks must exist for VM connections during deployment
 Creation of the CSV for Host Clusters
 Creation of the Host Clusters
21.2 SQL Tenant Database Configuration

When PDT completes, SQL Service VM has been installed called SQLCLOUD. To make use of it in the
system, the SQL server must be registered in the WAP portal. This can be done using the WAP Service
Management Admin Portal or via PowerShell.
The following PowerShell provides an example of registering a SQL VM in the WAP Portal. Assumptions
 WAP Admin Portal Site = WAPADMIN.CONTOSO.LOCAL

 SQL Server to register = SQLCLOUD.CONTOSO.LOCAL
 SQL Admin account = SA
 SQL Admin Account Password = Pass@word1
 Size of SQL database space = 5 GB
The following PowerShell automates the registration of the SQL Server in the Admin portal
$Adminuri = 'https://WAPADMIN.Contoso.local:30004/'
$token = Get-MgmtSvcToken -Type 'Windows' -AuthenticationSite
https://WAPADMIN.Contoso.local:30072 -ClientRealm http://azureservices/AdminSite -
DisableCertificateValidation
#Get the Hosting Group to add the Hosting Server to

$HostingGroup = Get-MgmtSvcSqlServerGroup -AdminUri $Adminuri -Token $token -
DisableCertificateValidation | where {$_.GroupName -eq "Default"}

#Add the hosting Server
$dbusername = 'sa'
$dbpassword = ConvertTo-SecureString "Pass@word1" -AsPlainText -Force
$dbcredential = New-Object System.Management.Automation.PSCredential
($dbusername,$dbpassword)
$dbServerName = 'SQLCLOUD'
Add-MgmtSvcSqlHostingServer -AdminUri $Adminuri `

-Token $token `
-ServerGroupId $HostingGroup.GroupId `
-Name $dbServerName `
-User $dbcredential `
-TotalSpaceMB 5000 `
-DisableCertificateValidation
Once you have the SQL Services for Tenant added to the WAP server, it can be added to plans and users
can subscribe to those plans.
21.3 VM Cloud Gallery Items

When PDT completes and the WAP infrastructure has been installed, there are no Gallery Items imported
into the system or assigned to any plans. There are a set of sample Gallery Items that can be imported
into the deployed environment or the customer can create their own Gallery Items.
The Product group has developed a tool to enable customers and partners to create and edit VM Role
Gallery Items definitions.
VM Role Authoring Tool: https://vmroleauthor.codeplex.com/
The following How-To Video will help understand how to use the tool
http://www.youtube.com/playlist?list=PLjbVGPEELuaSuM-0eh9GO05zDFUudydJ1
To quickly leverage the existing sample Gallery Items, you need to do the following:
1. Download the sample gallery items

2. Determine items to import
3. Import the Extension packages into VMM
4. Import the Definition packages into Service Management Admin Portal
21.3.1.1 Download the VM Cloud Gallery Items

Downloading and Installing Windows Azure Pack Gallery Resources can be accomplished using the
following resources as guidance.
 Video: Using the Service Models Web Platform Installer Feed

 Technet: Downloading and Installing Windows Azure Pack Gallery Resource
 Video: Virtual Hard Disk Requirements for the Virtual Machine Role Gallery
 Technet: System Center 2012 R2 Virtual Machine Role Authoring Guide

21.3.1.2 Determine Items to Import
Once you download all the Gallery items, you need to determine which ones you want to import. To
leverage the example PowerShell scripts provided in the following sections to automate the import
process, then you need to build a CSV for the import process. The following values that must be included
in the CSV:
Parameter Description
VHD VHD that will be associated with the Gallery item and will need the tags to be
applied
Path The subfolder under the C:\Gallery Resources folder that contains the gallery
item to import
EXTPackage The name of the Extension package file to import
DEFPackage The name of the Definition package file to import
Family The Family name that is required for the VHD
Release The release value that is required for the VHD
Tag1 The primary tag that must be assigned to the VHD
Tag2 The secondary tag that must be assigned to the VHD
Note
The Values for Family, Release, and Tag values are specified in a document provided with the
sample Gallery item folder.
The following example table defines the import values needed for two of the sample Gallery items.

VHD,Path,EXTPackage,DEFPackage,OS,Family,Release,Tag1,Tag2
Win2012R2RTM.VHDX,WS2012_R2_WG_VMRole_Pkg,,WS2012R2.resdefpkg,Windows Server 2012 R2
Datacenter,Windows Server 2012 R2 DataCenter,1.0.0.0,WindowsServer2012,R2
Win2012R2RTM.VHDX,WS2012_WG_VMRole_Pkg,,WS2012.resdefpkg,64-bit edition of Windows Server 2012
Datacenter,Windows Server 2012 DataCenter,1.0.0.0,WindowsServer2012,R1
Note
Note that there are no Extension Packages in this example file
Once you have the CSV values entered, save the file as GalleryItems.csv
21.3.1.3 Import the Extension package into VMM

The following PowerShell script leverages the GalleryItems.CSV input file to define the Gallery Items that
need to be imported. For this script the CSV is used to identify the VHDx that needs to be associated to
the Gallery item, the Family, Release and Tags that also need to be associated to the VHDx. It also gets the
Gallery Extension package file information so that it can import the extension file into VMM.
Note
The only way to import an extension package file into VMM is via PowerShell
#
# Register Gallery Extension Packages into VMM
#
# Establish Variables
$SPFHost = "SPF01"
#
# Import the Gallery Items and start the registration process
#
import-csv GalleryItems.csv | ForEach-Object {
#
# Import the Resource Extension package In the VMM Server if the package exists
#
If ( $_.EXTPackage -ne $null)

{
Write-Host "Registering Extension package...$_.EXTPackage"
Write-Host ".."
$libraryShare = Get-SCLibraryShare | Where-Object {$_.Name -eq
'MSSCVMMLibrary'}
$resextpkg = $Env:SystemDrive + "\GalleryResources\$_.Path\$_.EXTPackage"
Import-CloudResourceExtension -ResourceExtensionPath $resextpkg -SharePath

$libsharepath -AllowUnencryptedTransfer
Write-Host "Registered.."
} Else
{
# No Package to import

Write-Host "No Extension Package to Register"
Write-Host ".."
}
#
# Configure the Family, release, and Tags for the VHDx that you will be using for the
Gallery Item
#
Write-Host "Configuring VHD...$_.VHD"
Write-Host ".."
$myVHD = Get-SCVirtualHardDisk | where {$_.Name -eq '$_.VHD'}
$OPERATINGSYSTEM = Get-SCOperatingSystem | where { $_.name -eq $_.OS }
Set-scvirtualharddisk -virtualharddisk $myVHD -OperatingSystem $OPERATINGSYSTEM
Set-scvirtualharddisk -virtualharddisk $myVHD -FamilyName $._Family -Release

$_.Release
$tags = $myVHD.Tag
if ( $tags -cnotcontains $_.Tag1 ) { $tags += @($_.Tag1) }

if ( $_.Tag2 -ne $null)
{
if ( $tags -cnotcontains $_.Tag2 ) { $tags += @($_.Tag2) }
}
Set-scvirtualharddisk -virtualharddisk $myVHD -Tag $tags

Write-Host "VHD Configured and Tagged...$_.VHD"
Write-Host ".."
21.3.1.4 Import the Definition Packages into Service Management Admin Portal
The following PowerShell script leverages the GalleryItems.CSV input file to define the Gallery Items that
need to be imported. For this script the CSV is used to identify the Gallery Definition package file
information so that it can import the definition file into the WAP Admin portal.
Note
It is possible to import the definition package via the WAP Admin portal GUI also
#
# Read in the CSV and import the resource definition packages on the SPF server
#
#
# Import the Gallery Items and start the registration process
#
import-csv GalleryItems.csv | ForEach-Object {
#
# Import the Resource Definition package In the SPF Server if the package exists
#
If ( $_.DEFPackage -ne $null)

{
Write-Host "Importing Definition package...$_.DEFPackage"
Write-Host ".."
$resdefpkg = $Env:SystemDrive + "\GalleryResources\$_.Path\$_.DEFPackage"
$package = Import-SCSPFVMRoleGalleryItem -package $resdefpkg
If ($package -ne $null) {
Write-Host "Imported.."
} Else
{
Write-Host "Import Failed.."
}
} Else
{
# No Package to import
Write-Host "No Definition Package to Register"
Write-Host ".."
}

ESG Lab Validation Performance and Cost Efficiency of Intel and Microsoft Hyperconverged Infrastructure en US

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ESG Lab Validation Performance and Cost Efficiency of Intel and Microsoft Hyperconverged Infrastructure en US

Hochgeladen von

Copyright:

Verfügbare Formate

Infrastructure-as-a-Service

Product Line Architecture

© 2013 Microsoft Corporation. All rights reserved.

2 IaaS Product Line Architecture Deployment Guide

IaaS Product Line Architecture Deployment Guide 3

4 IaaS Product Line Architecture Deployment Guide

IaaS Product Line Architecture Deployment Guide 5

6 IaaS Product Line Architecture Deployment Guide

IaaS Product Line Architecture Deployment Guide 7

8 IaaS Product Line Architecture Deployment Guide

1.2 Microsoft Private Cloud Fast Track

IaaS Product Line Architecture Deployment Guide 9

Figure 1 Branches of the Microsoft Private Cloud

Server infrastructure Server infrastructure

Cluster Shared Volumes (CSV2) Cluster Shared Volumes (CSV2)

Network infrastructure Network infrastructure

Storage infrastructure Storage infrastructure

Small configuration Medium configuration

Figure 2 Examples of Small (SMB) and Medium (Open) reference architectures

10 IaaS Product Line Architecture Deployment Guide

2.1 Fabric Design Patterns Overview

Design Pattern #1: Software-defined Infrastructure

Design Pattern #2: Non-converged Infrastructure

Design Pattern #3: Converged Infrastructure

IaaS Product Line Architecture Deployment Guide 11

RDMA Hyper-V cluster Converged-

SAN-based storage SAN-based storage

1: Software Defined Infrastructure 2: Non-Converged 3: Converged

2.1.1 System Center Licensing

12 IaaS Product Line Architecture Deployment Guide

IaaS Product Line Architecture Deployment Guide 13

3.1.1 Design Pattern 1: Cloud Management Infrastructure

14 IaaS Product Line Architecture Deployment Guide

Microsoft SQL Server Microsoft SQL Server

System Center Orchestrator Management System Center Orchestrator

Active Directory Federation Services Active Directory Federation Services

System Center Service Manager System Center Service Manager

System Center Service Manager Windows Deployment Services,

Active Directory, DNS, DHCP

IaaS Product Line Architecture Deployment Guide 15

Node 1 Node 2 Node 3 Node 4

System Center Orchestrator System Center Orchestrator

Active Directory Federation Services Active Directory Federation Services

Windows Azure Pack (Scale Windows Azure Pack (Scale Distributed)

Windows Azure Pack (Scale Windows Azure Pack (Scale Distributed)

Windows Azure Pack (Scale Windows Azure Pack (Scale Distributed)

Windows Azure Pack

Windows Azure Pack

Active Directory, DNS, DHCP

Figure 5 Scale-Out Cloud Management infrastructure

16 IaaS Product Line Architecture Deployment Guide

Component Roles Virtual RAM Virtual Hard

IaaS Product Line Architecture Deployment Guide 17

4.1.2 Create Fabric Management Virtual Guests

Virtual Component Virtual RAM Virtual Hard

18 IaaS Product Line Architecture Deployment Guide

 Install a New Windows Server 2012 Active Directory Forest

1. Open the Failover Cluster

IaaS Product Line Architecture Deployment Guide 19

4. The New Virtual Machine

Note: You may select the Do not

20 IaaS Product Line Architecture Deployment Guide

9. On the Specify Generation

IaaS Product Line Architecture Deployment Guide 21