Win32_QuickFixEngineering access to domain controllers with a restricted user account


i trying grant restricted user account access pull hotfix data domain controllers using win32_quickfixengineering. application called servicenow.

the account using able pull sorts of other wmi information dcs no problem - example logicaldisk , operatingsystem.  pretty sure have dcom permissions setup properly, part.

however, when servicenow tries run win32_quickfixengineering code, no data returned , see 10016 errors show in system event log on dcs:

the application-specific permission settings not grant local activation permission com server application clsid

{752073a1-23f2-4396-85f0-8fdb879ed0ed}

and appid

{752073a2-23f2-4396-85f0-8fdb879ed0ed}

i have research error on web, far have not found solution - plus don't see either of these ids in dcom config tool (although find them in registry).  hoping might permissions need add, or tool needed use, to allow work.  mentioned above, various other wmi commands work fine user on our dcs.

thanks,

nk

hi,

according description, understanding application (servicenow - restricted user account pull hotfix data domain controllers using win32_quickfixengineering) failed run/function. 

>we see 10016 errors show in system event log on dcs
according clsid , appid, find appropriate/corresponding components, then, try manually add permission , check result.

event id 10016 — com security policy configuration:
https://technet.microsoft.com/en-us/library/cc726313(v=ws.10).aspx

application mentioned self-code, recommend post on msdn forum, focuses on developing/coding relate problem:
https://social.msdn.microsoft.com/forums/en-us/home 

best regards,
eve wang

please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  Management



Comments

Popular posts from this blog

Motherboard replacement

Remote Desktop App - Error 0x207 or 0x607

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state