WMI client (WMIC) for Linux

Windows Management Instrumentation (WMI)

WMI Allows you to remotely execute commands and query parameters on a Windows Host

Linux

In order to be able to communicate with WMI from Linux you need to install this functionability.
For Ubuntu 14.04:
Download this libraries and install them:

 dpkg -i libwmiclient1_1.3.14-3_amd64.deb
 dpkg -i wmi-client_1.3.14-3_amd64.deb

• Required: python-support

sudo apt-get install python-support

Examples

get the size of the WorkingSet of the process “java.exe” running on the remote host 192.168.20.20

wmic -U Administrator%mysecret //192.168.20.20 "Select WorkingSetSize from Win32_Process Where CommandLine like '%java.exe%'"

Get process ID for process

wmic -U Administrator%mysecret //10.140.10.10 "Select ProcessId from Win32_Process Where CommandLine like '%java.exe%'"

Get WorkingSetSize for process

wmic -U Administrator%mysecret //10.140.10.10 "Select WorkingSetSize from Win32_Process Where CommandLine like '%java.exe%'"

Get thread count for process

wmic -U Administrator%mysecret //10.140.10.10 "Select ThreadCount from Win32_Process Where CommandLine like '%java.exe%'"

Get private bytes for process

wmic -U Administrator%mysecret //10.140.10.10 "Select PrivateBytes from Win32_PerfFormattedData_PerfProc_Process Where IDProcess='%java.exe%'"

Get free physical memory for host

wmic -U Administrator%mysecret //10.140.10.10 "Select FreePhysicalMemory from Win32_OperatingSystem"

Windows host config

Step 1: DCOM permission

1. Open Dcomcnfg
2. Expand Component Service -> Computers -> My computer
3. Go to the properties of My Computer
4. Select the COM Security Tab
5. Click on "Edit Limits" under Access Permissions, and ensure "Everyone" user group has "Local Access" and "Remote Access" permission.
6. Click on the "Edit Limit" for the launch and activation permissions, and ensure "Everyone" user group has "Local Activation" and "Local Launch" permission.
7. Highlight "DCOM Config" node, and right click "Windows Management and Instruments", and click Properties.
8. <Please add the steps to check Launch and Activation Permissions, Access Permissions, Configuration Permissions based on the default of Windows Server 2008>

Step 2: Permission for the user to the WMI namespace

1. Open WMImgmt.msc
2. Go to the Properties of WMI Control
3. Go to the Security Tab
4. Select "Root" and open "Security"
5. Ensure "Authenticated Users" has "Execute Methods", "Provider Right" and "Enable Account" right; ensure Administrators has all permission

Step 3: Verify WMI Impersonation Rights

1. Click Start, click Run, type gpedit.msc, and then click OK.
2. Under Local Computer Policy, expand Computer Configuration, and then expand Windows Settings.
3. Expand Security Settings, expand Local Policies, and then click User Rights Assignment.
4. Verify that the SERVICE account is specifically granted Impersonate a client after authentication rights.

The windows machine you are connecting to must have LAN Manager Authentication level set to:
Send LM & NTLM - use NTLMv2 session security if negotiated

1. Start --> run --> gpedit.msc
2. Navigate to: Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/Security Options
3. In the right panel look for “Network Security : LAN Manager authentication level"

Remote admin must be enabled: from cmd type:

netsh firewall set service type = remoteadmin mode = enable