On the PC you want to remotely access (on same domain): $ErrorActionPreference = ($PSBoundParameters.ContainsKey('Credential')) ). I named it Set-WMINamespaceSsecurity.ps1 Param ( $Namespace, I got rid of the embedded function because it was too small and it was only used once.Because there are no leaf objects you can't use $OBJECT_INHERIT_ACE_FLAG In my case, the namespace was Root/Microsoft/SqlServer You must specify the full path of the namespace.So, I did not add my user to the Performance Monitor Users or Distributed COM Users local groups.

After granting my user the EnableAccount, RemoteEnable, and ExecuteMethods permissions on the target namespace, I was able to access WMI. My test user was a non-administrative domain user who was a member of the 'Remote Management Users' on the local system for reasons not related to this issue. at the Root level, and recurse the permissions to the sub-namespaces via the Advanced window in Securityīased on the chosen answer, I modified the script from Microsoft to set the WMI security.

If the user needs access to all the namespaces, you can set the settings in 2.

As an alternatively to step 3 and 4, one can assign the user to the group Distributed COM Users (Tested on Windows Server 2012 R2).

Select Windows Management Instrumentation under Component Services > Computers > My Computer > DCOM Config and give Remote Launch and Remote Activation privileges to Performance Monitor Users Group.

Add Performance Monitor Users and allow remote access, remote launch, and remote activation.

At Component Services > Computers > My Computer, in the COM security tab of the Properties dialog click 'Edit Limits' for both Access Permissions and Launch and Activation Permissions. In the Security tab, highlight Root/CIMV2, click Security add Performance Monitor Users and enable the options : Enable Account and Remote Enable Under Services and Applications, bring up the properties dialog of WMI Control (or run wmimgmt.msc).Add the user(s) in question to the Performance Monitor Users group.The following works on Window 2003 R2 SP 2, Windows Server 2012 R2

Wmi access denied lansweeper