# Deleting Duplicate Assets in Nexpose

**URL:** <https://discuss.rapid7.com/t/deleting-duplicate-assets-in-nexpose/1035>\
**Category:** API\
**Created:** [June 1, 2020, 6:20pm UTC](https://discuss.rapid7.com/t/deleting-duplicate-assets-in-nexpose/1035 "2020-06-01T18:20:12Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![nkershaw1](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/n/e9a140/32.png) [@nkershaw1](https://discuss.rapid7.com/u/nkershaw1)\
**Post date:** [April 4, 2024, 10:16am UTC](https://discuss.rapid7.com/t/deleting-duplicate-assets-in-nexpose/1035/21 "2024-04-04T10:16:13Z")

</div>

Last month we finally got a resolution to this after being persistent about not liking the change. It is correct, the Agent-ID was given a much higher weighting, in fact to me it has such a weighting that it ignores everything else!  
We were seeing duplicates every time we re-imaged a workstation.

Anyway, I got a custom property from support to revert back to the old correlation algorithm. (THERE ARE KNOWN ISSUES WITH DOING THIS IF YOU HAVE VDI/CITRIX so beware).

The command to set this is “set custom property com.rapid7.nexpose.nsc.asset.correlation.v2=false”.  
This saves to CustomEnvironment.properties in /opt/rapid7/nexpose/nsc/

Hope it helps, but do seek advise from support instead of just setting this!

[Previous page](https://discuss.rapid7.com/t/deleting-duplicate-assets-in-nexpose/1035.md?page=1)