Exam Ref 70-247 Configuring and Deploying a Private Cloud
Chapter 1. Design and deploy System Center
One of the first steps in deploying a private cloud using Microsoft technologies is the deployment of the System Center products that you will use to manage that private cloud. In this chapter you will learn which System Center products are appropriate for particular tasks within the private cloud, how to install those products, how to make those products highly available, how to back up and recover those products, and how to upgrade some of those products from previous versions.
Important: Have you read page xv?
It contains valuable information regarding the skills you need to pass the exam.
Objectives in this chapter:
Objective 1.1: Design a scalable System Center architecture
Objective 1.2: Install the System Center infrastructure
Objective 1.3: Upgrade System Center components
Objective 1.1: Design a scalable System Center architecture
This objective deals with knowing which System Center products you would deploy to accomplish specific goals in a private cloud deployment, how you can make those System Center products highly available, and how to back up and recover those System Center products.
This objective covers the following topics:
Understanding System Center 2012 R2 products
Examining System Center 2012 R2 high availability
Backing up and recovering VMM
Understanding System Center 2012 R2 products
Each System Center 2012 R2 product plays a different role within a private cloud environment. Understanding which product you would leverage to complete each task is an important part of the 70-247 exam. The following pages provide a brief description of the basic purpose of each System Center 2012 R2 product in a private cloud deployment.
Virtual Machine Manager
Virtual Machine Manager (VMM) allows you to manage your organization’s virtualization infrastructure, including virtualization hosts, storage, and networking resources. You can use VMM to create, manage, deploy, and update VMs. You can also use VMM to create, manage, deploy, and update applications and services that are hosted within your organization’s private cloud. VMM supports management of virtualization hosts running Hyper-V, VMware ESX and ESXi, as well as Citrix Xen.
You can use VMM to perform the following tasks:
Automatically place new VMs on virtualization hosts that have the most available resources. This feature is termed intelligent placement.
Automatically move virtual machines between cluster nodes based on cluster node workload and available resources. This includes evacuating VMs off of host cluster nodes so that VMM can shut those nodes down to preserve electricity.
Deploy and manage Server App-V applications.
Manage the process of VM live migration between virtualization hosts.
Manage software updates for VMM infrastructure, including VMM servers and virtualization hosts.
More Info: Virtual Machine Manager
You can learn more about Virtual Machine Manager at http://technet.microsoft.com/library/gg610610.aspx.
App Controller
App Controller includes a Self-Service Portal. You can grant access to this Self-Service Portal to allow users to deploy services and applications to your organization’s private cloud, as well as to the Microsoft Azure public cloud. You grant access by delegating the appropriate roles and permissions. App Controller allows an application’s owner to scale out, or scale back in, an application. Scaling out allows the application to have access to increased resources as demand for those resources escalates. In System Center 2012 R2, App Controller functions as VMM’s Self-Service Portal. Previous versions of VMM had their own Self-Service Portal.
More Info: App Controller
You can learn more about App Controller at http://technet.microsoft.com/library/hh546834.aspx.
Orchestrator
Orchestrator provides a drag-and-drop interface, allowing you to build complicated automation runbooks. A runbook is a branching automation workflow. You create runbooks by connecting together Orchestrator tasks. Integration packs are collections of tasks. Microsoft provides integration packs for each of the System Center products. Using the tasks contained within these integration packs, you can build complicated runbooks that enact intricate tasks. For example, you could create a runbook that deploys a VM from a template using VMM in response to an alert raised in Operations Manager, and then configures protection for that VM using Data Protection Manager. You use Orchestrator runbooks to automate activities in a private cloud deployment.
More Info: Orchestrator
You can learn more about Orchestrator at http://technet.microsoft.com/library/hh237242.aspx.
Operations Manager
Operations Manager allows you to monitor the performance and availability of private cloud elements, from being able to monitor individual virtualization hosts, through to monitoring specific virtual machines, and applications that run on those virtual machines and within the private cloud. Operations Manager supports automatic remediation of some problems. You can enhance the capability of Operations Manager by importing product-specific management packs.
More Info: Operations Manager
You can learn more about Operations Manager at http://technet.microsoft.com/library/hh205987.aspx.
Service Manager
Service Manager is a service management product that you can use to manage incidents and problems in a manner consistent with ITIL (Information Technology Infrastructure Library) or MOF (Microsoft Operations Framework) practices. You can configure Service Manager with connectors to Operations Manager.
You can configure Service Manager to trigger Orchestrator runbooks and publish this to the Service Manager Self-Service Portal as a service offering. For example, you could create an Orchestrator runbook that places a designated SQL Server database hosted in the private cloud into protection using Data Protection Manager. You could use Service Manager to publish this runbook automation as a service offering on the Self-Service Portal. Users could then use the Self-Service Portal to interact with the service offering, putting their SQL Server workload into protection without having to directly interact with Orchestrator or Data Protection Manager.
More Info: Service Manager
You can learn more about Service Manager at http://technet.microsoft.com/library/hh305220.aspx.
Data Protection Manager
Data Protection Manager (DPM) is Microsoft’s backup and recovery solution. You use Data Protection Manager to provide protection for your private cloud workloads. In addition to providing protection for physically deployed workloads, DPM supports backup and recovery of virtual machines running on Hyper-V virtualization hosts. This can take the form of fully recovering a VM to the original or a different Hyper-V host, or allows for item level recovery of elements within the protected VM. You can use DPM to perform the following tasks:
Perform bare metal recovery of protected Windows servers and desktops.
Back up and recover from disk, tape, or Microsoft Azure.
Manage multiple DPM servers from a single console.
Configuration Manager
Configuration Manager provides you with the ability to manage the configuration of computers and devices, including virtual machines deployed in a private cloud. You can use Configuration Manager to:
Deploy operating systems, software applications, software, updates, and operating system updates.
Monitor and correct operating system and application compliance settings.
Collect hardware and software inventory.
Perform remote administration.
In a private cloud environment, you would use VMM to manage virtual machine deployment, but might use Configuration Manager to manage software updates and monitor configuration drift for existing virtual machines.
Exam Tip
Remember that you use VMM to manage the software updates of your virtualization infrastructure, which includes the virtualization hosts and VMM servers. You could do this with Configuration Manager, but doing it with VMM has the benefit of ensuring that VMs are properly dealt with before a virtualization host is updated. You would use Configuration Manager to manage the software updates of the virtual machines that were deployed and running within your organization’s private cloud.
More Info: Configuration Manager
You can learn more about Configuration Manager at http://technet.microsoft.com/library/gg682129.aspx.
Examining System Center 2012 R2 high availability
The most straightforward method of making the server that hosts a System Center product highly available is to deploy that product within a highly available virtual machine. Additional protection is possible by configuring a replica virtual machine hosted on a second failover cluster.
You can make the databases for each System Center product highly available by deploying the databases on:
A SQL Server instance hosted on a highly available virtual machine
A SQL Server failover cluster
SQL Server availability groups
Using availability groups with System Center product databases involves substantial configuration of SQL Server prior to the deployment of the System Center product. You’ll have to specify the availability group listener name during product setup.
Beyond deploying the product on a highly available virtual machine, Table 1-1 lists additional high availability strategies for each System Center product.
TABLE 1-1 System Center high availability options
Backing up and recovering VMM
Perhaps the simplest method of protecting System Center products is to deploy them in virtual machines. Once you’ve done that, you can then configure DPM to protect those virtual machines. When recovering a VM protected by DPM, you can choose to recover the VM, or you can perform item level recovery. When recovering a VM, you can choose to recover the VM to its original location or to a separate Hyper-V host that has the DPM agent deployed. Item level recovery allows you to choose to recover specific files or folders from a VM, rather than having to recover the VM in its entirety.
More Info: Virtual Machine Recovery
You can learn more about virtual machine recovery at http://technet.microsoft.com/en-us/library/hh757981.aspx.
VMM
In order to recover a VMM deployment, you need to have a backup of the VMM database. You should also have a backup of the files stored in the VMM library. Microsoft recommends that you perform a full back up of the VMM database every 7 days and perform an incremental back up of the VMM database every day. You should back up at least one VMM library server whenever you substantially modify content stored on the server.
You can back up the VMM database using the VMM console, by using SQL Server Management Studio, or by configuring protection for the database using DPM. To back up the VMM database using the VMM console, perform the following steps:
1. In the Settings workspace of the VMM console, click Backup in the ribbon.
2. In the Virtual Machine Manager Backup dialog box, specify the location that will store the backup file.
You can restore the VMM database using SQL Server Management Studio, DPM, or by using the SCVMMRecover.exe utility from an elevated command prompt on the server that hosts VMM.
After restoring the VMM database, you will need to perform the following steps:
Manually remove any virtualization hosts that you had removed from VMM subsequent to when you performed the backup.
Manually remove any VMs that you had removed from VMM subsequent to when you performed the backup.
Manually add any virtualization hosts that had been added to VMM subsequent to when you performed the backup.
If you restore the VMM database to a separate computer, you may need to reassociate any virtualization hosts and library servers that display an Access Denied message.
More Info: Backing Up and Restoring VMM
You can learn more about backing up and restoring a VMM deployment at http://technet.microsoft.com/en-us/library/hh882397.aspx.
App Controller
All App Controller settings are stored within the App Controller database. You can use SQL Server Management Studio or DPM to back up the App Controller database. To be able to recover the database, you’ll need to ensure that you back up the App Controller AES key. You can back up the App Controller AES key using the Export-SCACAesKey cmdlet.
If your App Controller deployment is otherwise functioning, you can restore the App Controller database using either the SQL Server Management Studio tools or by using DPM. In the event that you are reinstalling App Controller on a new computer, you’ll need to restore the App Controller database and have access to the App Controller AES key before running the App Controller Installation Wizard and specifying that you want to perform recovery using an existing database.
More Info: App Controller Backup and Restore
You can learn more about backing up and restoring App Controller at http://technet.microsoft.com/en-us/library/hh771092.aspx.
Orchestrator
Backing up Orchestrator involves backing up the following elements:
Backup of the Orchestrator database
SQL instance service master key
File backup of the Orchestrator management server
File backup of each runbook server
File backup of each Orchestrator web server
Orchestrator runbooks are stored within the Orchestration database. As the Orchestration database uses encryption, you will also need to back up the service master key. Without the service master key, you will not be able to access the encrypted data stored in the Orchestration database if recovered to a separate instance. You back up a service master key with the BACKUP SERVICE MASTER KEY TO FILE Transact SQL statement.
On the management server, ensure that you back up the settings.dat file. This file stores information that allows the Orchestrator program files to access the Orchestration database. For Orchestrator web servers, ensure that the web.config files are being protected. DPM supports standard file backups of Orchestrator.
More Info: Back Up Orchestrator
You can learn more about backing up Orchestrator at http://technet.microsoft.com/en-us/library/hh852622.aspx.
Operations Manager
If you have not deployed Operations Manager within a VM, or if you want to just protect an Operations Manager deployment without requiring that the host computer or VM also be able to be recovered in its entirety, you should ensure that you regularly back up the following elements:
Operational database
Data warehouse database (if deployed)
Audit Collection Services (ACS) database (if deployed)
Custom management packs
Custom report definition files
Computer certificates
Microsoft recommends the backup schedule listed in Table 1-2 for an Operations Manager deployment.
TABLE 1-2 Operations Manager data protection
You can use SQL Server Management Studio to configure regular database backups. In a private cloud environment where you have deployed DPM, you should configure a custom DPM protection group to manage backups for Operations Manager. You back up custom management packs by exporting them using the Management Packs node of the Administration workspace of the Operations Manager console.
You perform recovery by restoring the appropriate databases, either using SQL Server Management Studio or by using DPM. You recover custom management packs by importing them using the Operations Manager console.
More Info: Backing Up Operations Manager
You can learn more about backing up Operations Manager at http://technet.microsoft.com/en-us/library/hh278864.aspx.
Service Manager
Backing up Service Manager involves backing up the following elements:
Service Manager encryption keys
Service Manager database
Service Manager data warehouse database
You can back up the Service Manager encryption keys using the SecureStorageBackup.exe command line utility from an elevated command prompt. You can back up the Service Manager database and the data warehouse database using SQL Server Management Studio or by using DPM.
To recover a Service Manager deployment, perform the following general steps:
1. Restore the encryption key.
2. Install the new Service Manager management server on a computer that has the same name as the original management server.
3. In the event that SQL Server was also installed on the Service Manager management server, install SQL Server and restore the Service Manager database.
4. Run the Service Manager Installation Wizard, and select the Use An Existing Database option, providing the details of the SQL instance that hosts the Service Manager database.
More Info: Service Manager Disaster Recovery
You can learn more about Service Manager disaster recovery at http://technet.microsoft.com/en-us/library/hh495602.aspx.
Data Protection Manager
Just because DPM functions as a data protection solution for other elements of your private cloud deployment, doesn’t mean that you don’t need to back up the DPM server itself. Your protection strategy for the DPM server should include backing up:
The DPM database
All local volumes and application data on the computer that hosts DPM
All replicas on the DPM server protected by that DPM server
There are two general strategies that you can use to protect a DPM server. These are:
Back up the DPM server using a second DPM server When you configure DPM in this way, the second DPM server functions as a replica of the first DPM server. In the event that the first DPM server fails, the secondary server will start protecting all of the workloads that were previously protected by the primary DPM server. Should it be necessary, you can configure a tertiary DPM server that will function as a replica of the secondary DPM server.
Back up the DPM database to tape You can configure DPM to back up the DPM database to a tape library. To recover the DPM database from tape, you’ll need to uninstall DPM from the original server, remove the DPM database that you want to restore using SQL Server Management Studio, reinstall DPM, perform a tape inventory, re-catalog the imported tape, recover the database to a network folder, and then use the DPMSync.exe utility to attach the database to DPM. You’ll need to then reestablish protection for all computers that were protected by the DPM server. You can do this by running the setdpmserver.exe command on each protected computer.
More Info: Backing Up DPM
You can learn more about backing up DPM at http://technet.microsoft.com/en-us/library/jj244607.aspx.
Configuration Manager
Configuration Manager includes a backup maintenance task that runs on a schedule. This task, shown in Figure 1-1, is available through the Site Maintenance item on the ribbon, which you can open when you select the Sites node in the Administration workspace of the Configuration Manager console. The Configuration Manager Backup Site Server site maintenance task backs up the following:
Site database
Configuration Manager registry keys
Configuration Manager files and folders
FIGURE 1-1 Backup site server task
DPM supports protecting Configuration Manager as a workload. When creating a DPM protection group for Configuration Manager, ensure that you select the SMS Writer Service item, and the site database on the Configuration Manager server.
More Info: Configuration Manager Backup and Recovery
You can learn more about Configuration Manager backup and recovery at http://technet.microsoft.com/en-us/library/gg712697.aspx.
If your organization uses custom Reporting Services reports with Configuration Manager, you will need to ensure that the following are protected:
Report Server database
Source files for reports and models
Encryption keys
Custom assemblies or extensions
Configuration files
Custom SQL views
Custom stored procedures
The backup site server scheduled maintenance task does not backup content files for software updates, applications, or operating system deployment. You should back up the SCCMContentLib folder on the Configuration Manager site server, using file backup to backup the content library. You will also need to ensure that you have taken a file backup of package source files. If you have not kept track of the location of package source files, you can determine the location by using the following Transact SQL query against the Configuration Manager database as shown in Figure 1-2:
SELECT PackageID, Name, PkgSourcePath FROM v_Package
FIGURE 1-2 Package source location
When recovering a site server, you can choose one of the following options:
Recover the site server using an existing backup You can leverage this option if you have created a backup using the scheduled maintenance task.
Reinstall the site server Only use this option if you don’t have a backup of the site server. When using this option, ensure that you use the same site code and site database name as the original site server.
It will be necessary to recover the Configuration Manager database if the database becomes corrupted or if the data is otherwise lost. If you are recovering a database in a hierarchy, any changes made to the site database since the backup will be retrieved from the central administration site if you are recovering a primary site database, or from a primary site database if you are recovering the central administration site. If you are recovering the database of a stand alone primary site, all changes made subsequent to the backup will be lost.
When performing database recovery, you have the following recovery options:
Recover the site database using a backup set This option allows you to restore the database using the backup created using the scheduled maintenance task.
Use a site database that has been manually recovered You use this option if you use SQL Server Management Studio, DPM, or another tool to back up the Configuration Manager database.
Create a new database for this site Use this option if you do not have access to a backup of the Configuration Manager site database. This option is only available if the site is part of a Configuration Manager hierarchy. You cannot use this option to recover the site database of a CAS if no primary sites are present and you can’t use this option to recover the site database of a stand-alone primary site.
After performing site recovery, you will need to perform the following steps:
Reenter user account passwords The final page of the recovery wizard will provide you with information about which accounts require password information. This information is also saved to the file C:\ConfigMgrPostRecoveryActions.html.
Reenter sideloading keys If you have entered sideloading keys for software deployment to Windows 8 and Windows 8.1 devices, you must reenter these keys, as they will be reset during site recovery.
Configure SSL for site system roles that use IIS You will also need to reconfigure IIS to use the appropriate SSL certificate for site system roles after performing recovery.
Recover custom reports If you have custom Configuration Manager reports, you will need to recover these reports after performing site recovery.
Recover content files You will need to recover content files to the same locations as they used on the site server prior to the failure that triggered the recovery process.
Update Microsoft Azure management certificates If your organization uses Microsoft Azure for cloud-based distribution points, you will need to update these management certificates for the newly recovered site server.
If you need to recover a computer that hosts a Configuration Manager secondary site, ensure that you configure the computer with the same name as the original computer that hosted the secondary site. Recovery of a secondary site requires that the primary site server is available. Configuration Manager secondary sites aren’t backed up by scheduled maintenance tasks.
Exam Tip
Remember the additional elements of each product that require backup beyond the product’s database to be able to perform full recovery.
Thought experiment: Highly available System Center infrastructure planning at Contoso
In this thought experiment, apply what you’ve learned about this objective. You can find answers to these questions in the “Answers” section at the end of this chapter.
You are in the process of integrating the VMM and DPM products into the plan for a private cloud deployment at Contoso. You want to avoid deploying the VMM management server and the Data Protection Manager server in a VM. Given these constraints:
1. What steps can you take to make VMM highly available?
2. What steps can you take to make DPM highly available?
Objective summary
Virtual Machine Manager allows you to manage your private cloud’s virtualization infrastructure.
App Controller allows you to manage both private and public clouds.
Orchestrator allows you to configure automation for private cloud processes.
Operations Manager provides you with performance and availability monitoring for private cloud workloads.
Service Manager provides a framework based on ITIL and MOF for private cloud management.
Data Protection Manager allows you to configure backup and recovery for private cloud workloads.
Configuration Manager allows you to deploy applications as well as managing and monitoring the configuration of virtual machines running in private clouds.
Protecting System Center products primarily involves ensuring that the product database is backed up on a regular basis.
Objective review
Answer the following questions to test your knowledge of the information in this objective. You can find the answers to these questions and explanations of why each answer choice is correct or incorrect in the “Answers” section at the end of this chapter.
1. Which System Center product would you deploy to monitor software update compliance for Windows 8.1 virtual machines hosted in your organization’s private cloud?
A. Virtual Machine Manager
B. Operations Manager
C. Configuration Manager
D. Orchestrator
2. Which of the following steps can you take to make System Center 2012 R2 Orchestrator more highly available?
A. Deploy multiple management servers.
B. Deploy multiple runbook servers.
C. Deploy the Orchestration database on a SQL Server failover cluster.
D. Deploy the management server on a highly available virtual machine.
3. A failure occurs in your datacenter and the computer hosting the Service Manager management service is lost. This computer also hosted the SQL Server instance that hosted the Service Manager database. You have backups of the database and the encryption key. The computer hosting the Service Manager data warehouse and the computer hosting the Service Manager Self-Service Portal is unaffected. Which of the following steps must you take prior to using the Service Manager installation media to recover Service Manager?
A. Restore the existing encryption key from backup.
B. Create a new encryption key.
C. Ensure that the replacement server has the same name as the failed Service Manager management server.
D. Install SQL Server and recover the Service Manager database.
Objective 1.2: Install the System Center infrastructure
This objective deals with the hardware requirements and software requirements for each System Center product. You’ll then learn how to install each system center product.
This objective covers the following topics:
Understanding hardware requirements
Software prerequisites
Installing System Center 2012 R2
Understanding hardware requirements
Each product in the System Center 2012 R2 suite has separate hardware requirements. These hardware requirements are just for the product itself, and don’t include items such as the SQL Server program files required to support the product, or the amount of disk space required to host elements such as the VMM library or Configuration Manager distribution points.
VMM
Table 1-3 describes the hardware or virtual machine resource requirements for the different elements of a VMM deployment where there are less than 150 users.
TABLE 1-3 VMM hardware requirements
Table 1-4 describes the hardware or virtual machine resource requirements for the different elements of a VMM deployment where there are more than 150 users. The requirements for VMM library servers do not change based on the number of users, only based on the amount of content to be stored on the library server.
TABLE 1-4 VMM hardware requirements for large deployments
More Info: Hardware Requirements
You can learn more about the hardware requirements for System Center 2012 R2 at http://technet.microsoft.com/en-us/library/dn726764.aspx.
App Controller
An App Controller server requires the following hardware or virtual machine resource allocation:
Minimum processor: 2 GHz Pentium 4
Recommended processor: 2.8 GHz dual core x64 processor
Minimum RAM: 1 GB
Recommended RAM: 4 GB
Minimum program file storage: 512 MB
Recommended program file storage: 1 GB
Orchestrator
Orchestrator has several elements: the management server, the runbook server, the runbook designer, and the web service. You can deploy these elements on separate computers or on the same computer. The elements require the following hardware or virtual machine resource allocation:
Minimum processor: 2.1 GHz dual core x64 CPU
Recommended processor: 2.1 GHz dual core x64 CPU
Minimum RAM: 1 GB
Recommended RAM: 2 GB
Minimum program file storage: 200 MB
Recommended program file storage: 200 MB
Operations Manager
Instead of having set minimum hardware requirements, you calculate the hardware requirements for Operations Manager using the Operations Manager Sizing Helper. The sizing helper is an Excel spreadsheet that takes into account the particular nature of your organization’s Operations Manager deployment, making hardware allocation recommendations based on that deployment. You can download the Operations Manager Sizing Helper files from Microsoft’s website.
More Info: Operations Manager Sizing Helper
You can learn more about the Operations Manager Sizing Helper at http://www.microsoft.com/en-us/download/details.aspx?id=29270.
Service Manager
The Service Manager management server and the Service Manager data warehouse management server must be deployed on separate computers or virtual machines. The requirements for the computer that host the Service Manager database exceed the requirements for the computer that hosts the management server or data warehouse management server roles. Table 1-5 describes the hardware or virtual machine resource requirements for the different elements of a Service Manager deployment.
TABLE 1-5 Service Manager hardware requirements
Data Protection Manager
A Data Protection Manager server requires the following hardware or virtual machine resource allocation:
Minimum processor: 1 GHz dual core x64 CPU
Recommended processor: 2.33 GHz quad core x64 CPU
Minimum RAM: 4 GB
Recommended RAM: 8 GB
Minimum program file storage: 3 GB
Recommended program file storage: 3 GB
Configuration Manager
Minimum and recommended Configuration Manager hardware configuration depends on the number of clients that need to be supported on the site system roles deployed. Table 1-6 lists different site configurations and the minimum recommended hardware configuration.
TABLE 1-6 Configuration Manager hardware requirements
The hardware requirements for remote site system servers are listed in Table 1-7.
TABLE 1-7 Site system server requirements
More Info: Configuration Manager Hardware Requirements
You can learn more about the hardware requirements for Configuration Manager at http://technet.microsoft.com/en-us/library/hh846235.aspx.
Software prerequisites
The software prerequisites for each product in the System Center 2012 R2 suite are varied. In most cases, any roles or features that are already included with the host operating system will be installed automatically as part of the product’s installation routine, and do not need to be installed prior to commencing installation.
Some products in the System Center 2012 R2 suite can only be installed on computers running Windows Server 2008 R2 SP1 and are not supported on computers running Windows Server 2008 R2.
A minimum of four separate computers are required if you want to deploy all products in the System Center 2012 R2 suite. This is because some products cannot coexist on the same computer as others. In production environments, Microsoft generally advises that each System Center 2012 R2 element be deployed on a separate computer.
SQL Server requirements
Each product in the System Center 2012 R2 suite uses a SQL Server database to host configuration and product data. SQL Server support is as follows:
App Controller SQL Server 2008 R2 SP2, SQL Server 2012 (RTM and SP1)
DPM SQL Sever 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM and SP1)
Operations Manager Data Warehouse SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM, SP1, and SP2)
Operations Manager Operational Database SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM, SP1, and SP2)
Operations Manager Reporting Server SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM, SP1, and SP2)
Orchestrator Management Server SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM and SP1)
Service Manager Database SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM and SP1)
Service Manager Data Warehouse Database SQL Server 2008 R2 (SP1 and SP2), SQL Server 2012 (RTM and SP1)
Virtual Machine Manager SQL Server 2008 R2 SP2, SQL Server 2012 (RTM and SP1)
In testing environments it is possible to use one SQL Server Database Engine element to host the databases for all System Center 2012 R2 products. The performance impact of this configuration means that it is not recommended for production environments. System Center R2 products cannot share an Reporting Services instance, and separate instances must be deployed for each product that uses Reporting Services.
More Info: System Center SQL Server Requirements
You can learn more about the System Center 2012 R2 SQL Server requirements at http://technet.microsoft.com/library/dn281933.aspx.
VMM
You can install the System Center 2012 R2 VMM management server on computers running the following operating systems:
Windows Server 2012
Windows Server 2012 R2
You must install the Windows ADK for Windows 8.1 on the computer that will host the management server role.
The SQL Server instance that supports VMM should have the following:
The SQL Server instance must allow for case-insensitive database objects.
The Database Engine Services And Management Tools - Complete features must be installed. Collation is configured during deployment.
Analysis server and reporting server elements should be deployed.
Other than SQL Server, a VMM management server has no external dependencies.
More Info: VMM Software Requirements
You can learn more about the VMM software prerequisites at http://technet.microsoft.com/library/dn771747.aspx.
App Controller
You can install System Center 2012 R2 App Controller on computers running the following operating systems:
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
App Controller has the following software prerequisites:
.NET Framework 4.5
VMM console
Supported version of SQL Server
SQL Server 2008 R2 (Standard, Enterprise, Datacenter) SP2
SQL Server 2012 (Standard, Enterprise)
Virtual Machine Manager 2012 R2 console
Installing App Controller will automatically install the Web Server (IIS) role and the following features:
Static Content
Default Document
Directory Browsing
HTTP Errors
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
HTTP Logging
Request Monitor
Tracing
Basic Authentication
Windows Authentication
Request Filtering
Static Content Compression
IIS Management Console
More Info: App Controller Software Requirements
You can learn more about the software requirements for App Controller at http://technet.microsoft.com/en-us/library/dn771748.aspx.
Orchestrator
You can install the System Center 2012 R2 Orchestrator management server, runbook server, web service, and Runbook Designer roles on computers running the following operating systems:
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Orchestrator has the following software requirements:
Internet Information Services (IIS)
.NET Framework 3.5
.NET Framework 4.5
WCF HTTP Activation
Microsoft Silverlight 4
More Info: Orchestrator Software Requirements
You can learn more about the software requirements for Orchestrator at http://technet.microsoft.com/en-us/library/hh420348.aspx.
Operations Manager
You can install the System Center 2012 R2 Operations Manager management server, data warehouse server, gateway server, reporting server, and web console roles on computers running the following operating systems:
Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
When installed on Windows Server 2012 R2, Operations Manager has software prerequisites listed in Table 1-8.
TABLE 1-8 Operations Manager software requirements
More Info: Operations Manager Software Requirements
You can learn more about the software requirements for Operations Manager at http://technet.microsoft.com/en-US/library/dn249696.aspx.
Service Manager
You can install the System Center 2012 R2 Service Manager management server, data warehouse management server, database, and data warehouse database on computers running the following operating systems:
Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2
You can install the Service Manager Self-Service Portal on computers running:
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Table 1-9 lists the software prerequisites for each System Center 2012 R2 Service Manager element when Service Manager is deployed on Windows Server 2012 R2.
TABLE 1-9 Service Manager software requirements
More Info: Service Manager Software Requirements
You can learn more about the software requirements for Service Manager at http://technet.microsoft.com/en-us/library/hh519608.aspx.
Data Protection Manager
You can install a System Center 2012 R2 Data Protection Manager server on computers running the following operating systems:
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
You can use DPM with both the Standard or Enterprise editions of SQL Server 2008 R2 SP1, and SQL Server 2012. DPM requires that the Database Engine services and Reporting Services elements of SQL Server be deployed.
More Info: DPM Software Requirements
You can learn more about the software requirements for DPM at http://technet.microsoft.com/en-US/library/hh758176.aspx.
The DPM server also has the following software prerequisites:
Microsoft .NET Framework 4.0
Windows Installer 4.5 or later
Visual C++ 2008 Redistributable
Windows PowerShell 3.0
Windows Single Instance Store (SIS)
Microsoft Application Error Reporting
Configuration Manager
You can install System Center 2012 R2 Configuration Manager on computers running the following operating systems:
Windows Server 2008 SP2
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
The site server has the software requirements listed in Table 1-10 when deployed on Windows Server 2012 or Windows Server 2012 R2.
TABLE 1-10 Configuration Manager software requirements
The Configuration Manger setup downloader is a stand-alone application that retrieves prerequisite files used for Configuration Manager setup. When you use this application, files are downloaded form Microsoft’s website to a directory that you specify. You run the setup downloader by running the setupdl.exe executable located in the \SMSSETUP\BIN\X64 folder of the Configuration Manager installation media. Figure 1-3 shows the setup downloader window with a folder that will store the setup downloader files.
FIGURE 1-3 Setup downloader
When you run Configuration Manager setup, you have the opportunity of specifying the location of these files. You don’t have to run the setup downloader prior to installing Configuration Manager. You’ll need to allow Configuration Manager to connect to the Internet to retrieve these files if you haven’t run the setup downloader.
More Info: Configuration Manager Software Requirements
You can learn more about the software requirements for Configuration Manager at http://technet.microsoft.com/en-us/library/gg682077.aspx.
Installing System Center 2012 R2 products
System Center 2012 R2 comes with a unified installer that allows you to use a single interface to deploy all System Center products in a specially prepared environment. The unified installer deploys products on a one-server per-product basis. It does not allow for complex deployments. You should only use the unified installer to deploy lab and proof of concept environments.
More Info: Supported Configurations for Configuration Manager
You can learn more about the software requirements for Configuration Manager at http://technet.microsoft.com/en-us/library/gg682077.aspx.
In the next few pages, you’ll learn the process for installing each of the System Center 2012 R2 products on a computer that has the necessary software prerequisites, including an appropriately configured SQL Server instance, deployed.
VMM
Once you have deployed the necessary software prerequisites, including the SQL Server instance that will host the VMM database and Windows ADK, you can install VMM by performing the following steps:
1. Run Setup.exe on the installation media. This will happen automatically if you mount the installation media ISO.
2. In the Microsoft System Center 2012 R2 dialog box, shown in Figure 1-4, click Install.
FIGURE 1-4 VMM installation dialog box
3. On the Select Features to install page, select VMM Management Server. VMM Console will automatically be selected.
4. On the Product Registration Information page, enter your product key. If you don’t enter your product key, VMM will be installed as an evaluation edition.
5. On the Please Read This License Agreement page, agree with the terms of the license agreement.
6. On the Customer Experience Improvement Program (CEIP) page, choose if you want to participate in this program.
7. On the Microsoft Update page, choose whether you want to use Microsoft Update to check for updates. The recommended choice is On.
8. On the Installation location page, select the installation location. The recommended location is C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager.
The prerequisite check will run.
1. On the Database Configuration page, shown in Figure 1-5, specify the connection settings for the VMM Database, including the Server Name, Port, Instance Name, and Database Name and then click next. You will not have to specify the port if you are using a local SQL Server instance.
FIGURE 1-5 Database configuration
2. On the Configure Service Account And Distributed Key Management page, specify whether to use a Local System Account or a Domain Account and then click next. If choosing a Domain Account, the account must be a member of the Local Administrators group on the VMM management server. You also use this page to specify whether encryption keys are stored locally or in Active Directory. If you are configuring a highly available VMM installation, you must store the encryption keys in Active Directory and must specify service account credentials that are members of the domain. Figure 1-6 shows this page of the installation wizard.
FIGURE 1-6 Service account and distributed key management
3. On the Port Configuration page, shown in Figure 1-7, review the configuration for the management server and then click Next.
FIGURE 1-7 Port configuration
4. On the Library Configuration page, shown in Figure 1-8, specify the location of the VMM library.
FIGURE 1-8 Library configuration
5. On the Installation Summary page, review the installation settings, and click Install.
6. When the installation completes, open the VMM console to verify that the installation has completed correctly.
More Info: Deploying VMM
You can learn more about deploying VMM at http://technet.microsoft.com/en-US/library/gg610669.aspx.
App Controller
To install App Controller once you have installed and configured the appropriate prerequisite software, perform the following steps:
1. Mount the App Controller installation media and run Setup.exe.
2. On the App Controller Setup dialog box, click Install.
3. On the Enter Your Product Registration Information page, provide a product key. If you don’t provide a product key, App Controller will install as an evaluation version.
4. You must agree to the license terms on the Review The Software License Terms page before you can continue the installation.
5. In the Install Missing Software page, you will have the option of installing any missing IIS role and role services, as well as WCF Data Services 5.0.
6. On the Select The Installation Path page, you can modify or accept the default installation path.
7. On the Configure The Services page, shown in Figure 1-9, select between using the Network Service Account or a Domain Account for App Controller services. If using a domain account, ensure that App Controller only uses the account. This account does not require any additional privileges beyond those assigned by default to a standard user account.
FIGURE 1-9 Service account setup
8. On the Configure The Website page, select an existing SSL certificate that has been installed on the web server, or choose to have the computer generate a self-signed certificate. You should use a certificate from a trusted CA, either internal or external third party, unless the App Controller server is only being used in a test environment. Figure 1-10 shows this page.
FIGURE 1-10 Website configuration
9. On the Configure The SQL Server Database page, shown in Figure 1-11, specify the details of the SQL instance that will host the App Controller database.
FIGURE 1-11 Database configuration
10. On the Help Improve App Controller For System Center 2012 R2 page, select whether you want to participate in the CEIP, and whether you want to use Microsoft Update to receive program updates.
11. On the Confirm The Settings page, review the settings, and click Install.
More Info: Install App Controller
You can learn more about installing App Controller at http://technet.microsoft.com/en-us/library/gg696046.aspx.
Orchestrator
Once you have deployed the necessary prerequisites, you can deploy Orchestrator by performing the following steps:
1. Mount the installation media, or run SetupOrchestrator.exe.
2. On the System Center 2012 R2 Orchestrator Setup dialog box, click Install.
3. On the Product Registration page, enter your product key and your organization name. If you do not enter a product key, Orchestrator will be installed as an evaluation edition.
4. On the License Terms page, accept the license terms to proceed with the installation.
5. On the Select Features To Install page, shown in Figure 1-12, select which features you will install. If no management server is present in the environment, the management server feature will be installed. On a single server deployment, you’d install each of these services. The web service feature is required if you will be configuring cross-product integration features such as the Orchestrator connector for Service Manager. You would also deploy this element if you want to use a web console to manage Orchestrator runbooks.
FIGURE 1-12 Feature installation
The setup routine will check for missing prerequisites. At this stage any Windows Server roles or features that haven’t been installed will be installed on the server.
6. On the Configure The Service Account page, specify which account will be used by Orchestrator to run runbooks and access remote system resources. This account should not have Domain Admin privileges but should have the “Log On As A Service” right. This right will be granted if not already assigned. Figure 1-13 shows this page. Click Test to verify that the credentials work.
FIGURE 1-13 Service account configuration
7. On the Configure The Database Server page, specify the location of the SQL Instance that will host the Orchestrator database. By default this instance will use port 1433. You can choose whether to use Windows Authentication or SQL Authentication, with the default being Windows Authentication. Click the Test Database Connection button to verify the connection to the database. This page is shown in Figure 1-14.
FIGURE 1-14 Database configuration
8. On the Configure The Database page, select to create a new database, or to use an existing database. This page is shown in Figure 1-15.
FIGURE 1-15 Orchestrator database
9. On the Configure Orchestrator Users Group page, specify which users will have access to the Runbook Designer and Deployment Manager. Figure 1-16 shows access granted to the ADATUM\OrchestratorUsers group. You also have the option to grant remote access to the Runbook Designer for this group.
FIGURE 1-16 Orchestrator user group
10. On the Configure The Ports For The Web Services page, review the ports assigned for the web service port and the Orchestration console port. You will need to use port information when configuring connectors, such as the Orchestrator connector for Service Manager. This page is shown in Figure 1-17.
FIGURE 1-17 Orchestrator ports
11. On the Select The Installation page, review the location for the program files.
12. On the Help Improve Microsoft System Center Orchestrator page, select whether you want to participate in the Customer Experience Improvement Program and whether you want to send error data to Microsoft.
13. On the Installation Summary page, review the installation settings, and click Install.
More Info: Installing Orchestrator
You can learn more about installing Orchestrator at http://technet.microsoft.com/en-us/library/hh420336.aspx.
Operations Manager
To install Operations Manager, ensure that you have deployed the necessary software prerequisites installed, and then perform the following steps:
1. Mount the Operations Manager installation media, or run Setup.exe.
2. In the Operations Manager Installation dialog box, click Install.
3. On the Select Features To Install page, shown in Figure 1-18, select the features that you want to install.
FIGURE 1-18 Feature selection
4. On the Select Installation Location page, review the installation location, and specify an alternative if appropriate.
5. On the Prerequisites page, verify that all necessary prerequisites are installed, and click Next.
6. On the Specify An Installation page, you can choose to create a new Operations Manager Management Group, or to add the management server to an existing Management Group. Figure 1-19 shows the creation of the Melbourne Management Group.
FIGURE 1-19 Management Group
7. On the License Terms page, you will need to agree to the license to continue installing the software.
8. On the Configure The Operational Database page, specify the details of the SQL Instance that will host the database. Figure 1-20 shows the database will be hosted on the server MEL-OPSMGR. The default name for the database is OperationsManager. You can also configure the database file and log file location in this dialog box.
FIGURE 1-20 Operational database
9. On the Configure The Data Warehouse Database page, you specify the details of the data warehouse database. This can be co-located on the same instance as the Operations Manager database, but with larger deployments, for performance reasons, should be located on a separate computer. The default database name is Operations-ManagerDW.
10. On the SQL Server Instance For Reporting Service page, select the SQL instance with Reporting Services installed that will function as the reporting server for Operations Manager. The SQL Server Agent must be running on the instance that hosts Reporting Services.
11. On the Specify A Web Site For Use With The Web Console page, specify which website to use for the web console. The default is the default IIS website. You can select an alternative website. If an SSL certificate is installed, you can choose to enable SSL.
12. On the Select An Authentication Mode For Use With The Web Console page, select whether to use Mixed or Network Authentication. Mixed Authentication is appropriate for intranet scenarios. Network Authentication is appropriate for users accessing the web console from an external location.
13. On the Configure Operations Manager Accounts page, specify the service accounts. You should use low-privileged domain accounts that are a member of the local Performance Monitor Users group and has the Allow Log On Locally Permission. If you want to enable Agentless Exception Monitoring, you’ll need an account that has local Administrator privileges. You will need to assign the action account the Manage Auditing and Security Log privilege if management packs require access to the security event log. This page of the setup wizard is shown inFigure 1-21.
FIGURE 1-21 Service Account configuration
14. On the Help Improve Operations Manager page, select whether you want to participate in the Customer Experience Improvement Program, Error Reporting, and Operational Data Reporting programs.
15. On the Microsoft Update page, select whether you want to use Microsoft Update to check for updates.
16. On the Installation Summary page, review the installation settings, and click Install.
More Info: Installing Operations Manager
You can learn more about installing Operations Manager at http://technet.microsoft.com/en-us/library/hh457006.aspx.
Service Manager
There are three main elements to a Service Manager deployment. These are: the Service Manager management server, Service Manager data warehouse, and Service Manager Self-Service Portal.
Service Manager Management Server
To install the Service Manager management server, ensure that you have deployed the necessary software prerequisites and then perform the following steps:
1. Mount the Service Manager installation media, and run Setup.exe from the AMD64 folder.
2. In the Microsoft System Center 2012 R2 Service Manager dialog box, shown in Figure 1-22, click Service Manager Management Server, under Install.
FIGURE 1-22 Service Manager setup
3. On the Product Registration page, enter your name, organization, product key, and agree to the license terms.
4. On the Installation Location page, verify the program files location, and click Next.
5. On the Prerequisites page, verify that the computer meets the prerequisite requirements.
6. On the Configure The Service Manager Database page, specify the details of the SQL instance that will host the database. The default database name is ServiceManager. Figure 1-23 shows this page.
FIGURE 1-23 Database setup
7. On the Configure The Service Manager Management Group page, specify a name for the Management Group. Also specify a security group for Management Group administrators. You should create a domain security group for this purpose and not use an existing security group, such as the Domain Admins group. Figure 1-24 shows this page where the Management Group Name is set to Melbourne and the Management Group Administrators is set to Service_Manager_Admins.
FIGURE 1-24 Management Group name
8. On the Configure The Account For Service Manager services, choose to use the Local System account, or a domain account that has local Admin privileges on the Service Manager server.
9. On the Configure The Service Manager Workflow page, choose to either use the Local System account, or a domain account that is a member of the local Users security group on the server.
10. On the Help Improve Microsoft System Center 2012 R2 Service Manager page, choose whether to participate in the CEIP.
11. On the Use Microsoft Update To Help Keep Your Computer Secure And Up-To-Date page, select whether or not you wish the server to use Microsoft Update to retrieve updates.
12. Review the installation summary, and click Install.
Service Manager Data Warehouse
To install the Service Manager data warehouse server, ensure that you have deployed the necessary software prerequisites, and then perform the following steps:
1. Mount the Service Manager installation media. In the AMD64 folder, run Setup.exe.
2. On the Microsoft System Center 2012 R2 Service Manager dialog box, click Service Manager Data Warehouse Management Server, under install.
3. On the Product Registration page, enter your Name, Organization, Product Key, and agree to the license terms.
4. On the Installation Location page, review the installation location, and change if necessary.
5. On the System Check Results page, verify that the prerequisite checks complete.
6. On the Configure The Data Warehouse Databases page, configure which instance will host the data warehouse. It is important to note that you cannot host the Service Manager data warehouse on the same SQL instance that host the Service Manager management server database. This page is shown in Figure 1-25.
FIGURE 1-25 Data warehouse databases
7. On the Configure Additional Data Warehouse Datamarts page, configure which instance will host data warehouse datamart databases. Datamart databases can be co-located with the data warehouse database.
8. On the Configure The Data Warehouse Management Group page, specify the data warehouse Management Group name, and specify which security group will be delegated the Management Group administrator permission. Figure 1-26 shows this page where the Management Group name is set to DW_Melbourne, and the Management Group administrators is set to ADATUM\Service_Manager_Admins.
FIGURE 1-26 Data Warehouse Management Group
9. On the Configure The Reporting Server For The Data Warehouse page, verify the configuration of the SQL Server Reporting Services instance that will be used by the data warehouse.
10. On the Configure The Account For Service Manager services, you can choose to use the Local System account, or a domain account that is a member of the local Administrators group on the server hosting the data warehouse. If using a domain account, this account can be the same account as the one used for the Service Manager service on the Service Manager management server.
11. On the Configure The Reporting account, specify the account that will be used to read data warehouse reporting data sources, and be used to generate reports. This should be an unprivileged domain account.
12. On the Configure Analysis Services For OLAP Cubes, specify an Analysis Services instance. Figure 1-27 shows this page.
FIGURE 1-27 Analysis Services configuration
13. On the Configure Analysis Services credential page, specify the credentials on a non-privileged domain account that can be used to communicate with the datamarts.
14. On the Help Improve Microsoft System Center 2012 R2 Service Manager page, specify whether you want to participate in the CEIP program.
15. On the Use Microsoft Update To Help Keep Your Computer Secure And Up-To-Date page, select whether you want to use Microsoft Update as the source of updates for the server.
16. On the Installation Summary page, review the installation settings, and click Install to begin the installation.
Once the installation has completed, you can connect the Service Manager management server to the data warehouse by performing the following steps:
1. Open the Service Manager console using the credentials of a user that has administrative privileges on the data warehouse management server.
2. In the Administration workspace of the Service Manager console, click Register With Service Manager Data Warehouse.
3. On the Data Warehouse page of the Data Warehouse Registration Wizard, enter the name of the data warehouse server, and click Test Connection.
4. On the Credentials page, select or create a Run As account that has credentials to connect to the data warehouse server.
5. On the Summary page, click Create, to create the connection. Verify that data warehouse registration has been successful as shown in Figure 1-28.
FIGURE 1-28 Data warehouse registration
Service Manager Self-Service Portal
To install the Service Manager Self-Service Portal, ensure that you have deployed the necessary software prerequisites, including SQL Server and SharePoint 2010 SP2, and then by performing the following steps:
1. Mount the Service Manager installation media. In the AMD64 folder, run Setup.exe.
2. On the Service Manager Setup Wizard dialog box, click Service Manager Web Portal under Install (Optional).
3. On the Portal Parts page, select Web Content Server, and SharePoint Web Parts, as shown in Figure 1-29.
FIGURE 1-29 Portal parts
4. On the Product Registration page, provide a Name, Organization Name, and agree to the license terms.
5. On the Installation Location page, review the installation location. This will be the website that will host the portal. Figure 1-30 shows this page.
FIGURE 1-30 Installation location
6. On the System Check Results page, review the prerequisite check.
7. On the Configure The Service Manager Self-Service Portal name and port, select whether to use SSL, and configure the website name.
8. On the Select The Service Manager Database page, specify the location of the Service Manager database. To connect to this database, you’ll need to be signed on as a member of the Administrators user role on the Service Manager management server.
9. On the Configure The Account For The Self-Service Portal page, specify the account that will be used to connect to the Service Manager database. This account will be added to the Service Manager Administrators user role.
10. On the Configure The Service Manager SharePoint Web Site page, configure the properties of the Service Manager SharePoint website, including whether SSL encryption will be used. Figure 1-31 shows this page.
FIGURE 1-31 Service Manager SharePoint Web site
11. On the Configure The Account For The Service Manager SharePoint application pool, specify a domain account that will be used to run the application pool. This account does not require special credentials or group membership.
12. On the Help Improve Microsoft System Center 2012 R2 Service Manager page, choose whether to participate in the CEIP program.
13. On the Use Microsoft Update To Help Keep Your Computer Secure And Up-To-Date page, choose whether to use Microsoft Update to provide updates to the server.
14. On the Installation Summary page, click Install to complete the installation.
More Info: Installing Service Manager
You can learn more about installing Service Manager at http://technet.microsoft.com/en-us/library/hh495575.aspx.
Data Protection Manager
To install DPM, ensure that you have deployed the necessary software prerequisites and then perform the following steps:
1. Mount the DPM installation media, or run Setup.exe from the \SCDPM folder.
2. On the Data Protection Manager screen, shown in Figure 1-32, click Data Protection Manager, under Install.
FIGURE 1-32 Data Protection Manager installation dialog box
3. On the Microsoft Software License Terms page, accept the license terms to continue the installation.
4. On the Welcome page of the Data Protection Manager Setup Wizard, click Next.
5. On the Prerequisites Check page, specify the details of the SQL Server instance that will support DPM. Figure 1-33 shows this set to MEL-DPM. Click Check, and install to perform the prerequisite check, and to install any missing elements. If elements are missing, it may be necessary to restart the computer after the missing elements are installed and to rerun the installation wizard.
FIGURE 1-33 Prerequisites check
6. On the Product Registration page, specify the User Name, Company Name, and Product Key.
7. On the Installation Settings page, review the location specified for the DPM program files.
8. On the Microsoft Update Opt-In page, choose whether or not to use Microsoft Update to check for updates.
9. On the Customer Experience Improvement Program page, select whether you want to participate in the Customer Experience Improvement Program.
10. On the Summary Of Settings page, review the installation settings, and click Install to deploy DPM.
More Info: Installing Data Protection Manager
You can learn more about installing Data Protection Manager at http://technet.microsoft.com/en-us/library/hh758153.aspx.
Configuration Manager
To install a Configuration Manager stand alone primary site, ensure that you have deployed the necessary software prerequisites installed, and then perform the following steps:
1. Mount the Configuration Manager installation media.
2. On the System Center 2012 R2 Configuration Manager Setup dialog box, click Install.
3. On the Before You Begin page, click Next.
4. On the Available Setup Options page, shown in Figure 1-34, select Install A Configuration Manager Primary Site. A primary site is appropriate for the majority of private cloud deployments. You would consider deploying a central administration site and multiple primary site if you needed to support more than 50,000 clients, or had multiple separate administration teams in a large national/regional or international deployment.
FIGURE 1-34 Available setup options
5. On the Product Key page, enter a product key, or choose to install the evaluation version of the product.
6. On the Microsoft Software License Terms page, you will need to accept the license terms to continue the installation process.
7. On the Prerequisite Licenses page, you will need to accept each of the prerequisite licenses to continue the installation process.
8. On the Prerequisite Downloads page, you can choose to download prerequisite files, or, if you’ve used the Prerequisite Download Tool, use the previously downloaded files, as shown in Figure 1-35.
FIGURE 1-35 Use previously downloaded files
9. On the Language Selection page, choose the languages that Configuration Manager will display in the console and in reports.
10. On the Client Language Selection page, choose the client languages that Configuration Manager will support.
11. On the Site And Installation settings, configure a site code, and provide a site name. Figure 1-36 shows the Site Code set to MEL and the site name set to Melbourne. Both the site code and the site name must be unique in the organization. On this page you can also choose whether you will install the Configuration Manager console on this server.
FIGURE 1-36 Site code and site name
12. On the Primary Site Installation page, you choose whether you want to join the site to an existing hierarchy, in which case you specify the address of the central administration site server, or if you are going to install the primary site as a stand alone site. With System Center 2012 R2 Configuration Manager, you can install a primary site as stand alone, and then later add a central administration site if it becomes necessary to add additional sites. Figure 1-37 shows this page.
FIGURE 1-37 Primary site installation
13. On the Database Information page, shown in Figure 1-38, specify the settings of the SQL Server instance information. The database will be named CM_xxx, where xxx is the site code of the primary site.
FIGURE 1-38 Database information
14. On the Database Information page, specify the location of the Configuration Manager database’s database and log files.
15. On the SMS Provider Settings page, specify the details of which server will host the SMS Provider. The SMS Provider facilitates communication between the Configuration Manager console and the Configuration Manager site database. Generally the SMS Provider is installed on the site server. Figure 1-39 shows this page.
FIGURE 1-39 SMS Provider Settings
16. On the Client Computer Communication Settings page, select whether all site system roles will only accept HTTPS communication from clients, or whether you will configure the communication method on a per-role basis. If choosing to require HTTPS communication from clients, you will need to ensure that clients trust the Certification Authority that issued the certificate. If choosing to configure communication for each site system role, you can also select the option for clients to use HTTPS when available and to fall back to insecure application when a certificate is not available.
17. On the Site System Roles page, specify whether to install a management point and a distribution point. If deploying a single Configuration Manager server, you would add these roles. If deploying multiple servers, you might host these roles on separate servers. This page is shown inFigure 1-40.
FIGURE 1-40 Site System Roles
18. On the Customer Experience Improvement Program page, choose whether to join the Customer Experience Improvement Program.
19. Review the installation settings. Configuration Manager will perform the prerequisite check to verify that all necessary prerequisite elements are installed. As long as the prerequisite check only shows Warnings, you will be able to begin the installation.
After you complete the installation, you may choose to extend the Active Directory schema so that Configuration Manager clients that are members of the Configuration Manager server’s Active Directory environment can query Active Directory to locate site servers.
More Info: Installing Configuration Manager
You can learn more about installing Configuration Manager at http://technet.microsoft.com/en-us/library/gg712320.aspx.
Exam Tip
Remember which products have the Windows ADK as a prerequisite.
Thought experiment: Planning Service Manager deployment at Fabrikam
In this thought experiment, apply what you’ve learned about this objective. You can find answers to these questions in the “Answers” section at the end of this chapter.
You are in the process of planning a service manager deployment at Fabrikam. You are in the planning the number of SQL Server instances necessary to support the deployment. You also want to ensure that you have access to any necessary software prerequisites prior to performing deployment. With this information in mind, answer the following questions:
1. Which software prerequisites for the Service Manager management server are not roles or features already included with Windows Server 2012 R2?
2. How many SQL instances will you need to support the Service Manager management database and the Service Manager data warehouse database?
Objective summary
The processor, RAM, and storage requirements for each System Center product, and each element within that product vary. You should avoid using the minimum specified hardware required in production environments.
Each System Center product has a unique set of software requirements. To simplify the deployment process, you should deploy software prerequisites prior to performing installation.
Some System Center products have multiple elements, which must be installed in a specific order. Some products, such as Service Manager’s management server and data warehouse server, cannot be installed on the same host server.
While it is possible to deploy the databases for different System Center products on the same SQL Server instance, Microsoft recommends this configuration only for test environments.
Objective review
Answer the following questions to test your knowledge of the information in this objective. You can find the answers to these questions and explanations of why each answer choice is correct or incorrect in the “Answers” section at the end of this chapter.
1. You are preparing to deploy App Controller on a computer running Windows Server 2012 R2. Which of the following System Center 2012 R2 consoles must be present on the server before you can deploy App Controller?
A. Service Manager console
B. Orchestrator console
C. Operations Manager console
D. VMM console
2. You are preparing to deploy VMM. You are in the process of preparing a domain account that will function as the service account for the VMM service. Which of the following local groups on the server that hosts VMM must the account used by the VMM service be a member of?
A. Administrators
B. Virtual Machine Manager servers
C. Hyper-V Administrators
D. Backup Operators
3. You want to deploy the System Center 2012 R2 Service Manager Self-Service Portal on a computer running Windows Server 2012 R2. Which version of SharePoint server must you deploy to support this configuration?
A. SharePoint Server 2013 SP1
B. SharePoint Server 2010 SP1
C. SharePoint Server 2010 SP2
D. SharePoint Server 2013 RTM
4. You are planning on deploying System Center 2012 R2 Virtual Machine Manager as a highly available role on a Windows Server 2012 R2 failover cluster. Which of the following configuration choices must you make when deploying this configuration?
A. Use the Local System account for the VMM Service.
B. Use a domain account for the VMM Service.
C. Store the encryption keys in Active Directory.
D. Deploy the SQL Server instance on a highly available virtual machine.
Objective 1.3: Upgrade System Center components
This objective deals with transitioning from one version of a System Center product to the System Center 2012 R2 version. It provides general detail about how you can transition from one version of a product, such as Virtual Machine Manager 2008 R2, to Virtual Machine Manager 2012 R2. This section also provides links to more detailed documentation that details the more intricate complexities that must be taken into account when transitioning between product versions.
This objective covers the following topics:
Upgrading or migrating from versions prior to System Center 2012.
Upgrading from System Center 2012 or System Center 2012 SP1.
Upgrading or migrating from versions prior to System Center 2012
Depending on the product and the versions involved, you can perform an in-place upgrade, or a migration from a pre-System Center 2012 version of a product, to the System Center 2012 R2 version of that product. In this section you’ll learn about transitioning from pre-System Center 2012 versions of products, such as VMM 2008 R2 SP1, or Configuration Manager 2007 SP2. Later in the chapter, you’ll learn about upgrading from the System Center 2012 or System Center 2012 SP1 version of a product, to the System Center 2012 R2 version of the product.
VMM
VMM supports performing an in-place upgrade from VMM 2008 R2 SP1, to VMM 2012 R2. In-place upgrades involve performing the upgrade on the existing server. When the upgrade is complete, the server that hosted the previous version of the product now hosts the new version of the product. When you perform an in-place upgrade from VMM 2008 R2 SP1 to VMM 2012 R2, you will retain the configuration and settings of the VMM 2008 R2 SP1 deployment in the new VMM 2012 R2 environment.
You can perform this in-place upgrade as long as the following conditions are met:
You continue to use Windows Server 2008 R2 as the host operating system. If VMM 2008 R2 SP1 is installed on Windows Server 2008 with SP2, you will need to upgrade the host operating system to Windows Server 2008 R2 before you can upgrade VMM 2008 R2 SP1 to VMM 2012 R2.
You continue to use SQL Server 2008 R2 SP2 to host the VMM database. VMM 2012 R2 can use SQL Server 2008 R2 SP2 to host the VMM database. If the database used with VMM 2008 R2 SP1 is running an earlier version of SQL Server, you will need to update to SQL Server 2008 R2 SP2 before upgrading to VMM 2012 R2.
You will need to ensure that Windows AIK for Windows 7 is installed on the VMM 2008 R2 SP1 server.
Library servers running Windows Server 2003 must be upgraded to Windows Server 2008 R2, as VMM 2012 R2 does not support library servers running on Windows Server 2003.
You also have the option of performing an upgrade where you install VMM 2012 R2 on a separate computer, and upgrade the database from the VMM 2008 R2 SP1 installation. As an alternative, you can backup the VMM 2008 R2 SP1 database from the original SQL Server instance and restore it on a newly deployed instance of SQL Server. You can then use this restored instance as part of the upgrade process when deploying VMM 2012 R2 on a new computer.
During the upgrade process you will be asked to specify which account to use for the System Center Virtual Machine Manager Service, and whether you want to use distributed key management to store encryption keys within the AD DS database. You can choose to use the Local System account or a domain account. If the VMM 2008 R2 deployment is configured to use a domain account for the VMM service, you must use the same domain account for the VMM 2012 R2 VMM service; otherwise encrypted data will not be preserved. Encrypted data will be preserved if the VMM 2008 R2 service account was configured to use the Local System account, and you choose to use a domain account for the VMM 2012 R2 service only if you choose to use distributed key management.
The VMM 2012 R2 upgrade process includes an automatic rollback function in the event that the upgrade fails. This will return the deployment to VMM 2008 R2.
More Info: Upgrading VMM
You can learn more about upgrading VMM at http://technet.microsoft.com/en-us/library/dn469623.aspx.
Orchestrator
System Center 2012 Orchestrator was the first version of Orchestrator. Prior to the release of System Center 2012 Orchestrator, the product was known as Opalis. You cannot perform an in-place upgrade from Opalis 6.3 to System Center 2012 R2 Orchestrator. You can perform a migration of Opalis policies to Orchestrator runbooks. To migrate, perform the following general steps:
1. Export the Opalis Integration Server 6.3 policies and global settings.
2. Import the policies on a computer where the Orchestrator Runbook Designer is installed. When prompted for a password, leave the Password option blank.
More Info: Migrating from Opalis to Orchestrator
You can learn more about migrating from Opalis to Orchestrator at http://technet.microsoft.com/en-us/library/hh420350.aspx.
Operations Manager
You can perform an in-place upgrading from Operations Manager 2007 R2 CU4 to Operations Manager 2012 R2 as long as all of the servers in the Management Group support Operations Manager 2012 R2.
When performing an in-place upgrade, you must upgrade servers in the Management Group in the following order:
1. Upgrade manually deployed agents, secondary management servers, and gateways, before you upgrade the Management Group.
2. Perform the Management Group upgrade on the Operations Manager 2007 R2 CU4 server that hosts the RMS. The exceptions to this rule include if the RMS is deployed on a 32-bit operating system, or if the RMS server is clustered. In these scenarios it is necessary to upgrade from a secondary server.
Prior to performing the upgrade, perform the following steps:
1. Import the Upgrade Helper Management Pack.
2. Back up the RMS encryption key.
3. Disable Notification Subscriptions.
4. Disable Connectors.
5. Verify that the Operational Database has more than 50 percent free space. Increase free space if needed.
6. Verify that the SQL Server collation is supported.
7. Backup the Operations Manager database.
8. Restore the RMS encryption key on a secondary management server if the RMS cannot be directly upgraded.
9. Upgrade SQL Server Reporting Services if SQL Server 2008 R2, or SQL Server 2008 R2 SP1 is not currently being used for the Reporting Services instance.
Once you have completed the pre-upgrade tasks, perform the following steps:
1. Upgrade all manually deployed Operations Manager agents.
2. Upgrade the secondary management servers.
3. Upgrade the gateway servers.
4. Perform the Management Group upgrade on the server that hosts the Operations Manager 2007 R2 CU4 RMS role.
5. Upgrade push-installed management agents.
More Info: Upgrading from Operations Manager 2007 R2
You can learn more about upgrading from Operations Manager 2007 R2 at http://technet.microsoft.com/en-us/library/hh476934.aspx.
Service Manager
You can upgrade from Service Manager 2010 SP1 to System Center 2012 R2 Service Manager. To perform an in-place upgrade, the source server needs to be able to support System Center 2012 R2 Service Manager. Upgrading involves performing the following general steps:
1. Back up the Service Manager management database and the data warehouse database.
2. Determine which data warehouse jobs are running.
3. Disable the data warehouse job schedules.
4. Verify that data warehouse jobs are no longer running.
5. Stop the Self-Service Portal.
6. Upgrade the data warehouse management server by performing an in-place upgrade.
7. Upgrade the Service Manager management server by performing an in-place upgrade.
8. Upgrade the Service Manager console on any computers that host the Service Manager 2012 SP1 console.
More Info: Upgrading from Service Manager 2012 SP1
You can learn more about upgrading from Service Manager 2012 SP1 at http://technet.microsoft.com/en-us/library/hh524234.aspx.
Data Protection Manager
You can upgrade from DPM 2010 with QFE4 to System Center 2012 R2 DPM as long as DPM 2010 is deployed on Windows Server 2008 R2 or a 64-bit version of Windows Server 2008. DPM 2012 R2 can be deployed on Windows Server 2008 as long as it is the x64 version. Prior to performing the upgrade, ensure that the following pre-requisites are met:
1. Ensure that at least 4.5 GB is available.
2. Back up the DPM 2010 database.
3. Stop sharing any tape libraries.
4. Upgrade agents on protected computers.
5. Add Microsoft$DPM$ACCT to the Access Control List (ACL) for the DPMDB folder, assigning the Full Control permission.
Once these steps have been taken, starting the DPM 2012 R2 installation process will trigger the upgrade, as the installation process detects the installation of DPM 2010.
More Info: Upgrade from DPM 2010
You can learn more about upgrading from DPM 2010 at http://technet.microsoft.com/en-us/library/hh848301.aspx.
Configuration Manager
You cannot perform an in-place upgrade of Configuration Manager 2007 SP2 to Configuration Manager 2012 R2. Instead you must create a new Configuration Manager 2012 R2 hierarchy and migrate objects from the Configuration Manager 2007 SP2 hierarchy to the new hierarchy. Once the migration is complete, you decommission the original hierarchy. When performing a migration, you specify a Configuration Manager 2007 SP2 source hierarchy, choosing a top-level site in that hierarchy as the source site. A migration job can migrate data from one or more source sites. You can only migrate data from Configuration Manager 2007 SP2 primary sites.
To perform the migration:
The account used to perform the migration must be a member of the Infrastructure Administrator security role in the destination site. This role has the necessary permissions to manage migration operations.
Configure the Source Site Account. This account needs read permission on all objects in the Configuration Manager 2007 R2 site. To upgrade distribution points, this account needs Read, Execute, and Delete permissions on the Site class on the Configuration Manager 2007 site server.
Configure the Source Site Database Account. This account is used to query the SQL Server site database of the source site. This account needs Connect, Execute, and Select permissions on the source site database.
Before migrating software updates, deploy a software update point in the Configuration Manager 2012 R2 hierarchy.
The data gathering process identifies objects in the source site that can be migrated. You can migrate the following objects from a Configuration Manager 2007 hierarchy to a Configuration Manager 2012 R2 hierarchy:
Collections
Advertisements
Boundaries
Software distribution packages
Virtual application packages
Software updates:
Deployments
Deployment packages
Templates
Software update lists
Operating system deployment:
Boot images
Driver packages
Drivers
Images
Packages
Task sequences
Desired configuration management:
Configuration baselines
Configuration items
Asset Intelligence customizations
Software metering rules
The following objects cannot be migrated from a Configuration Manager 2007 R2 hierarchy to a Configuration Manager 2012 R2 hierarchy:
Queries
Security rights and instances for the site and objects
Configuration Manager 2007 reports from SQL Server Reporting Services
Configuration Manager 2007 web reports
Client inventory and history data
AMT client provisioning information
Files in the client cache
Once the data gathering process is complete, you configure migration jobs to migrate specific objects to the Configuration Manager 2012 R2 environment. You should only migrate Configuration Manager clients after all objects that the client uses have been migrated. For example, you might have an advertisement for a program that is deployed to a custom collection that contains a specific client. Migrate the advertisement, program, and the custom collection before migrating the client.
More Info: Migration to Configuration Manager
You can learn more about migrating to System Center 2012 R2 Configuration Manager at the following address: http://technet.microsoft.com/en-us/library/gg681981.aspx.
Upgrading between System Center 2012, System Center 2012 SP1, and 2012 R2
Some organizations will have deployed System Center 2012, or System Center 2012 SP1, and will wish to upgrade to System Center 2012 R2. This is more straightforward than migrating from an earlier version as software and hardware configurations that support System Center 2012, and System Center 2012 SP1 support System Center 2012 R2. You can perform in-place upgrades to transition from the System Center 2012 R2 or System Center 2012 R2 SP1 version of a product to the System Center 2012 R2 version of a product.
If you have multiple System Center 2012 or System Center 2012 SP1 products deployed in your environment, you need to ensure that you upgrade them in the following order:
1. Orchestrator
2. Service Manager
3. DPM
4. Operations Manager
5. Configuration Manager
6. VMM
7. App Controller
Upgrading Orchestrator
If you plan to install Service Manager Automation to your environment, you should install it prior to upgrading Orchestrator to 2012 R2. The general process of upgrading Orchestrator involves:
1. Backing up the Orchestrator database.
2. Stopping all Orchestrator runbooks.
3. Uninstalling the Orchestrator management server, runbook servers, the Web Service, and the Runbook Designer.
4. Installing the System Center 2012 R2 Orchestrator management server.
5. Install additional System Center 2012 R2 Orchestrator runbook servers.
6. Install the System Center 2012 R2 Runbook Designer.
7. Install Orchestrator Web Service.
If you have configured Orchestrator to be monitored by Operations Manager, you should place Orchestrator servers into maintenance mode prior to performing the upgrade, and take them out of maintenance mode once the upgrade is complete. To upgrade integration packs, uninstall the earlier version of the integration pack, and then install the newer integration pack.
Upgrading Service Manager
The general process of upgrading Service Manager from 2012 to 2012 R2 involves doing the following:
1. Backup the databases and management packs.
2. If Operations Manager is monitoring the Service Manager servers, place them into maintenance mode.
3. Remove the integration pack for Service Manager 2012 from Orchestrator.
4. Upgrade the SQL Server 2008 R2 AMO to the SQL Server 2012 AMO.
5. Upgrade the data warehouse management server. You will need to stop data warehouse jobs.
6. Upgrade the Service Manager management server.
Upgrading Data Protection Manager
The general process of upgrading Data Protection Manager from 2012 to 2012 R2 involves doing the following:
1. If Operations manager monitors the DPM servers, put them into maintenance mode prior to commencing upgrade.
2. If you are using the DPM integration pack for Orchestrator, remove this integration pack.
3. Remove any tape library sharing.
4. Perform the DPM upgrade by running Setup.exe from the installation media. The existing DPM installation will be detected and installer will run in upgrade mode.
5. Upgrade the DPM protection agents on protected computers and servers.
6. Run a replica consistency check as all replicas will be marked as inconsistent after the upgrade.
7. Re-enable tape library sharing.
Upgrading Operations Manager
The general process of upgrading Operations Manager from 2012 to 2012 R2 involves doing the following:
If you are upgrading a single-server Management Group, you start the upgrade in the same manner as you would start Operations Manager installation, with the installation process detecting the existing deployment and entering upgrade mode. In upgrade mode, the Operations Manager Upgrade Wizard will perform a prerequisite check and offer solutions to allow you to resolve any blocking issues. If there are no blocking issues, you can perform the upgrade by completing the wizard.
If upgrading a multi-server Management Group, you must upgrade the management servers first, followed by gateways, operations consoles, agents, the web console, reporting, and finally Audit Collection Services. Upgrading each server involves running setup from the installation media as you would when performing a new installation. As Operations Manager 2012 does not have an RMS, you don’t have to upgrade any specific management server first.
Upgrading Configuration Manager
You can’t perform a direct upgrade from Configuration Manager 2012 to Configuration Manager 2012 R2. You must instead upgrade to Configuration Manager 2012 SP1, and then perform a second upgrade to Configuration Manager 2012 R2.
Prior to performing the upgrade you should:
Back up the site database.
Disable all site maintenance tasks.
Run the prerequisite checker for the new Configuration Manager version.
Ensure that there are no pending restarts on any servers you will upgrade.
Perform the installation of the new Configuration Manager version.
Upgrade Configuration Manager clients.
You can configure automatic client upgrade through Site Settings Properties, as shown in Figure 1-41.
FIGURE 1-41 Upgrade Configuration Manager client
When upgrading from Configuration Manager 2012 or Configuration Manager 2012 SP1, to Configuration Manager 2012 R2, you must upgrade sites in the following order:
1. Upgrade Central Administration site
2. Upgrade primary sites
3. Upgrade secondary sites
Prior to performing the upgrade, ensure that you remove any instances of the Windows AIK, and replace them with the Windows ADK.
Upgrading VMM
The process of upgrading to System Center 2012 R2 VMM from System Center 2012 VMM, or System Center 2012 SP1 VMM, involves uninstalling the previous version of VMM and installing the 2012 R2 version of VMM. When uninstalling the previous version of VMM, ensure that you select the Retain Data option. When performing the installation of VMM 2012 R2, use the Existing Database option, and specify the location of the VMM database from the previous version. You will be prompted to upgrade the database.
More Info: System Center 2012 to 2012 R2 Upgrade
You can learn more about upgrading between System Center 2012 and System Center 2012 R2 at http://technet.microsoft.com/en-us/library/dn521010.aspx.
Exam Tip
Remember that you can’t directly upgrade Configuration Manager 2007 SP2, and must instead perform a migration to a new Configuration Manager 2012 R2 hierarchy.
Thought experiment: Upgrading System Center at Tailspin Toys
In this thought experiment, apply what you’ve learned about this objective. You can find answers to these questions in the “Answers” section at the end of this chapter.
You have Opalis 6.3 and Service Manager 2010 deployed in your organization. You also want to upgrade your Service Manager deployment, which includes a data warehouse server, to Service Manager 2012 R2. You also want to retain the automation you created for Opalis 6.3 in Orchestrator 2012 R2. With this information in mind, answer the following questions:
1. Which should you upgrade first, the Service Manager data warehouse server, or the Service Manager management server?
2. What should you do to retain the automation you created for Opalis 6.3 in Orchestrator 2012 R2?
Objective summary
In-place upgrades are supported for some pre-System Center 2012 products, such as Operations Manager 2007 R2, to the System Center 2012 R2 version as long as the operating system and hardware that hosts the source version of the product supports the upgraded product.
Prior to upgrading each product, administrators must perform a set of product specific actions such as disabling certain SQL jobs.
Prior to upgrading, you should always create a backup.
Objective review
Answer the following questions to test your knowledge of the information in this objective. You can find the answers to these questions and explanations of why each answer choice is correct or incorrect in the “Answers” section at the end of this chapter.
1. You are in the process of upgrading your System Center 2012 SP1 deployment to System Center 2012 R2. You have deployed App Controller, Configuration Manager, DPM, Operations Manager, Orchestrator, Service Manager, and VMM. Which of the following products should you upgrade first?
A. DPM
B. Service Manager
C. Operations Manager
D. VMM
2. Your VMM 2008 R2 deployment is configured to use a domain account for the VMM service. Which of the following steps must you take when performing an in-place upgrade to VMM 2012 R2?
A. Use a new domain account for the VMM 2012 R2 VMM service
B. Use the same domain account for the VMM 2012 R2 VMM service
C. Use the Network Service account for the VMM 2012 R2 VMM service
D. Use the Local System account for the VMM 2012 R2 VMM service.
3. You want to perform a direct upgrade of Operations Manager 2007 to Operations Manager 2012 R2. Which versions support this direct upgrade assuming other operating system, SQL Server, hardware, and software requirements are met?
A. Operations Manager 2007
B. Operations Manager 2007 R2 CU4
C. You can’t perform a direct upgrade of Operations Manager 2007 to Operations Manager 2012 R2.
D. Operations Manager 2007 R2 CU3
Answers
This section contains the solutions to the thought experiments and answers to the objective review questions in this chapter.
Objective 1.1: Thought experiment
1. You can deploy VMM as a clustered role on a failover cluster, and the SQL database that supports it as a clustered role on a separate failover cluster. This meets the goal of making VMM highly available without deploying VMM on a highly available virtual machine.
2. You can configure a DPM secondary server as a replica. You can also deploy the DPM database on a SQL Server failover cluster. This meets the goal of making DPM highly available without deploying the workload in a virtual machine.
Objective 1.1: Review
1. Correct answer: C
A. Incorrect: While VMM does include the ability to determine whether a VMM server or virtualization host is compliant against a software update baseline, VMM does not include the ability to monitor the software update compliance of other virtual machines running in the private cloud.
B. Incorrect: Operations Manager does not include the ability to monitor software update compliance.
C. Correct: You can use Configuration Manager to monitor software update compliance for Windows 8.1 virtual machines.
D. Incorrect: Orchestrator does not include the ability to monitor software update compliance.
2. Correct answers: B, C, and D
A. Incorrect: You can only deploy one Orchestrator management server.
B. Correct: Deploying multiple runbook servers will make the Orchestrator deployment more highly available.
C. Correct: Deploying the Orchestration database on a SQL Server failover cluster will make the Orchestrator deployment more highly available.
D. Correct: Deploying the management server on a highly available virtual machine will make the Orchestrator deployment more highly available.
3. Correct answers: A, C and D
A. Correct: The encryption key allows Service Manager to access the encrypted data in the Service Manager database.
B. Incorrect: You will need to use the existing encryption key to access the data in the restored Service Manager database.
C. Correct: The server that will function as the replacement Service Manager management server must have the same name as the originally failed server.
D. Correct: You must install SQL Server and recover the Service Manager database before using the Service Manager installation media to recover Service Manager.
Objective 1.2: Thought experiment
1. The Service Manager management server requires the SQL Server 2008 R2 native client or the SQL Server 2012 native client, and the Microsoft Report Viewer Redistributable.
2. You will need at least two because the Service Manager management database and the Service Manager data warehouse database must be deployed on separate SQL Server instances.
Objective 1.2: Review
1. Correct answer: D
A. Incorrect: The Service Manager console is not a software prerequisite for the App Controller console.
B. Incorrect: The Orchestrator console is not a software prerequisite for the App Controller console.
C. Incorrect: The Operations Manager console is not a software prerequisite for the App Controller console.
D. Correct: The VMM console is a software prerequisite for the App Controller console.
2. Correct answer: A
A. Correct: The domain account that will function as the VMM service account must be a member of the local Administrators group on the VMM server.
B. Incorrect: The domain account that will function as the VMM service account does not need to be a member of the local Virtual Machine Manager Servers group on the VMM server.
C. Incorrect: The domain account that will function as the VMM service account does not need to be a member of the local Hyper-V Administrators group on the VMM server.
D. Incorrect: The domain account that will function as the VMM service account does not need to be a member of the local Backup Operators group on the VMM server.
3. Correct answer: C
A. Incorrect: System Center 2012 R2 Service Manager’s Self-Service Portal cannot be installed on SharePoint 2013 SP1.
B. Incorrect: While System Center 2012 R2 Service Manager’s Self-Service Portal can be installed on SharePoint 2010 SP1, SharePoint 2010 SP1 cannot be installed on Windows Server 2012 R2.
C. Correct: SharePoint Server 2010 SP2 is the only version of SharePoint that can be installed on Windows Server 2012 R2, and which is also supported for the Service Manager 2012 R2 Self-Service Portal.
D. Incorrect: System Center 2012 R2 Service Manager’s Self-Service Portal cannot be installed on SharePoint 2013 RTM.
4. Correct answers: B and C
A. Incorrect: You must use a domain account for the VMM service when deploying VMM as a highly available role on a Windows Server 2012 R2 failover cluster.
B. Correct: You must use a domain account for the VMM service when deploying VMM as a highly available role on a Windows Server 2012 R2 failover cluster.
C. Correct: You must store the encryption keys in Active Directory when deploying VMM as a highly available role on a Windows Server 2012 R2 failover cluster.
D. Incorrect: While the SQL Server instance should be highly available, it is not necessary for the instance to be deployed on a highly available virtual machine. You could deploy the SQL Server instance on a failover cluster to accomplish the same goal.
Objective 1.3: Thought experiment
1. When upgrading from Service Manager 2010 to Service Manager 2012 R2, you must upgrade the data warehouse server before upgrading the Service Manager management server.
2. You will need to export the Opalis policies and import them as runbooks into Orchestrator 2012 R2.
Objective 1.3: Review
1. Correct answer: B
A. Incorrect: You should upgrade Service Manager before DPM.
B. Correct: Of the products listed, you should upgrade Service Manager first. You should upgrade Orchestrator before Service Manager, but Orchestrator was not listed as an answer.
C. Incorrect: You should upgrade Service Manager and DPM before upgrading Operations Manager.
D. Incorrect: You should upgrade Services Manager, DPM, and Operations Manager before upgrading VMM.
2. Correct answer: B
A. Incorrect: If the VMM 2008 R2 deployment is using a specific domain account for the VMM service, you must use the same domain account for the VMM 2012 R2 service, otherwise encrypted data will not be retained.
B. Correct: If the VMM 2008 R2 deployment is using a specific domain account for the VMM service, you must use the same domain account for the VMM 2012 R2 service, otherwise encrypted data will not be retained.
C. Incorrect: If the VMM 2008 R2 deployment is using a specific domain account for the VMM service, you must use the same domain account for the VMM 2012 R2 service, otherwise encrypted data will not be retained.
D. Incorrect: If the VMM 2008 R2 deployment is using a specific domain account for the VMM service, you must use the same domain account for the VMM 2012 R2 service, otherwise encrypted data will not be retained.
3. Correct answer: B
A. Incorrect: You can perform a direct upgrade of Operations Manager 2007 R2 CU4 to Operations Manager 2012 R2. You cannot do this with previous versions of Operations Manager.
B. Correct: You can perform a direct upgrade of Operations Manager 2007 R2 CU4 to Operations Manager 2012 R2.
C. Incorrect: You can perform a direct upgrade of Operations Manager 2007 R2 CU4 to Operations Manager 2012 R2. You cannot do this with previous versions of Operations Manager.
D. Incorrect: You can perform a direct upgrade of Operations Manager 2007 R2 CU4 to Operations Manager 2012 R2. You cannot do this with previous versions of Operations Manager.