SCOM is not monitoring DHCP server cluster resource

here is interesting info:

My customer has DHCP server is running on a cluster node, all of the other cluster groups are monitored but not the DHCP group this result that the virtual server not  included in the windows 2003 DHCP group and DHCP on it is not monitored, I found the issue: the issue that the discovery is processing the start reg value with object of 2, on the cluster the attribute is set to 3:

<Configuration>

  <ComputerName>$Target/Property[Type="WindowsLibrary!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

  <RegistryAttributeDefinitions>

    <RegistryAttributeDefinition>

      <AttributeName>Microsoft_Windows_DHCP_Server</AttributeName>

      <Path>SYSTEM\CurrentControlSet\Services\DHCPServer\Start</Path>

      <PathType>1</PathType>

      <AttributeType>2</AttributeType>

As I searched and most of my fellow consultants did, it looks that the DHCP MP is not cluster aware, and this will be fixed in the next version, so be careful as this is not mention anywhere in the documentation either in DHCP MP or cluster MP.

 

Bye

Move MOM database to new SQL server-Active/Active SQL server

Here we go with the detailed steps of moving the MOM DB to a new SQL server, In my case I assumed that the server will be hosted on SQL active/active cluster, the steps are similar for SQL on stad alone server.

there is 2 tricks in the above setup, First Correct the SQL connection in the SQL reporting or it will not wwork, the second is to make sure that the disk that will host the MOM DB and Logs is a part of SQL server dependencies or the MOM DB will not be created.

1-     Uninstall all other MOM Server components (and any MOM Agent of the same management group) that reside on the destination computer.

2-     On the designated active SQL cluster Node create the MOM database using the momcreatedb.exe utility (this utlity could be found on the following path: “MOM CD”:\ SupportTools\x86).

3-      Stop the MOM service on all MOM Management Servers. If MOM to MOM Product Connector (MMPC) is installed, stop the momcomm service.

4-     Back up the current OnePoint database to a file.

5-     On the destination computer, Restore the SQL database using the backup created in step 4.

6-     Grant "db_owner" privileges to the DAS account. The DAS account was specified when you installed the original MOM database component. To grant these privileges, do the following:

a.     In the SQL Server Enterprise Manager navigation pane, expand the SQL instance associated with this database.

b.     Expand Security, and click Logins.

c.     Right-click the DAS account displayed, and open the properties page.

d.     From the Properties page, select the Database Access tab.

e.     Select the OnePoint checkbox.

f.      In the Database Roles for OnePoint pane, select the "db_owner" check box. Click OK.

7-     On the first MOM Management Server start Regedt32.exe, and change the following registry values from the current SQL Server Instance to the new SQL Server Instance SQLservername\instanceame:

·          HKEY_LOCAL_MACHINE\Software\Mission Critical Software\DASServer\DataSource Value

·          HKEY_LOCAL_MACHINE\Software\Mission Critical Software\Onepoint\Configurations\\Operations\Database Value

8-     Restart the MOM service.

1-     On the Designated SQL active node install IIS, and enable ASP.Net

2-     Install SQL Reporting.

3-     Install MOM Reporting As using Normal installation steps.

4-     After the installation complete open MOM reporting console.

5-     Select the SCDW link

6-     Edit the Connection string by Removing the . and replace it with SQLservername\instanceame.

7-     Restart IIS service.

8-     Edit the MOM DTS package job using the following steps:

·         Click Start, then select Settings, Control Panel, Administrative Tools, Scheduled Tasks.

·         Right-click the SystemCenterDTSPackage task and select Properties.

·         In the "Run" text-box change the /srcserver: parameter to the destination computer as in the example below:

MOM.Datawarehousing.DTSPackageGenerator.exe /silent /srcserver: SQLservername\instanceame /srcdb:OnePoint /dwserver: SQLservername\instanceame /dwdb:SystemCenterReporting /product:"Microsoft Operations Manager"

·         Click OK and reconfirm the password.

Regards

 

and you cannot install SCOM reporting

Some people reported and error in SCOM reporting:

 

MSI (c) (DC! E8) [13:47:30:933]: PROPERTY CHANGE: Adding FailedMsgProperty property. Its value is' CheckHttpAddressResponse: Failed Status Code of the remote server sent an error: (503) Server not available. ".

 

For people who are getting this error, please remove the proxy settings from the IE and try again.

And what about SCOM in multiple forests: design SCOM in multiple forests

Ok,

I have posted a nice amount of posts about SCCM in multiple forests, it looks like I have gave away all of the required info, not sure if I missed something but sure I recall anything I will post it.

 

For SCOM deployment across forests, it is very easy. More than SCCM, you have 2 options either allow the agent to talk directly to the RMS/MS servers or deploy a opsmgr gateway in the remote forest, based on studying here is the factors the controls your decisions:

-          If you have a small amount of agents with acceptable bandwidth and network connectivity I would go to allow them to connect directly t the SCOM server.

-          If you have a large amount of servers or WAN connectivity, I would go for deploying a GW in the other forest, check and Google about top 10 benefits of using GW servers, as data will be compressed better, less administrative overhead…etc

In both cases you will need a CA around, you cannot use self signed certificates, an enterprise or standard certificate will do the job, once certificates in place and configured communication will flow smoothly and here is 2 tips:

-          You will need to import and configure a certificate on the RMS/MS server in the original forest. And import the certificate using the certificate import utility, it is not clear in the document and people didn’t pay attention to this point.

-          You don’t need a trust in place between forests.

-          In the other forest where the GW installed you don’t need certificates for agents as long as servers are joined to the forest, agents will communicate with the GW using mutual authentication, GW to RMS communication will be secured using certificates.

-          Note the AD MP will not work across forests.

This is the major points I wanted to highlight, I will start posting about transitioning from SMS to SCCM soon, so keep reading J.

New Cluster MP released

It has been released yesterday, this is a very important update to implement in your infrastructure, it has a lot of fixes and improved cluster performance monitoring.

The download is here http://www.microsoft.com/downloads/details.aspx?FamilyId=AC7F42F5-33E9-453D-A923-171C8E1E8E55&amp;displaylang=en&displaylang=en you will have to uninstall the previous cluster MP before installing this one, check the MP guide file first.

 

Install/FIX reporting after upgrading RMS to SP1

Went yesterday through a nice SCOM installation, install SCOM then reporting then SP1 for SCOM and reporting, however I had an issue as reports were not showing, tried everything, and went to google and found that most of those cases solved using reporting reinstallation, uninstalled reporting, reset SRS, now I am trying to load the reporting to install, but it gets interrupted, checked the error log and found that reporting cannot be installed as it tries to load MP Warehouse library version that is old and the version will not load. And setup fails.

It gives the following error:

ImportMomManagementPack: Loading management pack C:\Program Files\System
Center Operations Manager
2007\Reporting\Microsoft.SystemCenter.DataWarehouse.Internal.mp. 5:26:43 AM
ImportMomManagementPack: We are using the Client API to load the MP.
ImportMomManagementPack: Error: Unable to load management pack C:\Program
Files\System Center Operations Manager
2007\Reporting\Microsoft.SystemCenter.DataWarehouse.Internal.mp
: Cannot import ManagementPack
<<Microsoft.SystemCenter.DataWarehouse.Internal, 31bf3856ad364e35,
6.0.6246.0>>. A newer version of this ManagementPack <6.0.6246.0> is already
imported in the database.

To fix this issue follow the following steps:

-          Uninstall SCOM reporting

-          Reset SRS if you

-          Export the default MP and remove the WH library reference and overrides.

-          Import it back

-          Delete the WH library and ORD library MP.

-          Install the reporting.

-          Import the original MP

This is a complex solution, I had a reply from the product team, to run the Reporting2007.msi directly and this should solve the problem, didn’t try this one so you have the both solutions now

 

OpsMgr 2007 SQL MP version 6.0.6278.8 Released

This fixes and changes introduced in this release were thanks in large part to the feedback that all of you have provided to us. 

http://blogs.technet.com/momteam/archive/2008/04/01/opsmgr-2007-sql-mp-version-6-0-6278-8-released.aspx

The OpsMgr 2007 MP for SQL 2000 and 2005 has been updated and was released to the MP Catalog on 3/31/2008 (version 6.0.6278.8).  This version includes the fixes from all previous versions of the MP and is supported on both OpsMgr 2007 RTM and OpsMgr 2007 SP1. The table below is an excerpt from the MP guide detailing the changes and fixes that were made in this release.  I'd like to specifically call out the final bullet in the "Changes to SQL Server 2005 Management Pack" as the behavior of the "Database Status" monitor has been updated to have three states now so it can more appropriate handle DB restore and recovery states.

Changes in this Update

The March 2008 update to the SQL Server Management Pack includes the following changes:

General changes	·       The “Transaction Log Space Free (%)” monitor was made public for both SQL 2000 and SQL 2005 to allow for further customization. ·       Some corrections were made and additional detail provided in the “Key Monitoring Scenarios” sections of this guide. ·       Removed the hard-coded exception for jobs with a specific name from the “A SQL job failed to complete successfully” rules for both SQL 2000 and SQL 2005. ·       Fixed an issue with the scripts used to calculate DB free space which was preventing some databases from having their free space correctly monitored on SQL installations that did not have DBs with contiguous IDs. ·       Corrected typographical errors.
Changes to SQL Server 2000 Management Pack	·       Fixed an issue where incorrect free space values were being calculated for some SQL 2000 databases.
Changes to SQL Server 2005 Management Pack	·       A fix was made to address issues with collection of performance data from specific instances of Analysis Services. ·       Significant changes were made to the “Database Status” monitor in the SQL 2005 MP.  The monitor now has three states reflecting good, bad, and neither.  The possible database states have been realigned into these categories which will reduce “false-positive” alert volumes specifically when log-shipping and database backups are occurring.

 

 

Monitoring Exchange SP1 with SCOM

Hello,

If you have noticed, some of you after applying SP1 will not be able to collect some performance data and get alerts as before, A some DB performance counters has been changed is SP1, this caused performance data not to be collected so here is what is going exactly. As far is reported the only performance counter object that was changed in SP1 was the Database object, which was renamed to the MSExchange Database object (affects mb, hub transport, edge transport roles). A list of where these counters appear is below.  the alerts customers could be missing would be the ones generated by the monitors. Obviously the views and data collection rules do not work either.

 

In terms of workarounds for this, you could disable the 2 rules and monitors and create a separate MP where the rules collect the “right” performance counters and the monitors take configuration from the rules. You’d need to do the proper targeting, but the MP classes are declared as public, so you could refer to them from another MP.

 

Note that for the updated MP, we will look for the updated (SP1) counters only, i.e. the customers could expect seeing similar types of behavior from their monitored Exchange 2007 RTM servers.

Rules

Collect__Database__I_O_Database_Reads_Average_Latency__Report_Collection_._5_Rule

Collect__Database__I_O_Database_Reads_sec__Report_Collection_._5_Rule

Collect__Database__I_O_Database_Writes_Average_Latency__Report_Collection_._5_Rule

Collect__Database__I_O_Database_Writes_sec__Report_Collection_._5_Rule

Collect__Database__I_O_Log_Writes_Average_Latency__Report_Collection_._5_Rule"

Collect__Database__Version_buckets_allocated._5_Rule

Information_Store__Version_buckets_allocated___Red_2000_._5_Rule"

Information_Store__Version_buckets_allocated___Yellow_1800_._5_Rule"

 

Monitors

Information_Store__Version_buckets_allocated___Red_2000_._5_Rule.AdvancedAlertCriteriaMonitor (takes data from the rule with the same name)

Information_Store__Version_buckets_allocated___Yellow_1800_._5_Rule.AdvancedAlertCriteriaMonitor (takes data from the rule with the same name)

 

Views

Microsoft_Exchange_Server_Exchange_2007_Mailbox_Information_Store_Database_I_O_Database_Reads_Average_Latency

Microsoft_Exchange_Server_Exchange_2007_Mailbox_Information_Store_Database_I_O_Database_Reads_sec

Microsoft_Exchange_Server_Exchange_2007_Mailbox_Information_Store_Database_I_O_Database_Writes_Average_Latency

Microsoft_Exchange_Server_Exchange_2007_Mailbox_Information_Store_Database_I_O_Database_Writes_sec

Microsoft_Exchange_Server_Exchange_2007_Mailbox_Information_Store_Database_I_O_Log_Writes_Average_Latency

 

SCOM: exchange management pack new CustomOwaUrls key

Hi,

I am in the airport now, I just wanted to give you a quick ip, the new Exchange management pack for SCOM is not looking for the old customurls key, it is looking for the CustomOwaUrls, so beware of that a it might trick you.

 

Wish me a safe trip.

Using SCOM SP1 to manage SCOM RTM

Well,

I am afraid this is cannot be done, if you try to do that you will get an error state that you tried to connect to server with version not supported, so you will have to use the RTM console to manage the RTM version and the SP1 versions to manage the SP1 version

SCOM 2007: Error in ADMP

A customer has imported an ADMP, and soon after running it, he started to get the following error:

AD Replication Monitoring : encountered a runtime error. Failed to obtain the InfrastructureMaster using a well known GUID.

The error returned was: 'Failed to get the 'fSMORoleOwner' attribute from the object 'LDAP://SERVERNAME/'.

The error returned was: 'There is no such object on the server.' (0x80072030)' (0x80072030)

 

To solve this issue follow the below steps:

1. Run Adsiedit.msc
2. Connect to the DC=DomainDnsZones,DC=xxx,DC=xxx ,DC=xxx partition.
3. Open the properties for the Infrastructure object.
4. Look at the fSMORoleOwner attribute and it is set to CN=NTDSSettings\0ADEL:ed7c8fe9-c5cd-4101-bf57-7468c606a6be,CN=IOWADC4\0ADEL:ecaeecd1-dea1-44ac-9a3c-fb827fd6d085,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=xxx,
DC=xxx
5. If this particular record is set to delete, then remove the above entry and then add the correct attribute for the current FSMO role holder.

Thanks to MCS SA for sharing this info that made my life easier.

SCOM 2007 How to remove discovered objects

Suppose that you have discovered an object and you want to delete this object from SCOM 2007, in SP1 In SP1 there is a new cmdlet that can be used to force the removal of discovery inventory (for example after you override a discovery for a particular object): Remove-DisabledMonitoringObject.

 

SQL 2000 running on x64 windows in not monitored

Yes this is true, SCOM cannot monitor x86 version of SQL running on x68 OS, x64 SQL 2000 version running on x64 OS but it will not monitor x86 version of SQL running on the x64 OS so if this happened to you ,you will have to move the SQL version to x64 version. Or better upgrade to SQL 2005.

Mahmoud

Building active/active SQL cluster- Part2

In this session we will continue illustrating how to build an active/active SQL cluster, we built the cluster in the last session, we will install the SQL cluster in this session.

i prefer that you copy the installation source files to the local harddisk, i have experienced some faulty CD and hardware in my work, and it it will cause a lot of time to fix the corrupted installation specially in cluster environment.

so let us begin:

before you start in the SQL cluster installation you have to create a named instance pipe on each node for each named instance you will install, this is a very important  step or the installation will fail.

To create a named pipe fpr the installation follow steps in the following KB:

http://support.microsoft.com/kb/815431

Install SQL in ACTIVW/ACTIVE cluster environment:

- from the SQL installation source double click on setup.exe.

 

- In the Welcome creen, click on SQL server 2000 components

 

- In the install component screen, click on Install database server.

 

- In the welcome screen, click next.

 

- In the licensing screen, enter the administrator name and organization name,Click Next.

 

in the installation option, enter the first virtual server name "DBVS1".

in the fail over clustering page, enter an IP that will be associated with the failover cluster,Click Next.

 

in the cluster disk selection, seelct a disk that SQL data file will be installed on,Click next.

 

in the cluster definition, be sure to select both nodes to be included in the cluster configuration,Click next.

 

In the Remote Information page, enter a valid administrator credentials,Click Next

 

 

in the instance name clear the default instance checn box, be sure to installed a named isntance as we identified in the named pipe before, because there is could be only one default instance on the cluster server.

 enter an instance name i chose (NI1), Click next.

in the setup type, choose custom, click next.

 

In the select components, clear the bookonline, and development tools.

 

in the service account, enter a valid user name and password which the SQL service will runder it's credentials.

 

in the authentication mode, select windows authentication (unless you will run application using SQL authentication), then click next.

 

in the collation setting, click next

 

wait until the setup finish, verify that the SQL cluster installed succesfully. the installation of the second node is typically similar to the first node instalaltion, but you will chose a diiferent virtual server name and different instance name (i chose DBVS2, NI2).

after that designate one server for a SQL virtual server, and designated the other node for the other VS and NI.

have fun

 

 

Moving MOM database ot different SQL server

I had a call from a customer last week, he called me to move his MOM database from the current partition a new SAN allocated disk space, it was easy "I guessed" a simple attach and detach thing, however when I reached the customer location and met the team i found that they want to move the database from the current SQL server which is the MOM server, to a new Active/Active SQL cluster.

I done this before but never move the SQL database to new SQL active/active cluster I was a little scared because the SQL cluster was holding all of the databases of that customers application use(about 2 terabyte of data) and holding his application (7 international subsidiaries are using it) so i was very careful specially that they wanted me to work on the fly and no testing.

I did it and it went "almost" smoothly , i will post a step by step guide later on how to do it.

so visit the blog later and you will find it.

 

Building Active/Active SQL cluster-part1

I have searched the internet for a detailed guide on how to implement SQL active/active cluster, I have implemented it couple of time before but It was so strange not finding a detailed and clear guide, most of the current articled that speaks about the subject either talking about windows 2000 clustring, or talking from a general prospective. So If you are looking for a detailed guide this one for you.

I will not talk about how to Virtualize the environment or configuring SAN/NAS there is a lot of documentation that talks about the process for VMWARE and Microsoft virtual server 2005. I will assume that you have configured every thing.

The storage is configured so that one partition for database file for instance1 and one partion for logs, the same applies for instance 2.

I will start from the building the cluster. Some of you will notice that I have removed the  domain name, this is because I used a customer real domain while capturing the screen shots, so I have removed the domain name but all you have to do is to put your domain name.

Let us start

open node 1 and open the cluster administrator and choose to create a new cluster

 

 

in the cluster name specify the cluster name "in my case otdb", click next

 

 

in the computer name select hte first node PC, click next.

 

in the Ip address specify the IP address for the Cluster, click next.

 

in the cluster service account spcify the account shich the clsuter service will run under it's priviledge ( i highly recommend that you create a special account for the cluster service and don't use an administrator account) ,click next

 

in the quorum disk select the disk which will hold the quorom in my case i chose the E drive and clik next

 

after the wizard finshes configuring the cluster on the first node open the cluster administrator and verify the succesfull installation.

 

to add the second node to the Cluster group:

from the File Menu, select new, and select Node:

 

in the add new node wizard select next.

 

in the computer name field, type the computer name or browse for the computer, add the computer using the add button, and click next.

after the analyzing configuration wizard finishes, Click next.

 

in the cluster service account page, specify the cluster service account password, click next:

 

the wizard will configure the second node and will join it to the existing cluster. there is some ocnfiguration are required for QA the cluster configuration, a etailed list of the QA procedure could be found here:

http://www.microsoft.atat.at/downloads/details.aspx?FamilyId=0E9B809D-2A7A-4ADF-9FDE-897210A461DB&displaylang=en

this is part one, i will continue in the part 2 in building the active/active cluster configuration.