Re: User rigths for WMI access
- From: "Scott McNairy \(MVP\)" <v-scomcn@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Apr 2005 10:29:48 -0700
Your user account should only require "Remote Enable" and "Enable Account"
security settings on the namespace to be able to read data, you can verify
these settings in winmgmt.msc.
Can you post the section of code where you do the connection to the
root\cimv2 namespace? Sometimes a common error that causes this problem is
specifying the user name without the domain\user format or the computer\user
format, sometimes users just specify the "user" and this error can result.
--
Scott McNairy
Microsoft MVP - Windows Server Management Infrastructure
"tango" <tango@xxxxxxxxxxxxxxxx> wrote in message
news:425CCF9B.8000207@xxxxxxxxxxxxxxxxxxx
> Scott McNairy (MVP) wrote:
>> See this link, however to help further a WMI class name would be helpful
>> and any relevant source code you can provide as well. Often times these
>> issues are client permissions related, so even if a client has access to
>> a namespace additional permissions may be required, having the class name
>> that the user is having trouble with will help us narrow it down.
>>
>> http://www.microsoft.com/technet/scriptcenter/resources/wmifaq.mspx#EFAA
>>
>> Thanks
>>
>
> Thank you for your answer, we have checked the link you gave us in your
> response, and we are now sure we have already correctly configured
> namespace permissions.
>
> Our application performs querys to operating system classes (such as
> win32_process, win32_service, win32_operatingsystem, win32_computersystem,
> and some more) and performance classes (such as
> win32_perfrawdata_perfos_processor, win32_perfrawdata_perfos_memory,
> win32_perfrawdata_perfproc_process), all in root/cimv2 namespace.
>
> We know a "local administrator" user can perform these queries, but we
> don't like to use administator due to security risks. We have searched in
> internet and we have not found any information that permits us to create a
> harmless user with enough permissions to perform these queries.
>
> Anytime we have detected an "Access denied" error with our application we
> have tried the same WMI query using wbemtest.exe and both applications
> have the same behabiour (access denied), so we understand there is not a
> problem with our application but a problem with user rights.
>
> Thanks
.
- Follow-Ups:
- Re: User rigths for WMI access
- From: tango
- Re: User rigths for WMI access
- References:
- User rigths for WMI access
- From: tango
- Re: User rigths for WMI access
- From: Scott McNairy \(MVP\)
- Re: User rigths for WMI access
- From: tango
- User rigths for WMI access
- Prev by Date: Re: User rigths for WMI access
- Next by Date: Re: Search for files
- Previous by thread: Re: User rigths for WMI access
- Next by thread: Re: User rigths for WMI access
- Index(es):
Relevant Pages
|