Jump to content

Easy way to remove 60+ day old agents?


JCourtney
 Share

Recommended Posts

Is there any easy way to see which agents haven't communicated in 60 days?  Need to clean up some computers that got replaced, etc.   I didn't know if there was a report that could be generated or if there was already that functionality built into the web app. 

What is the best procedure to free up agent licenses and remove non-communicating agents?

Edited by JCourtney
Link to comment
Share on other sites

  • 1 month later...

This function used to exist, however it was buggy and the order was not always correct (eg last online) - We had previously reported this and it was simply removed altogether!

This needs to be added back in, and checkbox should also be added to the screen to remove multiple. (Maybe this way we won't have a constant email telling us we need to pay for more subscriptions!) - if the above is too time-consuming for your devs a simple search box would assist your customers.

At this stage is seems it's intentionally difficult to remove devices from the manage systems screen (something we are billed for)

 

 

 

 

Link to comment
Share on other sites

  • 1 month later...

We are an internal IS department (versus an MSP) and we have 500+ computers, at over 23 locations, with continuous weekly refreshes, in which duplicate named systems often eat up licenses rather than replace. We need a way that we can efficiently maintain the systems monitored, last check in and the ability to remove multiple systems at once, versus single delete-confirm-rinse and repeat. When Pulseway removed the last check-in date, AND you went over, there was simply an increase in license cost...NOW the new systems don't register. It seems to me that this would be very basic to implement, as there are built in reports for last check in, but who wants to run a 50-page report and manually go through and read/sort for systems with duplicate names and their effective last check in? An RMM is supposed to increase efficiency, not hamper it.

Link to comment
Share on other sites

I would comment here that this falls back to not being able to call pulseway functions on a result set of queried endpoints based on any of the attributes in the pulseway data space. 

Even if the result set were compiled externally the Pulseway Interface to its own attributes doesn't exist.

Edited by timbuck2
Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...