Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Windows Server 2008 R2 Management > Windows 2008 R2 WMI problem
Ask a questionAsk a question
Search Forums:
 

AnswerWindows 2008 R2 WMI problem

  • Tuesday, October 20, 2009 12:49 PMAlexey Tulia Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello.
    I have a starnge problem with WMI on new Windows 2008 server R2 x84. So, let's drive in :

    For remote WMI access i use j-interop Java library, that works fine with all prevous version of Windows 2008 Server in default installation and configuration (i always use administrator credentials).
    In my code i create WbemScripting.SWbemLocator object and after that query needed COM interface, f.e. ISWbemLocator. Next i make WMI queries to WMI classes.
    In new Windows 2008 Server R2 x64 i  get this error: "Access is denied, please check whether the [domain-username-password] are correct. Also, if not already done please check the GETTING STARTED and FAQ sections in readme.htm. They provide information on how to correctly configure the Windows machine for DCOM access, so as to avoid such exceptions."
    I try to connect with administrator credentials on target system. Firewall is disabled. All WMI services are running. Whatever i did, the problem is not solved. Also  Anybody can help me?..
     

Answers

All Replies

  • Wednesday, October 21, 2009 9:45 AMJoachim NässlanderMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    You need to configure DCOM to allow remote/anonymous connections.

    A guide to where to configure DCOM: http://technet.microsoft.com/en-us/library/cc771387.aspx

    Best regards

    Joachim Nässlander
    IT-Expert, Knowledge Factory
    (http://www.knowledgefactory.se)

    MVP Cluster
    Member of Microsoft Extended Experts Team (MEET)
    Blog: http://www.nullsession.com
     
  • Wednesday, October 21, 2009 2:53 PMAlexey Tulia Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    On my server this option was enabled by default. All this days i continue investigation process with this issue and i want to post my results here:

    When j-interop library connecting  to WbemScripting.SWbemLocator object on target server, it try to create a surrogate dll. To perform this action j-interop library try to read a key from windows registry and at this step everything falls... Access denied error was occured.  But I can successfully connect to InternetExplorer.Application object remotely. In the security audit logs i see that log on was successful. That means, that i got the Administrator rights. But i still can not get REMOTE access to WbemScripting.SWbemLocator object.
    I will be very grateful, if anyone explain me, how to configure Windows 2008 R2/Windows 7 security policy to get access remotely to WbemScripting.SWbemLocator object with Administrator credentials. I asked Google many times and found the similar posts with same problem. But there is no solution yet... i think, the problem exist in the user's authorization, probably new Windows version use new authorization model or other security policy by default.
     
  • Friday, October 23, 2009 10:47 PMMarco ShawMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    You may want to consider using PowerShell to test the remote WMI connection?  That may help identify some problem with your app or it may also have the same access denied error...
     
  • Monday, October 26, 2009 9:03 AMAlexey Tulia Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    With powerShell all seems to be ok. i used VBScipt and it's ok too. I think, may be in new 2008 R2 (and probably Windows 7 ) something was changed with MS RPC protocol or quite possible with remote authentication for DCOM.  
     
  • Monday, October 26, 2009 9:05 AMAlexey Tulia Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    With powerShell all seems to be ok. i used VBScipt and it's ok too. I think, may be in new 2008 R2 (and probably Windows 7 ) something was changed with MS RPC protocol or quite possible with remote authentication for DCOM.  

    As far as i know, j-interop uses native MS RPC calls to interact with DCOM server and make authentication.
     
  • Monday, October 26, 2009 4:50 PMKarl Mitschke Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Alexey;

    I'd post your question on the j-Interop - DCOM Configuration forum:

    http://sourceforge.net/projects/j-interop/forums/forum/840678

    Karl