Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
Let’s face it: System Center 2012 is BIG. Microsoft literally took seven completely separate products – three of which were HUGE on their own, and combined them into a single product. It’s no wonder so many IT Pros and hopefuls are so intimidated by it.
I am not going to guide you through the actual installation of products in these articles. My reasoning behind that is that the installation process is fairly simple for each component; it is easy to get lost along the way, but by reading the guidance in your error messages you will be able to make it through. Nonetheless during the next week I will record a series of webcasts guiding you through the actual installation processes.
Additionally you do not need to go out and buy the software – you can download the evaluation versions which are good for 180 days by clicking on the following links: Download Windows Server 2012 and System Center 2012. Additionally you will need to download SQL Server; for these demos I used SQL Server 2012, which you can download as an evaluation as well.
A little bit of knowledge will take you a long way; in this article we are going to get you started with three of the components which are central to your private cloud: Virtual Machine Manager (VMM) and Operations Manager (OpsMgr).
I consider Virtual Machine Manager to be the focal point of the Private Cloud; it is the module where we create the Private Cloud, manage the resources, and build and manage the virtual machines. It does not work in a vacuum of course; but as with most of the components of System Center 2012 it interacts ‘upstream’ and ‘downstream’ with two main components: Orchestrator for scripting and runbooks, and OpsMgr for monitoring, reporting, and intelligent placement. For today we will focus on the connectivity requirements between VMM and OpsMgr.
The relevant portion of my virtual network is outlined in this diagram. All of these components are virtual (machines and switches) within one of the primary Hyper-V hosts.
The first step we will take is to prepare the OpsMgr to connect to VMM. In order to do this we need the following:
This is easy enough… attach the OpsMgr media to the VMM virtual machine and install only the console.
I am a strong believer in the old AGGUDLP philosophy – user Accounts go into Global Groups, which go into Universal Groups, which go into Domain Local Groups, which are then assigned permissions. As such I have created a Security Group in Active Directory called OpsMgr&VMM which I will assign to these roles.
Now that I have provided the appropriate credentials, I can move on to the Management Packs.
Several management packs are required in order to join OpsMgr and VMM, all of which are free and easily downloaded from Microsoft.com, or from within the OpsMgr Console. They are:
**Note: If your Operations Manager VM is not connected to the Internet you can download the management packs individually and then import them from Disk.
Now that we have laid the groundwork, connecting VMM and OpsMgr is relatively simple.
PowerShell! The script to connect the OpsMgr server to the VMM server should look like this: $vmmCredential = Get-Credential $opsMgrServerCredential = Get-SCRunAsAccount -Name "RunAdmin" -ID "02f51024-f502-44cd-94c4-87e304124818" New-SCOpsMgrConnection -EnablePRO $true -EnableMaintenanceModeIntegration $true -OpsMgrServer "swmi-opsmgr" -RunAsynchronously -VMMServerCredential $vmmCredential -OpsMgrServerCredential $opsMgrServerCredential
The script to connect the OpsMgr server to the VMM server should look like this:
$vmmCredential = Get-Credential $opsMgrServerCredential = Get-SCRunAsAccount -Name "RunAdmin" -ID "02f51024-f502-44cd-94c4-87e304124818" New-SCOpsMgrConnection -EnablePRO $true -EnableMaintenanceModeIntegration $true -OpsMgrServer "swmi-opsmgr" -RunAsynchronously -VMMServerCredential $vmmCredential -OpsMgrServerCredential $opsMgrServerCredential
At this point you are ready to go! OpsMgr will be monitoring your VMM environment, which means that not only can you begin monitoring the health of your VMM server, but your entire environment, allowing for great features like Performance and Resource Optimization (PRO), and more intelligent patch management using maintenance mode.
We’ll leave it here for now because you now have a lot to play with; start exploring your VMM on your own and see what it’s made of; start generating reports in OpsMgr and see what kind of data you can extract!
In my next article we will introduce another System Center component into play. Stay tuned for Orchestrator!