Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

WMI monitor non-domain servers

WMI connection from Orion server to the Windows 2016 server from a workgroup (is not a part of the same domain as Orion server) doesn't work. I have local administrator credentials, but the test connection from the "Add node" page still fails. WMI configuration on the remote server seems ok - all services running, wbemtest locally connects, tried also with Windows firewall turned off...

Is there a separate configuration needed, because the remote server is not a part of the same AD domain?

Find more posts tagged with

Accepted answers

All comments

jm_sysadmin

It works, I have had to use local credentials from time to time. I assume you are using the computer name for the domain if the domain is requested or computer\user format? Something like the code below would allow you to remotely test a WMI connection to the computer with your local accounts to isolate possible issues.

Get-WmiObject  -Credential (Get-Credential) -Namespace "root\cimv2" -Class Win32_Process -Impersonation 3 -ComputerName Computer_B

Gustelj

Thanks for your reply. I am getting "Access denied." for the above Powershell command. I'm not sure, how to specify credentials in computer\user format. I've tried multiple combinations without success. In the same time I've been able to RDP to the remote server with the same user credentials and the user is a member of the local administrators group on the remote server.

jm_sysadmin

Maybe some of this will assist:
https://docs.microsoft.com/en-us/windows/win32/wmisdk/connecting-to-wmi-remotely-starting-with-vista
https://docs.microsoft.com/en-us/windows/win32/wmisdk/troubleshooting-a-remote-wmi-connection

Also from Microsoft:
"The previous code samples are arguably the most basic remote connection you can perform with WMI. Specifically, the samples assume the following:

You are an administrator on the remote machine. Due to User Account Control, the account on the remote system must be a domain account in the Administrators group. For more information, see User Account Control and WMI.
The password on your current local machine is not blank. This is essentially a Windows security requirement that you must have logged onto your system with a password.
Both your local and remote computers are within the same domain. If you need to cross domain boundaries, you would need to supply additional information or use a slightly different programming model.
You are using your own account to access the remote machine. If you were trying to access a different account, you would need to supply additional credentials. (Note that trying to access WMI locally with credentials different than your current account is not permitted.)
Both computers are running IPv6. WMI supports connections to computers running IPv6. However, both your local machine and "Computer_B" must be running IPv6. Either computer may be running IPv4 also. For more information, see IPv6 and IPv4 Support in WMI.
Your script does not need to delegate - that is, it does not need to access additional remote computers through the targeted remote computer. For more information, see Delegating with WMI.
You are trying to make a specific call, rather than creating a remote process. For more information, see Creating Processes Remotely using WMI.

With those restrictions in mind, a remote WMI call is very similar to a local WMI call - the only difference being that you must specify the name of the remote system. However, you may choose to change many of those features: using different credentials, or routing your call through a 3rd party computer, or accessing a different domain."