Posts tagged ‘OpsMgr 2012 Beta’

Running both OpsMgr 2012 beta and 2007 R2 consoles on the same workstation

Connecting to a OpsMgr 2012 beta management server with a OpsMgr 2007 R2 console doesn’t work either does connecting with the 2012 beta console to a 2007 R2 RMS.

If you like me wants to be able to connect to both a 2012 beta management group and a 2007 R2 management group you can run 2 consoles on the same workstation. Just start with running the OpsMgr 2012 beta setup on your workstation, if an OpsMgr R2 console is already installed it will be upgraded, otherwise just install the console. If you don’t want to go through the setup GUI just run this from an elevated command prompt: setup.exe /silent /install /components:OMConsole /UseMicrosoftUpdate:[0|1]

When this is done, load your R2 media and install the console from that one.

This will give you two folders in %programfiles%:

folder

And also on the Start menu and Programs and Features:

startmenu 

features

Now we are able to run the consoles simultaneously

console

But you will soon notice that the Connect to Server.. windows is showing now and then when opening a console. This is also mentioned in this post:
http://www.opsmode.com/2011/03/manage-multiple-management-groups-with-powershell/

connect to

To get rid of this I edit the shortcut and add /Server:OPS-OMbeta-MS01.opsmgr.se for my 2012 console and /Server:OM.opsmode.local for the 2007 R2 console
"C:\Program Files\System Center Operations Manager 2007\Microsoft.MOM.UI.Console.exe" /Server:OM.opsmode.local
"C:\Program Files\System Center Operations Manager 2012\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe" /server:OPS-OMbeta-MS01.opsmgr.se

Download Management Packs, OpsMgr 2007 and 2012 Beta

One nice features is the possibility to download MP’s from the Catalog in the OpsMgr Console.
I really like being able to download MP’s to disk, that way I can back up the actual .MP file. Not having to download a .MSI, installing it and remove it from Programs and Features / Add/Remove programs if I don’t want it there. What you don’t get when you download it from the Console is the Management Pack Guide, and that one needs to be read before importing the MP.
So, to get hold of the guide document from the Console you do as follows.

Go to Administration, right click Management Packs (you can right click anywhere) and chose Download Management Packs.

Chose your download location and then click Add

Search for the MP you want to download, and select it in the list. Then click Properties

image

And there you have it!

image

A nice feature here would be to right click and Save As, but that doesn’t work. How ever you can click it and it will open in Word, if you don’t have Word installed you can mark it and copy the the link with Ctrl+C and paste it in a browser to open it on another machine.

Web Console prerequisites, OpsMgr 2012

When installing the Web Console there is a couple of components that is required, the Operations Manager 2012 Supported Configuration (http://technet.microsoft.com/en-us/library/hh205990.aspx) list these:

  • Recommended processor speed: 2.8 GHz or faster.
  • Minimum memory: not less than 2 GB.
  • Operating System: Windows Server 2008 R2
  • Processor Architecture: must be AMD64
  • Internet Information Services (IIS) v7.5 or later, 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
  • Default website: must have an http or https binding configured
  • Both .NET Framework 3.5 SP1 and .NET Framework 4 is required for setup to run. For more information, see the following.

 

The role services is easily installed with powershell, which makes it a little quicker then using Server Manager GUI:

Import-Module ServerManager
Add-WindowsFeature NET-Framework-Core,Web-WebServer,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Asp-Net,Web-Http-Logging,Web-Request-Monitor,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase

As you might see I’ve also added NET-Framework-Core  (.NET Framework 3.5.1) there as well.

When the IIS install is ready you should install .NET Framework 4. (http://www.microsoft.com/download/en/details.aspx?id=17851)

If you installed .NET Framework 4 before installing the IIS you’ll get an error:

The ASP.NET 4.0 handler is not registered with IIS.
The ASP.NET 4.0 handler is not registered with IIS 

To fix this, the Operations Manager 2012 Deployment document states that you should run:

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

I suggest that that you add the -enable option (%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -enable -r), that enables the ASP.NET ISAPI extension. And gets rid of this prerequisites error:

Web Console cannot operate properly because the ISAPI and CGI Restrictions in Internet Information Services (IIS) are disabled or missing for ASP.NET 4.0.
Web Console cannot operate properly because the ISAPI and CGI Restrictions in Internet Information Services (IIS) are disabled or missing for ASP.NET 4.0.

Lastly do a restart of the server before running the setup again.