These classes are defined by Configuration Manager-supplied instance providers and extend inventory collection beyond the standard Windows Management Instrumentation (WMI) providers. In general, these classes expose additional system data through WMI for inventory collection.
In my recent rollout of the Flexnet Inventory Agent for Windows (third-party deployment push of the 2021 R1 agent through SCCM), the agent was automatically installed on a Windows image in a non-persistent Citrix VDI environment. I know little about Citrix VDI. The question asked of me was "how does the agent work in a non-persistent VDI environment and what its impact might be?"
Could the experts kindly weigh in on my question or point me to documentation which answers it? If my question needs clarifying data (for example, "Windows image in a Citrix VDI environment" is too general), please let me know what is needed. Thanks for your help.
@mfeinman -- kclausen's link explains how FNM will make the tie between images and clones that use that gold image....so you want the agent to scan the image at some point--and then when the XenDesktop connector queries the Delivery Controllers---it will recognize what machines out there are using that image...and therefore have a complete picture.
There are cases where the agent baked into an image is needed---we used it at a large customer that wanted to track application usage with the agent. Typically the apps baked into the image aren't ones you care about---but in this case, the did.
At the moment, only #1 has been done. Is it OK to leave this "as is" (inventory agent running) or must it be stopped until I set up the inventory beacon connection? My assumption is, in this state, I'll just get inventory from the VDI template.
Snow Inventory Agent for Windows inventories Windows computers. The agent scans the computer and saves the collected data to a compressed and encrypted file, which is sent to a Snow Inventory endpoint (Snow Inventory Server or Snow Extender).
I've verified that my installation scripts are working, as I've had a number of the Macs show up in the Flexnet inventory, and I have verification that the app and certificate were installed successfully on all of them. Unfortunately with so many employees working remotely at the moment, many of them not often needing to use our VPN, having their Macs on our network when the inventory upload time rolls around is quite sporadic.
If I understand the way the agent works correctly, I won't normally see them show up in the inventory until several hours after the installation of the agent, at whatever time 'ndschedag -e' shows as the next event.
My question is, is there a command I can push out to the agents while they're on our network via the VPN after the install to get them to force an upload to inventory, so that they show up in the inventory list on the Flexnet Manager inventory page sooner?
I've tried manually running 'ndtrack -o UploadLocation=" -flexnet-server/ManageSoftRL"' as well as adding '-o InventoryType=User' to that, on a test Mac that is showing up in inventory, but it did not cause the LastInventory date to change, so I don't think that's going to work on the ones not reporting in either.
As a note, the inventory for new machines will not appear in the FNMS UI until after a reconcile completes, so there is a limit to how fast a machine will show up in the UI.
I can think of three ways to do this, but I am sure that others have ideas.
2. Set up a scheduled task (other than NDUpload) to move the stored copy of the NDI to the beacon when the Machine connects to the VPN. The agent stores a copy of the last generated NDI file in the following (platform-specific) locations. Moving the NDI file to an Inventory Beacon's Incoming\Inventories folder will allow the beacon to upload the NDI to your FNMS server.
Sorry if this is a simple fix somewhere, but I am trying to get the GLPI Inventory Agent to run and send details to the Server. I have installed the Agent on a machine using mostly default options. The path to the GLPI Server is [servername]/marketplace/glpiinventory as I managed to get the Marketplace version of the plugin to install.
The Agent does what it should do, in that it scans the machine and can output the information into an xml file, which I can then successfully import onto the GLPI Server. So far, so good. However, I have dozens of PC's across the organisation and I really don't want to have to manually import the information each time.
What the Agent does NOT do is send the information to GLPI automatically. When I look at the logfile I see the following:-
[Wed Dec 20 12:07:16 2023][info] GLPI Agent memory usage: WSS=3309568 PFU=136134656
[Wed Dec 20 12:07:43 2023][info] target server0: server [SERVERNAME]/marketplace/glpiinventory/
[Wed Dec 20 12:07:43 2023][info] sending prolog request to server0
[Wed Dec 20 12:07:46 2023][error] [http client] internal response: 500 Can't connect to [SERVERNAME]:443 (No connection could be made because the target machine actively refused it.), IO::Socket::IP configuration failed
[Wed Dec 20 12:07:46 2023][error] No supported answer from server at [SERVERNAME]/marketplace/glpiinventory/
[Wed Dec 20 12:07:46 2023][info] target server0: next run: Wed Dec 20 13:07:46 2023 - [SERVERNAME]/marketplace/glpiinventory/
Hi.
Sorry - we broke up for Christmas and New Year and I have only just seen this response. Notwithstanding, I seem to have managed a resolution that works. Or seems to!
I have set the GLPI Agent installation to read [x.x.x.x]/glpi/marketplace/glpiinventory/ and ensured that Enable Inventory is enabled in GLPI - Administration - Inventory
This seems to be working. Now all I need to do is figure out how to get this installed using a GPO!
I enabled the ocsinventory-server.conf and the ocsinventory-reports.conf with a2enconf ocsinventory-server; a2enconf ocsinventory-reports. After enabling the first one the server wasn't available anymore. So I disabled it again (a2disconf ocsinventory-server.conf) and the server is reachable again. But still the inventory isn't possible.
I've had similiar problems but all clients now work when I use version 2.6 agent. I also had to delete folder C:\ProgramData\OCS Inventory NG before installing new version, if I forgot to delete that folder the inventory did not work and there were no error on debug log. Not sure if your's is same issue but give it a try..
Open Computer and Software Inventory Next Generation (OCS inventory NG) is free software that enables users to inventory IT assets. OCS-NG collects information about the hardware and software of networked machines running the OCS client program ("OCS Inventory Agent"). OCS can visualize the inventory through a web interface. Furthermore, OCS includes the capability of deploying applications on computers according to search criteria. Agent-side IpDiscover makes it possible to discover the entirety of networked computers and devices.
The open-source OCS Inventory NG project started in late 2005 and produced its first release version of OCS Inventory in early 2007.[3] Since version 1.0rc3, most of OCS Inventory functionality can be adapted or extended via a module system.
The dialogue between OCS client machines and the server depends on the Hypertext Transfer Protocol (HTTP). The software formats data in XML. The management server uses Apache, MySQL and Perl. OCS runs on multiple platforms: under Unixes and under Microsoft Windows (95 or later). A web-interface written in PHP offers consultation of the inventory, user-rights management, and technical support features.
You need to install the agent .msi package and pass in the Site Key value, which can be done from CLI. This is accomplished in slightly different ways depending on your deployment method.
If you are not familiar with the different types of Spiceworks agents and why Spiceworks chose to rely on agents versus network scanning, we recommend reading this documentation Opens a new window first.
If you enable location reporting and deploy the updated agent to a device, location reporting won't happen unless a user on that device opts in to the Windows 8 Let apps use my location privacy setting.
The Software usage monitoring page is used to track usage statistics for Software License Monitoring. This feature collects information on three types of data: usage statistics from software license monitoring, additional inventory information, and application blocking capabilities.
When deploying agents to non-persistent virtual desktop interface (VDI) disk images, you must set a UNC path where software monitor data files will be stored. If you don't set a path, software license monitoring will store monitoring data in the registry. In a non-persistent environment, this data will be lost when the image resets. For more information, see Deploying agents to non-persistent VDI images.
Use the Configure inventory settings dialog box to manage your settings profiles. You can create multiple settings profiles and select the one that you want to be the default for new agent configurations.
I set up Fleet and a bunch of agents running on a Kubernetes (K8S) cluster with the Kubernetes' integration.
So far the log and metrics integration kind of work ( we see them on the DSs, the dashboards and the discovery view).
My problem is when i try to see the inventory graph ( at the observability section) because instead of seeing all my Kubernetes host i see all the elastic-agents and i'm unable to see the overall usage of the K8S nodes (like full node CPU and Memory usage).
The kubernetes integration used is the default with the aggregation of the orchestator.cluster field as pointed in here -> Run Elastic Agent on Amazon EKS managed by Fleet Fleet and Elastic Agent Guide [master] Elastic
Do we have any option in order for the agents to show the name of the node where they are running ?
In case we don't, what should we configurate in order to consolidate the metrics of the nodes when the pod are deleted and change they name in order to see a continuous metric historic for the K8S node no mater the agent's name ?