Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


JosefNT last won the day on January 31

JosefNT had the most liked content!

Community Reputation

2 Neutral

My Information

  • Location
    Monroe, LA, US
  • Agent Count
    3000 - 4000 Agents
  1. I can confirm the behaviors @avdlaan describes: scans/re-detections don't actually seem to be running when I attempt to trigger them manually, and my Probe Commands window remains empty even after attempting to initiate a scan or re-detection. Following the steps outlined here for upgrading from Gen1 to Gen2, I purged network devices from a probe for a selected client, then deactivated the Gen1 probe. When I re-activated and went through the Gen2 wizard, the probe functionality returned, but none of the options to perform manual actions appear to be working, and the Probe Commands window is empty. I have tried initiating a rescan via the "Play" button on the Device Discovery pane in the Overview screen and also tried via Commands > Probe > Initiate Network Scan and Commands > Probe > Run Device Detection. I also ensured the probe scan settings were set to have Only run discovery in scan window = UNCHECKED. I want to make sure I'm not missing something regarding manually initiating scans/re-detections, as well as the Probe Commands window appearing blank. Finally, I am interested in finding out what benefit we gain from activating the MAC Address Scanning feature? I have seen the documentation reviewing how it fits into discovery as the optional third step. But I haven't been able to determine what that third step of scanning the MAC addresses actually accomplishes. Is it enabling some new functionality? Does it allow more reliable agent push to detected devices? We face multiple client probes (Gen1 and Gen2) in which devices are mis-detected (Windows desktops appearing as "Manufacturer = Roku" or "Manufacturer = Apple, Inc.") or simply not allowing agent install (multiple VM servers at one client, for instance). If enabling MAC address scanning will remedy one or more of these situations, that's a strong argument for turning it on. If it is intended to perform some other function ... what might that be?
  2. JosefNT

    Dataview Creator on v12

    @Wade , if you (or any other users arriving at this thread) are still looking for this functionality, try this: Enable the Legacy menu as noted by @RDeBok (if needed) In Control Center select System > Configuration > Dashboard, then go to Config tab > Control Center subtab, and check the Legacy menu checkbox at the bottom Add a Property within the Dashboard In Dashboard go to Config tab > Configurations subtab > Properties subtab Name: DataViewCreator Value: True Click Add Click Force DBAgent to Reload Properties Close and re-open Control Center (Reload System Cache did not work in my case) Legacy menu should now expose Dataview Creator item. Profit.
  3. JosefNT

    Computer Warranty Updater (HP/Dell/Lenovo)

    Fantastic addition to our onboarding process! I can confirm the initial run completion delay. We have 4100+ agents in Automate, and I've been sitting with a PowerShell ISE cursor blinking for around 35 minutes so far. Based on the ComputerID it's stopped on (4197), it seems to be almost complete, but after reading the previous comments I'm hesitant to Ctrl+Break it for fear of missing any queued IDs. I see that the assorted functions within the script query to only return devices in which the warranty fields are empty, so I'm assuming that if I must break and re-run the script locally it will only attempt to process machines missed by the first run. If there's any reason I shouldn't re-run it locally to catch any stragglers, please let me know. Great work, and the installation instructions were spot-on!