SCOM - Duplicate Signature ID usage detected for STT Signature ID

1. The HealthService starts the new rules in the configuration 
2. The STT module starts up attempts to register the signature id and 
    cannot since another version of the same rule is running. 
    The module then logs the event and unloads the workflow. 
3. The HealthService stops any old rules not in the configuration. 
4. The old version of the rule is stopped hence the duplicate signature id 
   is unregistered. 
5. The HealthService reloads any rules which failed during step 1. 
6. The STT module starts up normally (no issues registering the duplicate id) 

Unable to discover IIS 7 web site as ASP.Net Web Application

Symptom

Unable to discover IIS 7 web site as ASP.Net Web Application 

Cause

IIS Web application discovery rule 

Resolution

Override the "IIS 7.0 Web Application Discovery" rule. Set below values to True.

        Discover All directories as ASP.Net web application
        Discover Empty directories as ASP.Net Web Application
        Discover Empty directories as ASP.Net Web Service 

NetBIOS over TCP/IP

Symptom
===========

Changing the Primary Domain DNS name of this computer to "" failed on

Windows 7 when joining to domain

Cause
=========

W2K8R2/Win7 known issue when joining to domain

http://support.microsoft.com/kb/2018583/en-us

Workaround

================

Add Domain DNS Suffix in the TCP/IP Properties. 

a) Click Start , click Run , type ncpa.cpl , and then click OK .

b) In Network Connections , right-click Local Area Connection ,

and then click Properties .

c) Click Internet Protocol Version 4 (TCP/IPv4), and then click

Properties .

d) In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog

box, click Advanced .

e) On the DNS tab, select these DNS Suffixes, click Add, type the

FQDN of the domain in the DNS Server Dialogbox, Click Add, and then click OK

three times

How to query Alert view ?

select * from dbo.AlertView 

Network location cannot be reached on joining domain

1. Open the Network and Sharing center
2. On the left side, click "Change Adapter Settings"
3. Right Click your connection and click on "Properties"
4. On the "Networking" tab, click Install
5. Install "Client for Microsoft Networks"
6. Reboot Server

How to open command prompt in WinPE

There are two different key combinations with which you can start command line (cmd) when in WinPE (Windows PreInstallation Environment).
In normal Windows Setup, when you just boot installation media from DVD or USB flash disk, you can press Shift-F10 to open command line.

In the case of System Center Configuration Manager (shortly SCCM, configmgr or even config manager) and its WinPE OSD installation or image capture, the boot image has a different key for that. You must press F8.

SCOM - Event id 14333 MSMQ error 'Public Queues registry key not found'

Problem

========

Getting event id 14333 MSMQ error 'Public Queues registry key not found.

Solution

========

we can resolve this issue by creating a dummy key under the registry

SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\MSMQ Management Pack\HOCSPFE01.camden.local\Public Queues.

First we  created the dummy key in 2003 machine .

Alerts stopped coming.