1 of 1 people found this helpful
You job may tied to a certain CO version to attempting to auto-detect a version it believes to be installed. In your deregistration job and you select the "Show all configuration objection versions" check-box in the select Configuration Objects tab. Here select the specific VMWare CO to match version 81020262 and then try to re-run the deregistration job.
Did Newton's response provide the solution for you?
If so, please mark the post as correct/helpful.
If not, please let us know how you solved the problem
Thanks & Regards,
Jim (Forum Manager/Facilitator)
After leaving this that weekend, I managed to deregister and re-register ok. I'm not sure what caused this issue but time seemed to allow it to re-distribute.
Perhaps some internal DB operations resolved the issue?
Thanks Nick :-)