System Center Operations Manager 2007

http://blogs.technet.com/momteam/archive/2008/05/14/data-warehouse-data-retention-policy-dwdatarp-exe.aspx  |  Comments

The tool linked in this article allows you to view and configure the data warehouse data retention policies configured within your Operations Manager DW.

Follow the instructions below to use.

Prerequisites

Operations Manager 2007 SP1

Operations Manager 2007 Reporting SP1

Installation

Download the attached zip file and copy the required version of the file either x86 or x64 to a local directory such as “c:\dwdatarp\”

Usage

·         To view dwdatarp.exe usage instructions run:
c:\dwdatarp\dwdatarp.exe

·         To view current Data Retention settings run:

c:\dwdatarp\dwdatarp.exe –s “dw servername” –d “dw databasename”

example:  C:\dwdatarp>dwdatarp -s opsmgrsp1 -d OperationsManagerDW

·         To set Data Retention for a particular dataset run:

c:\dwdatarp\dwdatarp.exe –s “dw servername” –d “dw databasename” – ds “dataset name” –a “aggregation name” –m “days”

example: C:\dwdatarp>dwdatarp -s opsmgrsp1 -d OperationsManagerDW – ds “Performance data set” –a “Hourly aggregations” –m 399

Notes:

1.        The server with dwdatarp.exe installed must have access to the OperationsManagerDW along with the user running the tool.

2.       Updates are applied with immediate effect and data will be groomed during next grooming workflow.

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included utilities are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Daniel Savage

Program Manager | System Center Operations Manager

NewsGator Inbox can be configured to automatically download attachments if you wish. For more information, please refer to the NewsGator Inbox help file (NewsGator Inbox > Help)

http://mcpguides.com/?p=12

For the Healthy Event Expression, click "Insert and select "Expression". For the Parameter name enter "Property[@Name="State"], Select "Equals" for the Operator, and type in "GOOD" (or whatever value you used in your script to represent a healthy state).

http://www.systemcenterforum.org/gateway-secrets-revealed-gateway-implementation-the-fast-way/  |  Comments

This is our updated the updated order of operations for implementing the Gateway role in the most efficient way possible, taking into account the latest Operations Manager 2007 SP1 features and tricks we’ve learned – some of which are undocumented. We’ve tested this process repeatedly, and demonstrated its use at MMS 2008. These should help ensure your next Gateway implementation is successful with a minimum of effort – on the first try.

For more complete troubleshooting tips, see HERE.

On the Management Server

1.       Issue and install a certificate on the Management Server

a.       Request, approve and install certificate on the MS

b.      Run MOMCertImport tool (GUI)

2.       Run the Gateway Approval Tool

a.       Copy Gateway Approval Tool to the Opsmgr install directory

b.      Run tool to approve the gateway server

On the Gateway Server

3.       Issue and install a certificate on the Gateway Server

a.       Request, approve and install certificate on Gateway

b.      Run MOMCertImport tool (GUI)

4.       Install the Gateway Server

a.       Run Gateway installation

5.       Configure Gateway for failover to secondary mgmt server (optional).

TIPS:

Below are some tips to avoid common mistakes in implementing the Gateway server.

Step 1a & 3a

In the Certificates mmc snap-in, make sure the root CA is trusted by the server to which the certificate is issued. If not, add a copy of the root CA certificate to the Trusted Root Certification Authorities folder in the certificate store on the affected server.

Step 1b

This only works when you double-click MOMCertImport.exe to launch the GUI version of the tool. The command line version looks for the Health Service, and if not found, generates a failure message.Be sure to use the 32-bit or 64-bit version of MOMCertImport as appropriate for your operating system.

Step 2

In global settings of the management group, be sure to set agent approval to manual approval of manually installed agents. In the event you install the Gateway before the upstream management server has received word of the Gateway approval, this ensures the management server will not see the Gateway Health Service as a simple agent by mistake.

Step 5

Configuring Gateway failover can only be performed through the Powershell interface. Click HERE for instructions.

http://blogs.technet.com/stefan_stranger/archive/2008/05/15/removing-the-operations-manager-2007-data-warehouse.aspx  |  Comments

Removing the Operations Manager 2007 Data Warehouse During some commandline installation testing I accidentally installed the OpsMgr Data Warehouse in a wrong directory, so I wanted to uninstall the database and used the GUI setup in an effort to delete the Data Warehouse (OperationsManagerDW). Luckily I did my testing on my demo systems because I saw some frightening screens during my uninstall of the Data Warehouse ;-) Screenshot of current installation: Screenshots of uninstall Data W

http://blogs.technet.com/momteam/archive/2008/05/13/secondary-management-server-install-fails-if-reporting-is-already-installed-with-dw-action-account-and-rms-action-account-are-the-same.aspx 

Issue: If you try to install a secondary Management Server (MS) in a scenario with Root Management Server(RMS) and Reporting installed with Data Warehouse(DW) action account and Root Management Server action account (default action account) is the same, the secondary Management Server setup rolls back with an error in the setup log:

Error from log file:

**********************

AddRunAsProfilesCA: Error: Index was out of range. Must be non-negative and less than the size of the collection.

Parameter name: index,

Stack:    at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)

   at System.ThrowHelper.ThrowArgumentOutOfRangeException()

   at System.Collections.Generic.List`1.get_Item(Int32 index)

   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfile(String profleGuid,

MonitoringObject hostedHealthService, ManagementGroup managementGroup, String currentActionUserDomain, String currentActionUserName)

   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AddRunAsProfiles(Session session)

Cause: In OpsMgr Service Pack 1 setup if DW Action account is same as RMS action account we do not configure DW RunAs profile. So, when you attempt to install second MS we try to configure its DW RunAs profile with DW Action account by looking at RMS DW RunAs profile which is empty. (This happens when default action account is same as DW action account and installation scenario is: RMS and Reporting is installed and then second MS is attempted to install).

Workaround:

Create a ‘Windows’ Run As Account with same domain user as that of RMS Action Account.

Associate this account to ‘Data Warehouse Account’ RunAs profile

Associate this account to ‘DW Configuration and Synchronization Reader Account’ profile (in SP1 this is called as ‘Reserved’, there would be three Reserved profiles in SP1, this one is third in the list). Re-run Management Server setup.

Needless to say this will be fixed in Service Pack 2.