Building a private cloud with System Center 2012: Part 2

Summary:The next stage in our investigation of Microsoft's Private Cloud Evaluation Software bundle involves deploying and configuring a series of Integration Packs that allow the various System Center tools to work together.

Configuring the Integration Packs
Next we needed to configure the Integration Packs to use our servers. This meant specifying the name of each server, its host domain and a suitable username and password, starting with the Virtual Machine Manager pack.

Before we could do that, however, we had to quickly log onto our VMM server and use PowerShell to allow configuration files and scripts to be run remotely.

System Center 2012
Before the VMM Integration Pack can be configured, PowerShell must be used to allow remote execution of scripts.

That done, we opened the Orchestrator Runbook Designer and, following the instructions in the evaluation guide, configured our VMM Integration Pack. Note that our test domain is called ellipsis.local and we were using the local administrator account for authentication.

System Center 2012
Each of the Integration Packs has to be configured for it to work.

We then repeated the process for each of the four other Integration Packs — not forgetting, when you do it, to include the Active Directory pack to save time rather than following the guide to the letter.

Some care is also needed to make sure that you type all the names in correctly as you're creating a fairly complex web of servers. Although some of the packs let you test the connection (as in Service Manager, shown below), some don't provide the option.

System Center 2012
Some of the Integration Pack connections can be tested, but not all.

Additionally, when it comes to the Operations Manager Integration Pack you must first install the Operations Manager console on the Orchestrator server. For some reason, the process required is documented in Appendix B at the back of the evaluation guide, where you're told that the Operations Manager console needs to be installed on the Virtual Machine Manager server as well.

Fortunately this proved to be relatively straightforward using the Operations Manager setup program included in the original Private Cloud download. We did, though, have to first install .NET Framework 4.0 onto our Orchestrator server and, once we had located it, the Microsoft Report Viewer 2010 distributable onto both this and our VMM server.

System Center 2012
The Operations Manager console has its own prerequisites and needs to be installed on both the Orchestrator and VMM server.

We were then able to go back to the Orchestrator VMM and configure the Operations Manager Integration Pack, this one having the option to test the connection.

System Center 2012
We had no problems configuring the Operations Manager Integration Pack.

And finally, we repeated the process for the Data Protection Manager, the only prerequisite here being to first enable PowerShell remoting on the DPM server by typing in another simple PowerShell command.

A magnum opus
The only other work required was to create some user accounts for the exercises to follow. The main ones were Jeff, our mythical datacentre administrator and Emily, an application owner responsible for a line-of-business application to be deployed on our Private Cloud. A couple of others are also required, but we'll talk about them, and the other steps required to join all our System Center components together, in part 3 of what's rapidly becoming something of a magnum opus.

Topics: Cloud, Microsoft, Reviews, Virtualization

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

The best of ZDNet, delivered

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.