how-to-move-the-operations-manager-2007-reporting-server

here are the two variables you will be adding to the monitor

parameter name: EventDescription

Alert description: $Data/EventDescription$

1. When you are creating the Event Expression click on insert, then click on button “…: under parameter name

2. Select Use Parameter Name not specified above and enter EventDescription

$Data/EventDescription$

Select an Event Property-EventDescription

3. change your operator to Contains

4. under the Value, enter the words you want to find in the desction field.

Build Event Expresion - operator and value

THIS IS NOT DONE!!!!

5. Continue to build your rule until you arrive at the Configure Alerts page. Enter the value $Data/EventDescription$ in the Alert description window. If you do not you will receive errors.

6. Create the rule, and refresh how ever you like. When i am in a hurry i will restart the health service on the server that I am monitoring.

7. To test your rule the OpsMgr Event Creator tool is not going to work. It does not allow you to create custom descriptions. Log onto the server that you want to monitor and open a command window. Using the eventcreate command type the following

eventcreate /t error /ID 1000/d “fieldxu.exe THIS IS JUST A TEST BY Brad Hearn”

/t sets as an error

/ID is the event id

/d is what will be placed into the description field. Remeber to place quotes around your text.

The alerts will look something like this.

Hope this helps out.

But if you did not like all the rest of have done at least once, then here is how you can remove the dependencies. But first please backup you management packs.

1. Download and install Microsoft’s XML Notepad
2. Export the Default management pack to any folder you like. This will export it into an XML file. Back this file up before making changes to it.
3. Open the XML file in XML Notepad
4. Expand the management pack in the left window to \\managmentPack\Manifest\References 

1. Look in each sub-folder named Reference for the Management pack that you are trying to remove. Once you find it Delete the Reference folder.
2. Import the Default XML file back into the console.
3. Try to delete the management pack again.

The OpsMgr Connector could not connect to MSOMHSvc\rms01.local

haha, I have.

Using a domain account is not supported and will not allow you to start the service. But it will register a second servicePrincipalName to the domain account. If this happens the agents will no longer be able to communicate with the server. Or at least until the duplicate servicePrincipalName is removed.

I found this out during the test phase when I changed the service login account during trouble shooting the health service. (The original problem with the health service was that it would keep failing and stopping. The resolution was never found, and that was with an open Microsoft call. We reinstalled the server and that resolved it. However the servicePrincipalName was still messed up in active directory.)

The following is what I have documented and used to fix this.

Here is a clipping from another post (http://www2.wolzak.com/index.php?option=com_frontpage&Itemid=1) on this that I found.

To generate a list of accounts that the SPNs are registered to, run the following command at the command prompt.

1. From the domain controller, open a command prompt and then type the following string: ldifde -f domain.txt
2. Open the text file in Notepad and then search for the SPN that is reported in the event log. ServiceClass/host.domain.com (in this case look for MSOMHSvc/rms01.local)
3. Note the user accounts under which the SPN is located and the organizational unit the accounts reside in….the userPrincipalName should be located directly above the servicePrincipalName registration as in the example below.
userPrincipalName: useraccount@domain.com
servicePrincipalName: ServiceClass/host.domain.com

Use one of the following options to delete the account SPN registrations from the accounts that should not contain registrations to ServiceClass/host.domain.com. (i.e. Typically any accounts containing an SPN registration for SeriviceClass/host.domain.com that services are not explicitly starting with). Make sure you know which credentials you want to keep (in this case the system account or the domain administrator) and see to it that the service is running with the credentials you want to use. Delete the other one.

Using ADSIEdit

1. Add ADSIEdit to the MMC and bind to the domain using the Domain well known naming context.
2. Navigate to each user account you previously documented as having a duplicate SPN registration and right click the account and select properties.
3. Scroll through the list of attributes until you see servicePrincipalName, double click servicePrincipalName and remove the duplicate SPN registration and click on OK and exit ADSIEdit.

Using SetSPN

1. From the command prompt type the following command and hit enter.setspn -D ServiceClass/host.domain.com:Port AccountName

Make sure to test before performing this operation in a production environment.

Brad Hearn

Enterprise Server Analyst

http://bradstechblog.com/