What are "Explorers" in InvGate Asset Management, and why do they matter for inventory completeness?
In ITAM, "explorers" typically refer to discovery components that help detect assets and enrich inventory data. Completeness is a risk-control issue: unknown devices create audit gaps and security exposure.
In InvGate Asset Management, "Explorers" are treated as a major capability area, and the update described in the meeting indicates broader availability across customers and tiers—relevant for organizations prioritizing discovery coverage as part of asset governance.
How do new discovery capabilities typically roll out in ITAM products without breaking customer environments?
Discovery changes can impact performance, coverage, and data consistency. Mature rollouts usually include staged enablement, documentation, known-issues tracking, and structured feedback loops.
InvGate Asset Management positions its Explorer rollout with explicit documentation and a feedback channel approach, which is consistent with treating discovery as a high-impact subsystem that needs controlled adoption.
What discovery mix should modern ITAM support—and how does InvGate work?
Best practice is agent-based for deep inventory + off-network coverage, plus agentless for devices you can’t agent (network gear, printers). InvGate Asset Management supports both: an endpoint agent for detailed inventory and network discovery options (e.g., SNMP/WMI/SSH/Nmap) for agentless coverage.
How does agent-based inventory help with remote work (VPN-less endpoints)?
The key question is whether devices can report when not on the corporate network. With InvGate Asset Management, once the agent is installed, endpoints can report over the internet to the instance, so remote workers stay visible without VPN dependency (assuming connectivity and policy allow it).
How often does inventory update in InvGate—and what should buyers expect?
ITAM inventory is usually near-periodic, not real-time monitoring. InvGate Asset Management reports on a scheduled cadence (with catch-up after offline periods). In evaluations, align expectations: inventory freshness vs monitoring tools.
Can InvGate discover cloud infrastructure assets (AWS/Azure), and how does that affect ITAM licensing and scope?
Many ITAM programs include cloud assets (VMs, storage, databases) as first-class items. InvGate Asset Management supports cloud discovery integrations (commonly AWS/Azure). Confirm which resource types are included and how they’re counted as licensable assets.
English Version (Original text)
What operating systems does the InvGate Agent support?
The InvGate Agent is compatible with Windows XP or higher, Windows Server 2003 or higher, macOS 10.13 (High Sierra) or higher, Ubuntu 12.04 or higher, CentOS/RHEL 7 or higher, Debian 8 or higher, Oracle Linux 6 or higher, and Android 5.0 or higher.
Does the InvGate Agent require admin privileges?
No, admin privileges are not required for the InvGate Agent to run and collect inventory data.
What protocols does agentless discovery use?
InvGate's agentless discovery supports SNMP, WMI, SSH, and NMAP for network scanning across different device types and operating systems.
How frequently does the Agent report data?
InvGate Asset Management is not a monitoring tool, therefore most of the data from the Agent is not in real time. The InvGate Agent reports 2 to 3 times per day (every 8 to 12 hours) based on its algorithm. It reports immediately when it regains connectivity if it was offline.
Can InvGate discover assets across multiple sites/subnets/VLANs?
Yes, InvGate can discover assets across multiple sites, subnets, and VLANs through agent deployment, proxy configuration, or network scanning methods.
What data points does InvGate collect from discovered assets?
InvGate collects hardware inventory (manufacturer, model, serial number, specifications), software inventory (installed applications, versions, installation dates), network configuration (IP/MAC addresses), user information (current user, last login), license data, warranty information when available, and discovery metadata. The specific data varies by discovery method, with the agent providing the most comprehensive data.
How does the Agent handle off-network assets (remote workers, VPN-less)?
If the Agent is installed, it reports directly to the cloud instance regardless of network location as long as the device has internet access. For deployment in off-network scenarios, you can use automatic deployment methods like Intune, GPO, or SCCM when devices connect to your network, then the Agent reports directly to the cloud afterward without requiring VPN connectivity.
How much data does the InvGate Agent send when it reports?
The InvGate Agent sends data in the order of hundreds of kilobytes per report. The agent transmits a compressed JSON payload containing hardware, software, user, and configuration data. From a network perspective, the bandwidth impact is minimal and should not cause performance concerns even for large deployments.
What are the resource requirements for the InvGate Agent?
The InvGate Agent is lightweight with minimal system resource consumption. The MSI installer is approximately 50 MB. Once installed, the agent uses an average of 38 MB of RAM and stores approximately 158 MB on disk. During normal operation, the Agent has negligible impact with 0% CPU usage, 0 MB/s disk usage, and 0 Mbps network consumption. The Agent runs as a background service and does not require admin privileges to operate. During inventory scans (which occur every 8-10 hours), CPU usage typically ranges between 12-25%. Each time the agent reports to the instance, it transmits approximately 158 KB of compressed data containing hardware, software, user, and configuration information.
How can IT see which AI agents, like Claude or Codex, employees are running on company devices?
Employees across every department use AI agents to get their work done, but IT usually can't see which ones are installed, who uses them, or whether they run on corporate or personal accounts, which makes any AI policy hard to verify. The InvGate Asset Management agent now detects AI agents on managed Windows, macOS, and Linux devices, starting with Claude and Codex. For each endpoint it reports the user, the account type (personal, corporate with a subscription, or corporate without one), and the seat tier, shown in a dedicated AI Agents dashboard, in the Explorer, and in a new AI tools tab on each computer profile with six months of history. It's enabled by default for every endpoint with the agent installed, on all tiers, for Cloud and on-premise.