Default scan server changing by itself

[Gururek]

We have two scan servers in place due to our network spanning two separate buildings, unfortunately due to the network configuration there is no current way to scan both buildings from one server. The setup is working great and both scan servers are able to scan their own buildings fine, however I have noticed that the default scan server the assets are being assigned are changing on their own. Just yesterday I went through and changed all the assets to use their respective server via the mass edit tool, but today I've found that they've changed again. What is causing these changes? Is it the AD scans?

[Bruce_B]

Indeed, since the scan server field is automatically updated with whichever scanning server last scanned an asset, the only way to prevent the "wrong" scanning server from being listed for an asset would be to make sure there can be no "cross-server scanning", which is most easily achieved by limiting your scanning targets to IP Range targets.

[Gururek · Accepted solution]

http://www.lansweeper.com/Forum/yaf_postsm41750_Lock-scanning-server.aspx#post41750
I found this and I'm guessing it's the same problem. I've turned off AD active scanning.