I would like to thank the speakers, Ken Galvin from Quest, Alec King from Veeam and Baelson Duque from Microsoft for taking time out from their busy schedules to take part in our user group.

I would also like to thank your Sponsor http://SystemCenterCentral.com

I’ve edited the live meeting file and sliced it up into three files for easier downloading.

I look forward to the next meeting which will be in a month or so.

Thank you,
Scott Moss

Microsoft MVP (Service Center Cloud and Datacenter Management)
Vice President Atlanta SMUG http://www.atlsmug.org
President System Center Virtual User Group  http://systemcentercentral.com/scvug
New Blog! http://om2012.wordpress.com

This installment of the System Center Virtual User Group is brought to you by SystemCenterCentral.com

Registration for the System Center Virtual User Group Meeting #18

http://www.clicktoattend.com/?id=159955

Speaker Bio's

Ken Galvin

Ken Galvin is the Program Manager of the QMX – System Center unit of Quest Software. He has been with the QMX product for over six years in a number of roles including project, operations, product and product marketing and business development – primarily in the international and public sectors. Before Quest, Ken worked at AT&T for 20 years in operations, sales operations, sales management and project management. He lives near the Blue Ridge Mountains in Virginia with his wife and four children and is very active in music and youth ministry in his community.

Alec King

Alec King is a Director of Product Management at Veeam, and the original author and architect of the hugely successful ‘nworks Management Pack for VMware’. An expert in monitoring, management and automation, Alec has been developing MPs in Microsoft Operations Manager since MOM 2000. Alec regularly delivers presentations at technology trade shows such as Microsoft Management Summit, Tech-Ed and VMworld.

Baelson Duque

Baelson Duque started at Microsoft a Systems Engineer and shortly thereafter, became a Tools Engineer building tools for Microsoft Game Studios Operations team that managed zone.msn.com. There he owned the Monitoring Infrastructure where Baelson pioneered MOM 2000 as the Operations Monitoring Platform. Baelson is now a proud member of the System Center Operations Manager Program Management team bringing with him over 5 years of Operational Expertise from many levels in the IT Operations stack. Baelson has been with the OpsMgr PM Team for over 8 years designing many features from core modules in the Infrastructure, many Management Packs, Distributed Application Designer, Synthetic Transactions, and various MP Templates. Baelson is currently a Sr. Program Manager responsible for the Next Gen UI Framework to support Dashboards in OpsMgr 2012 and the Authoring Tools for Management Packs.

I look forward to seeing you there!
Thank you,

Scott Moss
Microsoft MVP (Service Center Cloud and Datacenter Management)
President System Center Virtual User Group http://systemcentercentral.com/scvug

Vice President Atlanta SMUG http://www.atlsmug.org/

On February 21 & 22 Microsoft Learning is running a 2-day virtual training event to help the world learn about the upcoming enhancements with the Creating & Managing a Private Cloud with System Center 2012 Jump Start. 

It is 100% free and open to the public, so register now!

Sign up today at: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=298

Event Overview

Adopting this exciting new computing paradigm provides a whole new landscape of technology and career direction for IT professionals. Microsoft Learning and the Microsoft System Center 2012 team have partnered to bring you an exciting opportunity to learn what you need to know to deploy, manage and maintain Microsoft’s private cloud solution. Leveraging the popular Jump Start virtual classroom approach, the industry’s most gifted cloud experts will show attendees why this new private cloud solution, based on System Center 2012 and Windows Server, has garnered so much attention. Presenters include Symon Perriman, Sean Christensen, Adam Hall, Kenon Owens, Prabu Rambadran & Chris Van Wesep and there will be a live Q&A during the event.

Event Agenda

Day 1: Deployment & Configuration (Feb. 21)

· Part 1: Understanding the Microsoft Private Cloud

· Part 2: Deploying the Infrastructure Components

· Part 3: Deploying the Private Cloud Infrastructure

· Part 4: Deploying the Service Layer

· Part 5: Deploying the Applications & VMs

Day 2: Management & Operations (Feb. 22)

· Part 6: Managing the Infrastructure Components

· Part 7: Managing the Private Cloud Infrastructure

· Part 8: Managing the Service Layer

· Part 9: Managing the Applications & VMs

Sign up today at: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=298

Jump Start Overview

This accelerated Jump Start sponsored by Microsoft Learning is tailored for IT professionals familiar with Windows Server technologies, Hyper-V virtualization, and the System Center management solutions. The course is designed to provide a fast-paced and technical understanding of how and why Microsoft’s approach to the private cloud delivers scalability, security, flexibility and control. Here are few unique benefits of this course:

· Students have the opportunity to learn from and interact with the industry’s best cloud technologists!

· This high-energy, demo-rich learning experience will help IT Professionals understand why Microsoft private cloud solutions are making a splash in the industry.

· Students will see with their own eyes how Windows Server 2008 R2 and System Center 2012 work together to provide the best combination of security and scale.

· Information-packed agenda! Day one of this two-day online course will focus on designing and deploying the right solutions for your organization, while day two will provide an in-depth look at the tools available to help monitor, secure and control the operational aspects of a private cloud.

Sign up today at: http://mctreadiness.com/MicrosoftCareerConferenceRegistration.aspx?pid=298]]> Scott Moss Tue, 14 Feb 2012 21:26:02 GMT http://www.systemcentercentral.com/tabid/143/indexid/91716/default.aspx Looking at the complete picture can be difficult if under pressure, and your just trying to get a task done, and you get tunnel vision. Sometimes this is impossible due to the caffeine intake. Anyways I ran into a problem when doing a very normal task, of importing a Management pack. Wonk Error! What?!?!

If my trouble shooting side of my brain would have kicked in, I would have looked at the OpsMgr event log and seen the problem very quickly.

There were 3 warning Event ID 33333 with a Source of DataAccessLayer and one Error Event ID 26319 Source: OpsMgr SDK Service Events. Seeing these event details, would have cut my trouble shooting time in half. The event details state the problem was a duplicate Monitor name, apparently the Monitor Names are not case sensitive.

When you encounter an error in the opsmgr console always remember to look at the OpsMgr Event log. It might just save you some time.

Scott Moss
Microsoft MVP (Service Center Cloud and Datacenter Management)
Vice President Atlanta SMUG http://www.atlsmug.org
President System Center Virtual User Group  http://systemcentercentral.com/scvug

New Blog! http://om2012.wordpress.com]]> Scott Moss Tue, 07 Feb 2012 20:09:47 GMT http://www.systemcentercentral.com/tabid/143/indexid/91562/default.aspx This is a frequent item that is covered in the TechNet forums. So much so I’ve decided to make a post about how to do it so I don't have to type the directions any more.

Steps to clear the agent cache.

1. Logon to agent machine with admin rights (or enough rights to stop a service and delete files off the file system)

2. Open DOS box, click start run CMD, if Windows 2008 R2 start CMD with Admin Rights.

3. Type “net stop healthservice” to stop the Operations Manager Service.

4. open explorer and delete the folder ‘Health Service State’ that can be found here: C:\Program Files\System Center Operations Manager 2007\Health Service State

5. Go back to the dos box and type “net start healthservice” to start the Operations Manager Agent.

$Groups = Get-MonitoringObjectGroup
$Group = $Groups | where {$_.DisplayName -eq "Group Name"}
$Members = $Group.GetRelatedMonitoringObjects()
$Members | Sort DisplayName | FT DisplayName | out-file C:\GroupName.txt

Props to Andreas Zuckerhut, as I copied some of his code… ]]> Scott Moss Wed, 01 Feb 2012 22:12:55 GMT http://www.systemcentercentral.com/tabid/143/indexid/91458/default.aspx If you want to know more about the future direction of the System Center 2012 product line as well as what Microsoft is doing with the private cloud space don’t miss this web event Transforming IT with Microsoft Private Cloud.

Registration link below.

http://www.microsoft.com/business/events/en-us/PrivateCloudExec

http://www.microsoft.com/business/events/en-us/PrivateCloudExec

I would like to thank everyone that reads my blogs or follows me on twitter (http://twitter.com/jscottmoss) or attends the Atlanta SMUG http://www.atlsmug.org or attends the System Center Virtual User Group  http://systemcentercentral.com/scvug.

Let’s all have a great new year and if you have any topics that you would like to see me cover on this blog or in one of the user groups that I manage please drop me a line at jscottmossatgmaildotcom or leave a comment.

Thank you for your support!

Join the Atlanta Systems Management User Group for System Center Universe 2012, a one-day globally available technical event featuring Microsoft product gurus like Wally Mead and Travis Wright who will focus on the System Center 2012 products, features, and new capabilities resulting from these releases. View the live simulcast and engage in the conversation during the event via the SCU2012 twitter stream. Breakfast, lunch, and snacks will be provided throughout the day for all attendees. www.systemcenteruniverse.com

If your planning on attending please register as soon as possible so we can get an accurate head count for food, as we have something special planned for lunch. 

Registration Link https://app.e2ma.net/app2/survey/1404047/205029572/1f7eb1415d/

The agenda is set the final details on who will be presenting are being worked out. We will have Swag and some kind of give away during lunch or at the end of the day.

Did I mention Lunch will consist of Pizza and Beer? Not bad for a Thursday!

Agenda (Eastern Time Zone)

January 19th, 2012 from 8 am to 5 pm (CST) is going to be System Center Universe Day. This is a one-day globally available technical event which will focus on the System Center 2012 products and new capabilities resulting from these releases.

It is being held in Austin Texas, and if you are a member of the System Center Virtual User Group you can virtually attend from anywhere in the world for free, you just have to register and attend.

As the Agenda is still being built out for this event please check back on the System Center Universe agenda web page http://www.systemcenteruniverse.com/Agenda

TO register please check the following link https://app.e2ma.net/app2/survey/1404047/205029576/62306be74f/

System Center Universe 2012 Simulcast
Date: January 19, 2012
Time: 8AM - 5PM (CST)

Agenda (Central Time Zone)

Get-SCOMRMSEmulator

Remove-SCOMRMSEmulator

This is one of the cmdlets that requires the server name to be in FQDN format. Just entering the NetBIOS name will not cut it with this cmdlet, and there is no error or indication that the role was not moved if you used the NetBIOS name. For that matter there is no indication if the Role is moved either, so you should always verify that the role moved afterward.

The following example will move the RMSEmulator role to omvnextqa03.qa.net, so first we get the management server using the Get-SCOMManagementServer cmdlet, then piping it to Set-SCOMRMSEmulator.

PS C:\> Get-SCOMManagementServer -Name omvnextqa03.qa.net | Set-SCOMRMSEmulator

The next line verifies that the RMS Emulator role moved, by using get-SCOMRMSEmulator connecting to omvnextqa01, and lists the name of the RMSEmulator for that management group.

PS C:\> get-SCOMRMSEmulator -computername omvnextqa01.qa.net

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA03.qa.net 7.0.8443.0 QA\sdk

PS C:\> get-SCOMRMSEmulator

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA01.qa.net 7.0.8443.0 QA\sdk

PS C:\> Get-SCOMRMSEmulator -ComputerName OMVNEXTQA03

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA01.qa.net 7.0.8443.0 QA\sdk

PS C:\> Get-SCOMRMSEmulator -ComputerName OMVNEXTQA03.QA.NET

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA01.qa.net 7.0.8443.0 QA\sdk

PS C:\> Get-SCOMRMSEmulator -ComputerName "OMVNEXTQA03.QA.NET"

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA01.qa.net 7.0.8443.0 QA\sdk

PS C:\> Get-SCOMManagementServer

WARNING: column "Id" does not fit into the display and was removed.

HealthState DisplayName Version ActionAccountIdentity

----------- ----------- ------- -----------------

Success OMVNEXTQA03.qa.net 7.0.8443.0 QA\sdk

Success OMVNEXTQA01.qa.net 7.0.8443.0 QA\sdk

To find out what properties and methods are available to use with this cmdlet run

PS C:\> Get-SCOMManagementServer | GM

Lets list out the servers in the management group and what the proxy settings are and what version they are.

PS C:\> Get-SCOMManagementServer | ft name, proxyingenabled, version

Name ProxyingEnabled Version

---- --------------- -------

OMVNEXTQA03.qa.net True 7.0.8443.0

OMVNEXTQA01.qa.net True 7.0.8443.0

The Get-SCOMManagementServer cmdlet can be used with other SCOM cmdlets for example Set-SCOMRMSEmulator which will be show in my next post.

In the help file for Install-SCOMAgent there are 4 examples for deploying agents. I’ll describe the first two today. The first example will work in a small lab where the possibility of having admin rights on the OM12 system and the systems your deploying to is much more likely than in a production environment. The Server name should be in FQDN format or the get-scommanagementserver cmdlet will not return a value. While the agent is being deployed the Operations Manager Shell will only run that command till the agent install is completed, which should only take a few minutes to complete.

PS C:\> $PrimaryMgmtServer = Get-SCOMManagementServer -Name "omvnextqa03.qa.net"

PS C:\> Install-SCOMAgent -Name "Mdbqa01.qa.net" -PrimaryManagementServer $PrimaryMgmtServer

AgentOperation ErrorCode Description AgentName

-------------- --------- ----------- ---------

AgentInstall 0 The Operations Manager Ser... mdbqa01.qa.net

Example two worked well too. After executing the three lines of code, the server showed up in pending actions as the agent being installed. Line one allows you to enter credentials into a logon dialog box, that will be used to deploy the agents. Line two sets the primary management server. Don’t forget to use FQDN when specifying Management Server Names or agent names your deploying to. The third line installs the agent on machine MDBQA02 using the primary management Server from line two and the Action Account specified in line one.

$InstallAccount = Get-Credential

$PrimaryMgmtServer = Get-SCOMManagementServer -Name "omvnextqa03.qa.net"

Install-SCOMAgent -Name "MDBQA02.qa.net" -PrimaryManagementServer $PrimaryMgmtServer -ActionAccount $InstallAccount

Look for more in the near future.

PS C:\> Get-SCManagementPack | Export-SCManagementPack -path C:\MPDUMP

Running it with out any parameters will get you a list of agents in the management group your connected to.

PS C:\> get-scomagent

WARNING: 2 columns do not fit into the display and were removed.

HealthState DisplayName                                    Version       ActionAccountIdentity
-----------    -----------                                               -------       -----------------
Success     mdbqa01.qa.net                              7.0.8443.0    SYSTEM
Success     mdbqa02.qa.net                              7.0.8443.0    SYSTEM
Success     OMVNEXTQA02.qa.net                     7.0.8443.0    SYSTEM

To figure out what you can check out with this cmdlet pipe the get-scomagent | GM and you will see the properties and methods available for that cmdlet. The properties are listed below.

ActionAccountIdentity Property

AuthenticationName Property

CommunicationPort Property

ComputerName Property

CreateListener Property

DisplayName Property

Domain Property

HealthState Property

HeartbeatInterval Property

HostComputer Property

HostedHealthService Property

Id Property

InstalledBy Property

InstallTime Property

IPAddress Property

LastModified Property

ManagementGroup Property

ManagementGroupId Property

ManuallyInstalled Property

MaximumQueueSizeBytes Property

MaximumSizeOfAllTransferredFilesBytes Property

Name Property

NetworkName Property

PrimaryManagementServerName Property

PrincipalName Property

ProxyingEnabled Property

RequestCompression Property

Version Property

Just like SCOM 2007 and powershell version 1, you can sort, and filter on the properties.

PS C:\> get-scomagent | where-object {$_.DisplayName -like "mdbqa*"} | ft displayname, Proxyingenabled

DisplayName                 ProxyingEnabled

-----------                       ---------------

mdbqa01.qa.net           True

mdbqa02.qa.net           True

Good news is that bulk enable proxy PowerShell scripts like the one Kevin Holman did, works with one modification, changing the cmdlet name to reflect the new name GET-SCOMAGENT.

$NoProxy = get-scomagent | where {$_.ProxyingEnabled -match "False"}

$NoProxy|foreach {$_.ProxyingEnabled=$true}

$NoProxy|foreach {$_.ApplyChanges()}

http://www.mms-2012.com/registration

There is an excellent TechNet Document on this topic that is very through discussing SQL software requirements, and requirements by feature like Management Server, Operations Console, Web Console, etc.

http://technet.microsoft.com/en-us/library/hh205990.aspx

Scott Moss
Microsoft MVP (Operations Manager)
Vice President Atlanta SMUG http://www.atlsmug.org
President System Center Virtual User Group  http://systemcentercentral.com/scvug

Environment

This will illustrate a three server install. Server 1 will be the first management server in the Management group. Server 2 will be the Database Server, SQL SSRS Server, web Server, and will hold the following OM12 roles, as the Web Console server and the Report server, and holding the OM12 Databases. Server 3 will be a second management server in the Management Group. This will be a three part series:

Part One will Deal with the Server 1 installation of just the management server.

Part Two will deal with the Server 2 installation of the report server and web console.

Part Three will detail installing a second Management Server to the Management Group on Server 3.

Software Requirements

Requirements for Server 3, from the TechNet OM12 RC Supported Configurations page http://technet.microsoft.com/en-us/library/hh205990.aspx

Management Server

• Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
• Server Operating System: must be Windows Server 2008 R2 SP1.
• Processor Architecture: must be x64.
• Windows PowerShell version: Windows PowerShell version 2.0.
• Windows Remote Management: Windows Remote Management must be enabled for the management server.
• Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
• Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Installation

Start the installation logged using a domain account, that has local admin on the server as well as SQL Admin rights on the remote SQL node. Setup.exe should be run using the run As admin option. Click Install!

Server Three is just a management server, and does not need to have the management console installed. The Operations Manager 2012 Powershell module is still installed if the Management Console is not selected. So I selected the Management Server installation option and selected Next.

Select Installation Location, I kept the default and selected Next to continue.

Prerequisites check passed, so Select Next to continue.

Specify an installation Option, I selected Add a Managmeent Server to an existing management group, then selected Next.

Configure the Operational Database, enter the SQL server name and instance name of the SQL Server, and port number if it is different than 1433. Once its connected select the drop down box for the database name to select the OperationsManager database, then click Next.

Configure Operations Manager Accounts, which in my case were all domain accounts, after entering the information I selected Next to continue.

Installation Summary is now ready for your review. After review the installation summary, click the install button.

The Much improved Installation Progress bar will keep you informed of the installation progress and when it completes…

The Setup is complete screen will be displayed. Click Close to end the installation.

Scott Moss
Microsoft MVP (Operations Manager)
Vice President Atlanta SMUG http://www.atlsmug.org
President System Center Virtual User Group 
http://systemcentercentral.com/scvug

Environment

This will illustrate a three server install. Server 1 will be the first management server in the Management group. Server 2 will be the Database Server, SQL SSRS Server, web Server, and will hold the following OM12 roles, as the Web Console server and the Report server, and holding the OM12 Databases. Server 3 will be a second management server in the Management Group. This will be a three part series:

Part One will Deal with the Server 1 installation of just the management server.

Part Two will deal with the Server 2 installation of the report server and web console.

Part Three will detail installing a second Management Server to the Management Group on Server 3.

Software Requirements

Requirements for Server 2, from the TechNet OM12 RC Supported Configurations page http://technet.microsoft.com/en-us/library/hh205990.aspx

Server two has SQL 2008 R2 installed with the defaults, and is hosting both the OM12 Operational Database and Data Warehouse, the Web Console and Reporting Server, so the following are all the Requirements it must pass.

Note the following database considerations for Operations Manager:

• Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
• Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
• SQL Server collation settings for all databases must be SQL_Latin1_General_CP1_CI_AS; no other collation settings are supported.
• The SQL Server Agent service must be started, and the startup type must be set to automatic.
• Side-by-side installation of System Center Operations Manager 2007 R2 Reporting and System Center 2012 – Operations Manager Reporting on the same server is not supported.
• The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start. For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
• If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see tempdb Database.

Web Console

• Operating System: Windows Server 2008 R2 SP1.
• Processor Architecture: must be x64.
• Web browsers: Internet Explorer 7, Internet Explorer 8, Internet Explorer 9
• Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console and the following role services installed:
  • Static Content
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • HTTP Logging
  • Request Monitor
  • Request Filtering
  • Static Content Compression
  • Web Server (IIS) Support
  • IIS 6 Metabase Compatibility
  • ASP.NET
  • Windows Authentication
• Selected website for web console: requires a configured http or https binding.

  Warning

  Installing the web console on a computer that has SharePoint installed is not supported.

• Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Note

Installation of the web console requires that ISAPI and CGI Restrictions in IIS are enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.

Important

You must install IIS before installing .NET Framework 4. If you installed IIS after installing .NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt window by using the Run As Administrator option, and then run the following command:

%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

Operational Database

• Disk space: The operational database must have at least 1024 MB free disk space. This is enforced at the time of database creation, and it will likely grow significantly. For information about SQL Server Planning, see Initial Installation (SQL Server 2008).
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
• Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
• Processor Architecture: x64.
• Windows Installer version: at least Windows Installer 3.1.
• Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1.
• SQL Collation: SQL_Latin1_General_CP1_CI_AS.
• SQL Server Full Text Search is required.
• Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Operations Manager Reporting

• Disk space: The %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
• Operating System: Windows Server 2008 R2 SP1.
• Processor Architecture: x64.
• Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1.
• The Remote Registry service must be enabled and started.
• Microsoft SQL Server Reporting Services: SQL Server 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1.
• SQL Collation: SQL_Latin1_General_CP1_CI_AS.
• Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Operations Manager Data Warehouse

• Disk space: The data warehouse database must have at least 1024 MB free hard disk space. This is enforced at the time of database creation, and the required disk space will likely grow significantly. For information about requirements in SQL Server Planning, see Initial Installation (SQL Server 2008).
• File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
• Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
• Processor Architecture: x64.
• Windows Installer version: at least Windows Installer 3.1.
• Microsoft SQL Server: SQL Server SQL 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1.
• SQL Collation: SQL_Latin1_General_CP1_CI_AS.
• SQL Server Full Text Search is required.
• Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For more information, see the following documents:
  • .NET Framework 3.5 SP1 redistributable package
  • .NET Framework 4 redistributable package

Installation

Start the installation logged using a domain account, that has local admin on the server as well as SQL Admin rights on the SQL node. This account should also be an Administrator in Operations Manager. Setup.exe should be run using the run As admin option. Click Install!

Select the Web Console, and Reporting Server, then click Next.

Select installation Location, I kept the defaults and clicked next.

Prerequisites passed, so Proceed with Setup by clicking Next.

Specify a Management Server, so I enter Server 1’s name then click Next.

Select the SQL Server Instance on which you want to host the SQL SSRS. Note, I had OM12 Beta installed on this box, and I ran into problems trying to get OM 12 RC Reporting installed. The RESETSRS.EXE utility was not able to get SQL SSRS back in order to do the OM 12 RC install, so I verified that I had uninstalled all the OM12 Beta software, then Removed SQL SSRS from the box, then removed IIS, then rebooted, and added IIS back, then installed SQL SSRS. After all that was done, the OM12 RC Reporting install went smooth, with out errors on the prerequisite checker.

Specify a Web Site for Use with the Web Console. i kept the Defaults and clicked Next.

Select an Authentication Mode for use with the Web Console, then click Next.

Configure Operations Manager Accounts, enter an account and password that will fill this role and click next.

Help Improve Operations Manager 2012 participating anonymously in the Operational Data Reporting program. Click yes option box then click the Next button.

Installation Summary Screen, it is always a good idea to review this as a sanity check before clicking install.

Installation Progress bar. I’m glad that Microsoft has added more status messages to this screen than just having a progress bar!

Once Setup Is complete you will get the screen below. Click close to complete the install.

Next is Post will be Part three adding a second Management Server to the Management Group.

Scott Moss
Microsoft MVP (Operations Manager)
Vice President Atlanta SMUG http://www.atlsmug.org
President System Center Virtual User Group 
http://systemcentercentral.com/scvug