• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Subscribers 27 subscribers
  • Views 10840 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot protect machine because RR says it's already protected.

Marc L
over 6 years ago

We are protecting our VM's agentlessly and only have 1 VM that's causing issues. Whenever I try to add it to protection, RR says it's already protected. This VM has never been protected before so I don't know what's causing RR to think that. We deploy all of our machines via templates so I know it's not a duplicate SID issue or else we would have seen it before. Is there somewhere I can check to get more info on why RR is saying this? Or even better, remedy the situation?

Parents
  • 0 over 6 years ago
    I think trying to install an agent and then protect may produce different results vs agentless. But just a guess

    One idea is to check the Core registry to see if there are any guid OR DisplayName entries already. HKLM\Software\Apprecovery\Core\Agents
Reply
  • 0 over 6 years ago
    I think trying to install an agent and then protect may produce different results vs agentless. But just a guess

    One idea is to check the Core registry to see if there are any guid OR DisplayName entries already. HKLM\Software\Apprecovery\Core\Agents
Children
No Data