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?