Legacy API

WQL queries

WinRMWqlExecutor.executeWql(...)^[4]:

WinRMWqlExecutor result = WinRMWqlExecutor.executeWql(
    protocol,        // WinRMHttpProtocolEnum.HTTP or HTTPS (null → HTTP)
    hostname,        // mandatory
    port,            // Integer, null → 5985 (HTTP) / 5986 (HTTPS)
    username,        // "DOMAIN\\user" or "user", mandatory
    password,        // char[]
    namespace,       // null → ROOT\CIMV2
    wqlQuery,        // mandatory
    timeout,         // long, milliseconds, > 0
    ticketCache,     // java.nio.file.Path, null for NTLM
    authentications  // List<AuthenticationEnum>, null/empty → NTLM
);

result.getHeaders();        // List<String> — column names
result.getRows();           // List<List<String>> — values in header order
result.getExecutionTime();  // long, milliseconds

Declared exceptions: WinRMException^[5], WqlQuerySyntaxException^[6], java.util.concurrent.TimeoutException — all checked.

Remote commands

WinRMCommandExecutor.execute(...)^[7]:

WindowsRemoteCommandResult result = WinRMCommandExecutor.execute(
    command,              // mandatory
    protocol,             // null → HTTP
    hostname,             // mandatory
    port,                 // null → protocol default
    username,             // mandatory
    password,             // char[]
    workingDirectory,     // nullable
    timeout,              // long, milliseconds, > 0
    localFileToCopyList,  // List<String> of local files to copy first, nullable
    ticketCache,          // nullable
    authentications       // null/empty → NTLM
);

result.getStdout();
result.getStderr();
result.getStatusCode();     // process exit code
result.getExecutionTime();

Files listed in localFileToCopyList are copied to the host first, and each reference to them in command is rewritten to the remote copy — the same engine as the fluent upload(...); see File Transfers^[8].

Declared exceptions: java.io.IOException, java.util.concurrent.TimeoutException, WindowsRemoteException^[9] — all checked.

Behavior notes

• One connection per call: every invocation performs a full authentication handshake. Code that polls the same host repeatedly pays that cost on every call — the main reason to move to the reusable WinRMClient.
• The output character set of a command is detected before each call (one extra WQL query per call; the fluent client caches it).
• TLS configuration is global only: the org.metricshub.winrm.tls.insecure system property (see TLS / HTTPS^[10]); there is no per-call trust store.
• Authentication schemes come from AuthenticationEnum^[11] (NTLM, KERBEROS), with the same ordered-fallback semantics as the fluent AuthScheme^[12].
• For advanced use, the underlying reusable executor is also public: WinRMExecutorFactory.createInstance(...)^[13] returns a WindowsRemoteExecutor^[14] — but the fluent WinRMClient is the supported way to get connection reuse.