Error disabling AEM

On one customer site we have been testing AEM and have decided for the moment to disable it. But when tring to disable via Administration > Device Management > Management Servers – right click the Management Server that was used for AEM and chose “Disable Client Monitoring”, I kept getting the following error message:

Message: An object of type ManagementPackOverride with Id 59581fc1-b9f8-462e-7b45-3ab3655d0d6d was not found.
Microsoft.EnterpriseManagement.Common.ObjectNotFoundException: An object of type ManagementPackOverride with Id 59581fc1-b9f8-462e-7b45-3ab3655d0d6d was not found.
at Microsoft.EnterpriseManagement.Configuration.ManagementPackDatabaseReader.GetOverride(ManagementPackElementReference`1 reference)
at Microsoft.EnterpriseManagement.Configuration.ManagementPack.Microsoft.EnterpriseManagement.Configuration.IO.IManagementPackSearch.GetOverride(ManagementPackElementReference`1 reference)
at Microsoft.EnterpriseManagement.Monitoring.ClientMonitoring.ClientMonitoringSettings.ChangeRulesAndMonitors(MonitoringObject aemCrashListenerEntity, Boolean enabled)
at Microsoft.EnterpriseManagement.Monitoring.ClientMonitoring.ClientMonitoringSettings.DisableAem(ManagementServer mgmtServer)
at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.SDKHelper.c__DisplayClass64.b__63(Object sender, ConsoleJobEventArgs e)”

To resolve:

1. Delete “Client Monitoring overrides Management pack” – Go to SCOM Console -> Administration -> Management Packs -> Right click Client Monitoring Overrides Management Pack and choose Delete

2. Import “Client.SystemCenter.ClientMonitoring.Overrides.xml“ file from “C:\Program files\System Center Operation Manager 2007\Microsoft.SystemCenter.ClientMonitoring.Overrides.xml”

We could then disable AEM

ACS Collector (AdtServer) fails to start

This came up on the technet forums a couple of days ago. I’ll give the answer first and then the full error message – I hadn’t personally seen this problem before and it doesn’t look like a permissions problem from the error but the resolution was to

• Check that the ACS database had been created
• And then also check that there was a login for NT Authority\Network Service that is the database owner for the ACS database.

In this case, there was no login to SQL for the service account used by the ACS Collector and this seemed to cause the error. Manually creating the login and asssinging it to be the owner of the OperationsManagerAC database and then reinstalling ACS solved the problem.

Error Messages

While trying to install the Audit Collection Services on the Management Server the installation fails with the following output:
Find Source Folder: Success
Create Target Folder: Success
Install ACS: Success
Create AdtServer Service: Success
Write AdtServer Registry Parameters: Success
Write Password: Success
Register Application Log: Success
Register Performance DLL: Success
Register MOF File: Success
Create Data Source: Success
Create Database: Success
Create Database Tables: Success
Create Database Stored Procedures: Success
Create Database Login: Success
Configure Database Time Format: Success
Start AdtServer Service: Failure (0×00000002)
The service seems to start if I do it manually but immediately stops.
In the Operations Manager event log these events pop up in this order:
Event Type: Information
Event Source: AdtServer
Event Category: None
Event ID: 4609
Date: 9/2/2010
Time: 1:22:55 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: XXXXXXXXXX
Description:
AdtServer is starting up.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: AdtServer
Event Category: None
Event ID: 4660
Date: 9/2/2010
Time: 1:22:55 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: XXXXXXXXXX
Description:
AdtServer encountered the following problem during startup:
Task: Load Certificate
Failure: Certificate for SSL based authentication could not be found. SSL authentication will be disabled
Error: 0×00000002
Error Message:
The system cannot find the file specified.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: AdtServer
Event Category: None
Event ID: 4677
Date: 9/2/2010
Time: 1:22:55 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: XXXXXXXXXX
Description:
AdtServer encountered the following problem during startup:
Task: Open Admin Server
Failure: An error occured during creation of the RPC server for admin connections
Error: 0×00000002
Error Message:
The system cannot find the file specified.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: AdtServer
Event Category: None
Event ID: 4612
Date: 9/2/2010
Time: 1:22:55 PM
User: NT AUTHORITY\NETWORK SERVICE
Computer: XXXXXXXXXX
Description:
AdtServer shutdown complete.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Monitors – overview

Steve Rachui has a great run through of monitors here:

Part I – Unit Monitors

Part II – Aggregate Monitors

Part III – Dependency Monitors

Windows 2003 Stand alone Certificate Server

I found the information that Layne posted here:
http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/7e8dde55-6e55-4109-8da5-85a93fa64ea0 extremely useful when I was onsite the other day. The customer had a windows 2003 stand-alone certificate server and the servers to be monitored had no connectivity to the certificate server.

I found that the standard template that is documented for use with certreq didn’t work. But that the following that Layne gave in his post did the trick.

[Version]
Signature= “$Windows NT$”
[NewRequest]
Subject = “CN=agent.contoso.com,OU=MyOU,O=MyOrg,L=MyCity,S=MyState,C=US”
KeySpec= 1
KeyLength = 1024
KeyUsage = 0xa0
ProviderName = “Microsoft RSA Schannel Cryptographic Provider”
ProviderType = 12
RequestType = PKCS10
Exportable = TRUE
MachineKeySet = TRUE
UseExistingKeySet = FALSE
[EnhancedKeyUsageExtension]
OID = 1.3.6.1.5.5.7.3.1
OID = 1.3.6.1.5.5.7.3.2

Service Manager – Requirements Overview and Base Install

I was onsite last week deploying Service Manager 2010 and after much grumbling and moaning about it during the release candidate and beta releases, I’m actually starting to like it. Yes, it is still a little rough around the edges but what I do like is that rather than throw in lots of functionality that doesn’t work (remember Operations Manager 2007 RTM!), the Service Manager team have cut down on functionality but actually tried to make sure that what is there works and is stable. And I think they’ve done a good job.

I’ll start a few posts on the installation – as usual, the official documentation is really the place to look but I have taken this and tried to extract the key points and add some screen shots.

So, to start this series, the base install:
Part I – Overview of the service accounts and requirements. I can’t guarantee this is the “most” secure deployment but I have ensured that any administrator privileges handed out to service accounts are only ever local on a Service Manager core server.
Part II – Install Service Manager Management Server

Part III – Install Service Manager Data Warehouse Management Server

Operations Manager 2007 Versions numbers

SCOM 2007 RTM: 6.0.5000

SCOM 2007 SP1: 6.0.6278

SCOM 2007 R2 RTM: 6.1.7221

The monitoring of SNMP devices may stop intermittently in System Center Operations Manager or in System Center Essentials

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

Configuring SNMP monitoring with OpsMgr 2007

This comes up on the forums quite often so here are a summary of some of the best articles I’ve found on the net:

Configuring using the GUI:
The System Center Central team have a great series – Part I, Part II, Part III, and Part IV

David Allen has a good walkthrough here about creating SNMP Probe based monitors.

Issues with using the GUI to create monitors with numeric expressions – see Raphael Burri’s blog

Authoring Console:
Kris Bash at Operating Quadrant has some great articles on SNMP monitoring.

Watch your Service Manager service account password

When installing Service Manager 2010 RTM, I kept getting an error at the end of the install – “Finalize: An error occurred while executing a custom action:RollbackCleanup”.

This seems to be a password issue if the Service Manager service account password contains a | symbol.

We removed the | symbol and the install completed fine. This has been replicated on a forum thread.

Some extra reports for OpsMgr 2007 R2

I’m a bit late catching up on these but there were some “new” reports posted on the MOM Team blog which may be of interest. They do require that the OpsMgr Data Warehouse is running on SQL 2008 as they don’t work on SQL 2005.

http://blogs.technet.com/b/momteam/archive/2010/04/29/reporting-scenarios-more-samples.aspx

http://blogs.technet.com/b/momteam/archive/2010/05/10/reporting-scenarios-more-samples-updated-attachment.aspx