Security & Management : MOM

MOM 2005 SP1 Agent Prerequisite Component for Windows XP Embedded

daniel — Thu, 14 Sep 2006 23:01:00 GMT

The MOM 2005 SP1 Agent Prerequisite Component for Windows XP Embedded extracts the components required for the MOM 2005 SP1 Agent to work on Windows XP Embedded.

Download

MOM SLA Scorecard for Exchange Installation Tips and Tricks

daniel — Wed, 09 Aug 2006 06:10:00 GMT

I tested to install MOM SLA Scorecard for Exchange this week.

And i want to share some tips and tricks here.

After the installation of MOM Reporting, Run the DTS Job Manually to transfer the data of OnePoint database to the Report database first, Wait about 5-20 mins.

When the DTS job completed successfully, Install MOM SLA Scorecard for Exchange, and wait about 5-20 mins for transfer the data from System Center Data Warehouse to SLA Staging Database.

Finally, run the ProcessSLAJob manully.

Sizing Tools for MOM and SMS

daniel — Tue, 01 Aug 2006 06:57:00 GMT

Microsoft released some great sizing tools for MOM and SMS, You can use them to plan the Hardware Capacity for each of the MOM and SMS component.

MOM 2005 Sizer

The MOM 2005 Sizer provides recommendations for MOM server configurations based on modeled workloads.

SMS 2003 Capacity Planner

A planning tool that helps consultants, SMS administrators, and IT professionals perform scenario analysis on their existing and proposed SMS 2003 hierarchy

System Center Capacity Planner

Microsoft System Center Capacity Planner 2006 helps size and plan deployments of Microsoft Exchange Server 2003 and Microsoft Operations Manager (MOM) 2005. It provides you with the tools and guidance to deploy efficiently, while planning for the future by allowing for "what-if" analyses.

Move MOM 2005 Reporting Database

daniel — Wed, 19 Jul 2006 18:19:00 GMT

This article describes how to move Microsoft Operations Manager (MOM) 2005 Reporting together with the MOM Reporting database to a different computer.

http://support.microsoft.com/default.aspx/kb/922332/en-US

MOM 2005 Mobile Phone Operator Console

daniel — Wed, 14 Jun 2006 11:12:00 GMT

Michel tried to change the Japanese MOM 2005 Mobile Console to English SUCCESSFULLY! Great!

"Here are the steps I've taken:

Download the “mom2005Mpc.exe” at http://www.microsoft.com/japan/mom/evaluation/mpc.mspx
Download and Install the “mobile components update 4.0” from http://www.microsoft.com/downloads/details.aspx?FamilyId=02FA15FE-40D9-4DCE-9BB1-4DD61A5B7CCB&displaylang=en
Install the “mom2005Mpc.exe” . Just click the buttons you normally will click. Choose all the programs to install. The setup will create 2 websites on the given ports (default 1280 and 1281). It will also create an database MOMMPC on the database server you selected during the install. This database will contain 3 tables and stored procedures needed for the web service to authenticate the mobile devices.
Connect to the mobile phone console website http://localhost:1280/default.aspx You will see this in Chinese….
Change for the MobilePhoneConsole website the web.config as following. Search the text “DefaultLocaleId” and change the value to 1033. This is English US. Now we are almost there.
Connect again to http://localhost:1280/default.aspx . You will see this in English. Log on with a correct user that has mom privileges. I used the local administrator. Now you will see the “device not approved” message.
Go to the SQL server where the database MOMMPC and tables are created. Go to the table “MPChwId” . Query the table. You will see an entry in it . Change for al rows the vaule from the column “IdStatus” to 2. And change the “LocaleId” to 1033.
Connect to http://localhost:1280/default.aspx And you will see it WORKS!!

Have fun with it.

Michel"

Source: http://blogs.infosupport.com/michelk/archive/2006/06/14/7818.aspx

Installing MOM 2005 SP1 and SMS 2003 SP2 on SQL Server 2005 backend

daniel — Fri, 14 Apr 2006 02:33:00 GMT

For SMS 2003 SP2, It supports SQL Server 2005 already.

For MOM 2005 SP1, Microsoft released 3 hotfixes to let it supports SQL Server 2005.

But there are many customers to ask the procedure for install these hotfixes.

Andrej posted it on his blog already. (Step by Step) :)

http://blogs.technet.com/alipka/articles/424009.aspx

MOM Database Error 1105

daniel — Wed, 12 Apr 2006 06:07:00 GMT

If you installed MOM 2005 on the SQL Server machine that enabled Disk Quota.

You may get the following Error Alert.

Event ID: 17052
Source: MSSQLSERVER

Description:
Error: 1105, Severity: 17, State: 2
Could not allocate space for object 'Event_16' in database 'OnePoint'
because the 'PRIMARY' filegroup is full.

To solve this problem, Check the Disk Space first.

And then Disable quotas for the SQL service account(s).

Multiple Management Group Rollup Solution Accelerator for MOM 2005

daniel — Fri, 07 Apr 2006 03:00:00 GMT

In the multiple Management Groups environment, you may want to collect all of the data from each data warehouse for complete enterprise monitoring.

By default, each Management Group included it's data warehouse.

To configure multiple Management Groups to use a single data warehouse, You need to use Multiple Management Group Rollup Solution Accelerator.

Management Groups use DTS to transfer data to the single date warehouse.

More Information About Multiple Management Group Rollup Solution Accelerator

MOM Remote Pre-requisite Checker

daniel — Wed, 29 Mar 2006 02:16:00 GMT

Check if the required services and ports are allowed to push an agent or run discovery with this stand alone utility.

This is a new tool in the Resources Kit for MOM 2005.

Download

Service Continuity Solution Accelerator for MOM 2005

daniel — Tue, 28 Mar 2006 06:51:00 GMT

It is a great solution for implement a DR solution for MOM 2005. It provides automatic failover and monitoring continuity through:

Muliple Management Groups.
Failover Management Servers within a Management Group.
Clustered MOM Database.
MultiHome MOM Agent.
DR Sites.

More Information About Service Continuity Solution Accelerator.

Running MOM 2005 SP1 on SQL Server 2005

daniel — Tue, 14 Mar 2006 02:27:00 GMT

MOM 2005 SP1 is not compatible with SQL Server 2005 without these 3 hotfixes.

Unable to discover computers in AD after upgrading to .NET Framework 2.0

Errors can occur when data collected by MOM 2005 SP1 is queried with SQL Server 2005 Reporting Services

Deadlocks may occur with MOM 2005 SP1 on SQL 2005

MOM 2005 SP1 Resource Kit

daniel — Wed, 01 Mar 2006 19:28:00 GMT

•	Alert to RSS Utility: Now subscribe to alerts via RSS!
•	Computer Group Hierarchy Utility: Now export your Computer Group Hierarchy and recreate it else where. Also supports creating Computer Groups based on AD containers and it’s hierarchy
•	Console Scope Utility: Automatically update Console Scope membership with this utility. You can also mirror AD Security Group membership to a console scope using this utility
•	DAS Role Update Utility: Harden your MOM servers by using this utility to remove the BUILTIN\Administrators group from the MOM Administrator role
•	Management Group Utility: If you have orphaned Management Group data on your agents from Test Management Groups, then this tool is for you. Allows you to list and remove Management Groups from the agent side
•	MOM Remote Pre-requisite Checker: Check if the required services and ports are allowed to push an agent or run discovery with this stand alone utility

Download

MOM Reporting Server and Domain Controller

daniel — Wed, 08 Feb 2006 15:55:00 GMT

To install MOM Reporting Server on the Domain Controller is not recommended.
But sometimes, you must need to install it on the Domain Controller, for example, Demo VMs, Limited Hardware..etc.
When you installed the MOM Reporting Server on the Domain Controller and then try to generate the reports, You may experience the "Logon Failure" error in the Reporting Console.
To solve the problem, Open Administrative Tools, Domain Controller Security Policy, Local Policies, User Right Assignment. And add the MOM Report User Account and SQL Reporting Service Account to "Allow Logon Locally".

MOM 2005 Web Console HTTP Error 403 - Forbidden

daniel — Fri, 13 Jan 2006 00:31:00 GMT

When you try to access the MOM 2005 Web Console on any machine, You may get the HTTP Error 403 - Forbidden Error.

It is cause the IIS configuration problem, to solve the problem:

1. Open Internet Information Services.

2. Expand Web Sites

3. Right click MOM 2005 Web console and Choose Properties

4. Select documents tab

5. Add default.aspx to the list.

MOM 2005 Availability Management Pack Reporting Issue

daniel — Tue, 10 Jan 2006 02:52:00 GMT

When you try to create new availability report in MOM Reporting Console, You may see an error message.

"Invalid Object Name
'SC_Class_Group_View' and in the details it sais following: "An error has
occured trying to complete the operation. The result code returned was
0x80040e37. Please provide this number to technical support."

To solve this problem, Just run the "SystemCenterDTSPackageTask" scheduled tasks manually.

You receive "Invalid Parameter (0x80041008)" error messages in the Microsoft Operations Manager Operator Console

daniel — Wed, 28 Dec 2005 01:45:00 GMT

When you use Microsoft Operations Manager (MOM) 2000 or MOM 2005 to monitor a Microsoft Windows 2000-based or Microsoft Windows Server 2003-based domain controller that has the MOM Active Directory Management Pack installed, the MOM Replication health monitoring may fail. When this problem occurs, the Windows Server 2003-based domain controller reports an error event back to the MOM Management Server, and the following events appear in the Alerts pane of the MOM Operations Console:

The script ‘AD Replication monitoring’ encountered a runtime error. Failed to determine whether the WMI replication provider is installed. The error returned was: ‘Invalid Parameter’ (0x80041008)

AD Remote Topology Discovery cannot determine whether the WMI Replication Provider is installed. The error returned was: ‘Invalid Parameter’ (0x80041008).

This problem occurs when the Replprov.dll file tries to access a pointer that is not valid. The Replprov.dll file is used by the MOM Active Directory Management Pack to retrieve Active Directory replication-related information, including replication status. When this problem occurs, the Replprov.dll file cannot determine the replication status of the domain controller, and the error messages are generated.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article.

More Information: Microsoft KB Article 889054

MOM Reporting Installation Issue

daniel — Thu, 15 Dec 2005 08:54:00 GMT

Error Message:

Failed to create data source for data warehouse. An exception occurred.
Check that you can access the SQL Services Reporting Server from this
machine. Error Code : -2147467259 (Unspecified error)

Workaround:

1. Open Registry Editor.

2. In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

3. Right-click "Lsa", point to "New", and then click "DWORD Value".

4. Type "DisableLoopbackCheck" for the name, and then
press ENTER.

5. Right-click "DisableLoopbackCheck", and then click "Modify".

6. In the "Value data" box, type "1" to enable it, and
then click "OK".

7. Quit Registry Editor, and then restart your computer.

Source: My 9th Microsoft KB Article

Deploying MOM 2005 SLA Scorecard for Exchange: Part 2

daniel — Tue, 29 Nov 2005 21:07:00 GMT

After the installation and basic configuration of SLA Scorecard for Exchange, You should configure the advance settings to customize the SLA Scorecard.

Create and add users to SLAAdministrators local group on SQL server to allow users to enter the Outage Maintenance administration page and update the information about an outage.
Create and add users to SLANormalUsers local group on SQL server to allow users to view and browse the SLA Scorecard and reports.
Open MOM Reporting Console, Click Properties and select New Role Assignment, Enter the user name, Click Browser Permissions, Select New Role Assignment and add SLAAdministrators or SLANormalUsers. Configure the Security Settings.
Apply Security to the SQL server objects. Please refer Microsoft Technet
Customize the settings of Outage Maintenance, Server Maintenance and SLA Configuration in the SLA Scorecard UI.
Provide the SLA Scorecard and MOM Reporting URL to the users.
Use the SLA Scorecard views, trend reports or MOM Reporting Console to analyze the output.

More Information

Deploying MOM 2005 SLA Scorecard for Exchange: Part 1

daniel — Thu, 24 Nov 2005 21:47:00 GMT

These are the simple steps to install SLA Scorecard for Exchange. It is not supported on Windows Server Datacenter Edition or Cluster.

Prepare the core prerequisites (MOM Reporting, Exchange Server 2003 SP1, Exchange Server 2000/2003 Management Packs, SLA Scorecard for Exchange Management Pack and Outlook 2003 on the client)
Prepare the optional prerequisites (Exchange Intelligent Message Filter Management Pack and Sybari Anti-Virus Management Pack)
Run the installation by SLA Scorecard.msi on the MOM Reporting Server or separate SQL Server. To install SLA Scorecard.msi on the separate SQL Server, make sure that your user account is added to the MOM Reporting Server's Local Administartors group and add that server's computer account to the MOM Reporting Server's Local Administrators group.
Accept the License Agreement
Verify the Prerequisites
Type the name of the MOM Reporting/Data Warehouse Server
View the Log of the prerequisites check
Setup the Installation Path
Choose the SQL Server Instance
Configure the SLA Scorecard Reporting Databases name
Configure the Presentation Database Data and Log File Location
Process the Installation
Press Configure Exchange button to open SLA Scorecard UI, Click Server Maintenance to edit the In Service Date, Server Type and # of Exchange Databases for each Exchange Server. Click SLA Configuration to setup the SLA Target. Close the SLA Scorecard UI.
Press Test Configuration button and enable the Transfer data from MOM data warehouse now option
Finish the Installation.
If you unable to access the SLA Reports in MOM Reporting Console, Open MOM Reporting Folder, SLA Scorecard for Exchange, SLASA Configuration, Select Credentials stored security in the MOM Reporting Server. Enter the Local Administrator account information of the MOM Reporting Server. Select Use as Windows credentials when connecting to the data source. Click Apply.

Interview with Kelly Altom Microsoft Group Program Manager for MOM

daniel — Wed, 23 Nov 2005 14:47:00 GMT

It is a great interview for MOM v3.

Enjoy it!

http://bink.nu/Article5410.bink