OMG !!! I can't monitor new servers in OpsMgr

Recently I bumped into this problem. Apparently every new servers (that is being installed with SCOM monitoring agent) cannot be monitored by SCOM. You can clearly see from the OpsMgr console that I have tons of servers with the status of Not Monitored.

Bad News + Tension = ~non stop sweating~

I checked all my agent communication ports and nothing is wrong. My Management Server event logs doesn't show any significant errors. The only thing I got was heaps of


Event 20070
The OpsMgr Connector connected to (RMS FQDN), but the connection was closed immediately after authentication occured. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect.

Event 21023
OpsMgr has no configuration for management group (managementgroupname) and is requesting new configuration from the Configuration Service.

Event 21402
Operations Manager has discarded 1 items in management group (managementgroupname) , which came from $$ROOT$$. These items have been discarded because no valid route exists at this time. This can happen when new devices are added to the topology but the complete topology has not been distributed yet. The discarded items will be regenerated.

Not long after that, my RMS starts to generate heaps of Warning in the Event Viewer. I get tons of
Event 29106 indicating problem writing data into the OpsMgr database. Somehow I got an impression that something is not right the Management Pack.

I made a query to the OpsMgr database to look for which Management Pack that was affected and apparently something is amiss with the Windows Server 2003 MP in my case.

I quickly look back at the Management Pack and the Windows Server 2003 MP is not updated whilst the Windows Server Operating System library has been updated. Maybe certain objects was removed from the data structure when the new Base OS library was updated but then the Windows Server 2003 MP was not updated to tally with the changes done.

I updated the Windows Server 2003 Management Pack and all is well. The new servers have successfully reported back to the system and problem solved !

Synthetic Transaction: Cannot find Web Recorder in Internet Exploer

Issue:
When you start to capture a web session (for the application that you want to monitor, the browser does not load the Web Recorder component hence you could not capture the web session that you intend to monitor.
























Cause:
This happens if you try to record/capture the session on a x64 machine. This is because you need to launch Internet Explorer (x64) to get Web Recorder loaded.The default path of Internet Explorer is actually the x86 version hence the Web Recorder component could not be loaded.

Resolution:
Change the default path of Internet Explorer by changing the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\IEXPLORE.EXE\(Default)

The key value should be - C:\Program Files\Internet Explorer\IEXPLORE.EXE


Note: Internet Explorer needs to be close and reopen (if its open existingly). Once you are done, click on Start Capture from the Web Application Editor and the browser will now