Easy way to remove 60+ day old agents?

[JCourtney]

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 August 19, 2019 by JCourtney

[Chris]

Hi @JCourtney,

Please send an email to support@pulseway.com requesting this? Add some details regarding your Pulseway server and we might be able to create this list for you.

[Ahmet Eroglu]

It could be nice to have a function for sorting out old devices. We are running on prem server, and we want to be able to pull these lists ourself if its possible

[Ghostie]

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)

 

 

 

 

[jrtaylor3]

I agree, there is no data for any not connected device and this is bad on my levels. 

[Shawnc]

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.

[timbuck2]

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 December 2, 2019 by timbuck2

[Chris]

Hi All,

We have reintroduced the option to see the date when Pulseway server has seen the system for the last time. This option is available under Account section -> Manage systems. Also, you can sort that column by date, therefore it is easy to see old systems.

 

[noisygirlkk]

Good to know, i m also looking for that...

[Nick530]

Looks like this is a bit of an old post but has a feature been added to automate the removal of 60+ day old devices?