Jump to content


AdinE

SCOM 2012 SP1 in a LAB – Installation (Part A – Create The Lab Environment)

Recommended Posts

SCOM 2012 SP1 in a LAB – Installation (Part A – Create The Lab Environment)

 

TechNet Recommended Reading:
Release Notes for the System Center 2012 Operations Manager SP1: http://technet.microsoft.com/en-us/library/jj656651.aspx

Deploying System Center 2012 - Operations Manager: http://technet.microsoft.com/en-us/library/hh278852.aspx

System Requirements: http://technet.microsoft.com/en-us/library/jj656654.aspx

Getting Started with System Center 2012 - Operations Manager: http://technet.microsoft.com/en-us/library/hh509025.aspx

What’s New in Operations Manager: http://go.microsoft.com/fwlink/p/?LinkID=223462

Key Concepts for Operations Manager: http://go.microsoft.com/fwlink/p/?LinkID=224022

Operations Manager Release Notes: http://go.microsoft.com/fwlink/?LinkID=221147

Operations Manager for System Center 2012 Supported Configurations: http://go.microsoft.com/fwlink/p/?LinkId=223642

Deployment Guide for Operations Manager: http://go.microsoft.com/fwlink/p/?LinkID=213291

Operations Guide for Operations Manager: http://go.microsoft.com/fwlink/p/?LinkID=207751

 

Hardware Requirements

Note: The following page on TechNet describes the recommend hardware requirements for the Management Server(s) along with other features. Use this information to help plan for hardware requirements for your Management Server(s).

 

Management Server

  • Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
  • Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
  • Processor Architecture: must be x64.
  • Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
  • Windows Remote Management: Windows Remote Management must be enabled for the management server.
  • .NET Framework 4 is required.

 

Installation

There are 2 different deployment scenarios that you can use: Single-Server, and Distributed. Microsoft has created 2 diagrams to show the different deployments. In our example, we are going to use the Single-Server type.

Single-Server.gif

Single-Server Deployment of Operations Manager

 

Distributed.gif

Distributed Deployment of Operations Manager

 

For the purpose of our demonstration and simplicity, we are going to use the single server method, and install all features/elements within 1 server, this includes the databases, web console, reporting, ACS, etc.

 

 

Introduction:

I use Hyper-V in my LAB and that's what all these virtual machines will be running on. In my lab, I have Windows Server 2012 Datacenter installed as the server OS on the host machine. All other virtual machines will be running Windows Server 2012 Standard edition, with the graphical user interface (GUI).

 

My hardware consists of the following:

§ Intel Xeon E5-2620

§ Asus P90X79 WS

§ 64 GB G.Skill Ripjaws Z Series

§ 2 x 256 GB Samsung 840 Pro Series SSD

 

High Level Plan

Here is a high level of what we are going to complete in this initial part of the series.

1. Create the Lab Environment

2. Install the Operating System

3. Install Active Directory Domain Services

4. Install SQL Server

5. Install System Center Operations Manager

 

In a later posts, we will also cover installing agents, reporting/dashboards, management packs, ACS, etc.

 

So now let’s start with the first part, creating the lab environment.

 

 

Create the Lab Environment: Hyper-V Configuration

As mentioned, my environment uses Hyper-V. So, we’re going to start by configuring Hyper-V for our needs, and creating the Virtual Machines (VMs) required for our lab.

 

The first thing we need to do is setup a Virtual Switch for the VMs to connect through.

 

Launch Server Manager, click on Tools, and select Hyper-V Manager.

Server Manager - Tools.png

 

When Hyper-V loads, it will have nothing in it. Even if we were to create a VM, it wouldn’t have a network connection to use.

Hyper-V Manager.png

 

So we’ll start with creating a Virtual Switch. As you can from my screenshot, I have 2 LAN ports on my host. One of them has a connection to my home network and the Internet.

Network Connections.png

 

In the Hyper-V Manager, click the Virtual Switch Manager from the Actions pane.

Virtual Switch Manager.png

 

Now, click on the Create Virtual Switch button.

New Virtual Switch.png

 

From here, you now need to configure the virtual switch that your VMs will use. Give it a name to clearly identify it (in my case I called it ‘External Network’), and choose the connection type. For more information about virtual networks, see the following TechNet article: http://technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx.

 

Here is an excerpt from the article:

  • External virtual networks. Use this type when you want to provide virtual machines with access to a physical network to communicate with externally located servers and clients. This type of virtual network also allows virtual machines on the same virtualization server to communicate with each other. This type of network may also be available for use by the management operating system, depending on how you configure the networking. (The management operating system runs the Hyper-V role.) For more information, see “A closer look at external virtual networks” later in this topic.
  • Internal virtual networks. Use this type when you want to allow communication between virtual machines on the same virtualization server and between virtual machines and the management operating system. This type of virtual network is commonly used to build a test environment in which you need to connect to the virtual machines from the management operating system. An internal virtual network is not bound to a physical network adapter. As a result, an internal virtual network is isolated from all external network traffic.
  • Private virtual networks. Use this type when you want to allow communication only between virtual machines on the same virtualization server. A private virtual network is not bound to a physical network adapter. A private virtual network is isolated from all external network traffic on the virtualization server, as well any network traffic between the management operating system and the external network. This type of network is useful when you need to create an isolated networking environment, such as an isolated test domain.

 

For our demonstration, we are going to use an External Network so that the VMs can communicate with the Host system. Make all the appropriate selections and so forth, and then press OK. You may encounter the following warning message. This is because we are remotely connecting to the Host machine using the same network connection that we are about to setup as a Virtual Switch (hence selecting the ‘Allow management operating system to share this network adapter’ checkbox). Press ‘Yes’ to the dialog.

Apply Networking Changes.png

 

Now that we have the virtual switch setup, we can start creating VMs for our lab.

 

 

Create the Virtual Machines

Let’s now create the VM’s we will need for the lab, specifically one for Active Directory, and another for SCOM (since we are install all roles within the same server).

 

In Hyper-V Manager, from the Actions pane, click on New and choose Virtual Machine.

New Virtual Machine.png

 

On the New Virtual Machine wizard beginning screen, click read the information presented and then click Next.

New VM 01.png

 

Enter a name for the VM. Note that this is NOT the name the VM will have within the Operating System (unless you name it the same), but rather, used as an identifier in Hyper-V Manager. After you have entered a name, click Next.

New VM 02.png

 

Now assign the amount of memory you want your VM to have, and then press Next.

New VM 03.png

 

This is the screen where you connect your VM to the network that we created, then press Next.

New VM 04.png

 

This is the screen where you configure how large a hard drive the VM will have. Make the appropriate customizations and click Next.

New VM 05.png

 

For the Installation Options, choose if you will install an OS later, or if you want to use an ISO, then click Next.

New VM 06.png

 

On the Summary screen, review your selections and entries, and click Finish.

New VM 07.png

 

Once the VM is created, it will appear in the Hyper-V Manager.

New VM 08.png

 

If you want to configure further settings, like the number of CPUs and mounting an OS ISO, right click on the VM and choose Settings or click on Settings from the Actions pane.

VM Settings 01.pngVM Settings 02.png

 

Repeat these steps for each VM you need to create, in our case one for Active Directory and another for SCOM.

Here are the settings I have used for each of the VM’s:

 

Active Directory:

  • Virtual Machine Name: AD
  • Memory: 2048 MB
    • NOTE: Active Directory doesn't need 2 GB of RAM, it will run fine with 512 MB. I just increased the RAM so that the OS would install/respond faster.
  • CPUs: 2
  • OS: Windows Server 2012

 

SCOM:

  • Virtual Machine Name: SCOM
  • Memory: 8192 MB
    • NOTE: You may need to increase the amount of RAM this VM has, depending on performance.
  • CPUs: 2
  • OS: Windows Server 2012

 

 

In the next part, we will install the Operating System, so stay tuned.

  • Like 2

Share this post


Link to post
Share on other sites


Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...