- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there a new update for the 2.18 agent version to fix this issue? We are having this problem in our environment and we use agent version 2.18.
Thanks for the quick reply.