Recently we upgraded.
Recently we upgraded to 5.3.53053 and found that the system only keeps the last 24 hour disconnect/reconnect messages as follows:
2012/04/30 11:37:35 Machine connected with address
2012/04/30 11:35:15 Machine disconnected.
2012/04/30 11:34:20 Machine connected with address
We have used this to help us identify wireless issues, issues with people not leaving computers plugged in, and a host of other possibilities. Now that this is only recording 24 hours this has created an entirely different problem for us when researching issues. Having this information has been critical to our success.
As an example. If we do a wireless upgrade on Sunday and we want to see what might be happening it is nice to be able to see if computers are frequently connecting/disconnecting. Often we use this compare what we see in the Wireless logs on the controller. Sometimes we see a computer disconnecting from Kace but not the WAP. That helps us identify software issues on the computer. We should be able to set how much of this data we want to keep. In fact this might be a separate table that keeps a fixed amount of connects/disconnects, say the last 10 or 20. Then it can “self” manage and not grow. Also it could be useful in a separate table for reporting. Example: look at these 5 computers, did they disconnect at the same time?
As technology rapidly changes, we have implemented an auto-archival of aged and/or outdated suggestions. This suggestion has been declined under this process. If you feel your suggestion is still relevant in today’s marketplace, please resubmit.
We’re giving you your vote back, make it count!