We are getting a similar problem. I looked over the document, but the only resolution offered was to:
uninstall the agent completely from the registry and deploy it through AD GPO.
The agent was originally deployed through AD GPO, so I'm not sure why that would fix it.
Even if I delete the bottom asset and rename the top one to the correct name, if I scan it then SD gives it the _old name and creates a new asset.
Why is this happening? We've been able to scan purchased assets before and I'd like to keep the purchase information tied to the asset.
Thanks!