JAMA00

SCOM 2007 R2

Archive for January, 2010

Monitoring Multiple Active Directory Forests Without A Trust

Posted by rob1974 on January 26, 2010

SCOM can monitor other forests without have a trust to that forest. This can be achieved by using certificates. My colleague already made a post on how these certificates need to be set up. Even though  SCOM management servers and its agents have communication individual management packs might have the requirement of having a trust in place.

As we all read the management pack guides before we import a new management pack, you immediately see on page 9 multiple forest topology discovery and views: “to discover other forest, a trust relationship is required between the forest hosting the Operations Manager Manager Root Management Server and other forests”.

We don’t have a trust nor do we want one, but most of our monitored servers are in other forests and there are quite a lot of domain controllers amongst those servers. Does this line mean we don’t have to bother with importing the AD mp? Fortunately, this is only about topology and their corresponding views of forests and domains. All domain controllers are discovered and monitored by this MP, even when they are in different forests than the SCOM servers.

We’ve disabled the topology discoveries as we just have a single forest, single domain topology for SCOM and the people in charge of the domain controllers are scoped to those servers on the computer object, so they won’t see the topology anyway. However, I wouldn’t recommend disabling the discoveries when the main forest you are monitoring is the same as the SCOM forest or has a trust with that forest. By disabling these discoveries you basically lose your health model for AD and are left with just the health of domain controllers.

If you do want to disable the topology discovery, just disable the discoveries below:

image

As you can see i filtered on “root management server” and this is the reason why you need to have the trust. These discoveries all run on the RMS.

So, now we have monitoring of domain controllers without having knowledge about the domain/forest topology. Well not quite, we’re not there yet. We do have monitoring of domain controllers, but we also have lots of errors about several scripts not being able to run with an error description “failed to create the object ‘McActiveDir.ActiveDirectory’”.

The management pack guide states that the Active Directory Helper object will be installed when you install the agent. However, this is only true when you push the agent (well i think, i haven’t really tested it). For manual installed agents, none of the helper objects will be installed and you need to install this helper object (OOMADS.msi found on the SCOM CD) on all domain controllers manually.

The installation is so easy, i won’t even make a screenshot of it, no selections at all, just next, finish and done. But as soon as the installation has finished the “failed to create object McActiveDir.ActiveDirectory” errors have disappeared. And pretty soon after the health explorer for a domain controller looks like this instead of some warnings we had before:

image

So now all we have to do is install the OOMADS.msi on all domain controllers. However, we don’t like manual installs and want to script the helper object installation in our scripted agent install.

We can find some some setting to determine whether a server is a domain controller or not, but we’d prefer the same setting as SCOM would use to determine whether a server is a domain controller. So we started looking in the mp’s and AD discoveries for such a setting. Soon we found a script called ADLocalDiscoveryDC.vbs which has the following description (including the typo’s :)):

‘*************************************************************************
‘ Script Name – AD Local Discovery DC

‘ Purpose     – Discovers weather a local server is DC or not
‘              
‘ Parameters  – Targer fqdn, netbiosname

‘ (c) Copyright 2003, Microsoft Corporation, All Rights Reserved
‘ Proprietary and confidential to Microsoft Corporation             
‘*************************************************************************

So this must be how a DC is discovered, but it isn’t. If you look more closer, it’s actually targeted at domain controllers. This discovers a lot of roles of a DC, but it does not discover if a computer is a domain controller.

However, this script is still useful. Because it does install the helper object on a domain controller provided OOMADS.msi is located in scomagentinstallpath\HelperObjects (there are some more checks before OOMADS.msi will be installed, if you are interested just find the function InstallOOMADs() and figure out what it does; this function might be different for each os version). This means we just have to place the correct helper object (x86, amd64, ia64) in this directory and the next time this discovery script runs OOMADS will be installed automatically. As this discovery only runs on domain controllers, you can copy OOMADS.msi to all agent-managed servers, which also prevents manual action whenever a server will be promoted to DC after agent installation.

A bit off topic but we still wondered how SCOM determined whether a server is a DC or not. This discovery takes place in Microsoft.SystemCenter.Internal by a wmi query “SELECT NumberOfProcessors FROM Win32_ComputerSystem WHERE DomainRole > 3”. If this returns something the computer will be marked as a domain controller. Most likely NumberOfProcessors is used as each computer has at least 1, so it will always return something. Similar queries for client (domainrole =< 1) and server (domainrole >1 and < 4) computers are used and also discovered in the internal mp.

To sum things up:

– The AD mp discovers and monitors all domain controllers regardless of having a trust.

– Forest/domain topology is only discovered when there’s a trust between the SCOM forest and other forests. This only affects the health model of AD, not the health of an individual domain controller. In other words, domains/forests without a trust are not monitored, but all domain controllers are.

– To have all tests functional OOMADS.msi must be installed on all domain controllers. By placing the correct version of OOMADS.msi in “scomagentinstallpath\HelperObjects” it will be installed on each domain controller automatically.

Posted in management packs, troubleshooting | 3 Comments »

Setting agent proxying

Posted by MarcKlaver on January 21, 2010

Several management pack (if not all) require you to change the security settings for the agent to allow the agent to act as a proxy:

proxysetting

We are using a slightly modified version of the Operations Manager Support Team blog script, which will enable this setting, based on a class name. We run this script on a daily basis.

But then the question is: How do I know which class I can use.

When an agent does not have the proxy setting enabled (but should) an alert is generated on the management server and looks like this:

image

 Note: We have lowered the severity to warning instead of the default critical.

In the “Alert Description” you can find which management pack wants the proxy setting enabled (Microsoft Windows DFSReplication is this example). When you export this management pack to xml, you can retrieve the required class.

For our production environment we have now enabled agent proxying for these classes:

#——————————————————————————-
# Citrix servers for zone data collection.
#——————————————————————————-
Citrix.PresentationServer.ServerRole

#——————————————————————————-
# Cluster nodes.
#——————————————————————————-
Microsoft.Windows.Cluster.Node
Microsoft.Windows.Cluster.Service

#——————————————————————————-
# DFSReplication service
#——————————————————————————-
Microsoft.Windows.DfsReplication.Service

#——————————————————————————-
# DNS Server 2003
#——————————————————————————-
Microsoft.Windows.DNSServer.2003.Server

#——————————————————————————-
# DNS Server 2008
#——————————————————————————-
Microsoft.Windows.DNSServer.2008.Server

#——————————————————————————-
# Exchange 2003 Servers
#——————————————————————————-
Microsoft.Exchange.ServerRole.2003

#——————————————————————————-
# Exchange 2007 discovery helper.
#——————————————————————————-
Microsoft.Exchange2007.Component.DiscoveryHelper

#——————————————————————————-
# ISA server 2006
#——————————————————————————-
Microsoft.ISAServer.2006.Firewall.ServerRole

#——————————————————————————-
# NLB windows 2008.
#——————————————————————————-
Microsoft.Windows.NetworkLoadBalancing.2008.ServerRole

#——————————————————————————-
# SMS 2003
#——————————————————————————-
Microsoft.SMS.2003.Microsoft_SMS_2003_Providers_Installation
Microsoft.SMS.2003.Microsoft_SMS_2003_Site_Database_Servers_Installation

#——————————————————————————-
# System Center Configuration Manager 2007
#——————————————————————————-
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Providers_Installation
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Primary_Site_Servers_Installation
Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation

Posted in Agent Settings, Management Servers | 6 Comments »