211) 2/3/2012 885720 Alerts are not forwarded after you install a product connector from the MOM 2000 Resource Kit in Microsoft Operations Manager 2005
(885720) - Describes a problem that you may experience after you install a product connector from the MOM 2000 Resource Kit. Explains how to modify the registry to resolve this problem. 212) 2/3/2012 885736 'Incorrect Function - Result code: 80004005' error when you use the Uninstall Agents Wizard to remove the Microsoft Operations Manager 2005 agent
(885736) - Describes a problem that occurs in MOM 2005 when you install the MOM 2005 agent on a computer that has the MOM 2005 Administrator Console installed. When you try to remove the MOM 2005 agent, an error occurs. 213) 2/9/2012 883342 How the MOM 2005 internal monitoring feature uses event rules to monitor Windows service availability on computers that are running the MOM 2005 agent
(883342) - Describes how the MOM 2005 internal monitoring feature uses event rules to monitor Windows service availability on computers that are running the MOM 2005 agent. Discusses how to specify additional criteria to add more information to the event rule. 214) 2/3/2012 883347 The MOM agent or the MOM server does not start, and event 9029 is logged in Microsoft Operations Manager 2005
(883347) - Describes a problem that may occur when you try to use MOM 2005 on a domain controller. To resolve the problem, you may have to grant additional permissions to the action account. 215) 2/5/2012 883326 You receive a "Microsoft SQL Server Reporting Services is not installed" error message when you try to install Microsoft Operations Manager (MOM) Reporting in MOM 2005
(883326) - Describes an error message that you receive in the MOM 2005 Setup program when you try to install Microsoft Operations Manager (MOM) Reporting. 216) 2/7/2012 885719 The MOM service may not restart when a computer discovery task runs in Microsoft Operations Manager 2005
(885719) - Describes a problem that may occur if you do not use Active Directory in your network environment. Explains how to resolve this problem by creating a new registry key to increase the time-out value of the MOM service. 217) 2/2/2012 885724 Many false heartbeat alerts are generated by Microsoft Operations Manager 2005 servers
(885724) - Describes a problem where many heartbeat alerts appear in the Microsoft Operations Manager (MOM) 2005 Operator console. To resolve this problem, you must synchronize the time settings between the MOM server computer and the MOM database computer. 218) 1/26/2012 883348 Cannot use the push installation method to install the Microsoft Operations Manager 2005 agent on domain controllers in untrusted domains
(883348) - Describes a problem with the push installation method in MOM 2005. Problem prevents the installation of the MOM 2005 agent on domain controllers in untrusted domains. 219) 2/9/2012 883925 The W3wp.exe process causes 100% CPU utilization on Management Servers in MOM 2005
(883925) - Provides a fix for a problem where the W3wp.exe process causes 100% CPU utilization on a MOM 2005 Management Server and an error message is generated. 220) 1/27/2012 883329 "An error occurred on line while executing script " error message when you run a script in Microsoft Operations Manager 2005
(883329) - Describes a problem that may occur after you import a Management Pack from MOM 2000 SP1 that includes a script. When you run the script on a MOM 2005 server, an error occurs. 221) 2/5/2012 883336 You receive an Event ID 25109 "Class not registered" event in the application event log when computer discovery runs in Microsoft Operations Manager 2005
(883336) - Describes an event that may be logged in the application event log after you install Microsoft Operations Manager (MOM) 2005. To resolve this problem, apply the Internet Explorer cumulative security patch MS03-048. 222) 2/5/2012 885734 "Failed to create MOM database" error when you try to install MOM 2005 on a computer that has been upgraded to Windows Server 2003
(885734) - Describes a problem that may occur when you try to install MOM 2005 on a computer that has been upgraded to Windows Server 2003. You may receive the "Database setup fails with Error Code -2147221164 (Class not registered)" error. 223) 2/6/2012 883335 Event IDs 21249 and 21248 are logged in the application event log on a computer that is running Microsoft Operations Manager
(883335) - Describes a problem that occurs on a computer that is running Microsoft Operations Manager 2000 or Microsoft Operations Manager 2005 where two events with different event IDs that describe the same problem are logged in the application event log. 224) 2/6/2012 883331 Operator Console displays "Unknown" in the Operating System Type column for some devices in Microsoft Operations Manager 2005
(883331) - Describes why the Operator Console may display an Operating System Type of "Unknown" for some devices. This is expected behavior in MOM 2005. 225) 2/6/2012 883341 Microsoft Operations Manager 2005 supports Fully Qualified Domain Names for agent deployment and computer discovery
(883341) - This article describes changes in MOM 2005 name resolution features for the agent deployment and computer discovery.
1
.... 9
10
11
12
13
14
[ 15 ]
16
17
Previous Page
Page 15 of 17
Next Page
|