A script that was embedded by an authenticated MOM 2005 user in an alert object's alert history field is executed unexpectedly on the MOM 2005 SP1 Web console

When you use the Microsoft Operations Manager (MOM) 2005 Service Pack 1 (SP1) Web console, a script that was embedded by an authenticated MOM user in an alert object may be executed unexpectedly from the Web browser.

Note Scripts can be embedded only by an authenticated user who is a member of MOM user groups that have rights to access and to update alerts. For example, scripts can be embedded by MOM users.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Microsoft Operations Manager 2005 Service Pack 1 (SP1) installed. This hotfix must be applied to each computer that hosts a Microsoft Operations Manager 2005 Management Server Web console.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.To apply this hotfix, follow these steps:

1. Copy the MOM2005-SP1-KB969286-X86-ENU.msi file either to a local folder or to an available network shared folder.
2. Run the MOM2005-SP1-KB969286-X86-ENU.msi file locally on each applicable computer that meets the noted criteria.

Note You can run the MOM2005-SP1-KB969286-X86-ENU.msi file from either Windows Explorer or at a command prompt. The MOM Service will be restarted while the hotfix is being applied.

To apply a hotfix for the MOM Agent component, follow these steps:

• Use the MOM Administrator console to apply the hotfix to MOM agents by using a setting of Control Level = Full. A list of agents that can be automatically updated is shown in the MOM Administrator console in the following specific location:
  MOM/Administration/Computers/Pending Actions
• Manually apply the hotfix on each MOM agent by using a setting of Control Level = None. These agents, if any, are listed in MOM Administrator console in the following specific location:
  MOM/Administration/Computers/Agent-managed Computers
• For agents that are manually installed by using a setting of Control Level = Full after the hotfix was applied to the MOM server, you can either manually update the agent or follow these steps to have the MOM server perform the update:
  1. Make sure that the manual installation is approved through the Administrator Console Pending Actions folder.
  2. In the Agent-managed Computers folder, right-click the agent, and then run the Update Agent Settings task.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: