The Windows Registry is a hierarchical “database” that stores information about the operating system and applications on the local computer. The Registry is organized in a tree format and can be viewed using the Registry Editor program, regedit.exe.
Folders seen in the regedit utility represent keys. These folders are displayed in the left side or Navigation area in the Registry Editor window. There are five folders, or predefined keys:
HKEY_CURRENT USER (HKCU)—. Contains the root of configuration information for the currently logged-on user. This information is referred to as a user’s profile.
HKEY_USERS (HKU)—. Contains the root of all user profiles on the computer. The HKEY_CURRENT_USER folder is actually a subkey of HKEY_USERS.
HKEY_LOCAL_MACHINE (HKLM)—. Contains configuration information specific to the computer. This information can be used by any user.
HKEY_CLASSES_ROOT (HKCR)—. A subset of information stored in HKEY_LOCAL_MACHINE. Information stored here ensures the correct program starts when you open a file using the Windows Explorer. It contains the linking between executable programs and the program extension used by data files on the system.
HKEY_CURRENT_CONFIG (HKCC)—. Contains configuration data for the current hardware profile. The HKCCSYSTEM subkey contains a subset of the information (the CurrentControlSet) that is a subkey of HKEY_LOCAL_MACHINESYSTEM.
Every database has physical files stored on disk that hold the data you view using regedit. The physical files used by the Registry are called hives and are loaded by Windows at system startup. The hive files are stored in the %systemroot%system32config folder of your system. Table C.1 shows the relationship between the hive files and their corresponding Registry keys.
As shown in Table C.1, most of the hives are logical subkeys of HKEY_LOCAL_MACHINE. The exception is the Default hive, which is the default user profile.
The hive for the current logged on user profile, HKEY_CURRENT_USER, is the ntuser.dat file stored within %systemdrive%documents and settings<user name>. (The location of this file may vary based on the version of the Windows operating system installed on your system.)
HKEY_LOCAL_MACHINE also has a Hardware subkey. This hardware “hive” is dynamically built at system startup and is not stored on disk.
Other files stored at %systemroot%system32config include
Pristine versions of the five Registry hive files, which have an extension of .SAV. These are never-modified hive files for the corresponding keys, created when Windows was installed on the computer.
A transaction log of changes to the keys and value entries in the hive, with a .LOG extension.
The Windows event log files, with an extension of .EVT. The number of .EVT files on any particular system will vary based on the computer’s role. For example, domain controllers, DNS (Domain Name Server), and FRS (File Replication Service) servers will have additional event logs.
Operations Manager 2007 also maintains an event log, named MOMLog.evt; you will find this file on any system with an installed OpsMgr component.
Additional information about the Registry is available at http://support.microsoft.com/kb/256986 (“Windows registry information for advanced users”). For steps on backing up and restoring the Registry for the different versions of Windows supported by OpsMgr 2007, see the following:
http://support.microsoft.com/kb/322756 (“How to back up, edit, and restore the registry in Windows XP and Windows Vista”) provides information applicable to Windows XP and Vista
http://support.microsoft.com/kb/322755 (“How to back up, edit, and restore the registry in Windows 2000”) includes the steps for Windows 2000
http://support.microsoft.com/kb/326216 (“How to use the backup feature to back up and restore data in Windows Server 2003”) discusses backing up the System State in Windows Server 2003
Incorrectly modifying the Registry may render your system unusable, so you should always make a backup of the Registry or its subkeys prior to making changes—because results may be unpredictable.
Keys used by Operations Manager 2007 are located in quite a few places in both the software and system areas of the Registry. The presence and content of these keys will vary based on the computer’s role. The information we will look at is located in the following areas:
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0
HKLMSoftwareMicrosoftPowerShell
HKLMSystemCurrentControlSetServicesAdtServer
HKLMSoftwareODBCODBC.INIODBC
HKLMSoftwarePoliciesMicrosoftAdtAgentParameters
HKLMSystemCurrentControlSetServicesEventlogOperations Manager
HKLMSystemCurrentControlSetServicesHealthService
HKLMSystemCurrentControlSetServicesMOMConnector
HKLMSystemCurrentControlSetServicesOpsMgr Config Service
HKLMSystemCurrentControlSetServicesOMCFG
HKLMSystemCurrentControlSetServicesOMSDK
HKLMSystemCurrentControlSetServicesOpsMgr SDK Service
HKLMSoftwareMicrosoftSystemCertificates
HKLMSoftwarePoliciesMicrosoftSystemCertificatesOperations Manager
We discuss these Registry keys in the following sections of this appendix. Values and keys are as of the OpsMgr 2007 RTM (Released to Manufacturing) version 6.0.50000.0.
Tip: Values “0” and “1” in the Registry
Unless other indicated, for all Registry values, a setting of “0” designates no (or off) and a setting of “1” is yes.
In Operations Manager 2007, managed computers can be agent-managed or agentless managed. There are no Registry settings for agentless managed systems (on the management server or the agentless system). The Operations Manager database maintains information on agentless monitored systems; this data is stored in the BaseManagedEntity table. Table C.2 lists Registry settings for a managed agent. Remember that OpsMgr Server components are also agents, so you will find these Registry keys on every agent-managed server, including the Root Management Server (RMS).
Table C.2. Settings for a Managed Agent
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Agent Management Groups<ManagementGroup-Name> | AcceptIncomingConnections | REG_DWORD | 0x0 | Indicates if incoming connections are accepted. 0 unless agent is configured as a proxy; otherwise 1. |
IsRootHealthService | REG_DWORD | 0x0 | Indicates if system is RMS. | |
IsSCEAgent | REG_DWORD | 0x0 | Indicates if system is System Center Essentials agent. | |
IsServer | REG_DWORD | 0x0 | Indicates if system is management server. 0 on agent. | |
RequestCompresion | REG_DWORD | 0x1 | Indicates if compression is required. Default=1. | |
RequireAuthentication | REG_DWORD | 0x1 | Indicates if authentication is required. | |
RequireEncryption | REG_DWORD | 0x1 | Indicates if encryption is required. | |
RequireValidation | REG_DWORD | 0x1 | Indicates if validation is required. | |
UseActiveDirectory | REG_DWORD | 0x0 | Indicates if Active Directory is used for agent assignment. Default=0. | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Agent Management Groups<ManagementGroupName> | AuthenticationName | REG_SZ | RMS name | Fully Qualified Domain Name of RMS (example: “hydra.odyssey.com”). |
Parent Health Service | CanEstablishConnectionTo | REG_DWORD | 0x1 | |
MaxSendBytesPerSecond | REG_DWORD | 0xf4240 (1000000) | Upper limit of the number of bytes sent per second (1,000,000 bytes by default from the agent). | |
NetworkName | REG_SZ | RMS name | Fully Qualified Domain Name (example: “hydra.odyssey.com”). | |
NetworktimeoutMilliseconds | REG_DWORD | 0x3a98(15000) | Networking timeout, in milliseconds (15,000). | |
Port | REG_DWORD | 0x165b(5723) | Port used by agent to communicate with management server (5723 by default). | |
RetryAttempts | REG_DWORD | 3 | Number of retry attempts. | |
RetryDelayMs | REG_DWORD | 0x3e8(1000) | Amount of time for retry delay (in milliseconds). | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Registration | Company | REG_SZ | Company name entered when running OMSetup.exe. | |
RegisteredOwner | REG_SZ | Name of registered owner, entered when running OMSetup.exe. | ||
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Setup | AgentVersion | REG_SZ | 6.0.5000.0 | Version of Operations Manager software installed on the agent. OpsMgr 2007 RTM is 6.0.5000.0. |
CurrentVersion | REG_SZ | 6.0.5000.0 | Current installed version. | |
InstallDirectory | REG_SZ | %Program Files%System Center Operations Manager 2007 | Installation directory. | |
InstalledOn | REG_SZ | MM/DD/YY-HH:MM:SS | Date and time of installation (example: 6/27/2007-9:52:46). | |
InstalledOnLocalTimeStamp | REG_SZ | MM/DD/YY-HH:MM:SS | Example: 6/27/2007-9:52:46. | |
Product | REG_SZ | System Center Operations Manager 2007 | Name of product. | |
SKU | REG_SZ | Product SKU (example:“Select”). May be blank on an agent. |
An Operations Manager management group can have multiple management servers, but only one RMS. Table C.3 includes settings for these servers.
Table C.3. Management Server Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Config Service | Config Service State | REG_SZ | %ProgramFiles%System Center Operations Manager 2007Config Service State | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Machine Settings | DefaultSDKServiceMachine | REG_SZ | RMS Name | Fully Qualified Domain Name of system running SDK (example: “hydra.odyssey.com”). |
Channel-CertificateSerial Number | REG_BINARY | Example: 4D 00 00 00 00 00 4E 7E 6D 4D | Certificate information from MOMCertImport. Certificates are used as an alternative to Kerberos for mutual authentication and are found where there is a firewall, workgroup, or untrusted domain with agents you want to monitor. The Channel Certificate Serial Number is in the Registry on any machine that has a certificate. This can include a gateway server, management server, or RMS, as well as the agent if the agent is in a workgroup. To remove a certificate, delete the binary data. | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Registration | Company | REG_SZ | Company name | Company name entered when running OMSetup.exe. |
ProductID | REG_SZ | Product ID | Product key. | |
RegisteredOwner | REG_SZ | Owner Name | Name of registered owner. | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0SDK Service | SDK Service State | REG_SZ | %ProgramFiles%System Center Operations Manager 2007SDK Service State | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Server Management Groups | AcceptIncomingConnections | REG_DWORD | 0x1 | Indicates if incoming connections are accepted. |
<ManagementGroupName> | IsGateway | REG_DWORD | 0x0 | 0x1 for gateway server; otherwise, 0x0. |
IsRootHealthService | REG_DWORD | 0x0 | 0x1 for RMS; 0x0 for management server. | |
IsServer | REG_DWORD | 0x1 | 0x1 indicates a management server (including RMS). | |
Port | REG_DWORD | 0x165b(5723) | Port number used (5723 by default). | |
RequestCompression | REG_DWORD | 0x1 | Indicates if compression is required. | |
RequireAuthentication | REG_DWORD | 0x1 | Indicates if authentication is required. | |
RequireEncryption | REG_DWORD | 0x1 | Indicates if encryption is required. | |
RequireValidation | REG_DWORD | 0x1 | Indicates if validation is required. | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Server Management Groups | AuthenticationName | REG_SZ | RMS name | Fully Qualified Domain Name (example: “hydra.odyssey.com”). |
<Management Group Name>Parent Health Services | CanEstablishConnectionTo | REG_DWORD | 0x1 | |
MaxSendBytesPerSecond | REG_DWORD | 0xf4240(1000000) | Maximum number of bytes sent per second. | |
NetworkName | REG_SZ | RMS name | Fully Qualified Domain Name (example: “hydra.odyssey.com”). | |
NetworktimeoutMilliseconds | REG_DWORD | 0x3a98(15000) | Number of milliseconds for networking timeout. | |
Port | REG_DWORD | 0x165b(5723) | Port used. | |
RetryAttempts | REG_DWORD | 3 | Number of retry attempts. | |
RetryDelayMs | REG_DWORD | 0x3e8(1000) | Amount of time for retry delay (in milliseconds). | |
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Setup | UIVersion | REG_SZ | 6.0.5000.0 | Version of Operations Manager console. (This setting appears on any machine with an installed Operations console.) |
Settings for the SDK service are found on all management servers, although the service is only enabled on the RMS. These settings are listed in Table C.4.
Table C.4. SDK Service Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSystemCurrentControlSetServicesOpsMgr Config ServicePerformance | Counter Names | REG_MULTI_SZ | Dirty State Notifications Failed. Management Pack Requests Failed. | |
Avg. Management Pack Request (sec). | ||||
Avg. Management Pack Request Base. | ||||
Change Notifications Failed. | ||||
Avg. Change Notification (sec). | ||||
Avg. Change Notification Base. | ||||
Number of Requests per Sec. | ||||
Number of Active Requests. | ||||
Number of Queued Requests. | ||||
Avg. Request Queue Length. | ||||
Avg. Request Queue Wait Time (sec). | ||||
Avg. Request Queue Wait Time (sec) Base. | ||||
HKLMSystemCurrentControlSet | Description | REG_SZ | Microsoft Operations Manager SDK service | |
ServicesOMSDK | DisplayName | REG_SZ | OpsMgr SDK Service | |
ImagePath | REG_EXPAND_SZ | “%ProgramFiles%System Center Operations Manager 2007Microsoft.Mom.SDKServiceHost.exe” -start | ||
ObjectName | REG_SZ | ODYSSEYOM_SDK | Credentials used. | |
Start | REG_DWORD | 0x4 | Start type when not on the RMS. | |
Type | REG_DWORD | 0x10 |
Table C.5 lists settings for the Operations Manager Configuration service. These settings are on all management servers.
Table C.5. Settings for the Configuration Service
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSystemCurrentControlSetServicesOpsMgr Config Service | ||||
HKLMSystemCurrentControlSetServicesOMCFG | Description | REG_SZ | Microsoft Operations Manager Configuration service | |
DisplayName | REG_SZ | OpsMgr Config Service | ||
ImagePath | REG_EXPAND_SZ | “%Program Files%System Center Operations Manager 2007Microsoft.Mom.ConfigServiceHost.exe” -start | ||
ObjectName | REG_SZ | Example: ODYSSEYOM_SDK | Credentials used. | |
Start | REG_DWORD | 0x4 | Start type when not on the RMS. | |
Type | REG_DWORD | 0x10 |
There are no Registry settings specific to the Operations Database Server itself. Each management server has a Registry entry pointing to the database server, at HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0SetupDatabaseServerName. If you move the operational database to another server, you will need to modify this value on each management server.
The Data Warehouse server is also known as the Reporting Data Warehouse server. This server, which runs SQL Server 2005, contains the Data Warehouse database, with a default name of OperationsManagerDW. Table C.6 lists Registry settings that are unique for this OpsMgr server component.
Table C.6. Data Warehouse Server Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Reporting | DWDBInstance | REG_SZ | Name of database server running Data Warehouse database | Example: Quicksilver. |
DWDBName | REG_SZ | Name of Data Warehouse database | Example: OperationsManagerDW (default). | |
DWDBVersion | REG_SZ | Version | 6.0.5000.0 for RTM version. |
The Report Server Component is part of the SQL Server 2005 Reporting Services installation, and it is customized during Operations Manager setup. Operations Manager 2007 requires its own report server because it changes the security settings. This server component contains the ReportServer and ReportServerTempDB databases. Table C.7 lists Registry settings unique to this server.
Table C.7. Report Server Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwareMicrosoftMicrosoft Operations Manager3.0Reporting | DefaultSDKServiceMachine | REG_SZ | Location of RMS, which runs the SDK service | Example: Hydra. |
ReportingServerUrl | REG_SZ | URL and port for Reporting server | Example: http://Quicksilver:80/ReportServer. | |
ReportRootFolderName | REG_SZ | Subfolder under ReportingSerUrl that is used as the Report Root folder | / | |
SRSInstance | REG_SZ | Name of database server running SQL Reporting Services | Example: Quicksilver. | |
Using86SQLOnx64 | REG_SZ | Whether SQL Server is running 32 bit on a 64-bit machine |
Table C.8 shows the Registry settings for machines with PowerShell installed.
Table C.8. PowerShell Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwareMicrosoftPowerShell1PowerShellSnapInsMicrosoft.EnterpriseManagement.OperationsManager.Client | ApplicationBase | REG_SZ | %ProgramFiles%System Center Operations Manager 2007 | Example: C:Program FilesSystem Center Operations Manager 2007. |
AssemblyName | REG_SZ | Name of assembly | Example: Microsoft.EnterpriseManagement.OperationsManager.ClientShell, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. | |
ModuleName | REG_SZ | %Program Files%System Center Operations Manager 2007Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll | Example: C:Program FilesSystem Center Operations Manager 2007Microsoft.EnterpriseManagement.OperationsManager.ClientShell.dll. | |
PowerShellVersion | REG_SZ | 1.0 | Version of PowerShell installed. | |
Types | REG_SZ | %ProgramFiles%System Center Operations Manager 2007Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xml | Location of Program type Example: C:Program FilesSystem Center Operations Manager 2007Microsoft.EnterpriseManagement.OperationsManager.ClientShell.Types.ps1xml. | |
Vendor | REG_SZ | Microsoft Corporation | ||
Version | REG_SZ | 6.0.4900.0 | Version of PowerShell SnapIn installed. | |
HKLMSoftwareMicrosoftPowerShell1ShellIdsMicrosoft. | ExecutionPolicy | REG_SZ | RemoteSigned | |
PowerShell | Path | REG_SZ | %SystemRoot%system32WindowsPowerShellv1.0powershell.exe | Path to PowerShell executable. Example: C:WINDOWSsystem32WindowsPowerShellv1.0powershell.exe. |
Table C.9 includes the parameters stored in the Registry for the ACS server, including the size of the ACS collector queue. Table C.10 lists the Registry settings for the ACS forwarder.
Table C.9. Audit Collection Services—Server
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSystemCurrentControlSetServicesAdtServer | DependOnService | REG_MULTI_SZ | Eventlog | |
Description | REG_SZ | Service for receiving audit events over the network and writing them to a database | ||
DisplayName | REG_SZ | Operations Manager Audit Collection Service | ||
ErrorControl | REG_DWORD | 0x1 | If the driver fails, produce a warning but let startup continue. | |
ImagePath | REG_EXPAND_SZ | %SystemRoot%system32SecurityAdtServerAdtServer.exe | Location of executable. Example: C:WINDOWSsystem32SecurityAdtServerAdtServer.exe | |
ObjectName | REG_SZ | Credentials service is using | NT AUTHORITYNetworkService. | |
Start | REG_DWORD | 0x2 | When in the boot sequence, the service should start. x2 indicates Autoload, meaning the service is always loaded and run. | |
Type | REG_SZ | 0x10 | Defines the kind of service or driver. x10 indicates a Win32 service that should be run as a standalone process. | |
HKLMSystemCurrentControlSetServicesAdtServerParameters | AdtAgentPort | REG_DWORD | 0xcac5 (51909) | Port used by AdtAgent. |
BackOffThreshold | REG_DWORD | 0x4b | The percentage full the ACS collector queue can become before it denies new connections from the ACS forwarders. | |
ConfigFile | REG_SZ | %SystemRoot%system32SecurityAdtServerAcsConfig.xml | Configuration file. Example: C:WINDOWSsystem32SecurityAdtServerAcsConfig.xml. | |
DBQueueQuery | REG_SZ | SELECT * FROM AdtsEvent | ||
DefaultAssetValue | REG_DWORD | 0xffffffff | ||
DefaultGroup | REG_SZ | Default | ||
DisconnectThreshold | REG_DWORD | 0x5a | The percentage full the ACS collector queue becomes before the ACS collector begins disconnecting ACS forwarders (90% is the default). | |
EventRetentionPeriod | REG_DWORD | 0x150 | Retention period (336 days by default). | |
EventSchema | REG_DWORD | %SystemRoot%system32SecurityAdtServerEventSchema.xml | Location of Event Schema XML file. | |
MaximumQueueLength | REG_DWORD | 0x40000 | The maximum number of events that can queue in memory while waiting for the database (262144 by default). | |
ODBCConnection | REG_SZ | OpsMgrAC | Name of ODBC connection for Audit Collector database. | |
ScriptFilePath | REG_SZ | %SystemRoot%System32SecurityAdtServer | Path to ACS script files. | |
HKLMSoftwareODBCODBC.INIODBC Data Sources | OpsMgrAC | REG_SZ | SQL Server | Type of ODBC data source used for Audit Collection database. |
HKLMSoftwareODBCODBC.INIOpsMgrAC | Database | REG_SZ | OperationsManagerAC | Name of Audit Collection database, used with ODBC. |
Description | REG_SZ | Audit Collection Services | Database description for ODBC. | |
Driver | REG_SZ | %SystemRoot%/System32SQLSRV32.dll | Location of ODBC driver. | |
Server | REG_SZ | Example: Fireball | NetBIOS name of ACS database server. | |
Trusted_Connection | REG_SZ | Yes | Indicates if a trusted connection is used. |
Table C.10. Audit Collection Services—Forwarder
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSoftwarePoliciesMicrosoftAdtAgentParameters | AdtServers | REG_MULTI_SZ | Example: hurricane.odyssey.com | List of collectors that the forwarder should attempt to connect to. Format: <collector fqdn>[:<port>[,<priority>[,<asset value>]]] |
EventLogLoggingLevel | REG_DWORD | 0 | The level of logging that the forwarder performs when logging events to the Application log. | |
0=errors | ||||
1=warnings+errors | ||||
2=informational+warnings+errors | ||||
Instance | REG_SZ | _adtserver.instancename._tcp.sitename._sites.<domain> | If present, allows the forwarder to be associated with a named deployment instance when an organization deploys multiple instances of ACS. Instance name is used to query for SRV resource records. | |
LocalConfig | REG_DWORD | x01 | If present and value is not 0, the forwarder does not use SRV resource records for locating collectors. | |
NoCache | REG_DWORD | x01 | If present and value is not 0, the forwarder does not cache the last connector it used. Also does not use cache to preferentially connect to the collector. |
There are no ACS-specific Registry settings for the server hosting the ACS database (unless it is on the ACS server (collector) itself); the ODBC settings on the ACS server identify the database server and the name of the database.
Every monitored system has an Operations Manager Event log. Table C.11 documents the related Registry settings.
Table C.11. Operations Manager Event Log
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSystemCurrentControlSetServicesEventlogOperations Manager | AutoBackupLogFiles | REG_DWORD | 0x0 | |
File | REG_SZ | %SystemRoot%system32ConfigMOMLog.evt | Name of OpsMgr Event log. | |
MaxSize | REG_DWORD | 15728640 | ||
RestrictGuestAccess | REG_DWORD | 0x1 | ||
Retention | REG_DWORD | 0x0 | ||
Sources | REG_MULTI_SZ | OpsMgr SDK Service OpsMgr SDK Client OpsMgr Root Connector OpsMgr Connector OpsMgr Config Service HealthService Health Service Script Health Service Modules Health Service ESE Store DataAccessLayer Operations Manager | Sources that write to the OpsMgr Event log. Each of these sources has a subkey located under HKLMSystemCurrentControlSetServicesEventlogOperations Manager with information specific to that data source. This includes the specific DLL(s) for the EventMessageFile. |
Settings for the Health Service are found on all systems other than those that are agentless monitored. We list the settings in Table C.12.
Table C.12. Health Service Settings
Key Name | Name | Type | Data | Description |
|---|---|---|---|---|
HKLMSystemCurrentControlSetServicesHealthService | DependOnGroup | REG_MULTI_SZ | Groups depended on. | |
DependOnService | REG_MULTI_SZ | rpcss | Service depended on to be able to start. | |
Description | REG_SZ | Monitors health of the computer. The service may be configured to monitor the health of other computers in addition to this computer. If this service is stopped, detection of failures may not occur. If this service is disabled, any services that explicitly depend on it will fail to start. | Text describing the service. | |
DisplayName | REG_SZ | OpsMgr Health Service | ||
ErrorControl | REG_DWORD | 0x0 | ||
ImagePath | REG_EXPAND_SZ | “%ProgramFiles%System Center Operations Manager 2007HealthService.exe” | Location of executable. Example: “C:Program FilesSystem Center Operations Manager 2007HealthService.exe” | |
ObjectName | REG_SZ | LocalSystem | Credentials used. | |
Start | REG_DWORD | 0x2 | Service Start type (x2 indicates autoload) | |
Type | REG_DWORD | 0x20 | Defines the kind of service or driver. x20 indicates a Win32 service that can share address space with other services of the same type. | |
HKLMSystemCurrentControlSetServicesHealthServiceParameters | Error Reports Enabled | REG_DWORD | 0x1 | |
ManagedEnginePath | REG_SZ | %ProgramFiles%System Center Operations Manager 2007HealthServiceManaged.dll | ||
Persistence Cache Maximum | REG_DWORD | Management Server:0x6400 Agent:0x1900 | Maximum cache size. Management Server:25600 decimal Agent:6400 | |
Persistence Checkpoint Depth Maximum | REG_DWORD | Management Server:0x1400000 Agent:0xa00000 | Management Server:20971520 decimal Agent:10485760 decimal | |
Persistence Initial Database Page Count | REG_DWORD | Management Server:0x9600 Agent:0x3200 | Management Server:38400 decimal Agent:12800 | |
Persistence Maximum Sessions | REG_DWORD | Management Server:0x20 Agent:0x10 | Management Server:32 decimal Agent:16 decimal | |
Persistence Page Hint Cache Size | RE_DWORD | Management Server:0x40000 Agent:0x8000 | Management Server:262144 decimal Agent:32768 decimal | |
Persistence Version Store Maximum | REG_DWORD | Management Server:0x1400 Agent:0x789 | Management Server:5120 decimal Agent:1920 decimal | |
Queue Error Reports | REG_DWORD | 0x0 | 0 or 1 | |
Service Sizing | REG_DWORD | 0x1 | 0 or 1 | |
State Directory | REG_SZ | %ProgramFiles%System Center Operations Manager 2007Health Service State | ||
UseBackgroud Priority | REG_DWORD | 0x0 | ||
HKLMSystemCurrentControlSetServicesHealthServiceParametersConnectorManagerApproved AD Management groups | No values by default. | |||
HKLMSystemCurrentControlSetServicesHealthServiceParametersManagement Groups<ManagementGroupName> | IsSourcedfromAD | REG_DWORD | 0x1 | If value is 1, indicates the agent is AD-integrated and gathers settings from the Service Connection Point. This is only present if the agent is AD-integrated. |
MaximumQueueSizeKb | REG_DWORD | 0x19000 | 102400 decimal. Agent maximum queue size. | |
HKLMSystemCurrentControlSetServicesHealthServiceParametersManagement Groups<ManagementGroupName>AllowedSSIDs | RestrictSSIDs | REG_DWORD | 0x0 | |
HKLMSystemCurrentControlSetServicesHealthServiceParametersSecureStorageManager | (Default) | REG_BINARY | Private/private key pair |
Settings associated with the MOM Connector can be found at HKLMSystemCurrentControlSetServicesMOMConnectorPerformanceLibrary. This is string data (REG_SZ) describing the location of the Connector Performance Library. The data found at this key is %ProgramFiles%System Center Operations Manager 2007MOMConnectorPerformance.dll.
Operations console settings for the current logged-on user are listed in Table C.13.
Table C.13. Settings for the Current Logged-on User
Name | Type | Data | Description | |
|---|---|---|---|---|
HKCUSoftwareMicrosoftMicrosoft Operations Manager3.0Console | Various | Operations console settings that only affect the console for that user on that computer include the following: Connection history with the names of management groups the console has connected to. Show or Hide Views selections. Whether the console is in a window or full screen (if in a window, the size and position of the window). The last navigation pane the console was open to when it was closed. | ||
HKCUSoftwareMicrosoftMicrosoft Operations Manager3.0Console CacheParameters | PollingInterval | REG_DWORD | 1 | Controls how often the Operations console polls. The default value (normal interval) is 1. 0 turns off polling. 2 doubles the interval, meaning polling occurs half as often. Maximum value is 10; any number larger is treated as 10. Add this key to the Registry to lessen polling occurrence. |
HKCUSoftwareMicrosoftMicrosoft Operations Manager3.0User Settings | SDKServiceMachine | REG_SZ | RMS name | Fully Qualified Domain name of RMS (example: hydra.odyssey.com). |
Tip: Lost in Service Pack (SP) 1
In the RTM version of OpsMgr, you could right-click an alert and choose associated tasks from the context menu. This disappeared with SP 1, although the capability is still available on the Actions pane of the Operations console.
Microsoft removed this functionality to improve interactive responsiveness of the context menu. You can turn it back on if you want via a Registry entry—set EnableContextMenuTasks to 1 under HKCUSoftwareMicrosoftMicrosoft Operations Manager3.0Console. If this key does not already exist, create it with type REG_SZ. Because this is under HKCU, you would want to script this change for all users.
This information is current as of Release Candidate (RC) 0.