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”. 

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.

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.

Nothing difficult, just something I thought was neat.

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.

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.
• .NET Framework 3.5 SP1 redistributable package
• .NET Framework 4 redistributable package

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.

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.

• Legal License read and checked

• I want to install it all

• Expand each of the items to read up on what it is you’re installing and any requirements that are needed.

• another screen shot expanded on the funtions

• Since I do not install applications on my OS drive, I have established a number of drives that I will use.

• The first time I ran this, the system identified that my server needed to reboot. I rebooted and ran the setup again.

• Simple enough,

• 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.

• 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.

• 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.

• Once I started my SQL Server Agent service,I re-ran this again and passed.

• Default is fine for my environment.

• This installation I used the default, but choose what you’re requirements call for.

• Make sure you expand on these and apply your accounts and passwords.

• Because I am “Pro Support”, why not?

• Final step, a summary of what is going to be installed, verify and correct if you goofed somewhere.

• And Go!

• Done, Duh!

• And GO!

• 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