Windows 10 IOT enterprise not allowing remote WMI

Question

I am trying to connect to a windows 10 21h2 iot enterprise machine remotely using wmi. WMI is running and I turned off the firewall for testing. It works fine from the local console, but all the connections from outside receive "access denied" errors. I am using a local administrator to connect, the same credential that works locally. Is this a limitation of the IOT version? Thanks!

***Move from Windows / Windows 10 / Settings ***

Answer 1

Hello,

Access denied errors that are reported by scripts and applications that access WMI namespaces and data generally fall into three categories: | Error | Possible Issues | Solution | | :--- | :--- | :--- | | 0x800706BA HRESULT_FROM_WIN32(RPC_S_SERVER_UNAVAILABLE) <br>Firewall issue or server not available. | The computer really doesn't exist or the Windows Firewall is blocking the connection | Connecting to Vista: netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes Connecting to downlevel: Allow the "Remote Administration" rule in Windows Firewall. | | 0x80070005 E_ACCESS_DENIED <br>Access denied by DCOM security. | The user does not have remote access to the computer through DCOM. Typically, DCOM errors occur when connecting to a remote computer with a different operating system version. | Give the user Remote Launch and Remote Activation permissions in dcomcnfg. Right-click My Computer-> Properties. Under COM Security, click "Edit Limits" for both sections. Give the user you want remote access, remote launch, and remote activation. Then go to DCOM Config, find "Windows Management Instrumentation", and give the user you want Remote Launch and Remote Activation. For more information, see Connecting Between Different Operating Systems | | 0x80041003 WBEM_E_ACCESS_DENIED <br>Access denied by a provider | The user does not have permission to perform the operation in WMI. This could happen when you query certain classes as a low-rights user, but most often happens when you attempt to invoke methods or change WMI instances as a low rights user. The namespace you are connecting to is encrypted, and the user is attempting to connect with an unencrypted connection | Give the user access with the WMI Control (make sure they have Remote_Access set to true) Connect using a client that supports encryption. |

• Typically, DCOM errors occur when connecting to a remote computer with a different operating system version.
• Providers may also deny access to data in specific namespaces or may require certain levels of connection security. For more information, see Setting Client Application Process Security and Provider Hosting and Security.
• An access denied error is returned by DCOM security when a low-integrity client tries to access WMI. For example, an ActiveX control that is running in Internet Explorer, which has the security level set to low, does not have access to perform local WMI operations.

(see:WMI Troubleshooting - Win32 apps | Microsoft Learn)

Best Regards,

Karlie