Professor
NeophyteI ended up opening a ticket about this issue. This is the response received:
"
When running Netscan, the device group will be overridden to the one specified in the script along with the current NetScan Policy (i.e. NetScan configuration, the script it is using).
If you want to prevent the existing device from being updated and instead add a new device with the same IP, you can edit the Netscan and use the "Exclude duplicate IP address" option. In the dropdown, select "matching resources currently assigned to these collectors" and specify the collector please add the same collector that is performing the scan.
Note: Make sure that the other device (the existing one with the same IP) is not monitored by the same collector that will be performing the scan."
Our solution: Create a dynamic group. Our netscans are balanced around different collectors and the workaround suggested would not work, by design, apparently.
