Kaseya Community

Auto-generated tickets from Monitor sets creates a ticket associated with an asset rather than an agent

This question is answered

We make use of monitor sets to watch for low disk space on servers.  Prior to the upgrade to 6.3, these tickets were generated and associated with the agent running on the server.  Now, after 6.3, they are associated with the asset of the server.  This makes no difference to me, as I am a master user in our Kaseya system.  However, other users cannot access the ticket and receive error messages stating "the ticket X doesn't exist of you do not have permission to access it."

The only location I can find assets anywhere is in the Auditing and Discovery portions of the product.  How do we change the monitoring auto-generated ticket to create these tickets again using agents and not assets?  Or, how can I include assets in available scopes of roles in Kaseya?

Please note, we are using the ticketing module, not service desk.

Verified Answer
  • I have a case open with Kaseya.  This is a known issue and they are awaiting a hotfix to resolve.

All Replies
  • I have a case open with Kaseya.  This is a known issue and they are awaiting a hotfix to resolve.