F.A.Q.

IT Asset Tool server — the computer that runs the management console and the collection engine:

• Intel or AMD processor, 2 GHz or faster
• 8 GB of RAM or more
• 10 GB of free disk space or more
• 64-bit Windows 11 or Windows Server 2019
• display resolution of 1440 × 900 or higher for the console
• Internet access to activate and verify the licence

If in agentless mode the inventory does not collect data, or the data is incomplete:

• check the Active Directory settings (domain name, administrative user and password) and re-apply them if the installation was upgraded from a previous version;
• run Check AgentLess in Config > Utility > Debugger Tool: it opens the Active Directory Integration Debugger, where you enter the domain, the administrative account and its password — an optional target hostname as well — and press Check Connections;
• use the Troubleshooting connection problems to a remote computer box in the same tab to diagnose a single machine (see the next entry);
• make sure the host is not listed under Host Exclusions from agentless scanning;

If instead only some computers are missing, the problem is on those hosts: see the next entry.

For a host to be scanned by IT Asset Tool, the firewall on that computer must not interfere and the following Windows services must be enabled on it:

• Remote Procedure Call (RPC)
• Remote Registry
• Windows Management Instrumentation
• Windows Defender Firewall

The File and Printer Sharing component must also be active (required only for remote software removal/upgrade).

The host must answer an ICMP ping. Before attempting any WMI connection, the scan pings each computer and skips the ones that do not reply within the timeout. A firewall rule that blocks ICMP therefore makes a computer invisible to the inventory even when WMI is perfectly reachable.

Once those are in place, make sure the host name is resolvable by the internal DNS and that the computer exists in Active Directory as a Computers object. The scan enumerates the directory looking for computer objects whose operating system is Windows, so an object whose operatingSystem attribute is empty — typical of a machine that has never completed a domain logon — is not enumerated at all.

The quickest way to apply all of this to a whole domain is Set GPO, in Config > Miscellaneous: it creates and links a Group Policy named IAT Setting that sets Remote Registry and Windows Firewall to automatic start, sets RPC to automatic, and adds two inbound firewall rules — IAT Server (TCP) and IAT Server ICMP — allowing traffic from the IT Asset Tool server address on the domain profile.

To check a single computer, use Config > Utility > Troubleshooting connection problems to a remote computer: type the host name — a host name, not an IP address — and click Scan. The tool resolves the address, pings it, then tries the WMI connection with the AD credentials and reports at which of these steps it fails.

Configuration guide: https://www.it-asset-tool.com/documentation/agentless/agent-less-configuration

The free edition inventories up to 35 hosts. Once the database contains that many computers, the agentless scan does not simply refuse the new ones: it skips every host in the cycle, so the whole inventory stops being refreshed.

The Listener states the reason on its console and in its log file:

The maximum limit of USERS available for a Free edition of IT Asset Tool has been reached.
Host scanning is disabled due to exceeding the number of clients allowed by the free subscription.

To lift the limit, activate a licence in Config > General > Subscription Activation. Otherwise, bring the number of computers stored in the database back below 35 by deleting the ones you no longer need to monitor, and add them to Host Exclusions from agentless scanning so the next cycle does not put them back.

The agentless engine works in cycles: it enumerates the domain, contacts every reachable host one at a time, then waits before starting the next pass.

The pause between two passes is set in Config > Advanced > Microsoft Active Directory Integration with Interval Pooling, expressed in minutes; the default is 10.

It is the pause between cycles, not the total refresh time: on a large domain a single pass can take considerably longer than the interval itself, because each host is contacted in turn.

The wait is interruptible — a configuration change made in the console is picked up without having to wait for the current cycle to end. To refresh one computer immediately, right-click it in the inventory and choose Scan Now.

Make sure the Microsoft SQL server is reachable on its TCP port and that it accepts remote connections. The message quotes the port actually configured for the instance — 1433 unless you changed it — so if you use a different port the number in the message changes accordingly.

In the console you can check the connection parameters in Config > Advanced > MSSQL Configuration and test them with Check Sql Credential.

Note: remember to enable "SQL Server and Windows Authentication mode" so that connections from the SQL administrative user "sa" are allowed.

Configuration guide: https://www.it-asset-tool.com/documentation/agentless/microsoft-sql-server-installation

In version 2.x there is no file to copy by hand: the database is a Microsoft SQL Server instance, and the setup program has a dedicated mode for this.

1. Run the installer with an administrator account on the computer that will host the additional console.
2. In Subscription Verification, enter the registration e-mail and click Validate.
3. In Installation Type, choose Connect to Existing SQL Server (Additional Manager).
4. Fill in Host, Microsoft SQL Instance, SQL User, SQL Password and Port of the instance already used by the main server, then click Connect to SQL Server.
5. Start the console and log in with your existing credentials: the additional console works on the same data as the main one.

The DaemonIAT service is installed on this computer too. If you do not want the additional console to run its own collection engine, stop the service from Config > Advanced > Instances > Management Service with the Stop button.

To run a debug session, stop the Windows service "DaemonIAT". Stopping the service also terminates ListenerIAT and the other IAT processes it supervises.

Once done, and after making sure "ListenerIAT" is not running (otherwise end it from Task Manager), launch ListenerIAT.exe manually as administrator from the Server folder in the IT Asset Tool installation path.

Running it manually prevents the Listener from running in background mode; it will run in console mode instead, allowing you to view any logs or issues.

As an alternative you can run the daemon itself in console mode:

DaemonIAT.exe --console

It starts and supervises ListenerIAT exactly as the service does, while showing the service messages on screen. Do not use it while the service is started.

All modules also write their log files to C:\ProgramData\IT-Asset-Tool\logs; the level of detail is set with ErrorLevel in Config > General.