Hi all ...
I recently deployed the inventory agent, manually, to three different flavors of Linux:
Shortly after the agent was deployed, I noticed a familiar looking file with a slightly different name - mgs1-tracker.log. When I opened that file, I saw that the agent ran a hardware inventory, and when I checked the InventoryReport table, I saw entries for all three servers. The HWDate field had a value but the SWDate and FilesDate values were null, which is what I'd expect if all that ran was a hardware inventory. I was very surprised to see this.
I thought that you had to manually run the ndtrack command in Linux (or wait for the schedule to kick in) before being able to see anything from a Linux machine. But here's a case where the hardware inventory occurred on its own automatically. Is my belief mistaken or is this something recent? I've never seen the file name mgs1-tracker.log referenced anywhere. (The agent version was 2022R1).
--Mark
Apr 03, 2023 03:46 PM
What are your Inventory Settings for Inventory Agent Schedule?
I have found that if Run last missed event is checked, it will run at least a hardware inventory.
Apr 05, 2023 09:56 AM
Here are my settings:
As you can see, "run last missed event" is not checked.
Apr 05, 2023 10:44 AM
On Unix-like operating systems, policy will be applied and inventory gathered (with logging in a file named mgs1-tracker.log) if the MGSFT_RUNPOLICY setting is set to 1 (true) in the mgsft_rollout_response file that is used to bootstrap the agent.
Jun 01, 2023 07:29 PM