Select the product you need help with
The local credential is audited instead of the remote credential that you enter when you run an application that uses the System.Management namespace to connect to a remote computerArticle ID: 967622 - View products that this article applies to. SYMPTOMSYou have an application that uses the System.Management namespace to connect to a remote computer. You run the application. Then, you enter a credential of the remote computer to evaluate the ConnectionOption parameters. When you check the security event log in the remote computer, you find that a "Failure Audit" event is logged for the local credential. Additionally, a "Success Audit" event is logged for the remote credential.
Note When you use Wbemtest tool to connect to the remote computer, there is no audit log for the local credential. Only the "Success Audit" event for the remote credential exists. CAUSEThis problem occurs because of an issue in Windows Management Instrumentation (WMI) and in the Microsoft .NET Framework schema. WMI returns an IWbemServices pointer to the .NET Framework. The .NET layer then tries to determine whether this object implements the IManagedObject interface. The proxy has not set a security blanket. Then, the proxy calls the local account instead of the ConnectionOption parameters. RESOLUTIONA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have the .NET Framework 2.0 Service Pack 1 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix if no .net instance is in use.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.x86 edition for Windows 2000, Windows XP, and Windows Server 2003Collapse this table
x64 edition for Windows 2000, Windows XP, and Windows Server 2003Collapse this table
Itanium-based edition for Windows 2000, Windows XP, and Windows Server 2003Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about WMI .NET, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn.microsoft.com/en-us/library/ms257340(VS.80).aspx
(http://msdn.microsoft.com/en-us/library/ms257340(VS.80).aspx)
PropertiesArticle ID: 967622 - Last Review: April 28, 2009 - Revision: 1.0
|
Back to the top
