We often have multiple sesions listed in the console for the same computer.
I normally will right click on the older ones listed that are no longer valid and choose end session.
It would be nice to have a report or view that shows the duplicates and allows for easier cleanup.
Thanks!
Joshua
another problem I found with removing duplicates. Sometimes, the reinstalled agent will not reconnect to the original entry in the console. This means that there is an extensive history timeline of events on the old agent Access session and the new one that is now active has no history.
If we remove the old duplicate, we lose all that access history. is there a way around this? To make sure we retain audit history? Can we force it to reconnect to the original entry in the console instead of creating a new entry?
Hi David,
What sort of reinstallation are you performing? When reinstalling a client on the host page, there shouldn't be a second agent on your session list. Any additional information you can provide about the actions you're performing will help! We don't expect clients to be duplicating.
Thanks!
This happens when a computer is renamed also. We image computers and give them a "STOCKxxxx" name where the X's are the asset tag number. Then, when we rename the device to deploy it for an end user, the old STOCK name still persists. Using something like the serial number and/or GUID is all that is needed. If the machine was just renamed, simply rename the old session. There's no need to create a new one at all. The same goes for a reimage. There's enough unique info about any one machine that multiple checks could be used.
There is a problem with Report: Only admin can use it, and in my case, I'm not.
At least I have the ability to create groups based on filters.
I found group filtering is an awesome and flexible tool to exploit for this type of things.
I'm doing maintenance, admin won't do it. So a simple variable, field, whatever is convenience to get this done, it would be much appreciated.
Via Comparison: I found an easier and exact way to find out duplicated hardware/devices (no duplicated name in this case): Serial #,
In my experience same device can be renamed for several common reasons (reimage, restocking, reinstalled agent, etc), but serial will always be the same.
Now, if we can find a way to compare among those.
Chris Paetz got a nice method I will try.
After gazillion years... I came back to the same, but this time I fixed it by myself.
The idea is the same here proposed above by Silas Sulser , only this time instead to look for name (that can change or be duplicated) I go for Mac Address variable name, this is: GuestHardwareNetworkAddress
Yes, it will a list of many device you got, but you will see the EXACT duplication by the unique data: MAC Address.
Hope it helps you guys.
Here is how we do this... We've created two new groups... one of clients not connected for 90 days, and one of clients not connected for 180 days... then we make it part of our regular process to review disconnected clients every 90 days.
Our process is to end the old session when we deploy a new OS image... but this catches the ones that fall through the cracks, each disconnected session is investigated and then ended every 90 days. If were not sure, we may let it slide and we will catch it next time around in the 180 day filter.