Microsoft KB Archive/895195

From BetaArchive Wiki

Article ID: 895195

Article Last Modified on 7/24/2007



APPLIES TO

  • Microsoft Operations Manager (MOM) 2005, when used with:
    • Microsoft Windows Server 2003 Service Pack 1



Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.

SYMPTOMS

When you use the Install Agent Wizard to install a Microsoft Operations Manager (MOM) 2005 agent on an unmanaged computer, you receive the following error message:

The MOM Server could not access registry key or value 'SYSTEM\CurrentControlSet\Control \Session Manager\Environment' on computer unmanaged computer name.

Error code: 5

Error Description: Access is denied.

If you use computer discovery to install an agent, event ID 21034 is logged in the Application log on the computer that is running MOM Management Server. A corresponding alert appears in the MOM 2005 Operator console.

CAUSE

This problem occurs when the following conditions are true:

  • MOM Management Server is installed on a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1).
  • The server's action account does not have administrative credentials on the destination computer.


RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Operations Manager 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

905416 How to obtain the latest Microsoft Operations Manager 2005 service pack


Hotfix information

A supported hotfix is now 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 this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

This hotfix restarts the MOM service on the computer that is running MOM Management Server.

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 tool in Control Panel.

   Date         Time   Version      Size     File name
   ---------------------------------------------------------
   30-Mar-2005  12:49  5.0.2749.18  769,264  Momagentmgr.dll

Installation information

Install this hotfix on every MOM 2005 Management Server computer that is running Windows Server 2003 with SP1. To install this hotfix, run the MOM2005-RTM-KB895195-X86-ENU.exe executable file on the MOM Management Server computer. You can either double-click the file or type the full path of the file at a command prompt. The hotfix restarts the MOM service so that the changes can take effect.

WORKAROUND

Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.To work around this problem, change the action account that is used by the MOM Management Server computer to an account that has administrative credentials on the destination computer. After you change the action account, restart the MOM service on the MOM Management Server computer.

For more information about how to use a low-privileged account, see the "Using a Low-Privileged Account" section of the Microsoft Operations Manager 2005 Security Guide. To obtain this guide, visit the following Microsoft Web site:

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Operations Manager 2005 Service Pack 1.

MORE INFORMATION

For more information about other problems that are resolved by Microsoft Operations Manager 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

905420 List of bugs that are fixed in Microsoft Operations Manager 2005 service packs


For more information about the standard terminology that is used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the Standard Terminology That Is Used to Describe Microsoft Software Updates



Additional query words: MomActionActLowPriv MomActionAct push

Keywords: kbqfe kbhotfixserver atdownload kbgetsp kbbug kbopmaninterop kbopmaninstall kbopmandeploy kbopman2005spfix kbopman2005bug kberrmsg kbsetup kbinterop kbsecurity kbfix KB895195