Friday, July 29, 2011

SCOM Zombie PSA#20: Web Console: HTTP Error 404.2 – Not Found

 

I’ve encountered this issue this afternoon, after re-building my OpsMgr2012. From my computer I received this “404 – File or Directory not found”.  image

I tried to verify this from my server, which I showed a different error, just more details. Nothing populated into my event logs on either system.

image

What I really liked about getting this error was that It showed me how helpful the application is. The error populated a lot of information about causes, path that failed and some resolutions etc.It allow me to link Microsoft support site directly through the web console, where I was able to gather the resolution for the 404.2 error.

image

Nothing difficult, just something I thought was neat.

image

Made the changes, verified my work, tested and Bingo! working on both of my systems. I also verified the reporting as well just in case I broke something else.

image

SCOM Zombie PSA#19: OM12 VM Reverted back

 

Well, I did get my OM2012 operational and running with a couple of problems along the way. Resolved the issues and decided to revert my image to a staged starting point and go through the process again. Will I run into a problem this time? How well do I understand the process Microsoft provided from their documentation? What can I resolve if I come across that path?

Once I have this running, I will move on to other stuff with OM12 or OM02.

SCOM Zombie PSA#18: Monitored Item Capacity

 

Here is the recommended limits for OpsMgr 2012 from the Supported Configurations guide:

Monitored Item

Recommended Limit

Simultaneous Operations consoles

50

Agent monitored computers reporting to a management server

3,000

Agent monitored computers reporting to a gateway server

2,000

Agentless Exception Monitored computers per dedicated management server

25,000

Agentless Exception Monitored computers per management group

100,000

Collective client monitored computers per management server

2,500

Management servers per agent for multihoming

4

Agentless managed computers per management server

10

Agentless managed computers per management group

60

Agent-managed and UNIX or Linux computers per management group

6,000 (with 50 open consoles); 10,000 (with 25 open consoles

UNIX or Linux computers per dedicated management server

500

UNIX or Linux computers monitored per dedicated gateway server

100

URLs monitored per dedicated management server

3000

URLs monitored per dedicated management group

12,000

URLs monitored per agent

50

SCOM Zombie PSA#17: Operations Console Requirements

 

Straight from the Operations Manager 2012 Supported Configurations guide:

  • Microsoft Report Viewer 2008 SP1 Redistributable Package
  • Hotfix 976898
  • Recommended processor speed: 2.8 GHz or faster.
  • Minimum memory: not less than 2 GB.
  • Drive space: %SYSTEMDRIVE% must have at least 512 MB free space
  • File system: %SYSTEMDRIVE% must be formatted with the NTFS file system
  • Server Operating System: must be Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2
  • Processor Architecture: must be AMD64 for servers and AMD64 or i386 for a client computer
  • Windows Installer version: not less than version 3.1
  • Windows PowerShell version: Windows PowerShell version 2.0
  • Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see the following.

Thursday, July 28, 2011

SCOM Zombie PSA#16: Server Error in '/' Application

 

As I monitored my OpsMgr console, I notice my Operations Web Console suddenly became unavailable. So I fired up the web console and received this error along with some details.

Details:

Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

Resolution:

I came across Bruno Wouters post helping other with the exact same issue. The only difference was that I was running this in OpsMgr 2012.

use the ASP.NET IIS Registration Tool or ASP.NET Side-by-Side Overview and execute the “aspnet_regiis.exe –iru” utilizing the command prompt as an administrator and navagete to the systemroot\Microsoft.NET\Framework\versionNumber

After I completed that, my web console was back to normal.

SCOM Zombie PSA#15: The RPC server is unavailable Error Code: 0x800706BA

 

I ran into this earlier today while deploying a OpsMgr Agent in my lab.

image

So I did some digging and found some causes that this would appear. Depending on the description is start there, in my case it was a modification to my domain policy.

  • The remote system is being blocked by the firewall.
    • Solution: Modify the domain or local system Group Policy Object (gpedit.msc).
    • Navigate to Computer Configuration > Administrative Templates > Network >, open Network Connections > Windows Firewall > Domain Profile (or Standard Profile)
    • Enable the following exceptions:
    • Allow Remote Administration Exception
    • Allow File and Printer Sharing Exception
  • The "Remote Procedure Call (RPC)" service is not running on the remote system.
    • Solution: Verity on the remote system that "Remote Procedure Call (RPC)" service is running and set to auto start after restart. Enable service via domain policy.
  • The "Windows Management Instrumentation" service is not running on the remote system.
    • Solution: Verity that the remote system  "Windows Management Instrumentation" service is running and set to auto start after restart. Enable service via domain policy.
  • Host name or IP address is wrong or the remote computer is shutdown.
    • Solution: Verify and correct the remote system’s host name and/or IP address. Human error?
  • The "TCP/IP NetBIOS Helper" service isn't running.
    • Solution: Verity that the remote system’s "TCP/IP NetBIOS Helper" service is running and set to auto start after restart. (If you can remote to the system it is running) Enable this and Remote Registry via the domain policy.

SCOM Zombie PSA#14: Deploying OpsMgr 2012 Beta Attempt # ONE!



  • This is my first attempt installing Operations Manager 2012 Beta. I have all my pre-requisite completed. Now lets launch this installation application.
  • I have to say it was so much more easier to install than 2007 R2. Bravo Microsoft.
image
  • Legal License read and checked
image
  • I want to install it all
image
  • Expand each of the items to read up on what it is you’re installing and any requirements that are needed.
image
  • another screen shot expanded on the funtions
image
  • Since I do not install applications on my OS drive, I have established a number of drives that I will use.
image
  • The first time I ran this, the system identified that my server needed to reboot. I rebooted and ran the setup again.
image
  • Simple enough,
image
  • Applied my server name, and since I am using the default instance, it was smart enough to verify it.
  • Changed my drive locations for the database and log files for the Operational Database.
image
  • Isn’t this special, I’ve done the same thing for the Data Warehouse. I’ve notice that there is also an option to either create a new database or use one from another management group.
image
  • I wanted to show this screen, since I encountered it during my first attempt. If you hover your rat over the red X, it will inform you what is broken. Resolve it and try again.
image
  • Once I started my SQL Server Agent service,I re-ran this again and passed.
image
  • Default is fine for my environment.
image
  • This installation I used the default, but choose what you’re requirements call for.
image
  • Make sure you expand on these and apply your accounts and passwords.
image
  • Because I am “Pro Support”, why not?
image
  • Final step, a summary of what is going to be installed, verify and correct if you goofed somewhere.
image
  • And Go!
image
  • Done, Duh!
image
  • And GO!
image
  • Not too many things are popping out at me during my first look except these. Or at least I don’t recall seeing them in 2007 R2
  • Administrator > Resource Pools
  • Administrator > Run As Configurations > UNIX/Linux Accounts
  • Monitoring > New View
  • the blasted Default Management Pack seems to be gone from the View, as it was report at MMS2011. BUT it is still in the Management Packs.
  • Now it’s time to play

SCOM Zombie PSA#13: Zombie Instructions: Installing SQL 2008 R2

 

  • I am not a SQL expert, but this the process that I used to establish my Operations Manager 2012 Beta.
  • Launch the setup.exe as administrator
  • I always like to do checks first to verify that I do not run into problems during the installations so on the SQL Server Installation Center click on Tools & run the System Configurations Checker. If you failed any of the requirements, take care of them now & then come back.
  • Installation select New installation or add features to an existing installation.
  • The system will first validate the installation process. If you have any errors, correct them first before moving on

image

  • The next screen that will appear is the Product Key. Apply the key and move on.
  • Once you decide accept and agree to the License Terms and select Next to move on.
  • On the Support File window select the Install button. The setup will install the Setup Support Files. The window may disappear for a second or two

image

  • The warning that I get is because the firewall is turned on. However Since I’ve applied my firewall settings via my Domain Policy, I should be good.

image

  • I have select SQL Server Feature Installation for Operations Manager 2012.

image

  • I am choosing everything for now. I did change the default location since I do not want this installed on my C drive.

image

  • Everything passed or skipped. verify that everything is correct, resolve any errors and then re-run the test.

image

  • I changed the directory once again, and placed it somewhere else other than the C Drive.

image

  • Disk Space validated

image

  • Established NT Authority/Network Service as a default right now.

image

  • I ended up adding my user account to the administrators.

image

image

  • I’ve added my action and sdk service & my user account.

image

  • Default configurations for the Reporting services

image

  • Next

image

  • Installation Configuration Rules verifications. Again, correct any issues.

image

  • Ready to Install now, the only thing that I was not able  to modify was this part since I do not want anything installed on the C Drive. But no option for me to modify this.

image

  • SQL Server is not being installed.

image

  • & Done

image

Thursday, July 21, 2011

SCOM Zombie PSA#12: Zombie Instructions: SCOM 2012 Firewall Exceptions

 

Here are the firewall ports that are required for a full Operations Manager 2012 deployment. If you are not going to use certain parts of the product, done, enable the ports. Since I did not recognize any new or removed ports I believe they are the same as Operations Manager 2007 R2.

Feature

Exception

Port and Protocol

Configured By

Management server

· System Center Management service

· System Center Data Access service

· Operations Manager Connector Framework

· Operations Manager Customer Experience Improvement

· Operations Manager Application Error Monitoring

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

Web console

Operations Manager web console

51908/TCP

Setup

Web console, forms authentication, http

World Wide Web Services, http

80/TCP

Windows Firewall

Web console, forms authentication, https

Secure World Wide Web Service

443/TCP

Windows Firewall

Operational database

· SQL Server database server

· If using a named instance, add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager data warehouse database

· SQL Server database server

· If using a named instance add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager Reporting

SQL Server Reporting Services

80/TCP

Windows Firewall

Agent, manual installation of MOMAgent.msi

System Center Management service

5723/TCP

Windows Firewall

Agent, push installation

· System Center Management Service

· File and Print Sharing

· Remote Administration

5723/TCP

137/UDP, 138/UDP, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Agent, pending repair

· System Center Management service

· File and Print Sharing

· Remote Administration

5723/TCP

137/UPD, 138/UPD, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Agent, pending upgrade

· System Center Management service

· File and Print Sharing

· Remote Administration

5723/TCP

137/UDP, 138/UDP, 139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Gateway

System Center Management Service

5723/TCP

Setup

Operations Manager Audit Collection Service database

· SQL Server

· If using a named instance, add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager Audit Collection Service Collector

ACS Collector Service

51909/TCP

Windows Firewall

You can open the firewall management console by Start, Run, firewall.cpl

OR

Command Prompt way:

  • Using the netsh command:

  • Microsoft Windows Server 2008 also have an advanced firewall helper called advfirewall.

    netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = SUBNET profile = CURRENT

  • A similar example using the Windows Firewall for Advanced Security helper:

    netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN

  • This might be easier by creating a script with all the enable these firewall rules if you have multiple servers to run this against. Maybe if I have some time, I will write a script, if not, would love for someone to hook me up with one.

SCOM Zombie PSA#11: Zombie Instructions: SCOM 2012 Web Console Settings

 

Here are your Zombie Instructions for configuring the settings for the SCOM 2012 Web Console.

**** Do not install .NET Framework 4; but hey if you did install it ahead of time, like I had, then towards the end is the command line you can run to correct this.

Web Console Requirements:

· 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 (sorry intel) but I’m good.

· 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

image

· Both .NET Framework 3.5 SP1 and .NET Framework 4 is required for setup to run. For more information, see the following.

· .NET Framework 3.5 SP1 redistributable package

· .NET Framework 4 redistributable package

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

image

****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: (Since I had my server all patched up to the latest I had to run this)

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

image

Now your system is ready for you to install the Web Console for SCOM 2012.

Tuesday, July 19, 2011

SCOM Zombie PSA#10: Operations Manager 2012 System Requirements

 

Supported Operating Systems: Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2, Windows XP Service Pack 3

  • Other Software:
    • Any server role
      • .NET 3.5 and 4.0
    • Management Server, Reporting Server, Web Console, Gateway Server
      • Windows Server 2008 R2 (64 bit)
    • Operational & Data Warehouse
      • SQL 2008 SP1 and above
      • SQL Collation - SQL_Latin1_General_CP1_CI_AS
    • Supported Operating Systems for Operations Manager Agent
      • Windows Server 2003 SP2 and above
      • Windows Server 2008 SP2 and above
      • Windows Server 2008 R2
      • Windows XP Professional SP3 and above
      • Windows Vista SP2 and above
      • Windows 7
      • Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
      • SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
      • Solaris 8 and 9 (SPARC) and Solaris 10 (SPARC and x86)
      • HP-UX 11i v2 and v3 (PA-RISC and IA64)
      • AIX 5.3, 6.1, and 7.1 (POWER)

    Supported Hardware Configuration:
    • Operations Manager Operations database: 4 GB of RAM or higher, 50 GB of available hard disk space
    • Management server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Operations console: 2 GB of RAM or more, 20 GB of available hard disk space
    • Reporting data warehouse: 4 GB of RAM or more, 100 GB of available hard disk space
    • Reporting server: 2 GB or more, 20 GB of available hard disk space
    • gateway server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Web console server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Audit database: 4 GB of RAM or more, 100 GB of available hard disk space
    • Management server with audit collector: 2 GB of RAM or more, 50 GB of available hard disk space
    • Management server with Agentless Exception Monitoring file share: 2 GB of RAM or more, 30 GB of available hard disk space
    • Agent: Please refer to the recommended hardware requirement required by the operating system.

SCOM Zombie PSA#9: Operations Manager 2012 BETA!

 

Justin Incarnato released the news today on the System Center Operations Manager Team Blog. You’ll find more information about Operations Manager 2012 Beta. But I wanted to share the links out to everyone.

     I have been waiting for this for a while now, and now that the public beta for Operations Manager 2012 has been released, I am eager to drive right in. I encourage those of you that have the abilities to test this product to do so; I will be deploying it into my lab environment. But first I’ll need to research the documentation.

     As I work with the Operations Manager 2012 Beta and Operations Manager 2007 R2, I’ll provide my updates on how my testing go along with discoveries that are found. It may not be so much on 2007 R2 now.

Wednesday, July 13, 2011

SCOM Zombie PSA#8: Default MP Countermeasure

     In Operations Manager 2007 it’s really easy to apply modifications to the default management pack. This would be all fine except that any updates or re-import to the default management pack reverts everything you have applied to it previously.

     I am not even sure how migrating to Operations Manager 2012 will affect it, other than the default management pack is removed starting in this version. And it is almost impossible in preventing zombies from making poor choices if then modify the system. So I simply counter act by renaming the default management pack.

  • I search for the default Management Pack

image

  • I have chosen to rename the Name to “z DO NOT USE !!!!! (Default Management Pack” and apply it.

image

  • When you select a destination management pack to apply your modifications it will place it down at the bottom of the list, with nice notice not to use. If you want to make the extra countermeasures step you could remove the (Default Management Pack) out all together, if you notice zombies are still using it.

image