WMI is not accessible
Hi All i am facing issue on one of my domain controller. i am seeing the below error message.
LMD30496067 warn - DC01.mydomain.com WMI is not accessible. See error message for likely issue.-135 likelyError
ID: LMD30496067 DC01.mydomain.com is not responding to WMI or SNMP queries, yet is listening on the Microsoft RPC port
When i use the below syntax on the Logic Monitor Collector i am getting error No such interface supported but i am able to telnet on port 135 from Logic Monitor Collector to the Domain Controller. the account i am using is domain admin.
Get-WMIObject -Computername DC01.mydomain.com -Credential (Get-Credential) -Query {select * from win32_operatingsystem} i am getting the below error.
Get-WMIObject : No such interface supported
+ Get-WMIObject -Computername DC01.mydomain.com -Cred ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Get-WmiObject], COMException
+ FullyQualifiedErrorId : GetWMICOMException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
On the Domain Controller WMI is working fine, i am getting the below output.
PS C:\windows\system32> Get-WMIObject -Query {select * from win32_operatingsystem}
SystemDirectory : C:\windows\system32
Organization :
BuildNumber : 14393
RegisteredUser :
SerialNumber : 1234-89000-00000-BB786
Version : 10.0.14393
Justin Rider
·11 months agoFrom a PowerShell perspective (not directly LM), -Credential (Get-Credential) would prompt you for credentials. If LM is running that command, it probably wouldnt work. Because it would need to interact with the credential box. Instead, you would have to pass credentials to the command.
There are several different ways to do this.
Here is a simple way to test:
Note: I would not recommend storing plaintext credentials in your scripts. You might be able to pass them with a LogicMonitor property
Justin Rider
·11 months agoAlso, if the powershell process is running with an account that has permissions, you may not even need to include the -Credential parameter in the powershell script. It should run as that account.
Daniel Blanco
·11 months agoWhat was the solution to this? We have new DC's that are running 2025 OS and having the same WMI Error 135 and box has collector locally installed.
LM User
·3 years agoI'd reach out to support on this one.