ESET Server Security – Table of Contents

Accessing Provided Data

Copy current article URL Share via email

This article (PDF) Whole documentation (PDF)

Here are a few examples of accessing ESET WMI data using PowerShell or a Windows command line. Other scripting languages and tools can also be used to access the data.

Microsoft started deprecating WMIC with the release of Windows Server 2012 and completely removed it in Windows Server 2025. Therefore, WMIC may not be available on all operating systems, and we recommend using PowerShell instead of WMIC.

PowerShell provides a more efficient way of querying WMI

Command line without scripts

The wmic command line tool can be used to access various pre-defined or any custom WMI classes.

To display complete info about product on the local machine:

wmic /namespace:\\root\ESET Path ESET_Product

To display product version number only of the product on the local machine:

wmic /namespace:\\root\ESET Path ESET_Product Get Version

To display complete info about product on a remote machine with IP 10.1.118.180:

wmic /namespace:\\root\ESET /node:10.1.118.180 /user:Administrator Path ESET_Product

PowerShell

Get and display complete info about product on the local machine:

Get-WmiObject ESET_Product -namespace 'root\ESET'

Get and display complete info about product on a remote machine with IP 10.1.118.180:

$cred = Get-Credential # promts the user for credentials and stores it in the variable
Get-WmiObject ESET_Product -namespace 'root\ESET' -computername '10.1.118.180' -cred $cred

˄˅