For the complete documentation index, see llms.txt. This page is also available as Markdown.

WMI

Connection Requirements

1 - Targets

One or more Windows hosts to inventory over WinRM. Accepts a single IP, a CIDR (e.g. 10.0.11.0/24), a dashed range (e.g. 10.0.11.10-50), or a comma-separated list. Optional: leave this empty and use AD Host below to discover targets automatically. Each reachable host is collected independently; unreachable hosts are skipped.

2 - AD Host

Optional. An Active Directory domain controller (IP or hostname). When set, the adapter asks the domain controller for all enabled domain computers (with their resolved IP addresses) and inventories each over WinRM. With AD Host set you can leave Targets empty to sweep the whole domain. Provide either Targets or AD Host (the two may also be combined).

3 - Port

WinRM port (optional, default: 5985 for HTTP, 5986 for HTTPS).

4 - Username

The account OctoXLabs CSAM PLATFORM uses to connect over WinRM (and to bind to AD when AD Host is set). Use a dedicated least-privilege domain account with remote WMI/WinRM read access on the targets.

5 - Password

The password of the provided username.

6 - Auth Type

WinRM authentication type (default: NTLM). In a domain environment Kerberos is the standard and preferred method; when selected, set Kerberos Realm and KDC IP below.

7 - Is Secure?

Use HTTPS (WinRM over TLS, port 5986) instead of HTTP. Default is unchecked (HTTP, port 5985).

8 - AD Search Base (advanced)

Optional LDAP base DN / OU to narrow AD discovery (e.g. OU=Servers,DC=octo,DC=local). Defaults to the whole domain.

9 - Kerberos Realm / KDC IP (advanced)

Required only when Auth Type is Kerberos. Kerberos Realm is the uppercase domain (e.g. OCTO.LOCAL); KDC IP is the domain controller that issues tickets.

WinRM must be enabled on each target host (Enable-PSRemoting -Force) and reachable from the OctoXLabs CSAM PLATFORM host. AD Host mode uses the same WinRM channel (no extra ports); the AD Host must be a domain controller. Installed software is read from the registry, so Win32_Product is never queried.

Last updated