ISO Date Formatting
Could we have any field that displays a date changed to the ISO 8601 standard? By the standard, the proper way to represent a date is YYYY-MM-DD, rather than the MM-DD-YYYY format GoTo currently has implemented, at least in the Last Online field. I would note it's already implemented properly in the LMI Client.
Searchable "Last user login"
Really need a column for the last user that has signed into the PC (that is searchable). Being able to skip the step of having to get the hostname from users and just use their names to find their PC would eliminate a lot of redundant time. All other RMM's I've used have this feature. The data is already collected as we can pull it from the API, but this adds needless steps (and an external database search) for something that should really be built in.
Display logged in user on computers page and client app
I saw there was a similar post to this, but they had very specific needs and it was commented that this was not something being planned. All I want is a field on the computers page (and the client app computers) that is searchable (if possible) and displays the logged in user of the computer. Looking at the dashboard of the machine, that is the Interactive User Field. What happens is a user calls me and says they need help. I can narrow down what pc they use easily by location and department in the host name i set, but it is hard for me to determine if they have f-sal-01 or f-sal-02 or f-sal-03, etc. If i could see who logs in to the pc, i can quickly identify and connect. I know you can lable machines, but people bounce around regularly and that would be impossible to manage. Please add this field, so i can support users more effiently. I had continuum before and they had this feature and they used to use central for the remote piece. its definitely possible. Thanks!Windows update repository
The current LMI Windows update feature has it's flaws and reports incorrectly. The Windows update page on LMI Central reports the device as green with 0 pending updates. However, this also happens when the devices has not received any updates, for example with a fresh install and there's connectivity issues to the Windows update service. This results in incorrect details within the Windows update page. Can LogMeIn please use a Windows update repository or similar where it will compare what KB patches and current updates are installed and compare those to a baseline? Relying on the LMI Windows update facility currently does not fill confidence in the patch level of the operating systems. We are now performing this manually but this is the number one feature as to why we use LMI. Thank you.
Logmein Client Search by User
I believe adding the option to search computers within the Logmein Client by user would help a lot of techs. Right now it appears the only way to search in the Client is by name of the computer. However the option to search by "User & Session" information is available on the web portal, but not the Client. For example, say my org wants to name devices by a specific format, but we know "Bob" works on computer X. I want to search for "Bob" within the Client and it provides the computer named "X". If it is too difficult to remember what computer name "Bob" works on.
Correctly mark driver updates as optional
Currently, on a few older installations and all of my new LogMeIn installations, driver updates that are listed as optional on the local Windows 10/11 computers are showing up as important in LMI Central. This makes them appear on the Dashboard and Updates pages even when there aren't any important outstanding updates. That makes it difficult to track the updates that really do need to be installed. In older versions of LogMeIn, there was an option to only selected important updates and not recommended ones which caused the drivers to be listed as optional. Therefore all my computers that were set up with LogMeIn before 2022 are still reporting correctly. Could you please bring back that option or else fix LogMeIn Central to not list driver updates as important when Windows lists them as optional? Thank you!Logged In User integration into LogMeIn Client and Central
While we do have some computers that only is used by one user, alot of our computers are used by multiple users. Instead of naming each computer in our computer list with the name of user + hostname. It would be great If one of the fields in the list of computers in Central and the LogMeIn client was Current Logged In User. Than we can have it searchable in the search bar in central and the logmein client app. This way we can remote into computers without asking more questions to the users or getting them to follow instructions. It's not something super important but it would be a nice to have.Report for computers last online
I find the Computers view has a lot of information I use to communicate with my remote users. I have to get large groups of them online and use the computer view to see who was online when so I can prod them. I would like to be able to export that list so I can share it inline in an email so folks know their status. The report would include the same information available on the computer view tab when I log in as the top level manager. Health |status |Computer |updates |antivirus |last online Even just being able to export the data on the computers tab would be great. This page doesn't print and is difficult to copy paste as the paste doesn't keep the rows.
Hosts with more than 32 cores
nowadays common processors have up to 64 cores, and multi-socket machines corresponding numbers. I can see only 32 cores in the CPU load window (having 48 cores on a dual-socket workstation). Does the "sum" button show the load of 32 cores (which ones? the first 32 in the list?), or the load of all 48 cores? I would also be happy about time axes on the four CPU load diagrams which are very useful for me.
Option to not mute remote computer when logging on with Central
When logging on to a remote computer with Logmein Central, Logmein automatically mutes the remote computer. This should be an option in the Logmein Client/Central: "Mute remote client when logging on: true/false". The automatic muting as it functions now is causing a lot of issues.