Agentless discovery: inventory without a software rollout on endpoint devices.

The server asks. The endpoint answers.

The Inventory Service runs as a Windows service on the inventory server and scans defined network ranges on a schedule. Which protocol applies depends on the device. Configuration runs in a single interface.

For Windows devices, LOGINventory copies a small helper file (LOGINfo.exe) via a remote call, runs it, reads the result, and removes the file again. If RPC isn’t available, the scan falls back to pure remote API discovery. For Linux, Unix, and macOS, the scan runs exclusively over SSH. No file is left behind.

The difference between a remote scan and a local scan is small: a local scan additionally discovers connected network drives and user profile packages.

The Windows Firewall opens the required ports automatically once WMI remoting is enabled via Group Policy. If you want to restrict that access, restrict it via GPO to the IP of the LOGINventory server. No global RPC opening required.

Devices outside the LAN: Offline Agent and logon script

Laptops in the field or in home offices aren’t reachable over the network. There are two ways to handle that.

The Offline Agent runs locally on the device, collects the inventory data, and saves it as an .inv file as soon as the device reconnects to the company network or over VPN. Alternatively, a logon script controls the inventory run at the next sign-in, with no permanently installed service.

Devices without a network interface can be entered manually.

Computer and user accounts, permissions

Besides hardware and software, LOGINventory also discovers accounts and access rights.

Active Directory computer accounts and user accounts are read in with recursive resolution of group membership. LOGINventory also evaluates who has admin rights on which devices and who has access to which shares, folders, or databases.

This data lives in the same interface as the hardware and software inventory. No separate tool required.