I bet you got a agent in a “gray” state sometime. Now there is a very detailed KB that describe what can be the reason. This is useful for both SCE and SCOM admins
Last week Microsoft released the update 954049 that adds support to run/install System Center Operations Manager 2007 and System Center Essentials 2007 components on a Windows Server 2008 system.
More information about this update
Download the 954049 update from Microsoft
Dustin from the SCE team just posted a blog about two issues that can affect your SCE server (since SCE uses WSUS), have a look at the post and make sure you install the KB954960 hotfix on your SCE server.
KB941409 – The Discovery Wizard may stop responding during the discovery process in Microsoft System Center Operations Manager 2007
http://support.microsoft.com/kb/941409/en-us
KB938991 – The SQL Server 2000 database engine health is not monitored in System Center Operations Manager 2007
http://support.microsoft.com/kb/938991
KB937470 – A notification subscription’s Alert Criteria options do not work as expected in System Center Operations Manager 2007
http://support.microsoft.com/kb/937470/en-us
Have you tried to install SCE without success, try again! Microsoft has now released a ”Rollup QFE” that update original installation files with new files that includes fixes for three issues:
Note that this rollup can only be used if you do a new installation, you can’t use it if you already installed SCE.
Download the rollup package from Microsoft download site or download the 90-day evaluation that includes the rollup package
Update 2007-10-01 – On the download page for the rollup, it only state that the fix includes two fixes (936339 and 936481). This is incorrect and it will be updated
As you know, SCE has the function to import updates from third partners. As I wrote in one of my post, this function was not working in SCE RTM. Last week Microsoft released a new QFE (937467) that fixes this problem, but I would recommend you to wait a while since I found some problem after you imported HP catalog (not that this could also happen when importing from other vendors).
Problem 1
After importing the HP catalog, I got an update notification on one of my Vista machines. The notification informed me that two HP updates were needed (HP ProtectTools Security Manager, MSRC Number 2.00.D3 and HP Java Card Security for ProtectTools, MSRC Number 1.00.B4). When I tried to install them, both updates failed and the reason were ”operating system not supported”. I have reported this to HP and they will fix it in the next catalog.
Workaround
1. Wait for the updated version of the catalog (I think it is released ones per month)
2. Decline the updates that are failing.
Problem 2
The day after I installed the HP catalog, I saw that my clients failed to receive updates. When I looked in the windowsupdate.log on the client I saw a lot of 0×8024400D errors. With some help from the product team, we found that the issue is related to the HP catalog.
Workaround
1. Don’t import the HP catalog
2. Wait for a fix from Microsoft or HP (the product team is working on a solution)
3. If you already imported the HP catalog, decline some of the content which was imported from the HP catalog. Delete in batches of ten until the clients are able to successfully detect.
The QFE is not available from support.microsoft.com site but you can order it from the following link
Microsoft has now released a QFE (KB936339) that will fix the Network Topology diagram view in SCE. There has been two symptoms for this issue:
1) After discovering network routers in Essentials 2007, the Network Topology diagram view in the Monitoring space will be populated with subnet groups that contain network devices, but no Windows-based computers (se picture below).
2) If you looked in the Evenlog (Operations Manager) on your SCE server, you see the error 4509:
Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 4509
Date: 2007-07-12
Time: 12:46:24
User: N/A
Computer: TestSCEsrv
Description:
The constructor for the managed module type ”Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.GroupCalculationModule” threw an exception. This module was running in rule ”Microsoft.SystemCenter.WindowsComputer.IPSubnet.PopulateGroup” running for instance ”127.0.0.0″ with id:”{A1BD10CC-9996-26E1-65A0-8215A58F5B2B}” in management group ”TestSCE_MG”. The exception text is: Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.InvalidDatabaseQueryModuleConfigurationException: RelationshipTypeId = 6068f699-56a0-8ce1-f625-701a148a219b
at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipSubscription.ValidateRelationshipType(Guid relationshipTypeId, Guid sourceManagedTypeId, Guid targetManagedTypeId)
at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.MembershipSubscription.Create(IXPathNavigable configurationXml, RelationshipQueryResultMethod relationshipQueryResultMethod, NotifyFatalErrorMethod notifyFatalErrorMethod)
at Microsoft.EnterpriseManagement.Mom.DatabaseQueryModules.GroupCalculationModule..ctor(ModuleHost`1 moduleHost, XmlReader configuration, Byte[] previousState)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
After installing the QFE, the view will include both Windows -based computers and networking devices (see picture below).
The KB article is KB936339. Note that you will need to call CCS to receive the QFE (but they won’t charge for it)
There has been a lot of question about what version Opsmgr 2007 support and for RTM it was only SNMP V2c, but now they have released a QFE that will add support for SNMP v1.
How to Add a SNMP devices (both versions)
1)From the Administration space in the Console, Start the Discovery Wizard
2)On the Auto or Automatic dialog box, Select Advanced discovery
3)In the drop menu, select Network device and click Next
4)On the Discovery Method dialog box, add the IP-range you want to scan in and the SNMP community string. Note that after installing the QFE, you will have a drop menu where you can chose to scan for SNMP v1 or v2
The KB article is KB939364. Note that you will need to call CCS to receive the QFE (but they won’t charge for it)
Important to note that this QFE is only for Opsmgr 2007, there will be another for SCE!
There is a known issue when you try to install SCE or Opsmgr 2007 Reporting in an environment where the Netbios name is not the same as the Active Directory DNS name (FQDN) for example:
Netbios name:contoso
AD DNS name (FQDN):contosodomain.local
In the SCE scenario, this will happen in the last step of the setup when it starts to install the reporting part. Since it will fail, all other part will ”roll-back” and the installation will fail.
In the Opsmgr scenario, this will occur when you try to install the reporting ”add-on”. Since this is a standalone component in Opsmgr, the only thing that will ”rollback” is reporting and you can still use the Opsmgr console.
To verify this issue, look in the reporting log file (SCEReportingX.log) located under C:\Documents and Settings\username\Local Settings\Temp. In the log file, you should find the following error:
Property(S): UnableToGetUserNameFromManagementServerActionAccount = SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.
Property(S): UnableToGetUserNameFromManagementServerSDKAccount = SetPropertiesToManagementServerActionAndSDKAccountCA error: Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException : The specified domain does not exist or cannot be contacted.
Another way to verify this issue is to start a network monitoring trace from the SCE/Opsmgr reporting server. During the installation, you will see that the setup is trying to contact the domain with the AD DNS name, but without the suffix. In my example above, you would see the installation trying to contact the domain contosodomain!
I know that the team is working on a hotfix and I hope it will be release this week! Update – The KB article is KB937831.Note that you will need to call CCS to receive the QFE (but they won’t charge for it)
http://support.microsoft.com/kb/937831